Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!usenet.ins.cwru.edu!abvax!iccgcc!browns
From: browns@iccgcc.decnet.ab.com (Stan Brown, Oak Road Systems)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Semicolons in environment variables, how to get?
Message-ID: <822.26eb64de@iccgcc.decnet.ab.com>
Date: 10 Sep 90 15:03:10 GMT
References: <1510@wet.UUCP>
Distribution: na
Lines: 28

In article <1510@wet.UUCP>, naga@wet.UUCP (Peter Davidson) writes:
>                                  But when one tries to 
> SET LIB=\C\LIB;\C\OTHERLIB DOS (as usual) treats the semicolon
> as a command separator and rejects the second part.

The behavior you describe is _not_ MS-DOS.  MS-DOS doesn't have a
command separator.  Some thoughts:

1. Are you running some command shell?  Look in its manual to find out
change the command separator to something like ^ or & that isn't used in
valid commands.

2. If that's the actual command you typed, it won't work in any event.
Disk letters are not set off with backslashes; they are followed with
colons.  The correct form of the command would be
	SET LIB=C:\LIB;C:\OTHERLIB

3. Are you in fact certain that the SET command was not executed
correctly? Type "SET" as a command by itself to display the current
environment settings.

For future postings, you might want to include the exact error message
you get with a problem.  That would help you get a more focused answer.

Stan Brown, Oak Road Systems, Cleveland, Ohio, U.S.A.         (216) 371-0043
The opinions expressed are mine. Mine alone!  Nobody else is responsible for
them or even endorses them--except my cat Dexter, and he signed the power of
attorney only under my threat to cut off his Cat Chow!