Newsgroups: comp.sys.novell
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!news.cs.indiana.edu!cica!ogre!will
From: will@ogre.cica.indiana.edu (William Sadler)
Subject: Re: SYS:PUBLIC/MSDOS/Vx.xx
Message-ID: <1991Mar28.141425.15554@cica.indiana.edu>
Sender: news@cica.indiana.edu (News System)
Nntp-Posting-Host: ogre.cica.indiana.edu
Organization: Indiana University
References: <3125@beguine.UUCP>
Distribution: usa
Date: Thu, 28 Mar 91 14:14:25 GMT

In <3125@beguine.UUCP> mcphil@med.unc.edu (Philip McNamara) writes:

>Can anyone give me some really good reasons to map a search path
>to a DOS on the file server?  Is there some problem with keeping
>the DOS local?  I know for diskless staitons you need the dos
>on the file server, but I should think it is unnecessary for PC's.

I have DOS mapped on the server for two reasons.  The first (and most
important) is that most of my workstations are two floppy PCs.  
Consequently they would have to swap disks to get full DOS functionality.
With DOS on the server they don't have to worry about it.  The second 
reason is that through a login script variable I can automatically
set COMSPEC to whatever version of DOS the workstation is running. This
means that if I go log in on a machine running 4.0 I don't get the
INVALID COMSPEC message after running WordPErfect or something similar
that swaps command.com out to disk.

>I await enlightenment.

Don't we all.

Will
--
***************************************************************************
*   _______________\|/_      Will Sadler     will@cica.indiana.edu        * 
*   Laser 44888    /|\                       sadler@iubacs.bitnet         *     
***************************************************************************