SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Sun, 6 Jan 2002 12:39:41 PST7
From:	Harry Chris Motin <hmotin@attglobal.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Watcom C/C++ version 11.0c download

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

OK! Thanks very much for these answers. That's a big help. On your
previous response to me you said:

Huh? ConfigTest.cmd? FWIW, it don't have any such animal.

Sorry! I did not mean to confuse you. I simply used the pipe command,
">", to pipe the output of the SET command into an ASCII,
"C:\ConfigTest.TXT. Thus:

SET > C:\ConfigTest.TXT

creates the file, ConfigTest.TXT, on C:\, which contains the written
output from the SET command. I was simply saying that I had checked the
values of the environmental variables to confirm that I had indeed
configured my OS to run WATCOM C/C++. OK?
HCM
______________________________________________________________________________________________

Steven Levine wrote:
>
> =====================================================
> If you are responding to someone asking for help who
> may not be a member of this list, be sure to use the
> REPLY TO ALL feature of your email program.
> =====================================================
>
> In <3C384790.28027552@attglobal.net>, on 01/06/02
> at 07:48 AM, Harry Chris Motin said:
>
> >I am now able to run it and select various targets. Also, I now have
> >online help. Apparently, the file,
>
> > C:\WATCOM\BINP\BATSERV.EXE,
>
> >has to been run at OS/2 initialization, via the CONFIG.SYS. It cannot be
>
> Not true. In config.sys RUN= is equivalent to DETACH from the command
> line. You missed the other example which showed using DETACH.
>
> >for that file, and for C:\WATCOM\BINP\NMPBIND.EXE, in the CONFIG.SYS. I
> >also placed all the environmental variables in the CONFIG.SYS, instead of
> >a batch file.
>
> FWIW, if this is your only compiler and you are going to use it a lot,
> there's no reason not to do this.
>
> > 1. Is it true that I still need the Watcom version 11.0 CDROM install??
>
> See previous reply. :-)
>
> > 2. I notice that I cannot change the environmental variables, using a
> >batch file, by simply double clicking on the icon for the file. Instead,
> >I have to run the batch file from the commandline. Anyone know anything
> >about this (why)?
>
> This is how OS/2 works. When you run a program object, OS/2 starts a
> process. Any environment changes are local to the process and its
> children. To make the settings avialable to an application, create a
> program object with:
>
> Program *
> Parameters: setwat & appname
>
> where setwat is the .cmd file that sets up the environment. You can
> prefix the parameters with /c or /k to change what happens to the session
> when the app exits.
>
> Steven
>
> --
> ----------------------------------------------------------------
> "Steven Levine" MR2/ICE 2.30a #10183 Warp4/FP15
> www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
> ----------------------------------------------------------------
>
> =====================================================
>
> To unsubscribe from this list, send an email message
> to "steward@scoug.com". In the body of the message,
> put the command "unsubscribe scoug-help".
>
> For problems, contact the list owner at
> "rollin@scoug.com".
>
> =====================================================

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 06 | January | 2002 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.