Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!news.cs.indiana.edu!cica!ogre!will From: will@ogre.cica.indiana.edu (William Sadler) Newsgroups: comp.sys.novell Subject: Re: MS/DOS directories Message-ID: Date: 26 Jun 91 13:22:33 GMT References: <1991Jun25.192003.18195@keinstr.uucp> Sender: news@cica.indiana.edu (News System) Distribution: usa Organization: Indiana University Lines: 35 Nntp-Posting-Host: ogre.cica.indiana.edu In <1991Jun25.192003.18195@keinstr.uucp> brinich@keinstr.UUCP (Mark Brinich) writes: >I'd like to know why Novell wants you to put a seperate directory on your file >server for every flavor of DOS you're running with all the DOS system files. I >don't know how many versions we're running here, but it's probably around 5-10. >Since none of our workstations are diskless, I don't see why I need to keep >this stuff hanging around on our fileserver. I wasn't aware that they *wanted* anyone to do anything, but I have been doing this because I have many workstations that do not have hard drives. Putting DOS on the network allows these workstations to have full DOS functionality without placing two disks in the machine. This means they can use those drives for other more important stuff. Each version of DOS goes into a directory als so: sys:\msdos\v3.30 There is then a line in the system login script that sets comspec to the version of DOS the boot machine uses: map ins s1:=sys:\%OS\%OS_VERSION comspec = s1:command.com The only problem I have encountered is that DOS 4.0 and 4.01 are not differentiated by the OS_VERSION variable. You do not have to do this. A "comspec = c:\command.com" in each users login script will work just fine if they all have hard drives. Will -- *************************************************************************** * _______________\|/_ Will Sadler will@cica.indiana.edu * * Laser 44888 /|\ sadler@iubacs.bitnet * ***************************************************************************