🚀 go-pugleaf

From article <5253@bgsuvax.UUCP>, by maner@bgsuvax.UUCP (Walter Maner):
> 
> DocuComp aborts in 4DOS unless it's run from within its own directory.
> Apparently, this is due to the fact that 4DOS stores path info in
> lowercase but DocuComp expects uppercase.  (Path info is stored just
> past the environment table.  DocuComp looks there to see where its
> overlays are.)  Any suggestions on how to work around this problem?
> And whose fault is it, 4DOS or DocuComp?
> 
The "fault" is with both.  4DOS has a UNIX flavor to it and as such
will create files and such with the case your keyboard is in when
the creation occurs.  It promotes nothing to uppercase for you as
does COMMAND.COM.  This is not a problem if the program you are
running is smart enough to convert anything it gets out of the
environment to uppercase before using it.

When I first got 4DOS, it broke one of the programs I had written
because of just this behaviour.  I went in and re-wrote the program
to upper-case before using.  Of course, you cand't do that.  Maybe,
however, you could invoke the program when your keyboard is in all
caps mode?
	Dion Hollenbeck             (619) 455-5590 x2814
	Megatek Corporation, 9645 Scranton Road, San Diego, CA  92121

        uunet!megatek!hollen       or  hollen@megatek.uucp