Xref: utzoo comp.os.msdos.apps:2299 comp.os.msdos.programmer:5865
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!mips!cs.uoregon.edu!ogicse!plains!jnelson
From: jnelson@plains.NoDak.edu (Jim Nelson)
Newsgroups: comp.os.msdos.apps,comp.os.msdos.programmer
Subject: Re: LRH - Dos5 LoadHigh as an EXE (Was: DOS 5.0 w/4Dos)
Message-ID: <10928@plains.NoDak.edu>
Date: 23 Jun 91 21:05:10 GMT
Article-I.D.: plains.10928
References: <1991Jun14.065701.15680@agate.berkeley.edu> <1991Jun14.091432.8816@nntp-server.caltech.edu> <1991Jun18.083844.8894@davasun.data.nokia.fi>
Organization: North Dakota State University, Fargo, ND
Lines: 33

In article <1991Jun18.083844.8894@davasun.data.nokia.fi> jpk@davasun.data.nokia.fi writes:
>nyet@nntp-server.caltech.edu (n liu) writes:
>
>>Hmm. Yeah, it took me a while to realize that loadhi was an INTERNAL
>>command. (Gee, no wonder it doesn't work in a 4dos shell!). Unfortunately,
>>by not including a external executable, you can't load hi
>>in config.sys. So now were back to QEMM...
>
>>Somebody want to try to write dos 5.0 loadhi as an executable?
>
>Well, I did just that.  I call it LRH - for Load Real High -
>as it is 'improved' from the internal LoadHigh.


Well, my solution was simpler.  I just put the following in my autoexec.bat:

command /c loadhi whatever.ext 

Works fine for me.  If you are having problems with devicehigh in your
config.sys, then put the shell=c:\4dos etc line after your devicehigh
statements.  That way, 4dos will get loaded after your devices.

---
	Jim, in the Land of the Lost. 
disclaimer:  I disclaim nothing.  However, I claim nothing.  

Warning: These are probably opinions.  I'm probably not supposed to have any.

-- 
.sig?  What .sig?  Ohhhh, *THIS* .sig.

	Jim, in the Land of the Lost. 
disclaimer:  These are just opinions.  If you want 'em, you can have 'em.