I am using Dos 6.22 and what my config file looks like is below and I get a message when trying to run programs in dos or under WINDOWS 3.1 that says EMM386 error #12 has halted your computer at C000:3BBD, the lines with REM are what I have found searching but have not yet tried yet. Can any one see any THING wrong? I do not currently use smartdrive.

John


DEVICE=C:\DOS\Himem.sys
DEVICE=C:\DOS\EMM386.EXE 4096
BUFFERS=17,0
FILES=20
LASTDRIVE = j
FCBS=4,0
STACKS = 18,512
DEVICE=C:\DOS\SETVER.EXE
DEVICE=C:\DOS\DMDRVR.BIN
Dos = UMB
Dos = HIGH
NUMLOCK=ON
DEVICE=C:\DOS\ANSI.SYS/X/K/R


REM DEVICE=c:\windows\smartdrv.exe /double_buffer+

REM Add to autoexec file c:\windows\smartdrv.exe /L

REM DEVICE=EMM386.EXE NOEMS X=A000-EFFF

REM DEVICE=EMM386.EXE NOEMS X=C000-DFFF

REM DEVICE=EMM386.EXE NOEMS X=C800-CFFF

REM Stacks set at 16,256There's nothing wrong, however, some other device is mapped to that location (C000:3BBD). You have to keep experimenting. Why do you need the Expanded Memory Manager?As I understand when running windows even 3.11 you do not use emm386.exe, but runing dos based lotus 2.2 you get a message windows
has stoped application becuase of a protection fault. With a partioned hard drive
you can not install windows XP no more. I have come to the conclusion I need to look for a different motherboard.

Johnthe FOLLOWING is a "map" of the first 1MB of RAM:

0000-9FFF : 640K conventional
A000-BFFF : 128K Video ROM
C000-C7FF: 32K Mapped ROM
C800-D7FF: 64K High RAM
D800-DBFF: 16K Adapter RAM
DC00-EFFF : 80K High RAM
F000-FFFF : 64K ROM


the error message seems to indicate an error when memory around C000-C7FF is accessed. try changing your emm386 command in config.sys to:

Code: [Select]DEVICE=C:\windows\EMM386.EXE NOEMS X=C000-DFFF NOMOVEXDBA VERBOSE HIGHSCAN

Note that it is true that windows does not use EMM386; however, it's own memory manager must be told not to use these SPECIFIC areas of memory.

Open C:\Windows\System.ini, and add the line:

Code: [Select]EMMExclude=C000-DFFF


Another thing to check would be the system CMOS setup. Try enabling or disabling "BIOS RAM shadow" options.