chad@csd4.csd.uwm.edu (D. Chadwick Gibbons) (12/22/89)
I have run into an interesting problem/bug/oversight with the path setting mechanism of DOS V3.3, and Novell NetWare 2.15. Take, for example, an autoexec file containing the following PATH statement: path c:\bin;c:\dos When logging onto the network, the system automatically will include the two path directories as search drives. However, if the path statement is structured as: set path=c:\bin;c:\dos The search drive mappings will _not_ take place. We have just received an update to our Novell NetWare, so it should be interesting to see if the new version suffers from this problem. I'd like to say "problem with Novell" but I have a feeling it's more a problem with DOS, since path c:\bin and set path=c:\bin should be indentical, as far as I know. Anyone with similiar experiences?
leonard@bucket.UUCP (Leonard Erickson) (12/24/89)
chad@csd4.csd.uwm.edu (D. Chadwick Gibbons) writes: >path c:\bin;c:\dos >When logging onto the network, the system automatically will include >the two path directories as search drives. However, if the path >statement is structured as: >set path=c:\bin;c:\dos >The search drive mappings will _not_ take place. You'll *love this.... "path xyz" will result in a path variable containing "XYZ" "set path=xyz" results in a path variable containing "xyz" Netware expects the path to be uppercased! #^%$^$#*%( Anyone who has used 4dos with Novell ran into this a long time ago... As a temporary fix, make sure to use ALL CAPS in any path setting statements. And point out to Novell that this is a *stupid* assumption to make. Anybody know why Novell's menus won't work under 4dos? -- Leonard Erickson ...!tektronix!reed!percival!bucket!leonard CIS: [70465,203] "I'm all in favor of keeping dangerous weapons out of the hands of fools. Let's start with typewriters." -- Solomon Short