If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
DBMS problem: MS-DOS window vs. MS-DOS mode
You'll recall that the problem I reported in mid-October concerned my
inability to enter dates or search by date in a data entry/QBE module of an older MS-DOS DBMS program. After considering several of the comments, I've decided that I don't really want to use MS-DOS mode Some of the responses appeared to recommend doing that, including those that suggested ways that I might be able to run the program using DOS 6.22 instead of 7.0 or 7.1. Instead, I'd like to keep using the program in an MS-DOS window under Win 98SE and this means that I am currently using a workaround to cope with my problem. The workaround involves creating new database records using the software's SQL editor. When new records are inserted in this way, there are no problems entering dates. Similarly, when searching for records by date, there is no problem entering the appropriate SQL select statements; the problem only exists when entering a date from the QBE user interface. The problem previously reported was that Windows shut down the window when I tried to enter or search dates in the way that I had been doing before, advising that the program tried to execute an invalid instruction at address 0000:0019. At this time, assuming that using MS-DOS mode is no longer my preferred option, I am wondering about the previous questions as to my config.sys and autoexec.bat files. In fact, I'm interested in the purpose and use of those files in Win 98SE even if they don't help with the above DBMS problem. Win 98SE was preloaded onto my system by a VAR who built the hardware with a view both to my existing data and my future Windows needs. This person, who generally seems very competent, told me that I need neither a config.sys nor an autoexec.bat file with Win 98SE. As a result, I was generally working without them. However, reacting to some of the comments made here I created a config.sys file that merely contains the line DOS=LOW. My current autoexec.bat file is similarly thin. It merely contains the following line added by Norton Antivirus: "C:\PROGRA~1\NORTON~1\NAVDX.EXE /startup." Is there any possibility that my DBMS problem could be made to go away if these files were correctly written? And forgetting about that issue, is it true that users of Win 98SE should have little or nothing in those files, or would it make more sense for traditional former DOS users like myself to have the more elaborate config.sys and autoexec.bat files that were customary under DOS and that I continued to use with Win 95B, regardless of whether I was booting to Windows as opposed to MS-DOS mode? Thanks in advance for your guidance. |
#2
|
|||
|
|||
DBMS problem: MS-DOS window vs. MS-DOS mode
Really, you should go back to that thread & respond to cquirke. He would
say something like these, from my Keepers.dbx... .......Quote cquirke.... Win9x provides native 32-bit EMS, so it's unlikely you'd need the RAM parameter unless some really lame app couldn't "see" what Win9x was offering as EMS, or refusded to believe EMS existed unless it saw a line to that effect in Config.sys (which gongs out WinME users if so) But Win9x does not provide UMB access to DOS sessions - so if a DOIS app needs UMB access, or just needs more conventional RAM than can be freed without use of UMB, then you'd find NoEMS useful. As the parameter's name implies, NoEMS causes EMM386 to be active and provide access to UMB, without hogging a chunky-aligned 64k for an EMS frame. You can also exclude UMB ranges via System.ini (useful for WinME users) but I can't remember the syntax. .......EOQ............ Also... .......Quote cquirke...... Extended memory (XMS) is provided by HiMem.sys, not Emm386.exe What emm386.exe does, is to either/both provide access to puddles of RAM between 640k and 1M (UMB) and/or create an EMS frame there to emulate Expanded Memory Services. All but the oldest of DOS games will prefer more conventional RAM using the NoEMS parameter, rather than waste that space to provide EMS that newer DOS games don't use anyway. Syntax: Emm386.exe RAM ; provides EMS, UMB if space permits Emm386.exe NoEMS ; provides UMB but no EMS With no parameter, defaults to RAM. Actually, whether or not UMB is provided is dependent on the DOS=UMB setting, but with an EMS frame in there, there's unlikely to be much UMB to offer. But you are right to pick on Emm386.exe, as often there are conflicts within the UMB area that cause hard lockups. Swot up on Emm386.exe syntax so you can exclude regions of UMB and thus avoid the clash... Emm386.exe X=mmmm-nnnn Prevents EMM386 from using a particular range of segment addresses for an EMS page or for UMBs. Valid values for mmmm and nnnn are in the range A000h through FFFFh and are rounded down to the nearest 4-kilobyte boundary. .......End of quote........ All I can says is... Config.sys & Autoexec.bat set the initial environment for a Windows DOS box too. All the variables set there will show up in a box. The EMM386.exe line in Config.sys determines whether a DOS box gets Expanded Memory. So, for one thing, try varying your EMM386 line in Config.sys to see whether the DBMS problem goes away... DEVICE=C:\Windows\EMM386.exe NOEMS DEVICE=C:\Windows\EMM386.exe RAM ...Actually, that's the default you already got by omission.. DEVICE=C:\Windows\EMM386.exe i=b000 b7fff NOEMS DEVICE=C:\Windows\EMM386.exe i=b000 b7fff RAM DEVICE=C:\Windows\HIMEM.sys ....Put the line here, between these, at the top of Config.sys... DOS=HIGH,UMB -- Thanks or Good Luck, There may be humor in this post, and, Naturally, you will not sue, should things get worse after this, PCR "Alan Seltzer" wrote in message ink.net... | You'll recall that the problem I reported in mid-October concerned my | inability to enter dates or search by date in a data entry/QBE module of | an older MS-DOS DBMS program. After considering several of the | comments, I've decided that I don't really want to use MS-DOS mode | Some of the responses appeared to recommend doing that, including | those that suggested ways that I might be able to run the program using | DOS 6.22 instead of 7.0 or 7.1. Instead, I'd like to keep using the | program in an MS-DOS window under Win 98SE and this means that | I am currently using a workaround to cope with my problem. The | workaround involves creating new database records using the software's | SQL editor. When new records are inserted in this way, there are no | problems entering dates. Similarly, when searching for records by date, | there is no problem entering the appropriate SQL select statements; | the problem only exists when entering a date from the QBE user | interface. | | The problem previously reported was that Windows shut down the | window when I tried to enter or search dates in the way that I had | been doing before, advising that the program tried to execute an | invalid instruction at address 0000:0019. | | At this time, assuming that using MS-DOS mode is no longer my | preferred option, I am wondering about the previous questions as to | my config.sys and autoexec.bat files. In fact, I'm interested in the | purpose and use of those files in Win 98SE even if they don't help | with the above DBMS problem. Win 98SE was preloaded onto my | system by a VAR who built the hardware with a view both to my | existing data and my future Windows needs. This person, who | generally seems very competent, told me that I need neither a | config.sys nor an autoexec.bat file with Win 98SE. As a result, | I was generally working without them. However, reacting to some | of the comments made here I created a config.sys file that merely | contains the line DOS=LOW. My current autoexec.bat file is | similarly thin. It merely contains the following line added by Norton | Antivirus: "C:\PROGRA~1\NORTON~1\NAVDX.EXE /startup." | | Is there any possibility that my DBMS problem could be made to | go away if these files were correctly written? And forgetting about | that issue, is it true that users of Win 98SE should have little or | nothing in those files, or would it make more sense for traditional | former DOS users like myself to have the more elaborate | config.sys and autoexec.bat files that were customary under DOS | and that I continued to use with Win 95B, regardless of whether | I was booting to Windows as opposed to MS-DOS mode? | | Thanks in advance for your guidance. | | | |
#3
|
|||
|
|||
DBMS problem: MS-DOS window vs. MS-DOS mode
Look inside C:\Windows\MSDOSDRV.TXT for the syntax of EMM386.exe. Well,
here it is...!... EMM386.EXE ========== EMM386.ext provides access to the upper memory area and uses extended memory to simulate expanded memory. This device driver must be loaded by a DEVICE command in your Config.sys file and can be used only on computers that have an 80386 or higher processor. EMM386 also makes it possible to load programs and device drivers into upper memory blocks (UMBs). Syntax DEVICE=[drive:][path]EMM386.EXE [ON|OFF|AUTO] [memory] [MIN=size] [W=ON|W=OFF] [Mx|FRAME=address|/Pmmmm] [Pn=address] [X=mmmm-nnnn] [I=mmmm-nnnn] [B=address] [L=minXMS] [A=altregs] [H=handles] [D=nnn] [RAM=mmmm-nnnn] [NOEMS] [NOVCPI] [HIGHSCAN] [VERBOSE] [WIN=mmmm-nnnn] [NOHI] [ROM=mmmm-nnnn] [NOMOVEXBDA] [ALTBOOT] [NOBACKFILL] Parameters [drive:][path] Specifies the location of the EMM386.exe file. [ON|OFF|AUTO] Activates the EMM386 device driver (if set to ON), or suspends the EMM386 device driver (if set to OFF), or places the EMM386 device driver in auto mode (if set to AUTO). Auto mode enables expanded-memory support and upper-memory-block support only when a program calls for it. The default value is ON. Use the EMM386 command to change this value after EMM386 has started. memory Specifies the maximum amount of extended memory (in kilobytes) that you want EMM386 to provide as expanded/Virtual Control Program Interface (EMS/VCPI) memory. This amount is in addition to the memory used for UMBs and EMM386 itself. Values for memory are in the range 64 through the lesser of either 32768 or the amount of extended memory available when EMM386 is loaded. The default value is the amount of free extended memory. If you specify the NOEMS switch, the default value is 0. EMM386 rounds the value down to the nearest multiple of 16. Switches MIN=size Specifies the minimum amount of EMS/VCPI memory (in kilobytes) that EMM386 will provide, if that amount of memory is available. EMM386 reserves this amount of extended memory for use as EMS/VCPI memory when EMM386 is loaded by the DEVICE=EMM386.EXE command in your Config.sys file. EMM386 may be able to provide additional EMS/VCPI memory (up to the amount specified by the MEMORY parameter) if sufficient XMS memory is available when a program requests EMS/VCPI memory. Values are in the range 0 through the value specified by the MEMORY parameter. The default value is 256. If you specify the NOEMS switch, the default value is 0. If the value of MIN is greater than the value of MEMORY, EMM386 uses the value specified by MIN. W=ON|W=OFF Enables or disables support for the Weitek co-processor. The default setting is W=OFF. Mx Specifies the address of the page frame. Valid values for x are in the range 1 through 14. The following list shows each value and its associated base address in hexadecimal format: 1 = C000h 8 = DC00h 2 = C400h 9 = E000h 3 = C800h 10 = 8000h 4 = CC00h 11 = 8400h 5 = D000h 12 = 8800h 6 = D400h 13 = 8C00h 7 = D800h 14 = 9000h Values in the range 10 through 14 should be used only on computers that have at least 512K of memory. FRAME=address Specifies the page-frame segment base directly. To specify a specific segment-base address for the page frame, use the FRAME switch and specify the address you want. Valid values for address are in the ranges 8000h through 9000h and C000h through E000h, in increments of 400h. To provide expanded memory and disable the page frame, you can specify FRAME=NONE; however, this setting may cause some programs that require expanded memory to work incorrectly. /Pmmmm Specifies the address of the page frame. Valid values for mmmm are in the ranges 8000h through 9000h and C000h through E000h, in increments of 400h. Pn=address Specifies the segment address of a specific page, where n is the number of the page you are specifying and address is the segment address you want. Valid values for n are in the range 0 through 255. Valid values for address are in the ranges 8000h through 9C00h and C000h through EC00h, in increments of 400h. The addresses for pages 0 through 3 must be contiguous to maintain compatibility with version 3.2 of the Lotus/Intel/Microsoft Expanded Memory Specification (LIM EMS). If you use the Mx switch, the FRAME switch, or the /Pmmmm switch, you cannot specify the addresses for pages 0 through 3 for the /Pmmmm switch. X=mmmm-nnnn Prevents EMM386 from using a particular range of segment addresses for an EMS page or for UMBs. Valid values for mmmm and nnnn are in the range A000h through FFFFh and are rounded down to the nearest 4K boundary. The X switch takes precedence over the I switch if the two ranges overlap. I=mmmm-nnnn Specifies a range of segment addresses to be used (included) for an EMS page or for UMBs. Valid values for mmmm and nnnn are in the range A000h through FFFFh and are rounded down to the nearest 4K boundary. The X switch takes precedence over the I switch if the two ranges overlap. B=address Specifies the lowest segment address available for EMS "banking" (swapping of 16K pages). Valid values are in the range 1000h through 4000h. The default value is 4000h. l=minXMS Ensures that the specified amount (in kilobytes) of extended memory will still be available after EMM386 is loaded. The default value is 0. A=altregs Specifies how many fast alternate register sets (used for multitasking) you want to allocate to EMM386. Valid values are in the range 0 through 254. The default value is 7. Every alternate register set adds about 200 bytes to the size in memory of EMM386. H=handles Specifies how many handles EMM386 can use. Valid values are in the range 2 through 255. The default value is 64. D=nnn Specifies how many kilobytes of memory should be reserved for buffered direct memory access (DMA). Discounting floppy disk DMA, this value should reflect the largest DMA transfer that will occur while EMM386 is active. Valid values for nnn are in the range 16 through 256. The default value is 32. RAM=mmmm-nnnn Specifies a range of segment addresses to be used for UMBs; also enables EMS support. If you do not specify a range, EMM386 uses all available adapter space to create UMBs and a page frame for EMS. NOEMS Provides access to the upper memory area but prevents access to expanded memory. NOVCPI Disables support for VCPI programs. This switch must be used with the NOEMS switch. If you specify the NOVCPI switch without specifying the NOEMS switch, EMM386 does not disable VCPI support. If you specify both switches, EMM386 disregards the MEMORY parameter and the MIN switch. Disabling support for VCPI programs reduces the amount of extended memory allocated. HIGHSCAN Specifies that EMM386 use an additional check to determine the availability of upper memory for use as UMBs or EMS windows. On some computers, specifying this switch may have no effect or might cause EMM386 to identify upper memory areas as available when they are not. As a result, your computer may stop responding. VERBOSE Directs EMM386 to display status and error messages while loading. By default, EMM386 displays messages only if it encounters an error condition. You can abbreviate VERBOSE as V. (To display status messages without adding the VERBOSE switch, press and hold the ALT key while EMM386 starts and loads.) WIN=mmmm-nnnn Reserves a specified range of segment addresses for Windows instead of for EMM386. Valid values for mmmm and nnnn are in the range A000h through FFFFh and are rounded down to the nearest 4K boundary. The X switch takes precedence over the WIN switch if the two ranges overlap. The WIN switch takes precedence over the RAM, ROM, and I switches if their ranges overlap. [NOHI] Prevents EMM386 from loading into the upper memory area. Normally, a portion of EMM386 is loaded into upper memory. Specifying this switch decreases available conventional memory and increases the upper memory area available for UMBs. [ROM=mmmm-nnnn] Specifies a range of segment addresses that EMM386 uses for shadow RAM--random-access memory used for read-only memory (ROM). Valid values for mmmm and nnnn are in the range A000h through FFFFh and are rounded down to the nearest 4K boundary. Specifying this switch may speed up your system if it does not already have shadow RAM. [NOMOVEXBDA] Prevents EMM386 from moving the extended BIOS data from conventional memory to upper memory. [ALTBOOT] Specifies that EMM386 use an alternate handler to restart your computer when you press CTRL+ALT+DEL. Use this switch only if your computer stops responding or exhibits other unusual behavior when EMM386 is loaded and you press CTRL+ALT+DEL. [NOBACKFILL] When EMM386 is configured to provide upper memory blocks (by the NOEMS or RAM switches), EMM386 will also automatically backfill less than 640K of conventional memory to bring total conventional memory up to 640K. However, because Windows does not support backfilled conventional memory, use the NOBACKFILL switch if your computer has less than 640 KB of conventional memory. -- Thanks or Good Luck, There may be humor in this post, and, Naturally, you will not sue, should things get worse after this, PCR "PCR" wrote in message ... | Really, you should go back to that thread & respond to cquirke. He would | say something like these, from my Keepers.dbx... | | ......Quote cquirke.... | Win9x provides native 32-bit EMS, so it's unlikely you'd need the RAM | parameter unless some really lame app couldn't "see" what Win9x was | offering as EMS, or refusded to believe EMS existed unless it saw a | line to that effect in Config.sys (which gongs out WinME users if so) | | But Win9x does not provide UMB access to DOS sessions - so if a DOIS | app needs UMB access, or just needs more conventional RAM than can be | freed without use of UMB, then you'd find NoEMS useful. As the | parameter's name implies, NoEMS causes EMM386 to be active and provide | access to UMB, without hogging a chunky-aligned 64k for an EMS frame. | | You can also exclude UMB ranges via System.ini (useful for WinME | users) but I can't remember the syntax. | ......EOQ............ | | Also... | | ......Quote cquirke...... | Extended memory (XMS) is provided by HiMem.sys, not Emm386.exe | | What emm386.exe does, is to either/both provide access to puddles of | RAM between 640k and 1M (UMB) and/or create an EMS frame there to | emulate Expanded Memory Services. | | All but the oldest of DOS games will prefer more conventional RAM | using the NoEMS parameter, rather than waste that space to provide EMS | that newer DOS games don't use anyway. Syntax: | | Emm386.exe RAM ; provides EMS, UMB if space permits | Emm386.exe NoEMS ; provides UMB but no EMS | | With no parameter, defaults to RAM. Actually, whether or not UMB is | provided is dependent on the DOS=UMB setting, but with an EMS frame in | there, there's unlikely to be much UMB to offer. | | But you are right to pick on Emm386.exe, as often there are conflicts | within the UMB area that cause hard lockups. Swot up on Emm386.exe | syntax so you can exclude regions of UMB and thus avoid the clash... | | Emm386.exe X=mmmm-nnnn | | Prevents EMM386 from using a particular range of segment addresses for | an EMS page or for UMBs. Valid values for mmmm and nnnn are in the | range A000h through FFFFh and are rounded down to the nearest | 4-kilobyte boundary. | ......End of quote........ | | All I can says is... Config.sys & Autoexec.bat set the initial | environment for a Windows DOS box too. All the variables set there will | show up in a box. The EMM386.exe line in Config.sys determines whether a | DOS box gets Expanded Memory. | | So, for one thing, try varying your EMM386 line in Config.sys to see | whether the DBMS problem goes away... | | DEVICE=C:\Windows\EMM386.exe NOEMS | DEVICE=C:\Windows\EMM386.exe RAM | ..Actually, that's the default you already got by omission.. | DEVICE=C:\Windows\EMM386.exe i=b000 b7fff NOEMS | DEVICE=C:\Windows\EMM386.exe i=b000 b7fff RAM | | DEVICE=C:\Windows\HIMEM.sys | ...Put the line here, between these, at the top of Config.sys... | DOS=HIGH,UMB | | | -- | Thanks or Good Luck, | There may be humor in this post, and, | Naturally, you will not sue, | should things get worse after this, | PCR | | "Alan Seltzer" wrote in message | ink.net... | | You'll recall that the problem I reported in mid-October concerned my | | inability to enter dates or search by date in a data entry/QBE module | of | | an older MS-DOS DBMS program. After considering several of the | | comments, I've decided that I don't really want to use MS-DOS mode | | Some of the responses appeared to recommend doing that, including | | those that suggested ways that I might be able to run the program | using | | DOS 6.22 instead of 7.0 or 7.1. Instead, I'd like to keep using the | | program in an MS-DOS window under Win 98SE and this means that | | I am currently using a workaround to cope with my problem. The | | workaround involves creating new database records using the software's | | SQL editor. When new records are inserted in this way, there are no | | problems entering dates. Similarly, when searching for records by | date, | | there is no problem entering the appropriate SQL select statements; | | the problem only exists when entering a date from the QBE user | | interface. | | | | The problem previously reported was that Windows shut down the | | window when I tried to enter or search dates in the way that I had | | been doing before, advising that the program tried to execute an | | invalid instruction at address 0000:0019. | | | | At this time, assuming that using MS-DOS mode is no longer my | | preferred option, I am wondering about the previous questions as to | | my config.sys and autoexec.bat files. In fact, I'm interested in the | | purpose and use of those files in Win 98SE even if they don't help | | with the above DBMS problem. Win 98SE was preloaded onto my | | system by a VAR who built the hardware with a view both to my | | existing data and my future Windows needs. This person, who | | generally seems very competent, told me that I need neither a | | config.sys nor an autoexec.bat file with Win 98SE. As a result, | | I was generally working without them. However, reacting to some | | of the comments made here I created a config.sys file that merely | | contains the line DOS=LOW. My current autoexec.bat file is | | similarly thin. It merely contains the following line added by Norton | | Antivirus: "C:\PROGRA~1\NORTON~1\NAVDX.EXE /startup." | | | | Is there any possibility that my DBMS problem could be made to | | go away if these files were correctly written? And forgetting about | | that issue, is it true that users of Win 98SE should have little or | | nothing in those files, or would it make more sense for traditional | | former DOS users like myself to have the more elaborate | | config.sys and autoexec.bat files that were customary under DOS | | and that I continued to use with Win 95B, regardless of whether | | I was booting to Windows as opposed to MS-DOS mode? | | | | Thanks in advance for your guidance. | | | | | | | | |
#4
|
|||
|
|||
DBMS problem: MS-DOS window vs. MS-DOS mode
Okay, I'll try some of these things and try to see what happens, although
I've begun to think in terms of DBMS software that's compatible with Win 98 and above and that also meets my somewhat idiosyncratic requirements. The latter are pretty basic, but I'm also finding that software that's supposed to do what I want is often disappointing. For example, I've been fooling around with StarOffice 5.1, a version which although now superseded should have provided the tools for simple creation of relational tables. Yet I find that it's so difficult to work with, as compared with what I'm used to, that my immediate inclination is to forget about it and try something else, maybe the current versions of StarOffice or OpenOffice, maybe Informix or Access or DB2 Personal Edition. (The free Oracle 10g Express requires Win 2K or XP Pro.). My difficulty is in trying to find out what the user interfaces look like in such products, but maybe it's possible to get demo. or trial versions. Regarding EMM386.EXE and/or HIMEM.SYS, someone posted a comment to the effect that QEMM is the road to pain. I have the last version of QEMM that was released before Symantec acquired Quarterdeck and abandoned Quarterdeck's software. What's the basis of objection to QEMM, apart from the fact that the only remaining support for it is in the manual and tech notes? The claim was that QEMM was superior to the regular Windows memory managers and it did seem to do a good job under Windows 95. I have copies of my old config.sys and autoexec.bat files as written by or for QEMM, but of course I'm not using them now. Still, there's a continuing newsgroup devoted to DESQview and some of its participants say they are using QEMM with Windows 98. Thanks, Alan "PCR" wrote in message ... Look inside C:\Windows\MSDOSDRV.TXT for the syntax of EMM386.exe. Well, here it is...!... EMM386.EXE ========== EMM386.ext provides access to the upper memory area and uses extended memory to simulate expanded memory. This device driver must be loaded by a DEVICE command in your Config.sys file and can be used only on computers that have an 80386 or higher processor. EMM386 also makes it possible to load programs and device drivers into upper memory blocks (UMBs). Syntax DEVICE=[drive:][path]EMM386.EXE [ON|OFF|AUTO] [memory] [MIN=size] [W=ON|W=OFF] [Mx|FRAME=address|/Pmmmm] [Pn=address] [X=mmmm-nnnn] [I=mmmm-nnnn] [B=address] [L=minXMS] [A=altregs] [H=handles] [D=nnn] [RAM=mmmm-nnnn] [NOEMS] [NOVCPI] [HIGHSCAN] [VERBOSE] [WIN=mmmm-nnnn] [NOHI] [ROM=mmmm-nnnn] [NOMOVEXBDA] [ALTBOOT] [NOBACKFILL] Parameters [drive:][path] Specifies the location of the EMM386.exe file. [ON|OFF|AUTO] Activates the EMM386 device driver (if set to ON), or suspends the EMM386 device driver (if set to OFF), or places the EMM386 device driver in auto mode (if set to AUTO). Auto mode enables expanded-memory support and upper-memory-block support only when a program calls for it. The default value is ON. Use the EMM386 command to change this value after EMM386 has started. memory Specifies the maximum amount of extended memory (in kilobytes) that you want EMM386 to provide as expanded/Virtual Control Program Interface (EMS/VCPI) memory. This amount is in addition to the memory used for UMBs and EMM386 itself. Values for memory are in the range 64 through the lesser of either 32768 or the amount of extended memory available when EMM386 is loaded. The default value is the amount of free extended memory. If you specify the NOEMS switch, the default value is 0. EMM386 rounds the value down to the nearest multiple of 16. Switches MIN=size Specifies the minimum amount of EMS/VCPI memory (in kilobytes) that EMM386 will provide, if that amount of memory is available. EMM386 reserves this amount of extended memory for use as EMS/VCPI memory when EMM386 is loaded by the DEVICE=EMM386.EXE command in your Config.sys file. EMM386 may be able to provide additional EMS/VCPI memory (up to the amount specified by the MEMORY parameter) if sufficient XMS memory is available when a program requests EMS/VCPI memory. Values are in the range 0 through the value specified by the MEMORY parameter. The default value is 256. If you specify the NOEMS switch, the default value is 0. If the value of MIN is greater than the value of MEMORY, EMM386 uses the value specified by MIN. W=ON|W=OFF Enables or disables support for the Weitek co-processor. The default setting is W=OFF. Mx Specifies the address of the page frame. Valid values for x are in the range 1 through 14. The following list shows each value and its associated base address in hexadecimal format: 1 = C000h 8 = DC00h 2 = C400h 9 = E000h 3 = C800h 10 = 8000h 4 = CC00h 11 = 8400h 5 = D000h 12 = 8800h 6 = D400h 13 = 8C00h 7 = D800h 14 = 9000h Values in the range 10 through 14 should be used only on computers that have at least 512K of memory. FRAME=address Specifies the page-frame segment base directly. To specify a specific segment-base address for the page frame, use the FRAME switch and specify the address you want. Valid values for address are in the ranges 8000h through 9000h and C000h through E000h, in increments of 400h. To provide expanded memory and disable the page frame, you can specify FRAME=NONE; however, this setting may cause some programs that require expanded memory to work incorrectly. /Pmmmm Specifies the address of the page frame. Valid values for mmmm are in the ranges 8000h through 9000h and C000h through E000h, in increments of 400h. Pn=address Specifies the segment address of a specific page, where n is the number of the page you are specifying and address is the segment address you want. Valid values for n are in the range 0 through 255. Valid values for address are in the ranges 8000h through 9C00h and C000h through EC00h, in increments of 400h. The addresses for pages 0 through 3 must be contiguous to maintain compatibility with version 3.2 of the Lotus/Intel/Microsoft Expanded Memory Specification (LIM EMS). If you use the Mx switch, the FRAME switch, or the /Pmmmm switch, you cannot specify the addresses for pages 0 through 3 for the /Pmmmm switch. X=mmmm-nnnn Prevents EMM386 from using a particular range of segment addresses for an EMS page or for UMBs. Valid values for mmmm and nnnn are in the range A000h through FFFFh and are rounded down to the nearest 4K boundary. The X switch takes precedence over the I switch if the two ranges overlap. I=mmmm-nnnn Specifies a range of segment addresses to be used (included) for an EMS page or for UMBs. Valid values for mmmm and nnnn are in the range A000h through FFFFh and are rounded down to the nearest 4K boundary. The X switch takes precedence over the I switch if the two ranges overlap. B=address Specifies the lowest segment address available for EMS "banking" (swapping of 16K pages). Valid values are in the range 1000h through 4000h. The default value is 4000h. l=minXMS Ensures that the specified amount (in kilobytes) of extended memory will still be available after EMM386 is loaded. The default value is 0. A=altregs Specifies how many fast alternate register sets (used for multitasking) you want to allocate to EMM386. Valid values are in the range 0 through 254. The default value is 7. Every alternate register set adds about 200 bytes to the size in memory of EMM386. H=handles Specifies how many handles EMM386 can use. Valid values are in the range 2 through 255. The default value is 64. D=nnn Specifies how many kilobytes of memory should be reserved for buffered direct memory access (DMA). Discounting floppy disk DMA, this value should reflect the largest DMA transfer that will occur while EMM386 is active. Valid values for nnn are in the range 16 through 256. The default value is 32. RAM=mmmm-nnnn Specifies a range of segment addresses to be used for UMBs; also enables EMS support. If you do not specify a range, EMM386 uses all available adapter space to create UMBs and a page frame for EMS. NOEMS Provides access to the upper memory area but prevents access to expanded memory. NOVCPI Disables support for VCPI programs. This switch must be used with the NOEMS switch. If you specify the NOVCPI switch without specifying the NOEMS switch, EMM386 does not disable VCPI support. If you specify both switches, EMM386 disregards the MEMORY parameter and the MIN switch. Disabling support for VCPI programs reduces the amount of extended memory allocated. HIGHSCAN Specifies that EMM386 use an additional check to determine the availability of upper memory for use as UMBs or EMS windows. On some computers, specifying this switch may have no effect or might cause EMM386 to identify upper memory areas as available when they are not. As a result, your computer may stop responding. VERBOSE Directs EMM386 to display status and error messages while loading. By default, EMM386 displays messages only if it encounters an error condition. You can abbreviate VERBOSE as V. (To display status messages without adding the VERBOSE switch, press and hold the ALT key while EMM386 starts and loads.) WIN=mmmm-nnnn Reserves a specified range of segment addresses for Windows instead of for EMM386. Valid values for mmmm and nnnn are in the range A000h through FFFFh and are rounded down to the nearest 4K boundary. The X switch takes precedence over the WIN switch if the two ranges overlap. The WIN switch takes precedence over the RAM, ROM, and I switches if their ranges overlap. [NOHI] Prevents EMM386 from loading into the upper memory area. Normally, a portion of EMM386 is loaded into upper memory. Specifying this switch decreases available conventional memory and increases the upper memory area available for UMBs. [ROM=mmmm-nnnn] Specifies a range of segment addresses that EMM386 uses for shadow RAM--random-access memory used for read-only memory (ROM). Valid values for mmmm and nnnn are in the range A000h through FFFFh and are rounded down to the nearest 4K boundary. Specifying this switch may speed up your system if it does not already have shadow RAM. [NOMOVEXBDA] Prevents EMM386 from moving the extended BIOS data from conventional memory to upper memory. [ALTBOOT] Specifies that EMM386 use an alternate handler to restart your computer when you press CTRL+ALT+DEL. Use this switch only if your computer stops responding or exhibits other unusual behavior when EMM386 is loaded and you press CTRL+ALT+DEL. [NOBACKFILL] When EMM386 is configured to provide upper memory blocks (by the NOEMS or RAM switches), EMM386 will also automatically backfill less than 640K of conventional memory to bring total conventional memory up to 640K. However, because Windows does not support backfilled conventional memory, use the NOBACKFILL switch if your computer has less than 640 KB of conventional memory. -- Thanks or Good Luck, There may be humor in this post, and, Naturally, you will not sue, should things get worse after this, PCR "PCR" wrote in message ... | Really, you should go back to that thread & respond to cquirke. He would | say something like these, from my Keepers.dbx... | | ......Quote cquirke.... | Win9x provides native 32-bit EMS, so it's unlikely you'd need the RAM | parameter unless some really lame app couldn't "see" what Win9x was | offering as EMS, or refusded to believe EMS existed unless it saw a | line to that effect in Config.sys (which gongs out WinME users if so) | | But Win9x does not provide UMB access to DOS sessions - so if a DOIS | app needs UMB access, or just needs more conventional RAM than can be | freed without use of UMB, then you'd find NoEMS useful. As the | parameter's name implies, NoEMS causes EMM386 to be active and provide | access to UMB, without hogging a chunky-aligned 64k for an EMS frame. | | You can also exclude UMB ranges via System.ini (useful for WinME | users) but I can't remember the syntax. | ......EOQ............ | | Also... | | ......Quote cquirke...... | Extended memory (XMS) is provided by HiMem.sys, not Emm386.exe | | What emm386.exe does, is to either/both provide access to puddles of | RAM between 640k and 1M (UMB) and/or create an EMS frame there to | emulate Expanded Memory Services. | | All but the oldest of DOS games will prefer more conventional RAM | using the NoEMS parameter, rather than waste that space to provide EMS | that newer DOS games don't use anyway. Syntax: | | Emm386.exe RAM ; provides EMS, UMB if space permits | Emm386.exe NoEMS ; provides UMB but no EMS | | With no parameter, defaults to RAM. Actually, whether or not UMB is | provided is dependent on the DOS=UMB setting, but with an EMS frame in | there, there's unlikely to be much UMB to offer. | | But you are right to pick on Emm386.exe, as often there are conflicts | within the UMB area that cause hard lockups. Swot up on Emm386.exe | syntax so you can exclude regions of UMB and thus avoid the clash... | | Emm386.exe X=mmmm-nnnn | | Prevents EMM386 from using a particular range of segment addresses for | an EMS page or for UMBs. Valid values for mmmm and nnnn are in the | range A000h through FFFFh and are rounded down to the nearest | 4-kilobyte boundary. | ......End of quote........ | | All I can says is... Config.sys & Autoexec.bat set the initial | environment for a Windows DOS box too. All the variables set there will | show up in a box. The EMM386.exe line in Config.sys determines whether a | DOS box gets Expanded Memory. | | So, for one thing, try varying your EMM386 line in Config.sys to see | whether the DBMS problem goes away... | | DEVICE=C:\Windows\EMM386.exe NOEMS | DEVICE=C:\Windows\EMM386.exe RAM | ..Actually, that's the default you already got by omission.. | DEVICE=C:\Windows\EMM386.exe i=b000 b7fff NOEMS | DEVICE=C:\Windows\EMM386.exe i=b000 b7fff RAM | | DEVICE=C:\Windows\HIMEM.sys | ...Put the line here, between these, at the top of Config.sys... | DOS=HIGH,UMB | | | -- | Thanks or Good Luck, | There may be humor in this post, and, | Naturally, you will not sue, | should things get worse after this, | PCR | | "Alan Seltzer" wrote in message | ink.net... | | You'll recall that the problem I reported in mid-October concerned my | | inability to enter dates or search by date in a data entry/QBE module | of | | an older MS-DOS DBMS program. After considering several of the | | comments, I've decided that I don't really want to use MS-DOS mode | | Some of the responses appeared to recommend doing that, including | | those that suggested ways that I might be able to run the program | using | | DOS 6.22 instead of 7.0 or 7.1. Instead, I'd like to keep using the | | program in an MS-DOS window under Win 98SE and this means that | | I am currently using a workaround to cope with my problem. The | | workaround involves creating new database records using the software's | | SQL editor. When new records are inserted in this way, there are no | | problems entering dates. Similarly, when searching for records by | date, | | there is no problem entering the appropriate SQL select statements; | | the problem only exists when entering a date from the QBE user | | interface. | | | | The problem previously reported was that Windows shut down the | | window when I tried to enter or search dates in the way that I had | | been doing before, advising that the program tried to execute an | | invalid instruction at address 0000:0019. | | | | At this time, assuming that using MS-DOS mode is no longer my | | preferred option, I am wondering about the previous questions as to | | my config.sys and autoexec.bat files. In fact, I'm interested in the | | purpose and use of those files in Win 98SE even if they don't help | | with the above DBMS problem. Win 98SE was preloaded onto my | | system by a VAR who built the hardware with a view both to my | | existing data and my future Windows needs. This person, who | | generally seems very competent, told me that I need neither a | | config.sys nor an autoexec.bat file with Win 98SE. As a result, | | I was generally working without them. However, reacting to some | | of the comments made here I created a config.sys file that merely | | contains the line DOS=LOW. My current autoexec.bat file is | | similarly thin. It merely contains the following line added by Norton | | Antivirus: "C:\PROGRA~1\NORTON~1\NAVDX.EXE /startup." | | | | Is there any possibility that my DBMS problem could be made to | | go away if these files were correctly written? And forgetting about | | that issue, is it true that users of Win 98SE should have little or | | nothing in those files, or would it make more sense for traditional | | former DOS users like myself to have the more elaborate | | config.sys and autoexec.bat files that were customary under DOS | | and that I continued to use with Win 95B, regardless of whether | | I was booting to Windows as opposed to MS-DOS mode? | | | | Thanks in advance for your guidance. | | | | | | | | |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Can't Restart to DOS after USB card reader installed | akuma | General | 1 | February 2nd 05 12:42 AM |
serial mouse no where to be seen | twins2 | Hardware | 18 | January 28th 05 09:48 AM |
Control Panel/Networking Window problem | maggie | Networking | 3 | October 21st 04 01:09 PM |
IE Window Problem | [email protected] | General | 1 | August 10th 04 11:37 PM |
AV software and PC in safe mode | Jane | New Users | 20 | July 1st 04 08:57 PM |