qemm ibm cd help
3 messages in this thread
I have just installed a ibm cdrom I (external) in my ibm 95 okd. The
installation was successful (as drive g) save one problem: when I tried to load
the cd-rom drivers high with qemm, the machine looses the cd-rom drive.
I have loaded the lastest version of mscdex from dos 6.
My config. and autoexec. CONFIG
device=c:\tecmar.sys DEVICE=C:\IBMCDROM.SYS /D:IBMCD001
DEVICE=C:\QEMM\QEMM386.SYS R:3 X=B000-B7FF RAM ST:M EMBmem=24192
DEVICE=C:\QEMM\LOADHI.SYS /R:2 C:\WINDOWS\RAMDRIVE.SYS 8192/A
DEVICE=C:\QEMM\LOADHI.SYS /R:1 C:\DLITEDOS.SYS DEVICE=C:\QEMM\LOADHI.SYS /R:1
/RES=11744 /SQT=C300-C3FF C:\IBMRWOPT.SYS /U DEVICE=C:\QEMM\LOADHI.SYS /R:2
C:\DOS\SETVER.EXE DOS=HIGH FILES=25 rem DEVICE=C:\WINDOWS\SMARTDRV.EXE
/DOUBLE_BUFFER STACKS=9,256 BUFFERS=15 shell=c:\dos\command.com/p LASTDRIVE=Z
AUTOEXEC
C:\QEMM\LOADHI /R:2 C:\WINDOWS\SMARTDRV.EXE rem SET PCPLUS=C:\PCPLUS\
C:\QEMM\LOADHI /R:2 \MSCDEX /D:IBMCD001 @ECHO OFF PROMPT $p$g set
mouse=C:\MOUSE C:\QEMM\LOADHI /R:2 C:\MOUSE\mouse path
D:\CPS;C:\ALDUS;C:\PM4;C:\QEMM;C:\WINWORD;C:\MOUSE;C:\WINDOWS;C:\DOS;C:\SYSTEM;
:\GARBAGE;C:\NORTON D:\CPS\mirror c: d: NUML>NUL SET TEMP=e:\ C:\QEMM\LOADHI
/R:2 C:\DOS\SHARE.EXE SET DMQSPATH=C:\XGA$DMQS set comspec=c:\dos\command.com
CHKDSK
I get 620k at chkdsk.
Any comments? or help?
Richard,
I had a similar problem using QEMM and Optimize, then losing my CD ROM. I
suspect the problem is that the mscdex driver is not getting loaded. If it
were, I think you would be getting less than 620k on chkdsk. During the last
phase of the optimize process, if you select "O" options, you should be able to
look at the size of all of your device drivers. The mscdex ends up being too
large to get loaded high and as a result, no CD. If you remove the loadhi
command in the line which loads the mscdex, it will load low and the CD ROM
will show up, but you will chew up some low memory in the process. I'm not sure
how to optimize this correctly. You might check with the folks over in the
Quarterdeck forum. Let me know if you get anywhere with this as I would like
to regain some low memory of my own.
Good Luck,
Ken
Ken:
PMJI, but I just went through this as well. I put a /E after the MSCDEX
parameter in autoexec. Fixed the problem. Got the solution from a nice young
guy on the phone at Quarterdeck.
Hope this helps!
Best – Rich Bowers