Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!ames!uhccux!todd From: todd@uhccux.uhcc.hawaii.edu (Todd Ogasawara) Newsgroups: comp.sys.ibm.pc Subject: Re: distinguishing between MS and IBM(PC) DOS Message-ID: <6311@uhccux.uhcc.hawaii.edu> Date: 23 Jan 90 04:10:30 GMT References: <5134@solo6.cs.vu.nl> <261@utrcu1.UUCP> <2638@jato.Jpl.Nasa.Gov> <1354@maytag.waterloo.edu> Reply-To: todd@uhccux.UUCP (Todd Ogasawara) Organization: University of Hawaii Lines: 29 In article <1354@maytag.waterloo.edu> dmurdoch@watstat.waterloo.edu (Duncan Murdoch) writes: ]In article <2638@jato.Jpl.Nasa.Gov> kaleb@mars.UUCP (Kaleb Keithley) writes: ]>Which means that Olivetti licensed it's DOS from IBM rather than Microsoft, ]>therefore, it's really PC-DOS instead of MS-DOS. ]This raises the question: is there any systematic difference between ]MS-DOS and PC-DOS, other than who collected the royalties and what "ver" ]prints? ]In other words, a question to the original poster: why would ]anyone want to distinguish between them? Be glad to answer that question... I'm about to put some diskless workstations (hard diskless might be more accurate, some might have floppies) on a Novell network. I wanted to be able to have simple way to determine what DOS is being used on any particular workstation so that I could point to the appropriate COMMAND.COM on the server. I.e., I want to let anyone login in from anywhere on the LAN. This is important when people fire up large programs that reloads COMMAND.COM on exit. Since a person who normally works on a hard disk might sometimes move to a diskless machine and login, I wanted everyone to have a COMSPEC pointing to the server so workstation crashes would be reduced. We have noted, for instance, that MS-DOS 3.3 and IBM-DOS 3.3 are in fact different...todd -- Todd Ogasawara, U. of Hawaii UUCP: {uunet,ucbvax,dcdwest}!ucsd!nosc!uhccux!todd ARPA: uhccux!todd@nosc.MIL BITNET: todd@uhccux INTERNET: todd@uhccux.UHCC.HAWAII.EDU