CompuServe Messages

I have narrowed the problem down to the EMM386 memory manager. With it rem-ed out of the config.sys, 3DS does not lock up anymore. In the 3DS instalation guide, it gives a suggestion for how to configure the EMM386 so that it will work with 3DS – the line recomended is "DEVICE=EMM386.EXE xxxx RAM ON". xxxx is the amount of extended memory minus 1024 kb. The DOS 6.22 manual says this can be a maximum of 32768. This system has 48 MB of ram, so I cannot follow this exactly. With EMM386 configured with the maximum allowed value of xxxx (32768), it still locked up. The config.sys file reads: DEVICE=C:\WINDOWS\HIMEM.SYS /TESTMEM:ON /V (DEVICE=C:\DOS\EMM386.EXE 32768 RAM ON) DEVICE=C:\WINDOWS\SMARTDRV.EXE /DOUBLE_BUFFER DOS=HIGH,UMB STACKS=9,256 BUFFERS=15,0 FILES=40 LASTDRIVE=Z FCBS=4,0 SHELL=C:\COMMAND.COM /E:1024 /P DEVICEHIGH /L:1,4560 =C:\WINDOWS\IFSHLP.SYS [a number of device drivers ] [(CD, soundcard, scanner) ] [loaded with the DEVICEHIGH command – ] [memory locations set using "MEMMAKER" ] Question – how to configure the EMM386 to work with 3DS – or is it ok to not load it up at all? We are also running Autocad 13 under Windows for Workgroups 3.11 – what are its requirements for memory management? (Is EMM386 necessary for Windows in Enhanced mode?) How will we have to reconfigure the various drivers? – can the "DEVICEHIGH" command to load drivers into upper memory be used without the EMM386? Thanks. Caleb