Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!psuvax1!psuvm!trl3
From: TRL3@psuvm.psu.edu (Tim Larson)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: Networked PC (without hard disc)
Message-ID: <90068.083604TRL3@psuvm.psu.edu>
Date: 9 Mar 90 13:36:04 GMT
References: <1990Mar6.180320.28421@axion.bt.co.uk> <123@qmsseq.imagen.com>
Organization: Penn State University
Lines: 26

In article <123@qmsseq.imagen.com>, pipkins@qmsseq.imagen.com (Jeff Pipkins)
says:
>
>In article <1990Mar6.180320.28421@axion.bt.co.uk> iwarner@axion.bt.co.uk      :
>writes
>>       I also have encountered one problem: when exiting from MicroSoft Word,
>>the beast insists on reading COMMAND.COM from the floppy drive (A:) from     e
>>whence
>>it was booted. I need to tell it to look on the network drive, but NOT when
>>first booting up. When powering up command.com, autoexec & config.sys are
>>all read from a system floppy. This also contains code to boot up & log in to
>>PC-NFS. Once this has been done, all interaction should be with the networked
>>drives.
>The quickest way for you to fix this, is to put a line like this in your
>config.sys file:
>
>        SHELL=A:\COMMAND.COM C:\ [/E:envsize] /P
>
This is the first step, the second (and the more important one to the
original question) is to include the following line in your autoexec.bat:

         SET COMSPEC=E:\COMMAND.COM

or whatever the full pathname of the command.com on the network drive is.
You must be certain, too, that the DOS version is the same on the boot disk
and the network disk (at least the command.com's must be the same).