CompuServe Thread

LOADHIGH/DeviceHigh

2 messages in this thread
#42410From: James ChinMar 9, 1993 6:52 AM
That's the usual case of waht I call "Memory Shock." No real good suggestions out there about what to do about it. No familarity with 386MAX. In a DOS5 environment, the usual answer is to enable the /E switch and try to load MSCDEX into expanded memory. The other work around for some is the use DEVICEHIGH in your Config.sys for your CD Drive device driver. For example, for a PAS16 default setup it would be: DEVICEHIGH=c:\PROAUDIO\TSLCDR.SYS /D:MVCD001 / S:31 DEVICEHIGH=C:\PROAUDIO\MVSOUND.SYS D:1 Q:7 You would then modify your Autoexec.bat with LOADHIGH: LOADHIGH C:\PROAUDIO\MSCDEX.EXE /D:MVCD001 /L:D /M:8 /V /E This works with the older version of MSCDEX 2.2. For some reason only known to Microsoft, the latest verison of MSCDEX ver 2.21, can not be loaded high with DOS 5.0 (CD-Rom Programmer's Guide for MS-D)S CD-ROM Extension Verison 2.21, Microsoft Corp., Jan 1992, p.12-8). If you are using V2.21, you only option with DOS 5 is /E, but this will only save you 16K. Let me know what your solution for 386Max is. Good Luck. JC
#42470From: kevin kellyMar 9, 1993 9:18 PM
James, despite what MS says about loading mscdex v2.21 high, there are thousands of us who've done it very successfully. V2.21 loads high more easily than its predecessor. I've only heard of one truly knowledgeable folk who couldn't get it to happen when he worked on it. MS also said that v2.20 shouldn't be loaded high either. And, not wanting to get overwhelmed, most mfgrs. don't recommend loading it high — probably cuz the majority of their customers wouldn't know what loading high is and the mfgrs. clearly can't afford to provide free DOS 5 lessons. Inasmuch as loading it high can save substantial conventional memory, about 15K+, why not try? Software seldom breaks machines… it just looks that way sometimes <g>. I've got 18 programs loaded at any one time, almost all high; I had a fit gettin' them all to co-exist, but it hums now. Strange things do happen sometimes if I'm adding a new TSR or device driver, but moving the loading order usually clears it up. Happy computing!