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 [ 03 | October | 2003 ]

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


Date: Fri, 3 Oct 2003 08:08:52 PDT7
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: TCPIP Loopback Interface

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

John A. Morrow, Jr. wrote:
>
> When editing [protocol.ini] with the default editor
> (e.exe) should I save as a text file or a command
> file, or should I use a different editor?

Won't make any difference. The text/command save option just sets the
file's .TYPE extended attribute.

As for using a different editor, e.exe is fine but it does have a minor
"quirk" -- it puts a hex 1A at the end of every file. This is allowed;
it's the EOF (End Of File) ASCII character. *However*, it messes up
things if a program later appends something to the end of the file (for
example, if you use >> redirection from the command line) because the
resulting file has the new information _after_ the 1A (End Of File
character) and the next program to read the file may not see it
depending on how the file is read.

Thus, e.exe is fine for control file updates (such as protocol.ini) but
be careful when using it for data files that might be updated by
appending.

> > [put ifconfig lo 127.0.0.1] after the route command.
>
> There is no route command [in my Setup.cmd]

There are several commands you won't see in your SETUP.CMD because
you're on dialup rather than a network.

- Peter

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

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 [ 03 | October | 2003 ]



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.