swolvert@orion.oac.uci.edu (Susan Wolverton) (12/13/90)
I have an AST 386 machine with MSDOS 4.01. When I use that machine to log on Novell, Novell interprets it as IBM_PC, MSDOS V4.00. Since we do have other machines using DOS 4.00 on the network, that connects the AST to the wrong network DOS directory, and sometime it causes COMMAND.COM not found error. I like to hard code the AST's OS VERSION to 4.01. Someone suggested to do it with the SHELL.CFG file. I tried it but it didn't work. Also the Novell manual doesn't say anything about how to change OS VERSION. Does anyone has suggestions regarding how to resolve this problem? Thanks. Hank AdCom, UCI hhliao@uci.edu
castillo@media-lab.MEDIA.MIT.EDU (Brian Anderson) (12/13/90)
In article <2766C988.9806@orion.oac.uci.edu> swolvert@orion.oac.uci.edu (Susan Wolverton) writes: >I have an AST 386 machine with MSDOS 4.01. When I use that machine to >log on Novell, Novell interprets it as IBM_PC, MSDOS V4.00. Since we >do have other machines using DOS 4.00 on the network, that connects the >AST to the wrong network DOS directory, and sometime it causes COMMAND.COM >not found error. . . . I've had the same problem with the variables %OS and %OS_VERSION. I'm using Advanced Netware 286 version 2.15C and everything on my network (even IBM PS/2s) sets %OS to "MSDOS", not "PCDOS". The %OS_VERSION variable also comes up as "V4.00" instead of "V4.01" as it should. You can't just add your own shell.cfg variables, so the solution I came up with involves setting LONG MACHINE NAME = "XXXXXX". I set this to "IBMPS2" or "DELL" or "GATEWY" as required and set the appropriate DOS search path mapping in the default login script. I've also found numerous problems with locating the right command.com file, which only disappeared when I set it to C:\command.com for all our workstations. I've noticed that Novell likes to find shell.cfg and command.com in the root directory of the workstation boot drive (almost always C:\) and is extremely stubborn when trying to do anything else. I am beginning to understand just how Novell can get away with charging $200/hr for phone support :-( -- "make lots of money", "enjoy the work", "operate within the law": pick any 2 ----------------------------------------------------------------------------- Brian Anderson | "It's hard to work in groups when you're castillo@media-lab.media.mit.edu | omnipotent." - Q, ST-thg "Deja-Q"
bdelvecc@kinetics.com (Brian Del Vecchio) (12/21/90)
In article <2766C988.9806@orion.oac.uci.edu>, swolvert@orion.oac.uci.edu (Susan Wolverton) writes: > I have an AST 386 machine with MSDOS 4.01. When I use that machine to > log on Novell, Novell interprets it as IBM_PC, MSDOS V4.00. Somehow, millions of boxes were shipped by IBM and maybe M*Soft, which were marked on the box and diskette labels as "DOS 4.01", but were labelled internally as 4.00. Here's how you can tell: The NetWare shell gets the OS version from DOS using DOS function 0x30, "GetDOSVersion". If DOS tells NetWare that it is 4.00, NetWare will tell you the same. Try this on your home `puter, hacker friends: debug -a xxxx:0100 mov ax,3000 xxxx:0103 int 21 xxxx:0105 int 20 xxxx:0107 <return> -g Program terninated normally -r AX=0004 ... ... -q [----------------------------------------------------------------------------] brian del vecchio; software engineer; novell, inc.; walnut creek, ca, usa; "But for what purpose was the earth formed?" asked Candide. "To drive us mad," replied Martin. - Voltaire, _Candide_ [---the opinions expressed are mine...the official Big Red Word may differ---]