SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

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.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 14 | March | 2004 ]

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


Date: Sun, 14 Mar 2004 12:58:03 PST8
From: "J. R. Fox" <jr_fox@pacbell.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Win 3.1 TCPIP HELP

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.
=====================================================

Steven Levine wrote:

> >(And now I'd like to
> >know if there is something for adding on to PATH on the fly, without the
> >need to reboot,
>
> PATH is easy. Edit it and the new value will be used. The same is true
> for all the path-live environment variables. LIBPATH is different. I'm
> sure there were valid technical reasons for this when the decisions that
> resulting in this behavior were made.

Just want to see if I've got this right: Capture the existing PATH to a temp
file, bring it into your editor of choice, tack some new item on at the end,
then re-issue the edited version from an OS/2 command prompt, and voila,
you have an altered Path until the next reboot ?

> Correct. BEGINLIBPATH exists as a partial workaround to the limitations
> of the LIBPATH implementation.

Guess I need some remedial instruction, because after all this time I still have
pause trying to keep straight the differences between PATH, DPATH, LIBPATH,
and any other Paths I may have lost track of. (This is but one example.)

[Jeffrey, can we do a timeshare on that dunce cap ?]

Jordan

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

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".

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


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

Return to [ 14 | March | 2004 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

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.