"insufficient memory or address space to initialize windows in 386 enhanced mode"
SmokeyMtnBelle
DEVICE=C:\DOS\EMM386.EXE RAM HIGHSCAN I=B000-B7FF
to
DEVICE=C:\DOS\EMM386.EXE /noems
?? --- backup your file first of course!
--
good luck!
SmokeyMtnBelle
For solutions to common Windows' problems, visit:
<<<http://members.xoom.com/WinWoes>>>
Last Updated: March 1999
L.J. LaMere wrote in message <36f6db3...@NEWS.ACD.NET>...
|When 32 bit disk access is on I get the following message "insufficient
memory
|or address space to initialize windows in 386 enhanced mode". The computer
then
|drops to the dos prompt but is locked up.
|
|I,m running WFWG 3.11 and DOS 6.22.
|
|My config sys file is:
|DEVICE=C:\DOS\HIMEM.SYS
|DEVICE=C:\DOS\EMM386.EXE RAM HIGHSCAN I=B000-B7FF
|BUFFERS=15,0
|FILES=30
|dos=high,UMB
|LASTDRIVE=M
|FCBS=16,0
|DEVICEHIGH /L:1,12048 =C:\DOS\SETVER.EXE
|
|
|DEVICE=C:\WINDOWS\ES1868.COM /A:168 /I:C
|
|STACKS=9,256
|SHELL=C:\DOS\COMMAND.COM C:\DOS /p
|rem ---------------------- MTM ATAPI CD-ROM ----------------------
|[COMMON]
|DEVICEHIGH /L:1,15792 =C:\MTM\MTMCDAI.SYS /D:MTMIDE01
|rem ---------------------- MTM ATAPI CD-ROM ----------------------
|DEVICEHIGH /L:1,4560 =C:\WINDOWS\IFSHLP.SYS
|
|Is there anything I can do, or am I just going to have to live without 32
bit
|disk access?
|--
|L.J. LaMere
|ljlamer...@acd.net
|Lansing Mi. USA
|--
L.J. LaMere
L.J. LaMere
and still get the same message.
On Mon, 22 Mar 1999 20:38:26 -0500, "SmokeyMtnBelle" <smokeym...@yahoo.com>
wrote:
>Have you tried changing this line-----
>DEVICE=C:\DOS\EMM386.EXE RAM HIGHSCAN I=B000-B7FF
>to
>DEVICE=C:\DOS\EMM386.EXE /noems
>?? --- backup your file first of course!
--
SmokeyMtnBelle
prompt, instead of typing say << win >> type in << win /3 >> if this
works, you do not have enough extended memory-- remming things in your
autoexec.bat and config.sys file though should work. [-- you didn't say what
was in your config.sys file]
You could also try << win /d:xvs >> . If this works then use 1 switch at a
time--
<< win /d:x >> -- if this works, add EmmExclude=A000-EFFF to the [386enh]
section of your system.ini
<< win /d:v >> --if this works, add VirtualHDIrq=OFF to the [386enh] section
of your system.ini
and
<< win /d:s >> --if this works, add SystemROMBreakPoint=OFF to the [386enh]
section of your system.ini
This problem can also occur if the hdd has more than 1024 cylinders-- the
most noted being Western Digital's model 2540--- however, they do at least
have a fix for it. Others will simply let you reset the # of cylinders in
your cmos to 1024-- and then if the error still occurs, smartdrive gets
loaded with the switch NOMOVEXBDA
However, do understand that if your problem is w/the hdd and you must do
this, it means fdisk and reformat as well.
--
good luck!
SmokeyMtnBelle
For solutions to common Windows' problems, visit:
<<<http://members.xoom.com/WinWoes>>>
Last Updated: March 1999
L.J. LaMere wrote in message <36f788a...@NEWS.ACD.NET>...
L.J. LaMere
wrote:
>Try starting your machine by keeping smartdrive disabled and then at the
>prompt, instead of typing say << win >> type in << win /3 >> if this
>works, you do not have enough extended memory-- remming things in your
>autoexec.bat and config.sys file though should work. [-- you didn't say what
>was in your config.sys file]
>
>You could also try << win /d:xvs >> . If this works then use 1 switch at a
>time--
>
><< win /d:x >> -- if this works, add EmmExclude=A000-EFFF to the [386enh]
>section of your system.ini
>
><< win /d:v >> --if this works, add VirtualHDIrq=OFF to the [386enh] section
>of your system.ini
>
> and
>
><< win /d:s >> --if this works, add SystemROMBreakPoint=OFF to the [386enh]
>section of your system.ini
>
>This problem can also occur if the hdd has more than 1024 cylinders-- the
>most noted being Western Digital's model 2540--- however, they do at least
>have a fix for it. Others will simply let you reset the # of cylinders in
>your cmos to 1024-- and then if the error still occurs, smartdrive gets
>loaded with the switch NOMOVEXBDA
>
>However, do understand that if your problem is w/the hdd and you must do
>this, it means fdisk and reformat as well.
Thanks, you've been a lot of help. The problem turns out to be a driver
incompatibility ( Western Digital ). I had to get the driver from their web
site. The little ghit who sold me the thing never said anything about it's being
incompatible with windows' wdctrl driver. I don't mind haveing to find the
driver online, this makes about the 20th time I've done it, but I do like to
know.
Anyway thanks for the help.