Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!tektronix!pogo!andyd
From: andyd@pogo.GPID.TEK.COM (Andy Davidson)
Newsgroups: comp.sys.ibm.pc
Subject: MKS Tools on Toshiba T1000
Message-ID: <6707@pogo.GPID.TEK.COM>
Date: 30 Jan 89 21:05:03 GMT
Reply-To: andyd@pogo.GPID.TEK.COM (Andy Davidson)
Distribution: usa
Organization: Tektronix, Inc., Wilsonville,  OR.
Lines: 47


I have been helping a friend try to install the MKS Toolkit (or part of
it) on a Toshiba 1000 laptop. (Ah-ah; you're not allowed to ask
questions like that!) This machine has MS-DOS (version 2.11) in ROM,
which is known as drive c: and a "Hard RAM" drive known as drive d:
on which everything else resides. (We are trying to avoid using the
floppy drive.)

For a first level of success, we were trying to install sh as the
default shell.  If that failed, then set it up so he can use vi and few
of the other tools from DOS.

If I boot the machine with the following autoexec.bat:
		echo off
		path d:\bin;d:\;d:\andyd;c:\;d:\kermit
		prompt $p$g
then the MKS tools are found ok, though of course wild card expansion
doesn't work right.  (Thus,  'wc *.bat' gives the error message 'wc:
cannot open file "*.bat"'.  The one exception is ls which fails no
matter what I do.  The command 'ls' fails for 'ls: File or directory ""
is not found' and 'ls bin' fails for 'ls: File or directory "bin" is
not found') Now, however, if I go into the shell with 'sh -L' I cannot
find anything, including the DOS commands.  All commands (except shell
built-ins) fail for 'xxx: not found' where xxx is the command tried.
It makes no difference whether I do the 'sh -L' in the root directory
(which has no profile.ksh) or in my subdirectory (andyd) which does.
(That's not quite true.  My profile.ksh has the same aliases in it that
MKS shows in their example: for things like dir, etc.  These fail
instead for 'c:/command.com not found')

If I boot the machine with the following autoexec.bat:
		PATH d:\bin;d:\;d:\andyd;c:\;d:\kermit
		prompt $p$g
		set GLOB=d:\etc
the MKS tools are found ok, though now wild card expansion fails for 
'glob: EXEC error'.  The effect when in the shell is the same as before.
(The path statement in profile.ksh, by the way is
		export PATH=";d:/bin;d:/;$HOME;c:/;d:/kermit"
where $HOME="d:/andyd" as you might expect.)

Does anybody have clue as to what I'm doing wrong or is there something
fundamentally wrong with the Toshiba BIOS?

-- 
Andy Davidson    Toolsmith-in-residence    (503) 685-3033
Tektronix, Inc.  MS 63-356 P.O. Box 1000, Wilsonville, OR 97070
Internet: andyd@pogo.GPID.TEK.COM     uucp: ...!tektronix!pogo!andyd