🚀 go-pugleaf

In article <89121614031714@masnet.uucp> bradley.grigor@canremote.uucp
(BRADLEY GRIGOR) writes:
>Re:
>  INVALID COMMAND.COM
>  SYSTEM HALTED
>U>it's no big problem for me. Could it have something to do with
>U>redefining SWITCHAR to '-'? I do that on my machine. Maybe it means
>U>DOS cannot find the path given by the COMSPEC env. variable?
>
>  I have not redefined the SWITCHAR but I have added 64K and patched
>  my system for 704K.  I first noticed the "INVALID COMMAND.COM" after
>  making that change.  Any clues here?
>
I do that too, using QEMM (Quarterdeck Extended Memory Manager). How-
ever, I had this problem long before I started to use the 386 memory
mapping features (at least I'm 98.5% certain about this). ON the
other hand it sounds interesting - those re-mapped 64k, above 640k,
is where the memory resident copy of COMMAND.COM will be. But the
fact that the error is 'cannot find it' indicates it is not found
*on the disk*. Not finding it in memory is normal, and causes the
re-load from disk.

For what it's worth...:->				Bjorn

-- 
 ====================== InfoVox = Speech Technology =======================
 Bjorn Larsson, INFOVOX AB      :      ...seismo!mcvax!kth!sunic!infovax!bl
 Box 2503                       :         bl@infovox.se
 S-171 02 Solna, Sweden         :         Phone (+46) 8 735 80 90