This is my attempt at listing some Frequently Asked Questions for the
newsgroup comp.os.os2.networking.tcp-ip, which is where IBM tells us
all to look for support and exchange information about OS/2 Warp when
running the Internet Access Kit.

DISCLAIMER:  The information contained within this document was mostly
extracted from posts made to comp.os.os2.networking.tcp-ip and thus
has only the credibility of the original poster, which can range
anywhere from "propagator of ill-founded rumors," right on up to the
"official words of IBM," or even higher. ;-)

     THIS DOCUMENT IS PROVIDED "AS-IS" AND ANY USE HEREOF IS AT THE
     RISK OF THE USER.  ABSOLUTELY NO REPRESENTATION IS MADE AS TO
     THE COMPLETENESS, ACCURACY, TRUTHFULNESS, USABILITY, OR OTHER
     CHARACTERISTIC OF THE INFORMATION CONTAINED HEREIN.  FURTHER,
     ABSOLUTELY NO REPRESENTATION IS MADE AS TO THE OWNERSHIP OF
     ANY RIGHTS TO ANY OF THE INFORMATION CONTAINED HEREIN.  IF YOU
     NEED SOMEONE TO EXPLAIN TO YOU THAT YOU USE THE INFORMATION
     CONTAINED HEREIN AT YOUR OWN RISK, THEN YOU ARE EXPLICITLY
     PROHIBITED FROM USING ANY INFORMATION CONTAINED HEREIN.

All information contained herein is copyright by the various authors
thereof, and on their behalf, I am demanding a royalty of $1,000 per
use for any use by Microsoft Network.  Any such usage is deemed to be
consent to this royalty agreement, and payment shall be immediately
remitted to:

     William A. Schultz          guru@deltanet.com (Bill Schultz)
     P. O. Box 18732
     Irvine, CA  92713-8732

I am actively soliciting comments, clarifications, and requests for
changes to this FAQ.  Either questions, answers, or both may be
submitted.  Of course, the bulk of the information contained herein
has been, and will continue to be, extracted from the newsgroup
discussion threads in comp.os.os2.networking.tcp-ip as time goes by.

This is file number 2 of 12.  It contains the second part of the FAQ.

TABLE OF CONTENTS:

     FAQ PART ONE:

          1.0  GENERAL QUESTIONS
          2.0  GENERAL IBM QUESTIONS
          3.0  GENERAL OS/2 QUESTIONS
          4.0  OS/2 INTERNET ACCESS KIT (IAK) QUESTIONS
          4.1  GENERAL IAK QUESTIONS
          4.2  GENERAL PROXY SERVER QUESTIONS
          4.3  DIAL OTHER PROVIDER QUESTIONS
          4.3.1  GENERAL DIAL OTHER PROVIDER QUESTIONS

     FAQ PART TWO:

          4.3.2  SLIP SPECIFIC QUESTIONS

     FAQ PART THREE:

          4.3.3  PPP SPECIFIC QUESTIONS

     FAQ PART FOUR:

          4.3.4  TIA SPECIFIC QUESTIONS
          4.4  ULTIMAIL/LITE QUESTIONS
          4.5  NEWS READER/2 QUESTIONS
          4.6  SENDMAIL QUESTIONS

     FAQ PART FIVE:

          4.7  WEB EXPLORER QUESTIONS
          4.8  FTP QUESTIONS
          4.9  GOPHER QUESTIONS
          4.10  RETRIEVE SOFTWARE UPDATES QUESTIONS
          4.11  OTHER IAK SOFTWARE QUESTIONS
          4.12  WINDOWS TCP/IP WITH IAK SOFTWARE QUESTIONS

     FAQ PART SIX:

          5.0  OS/2 TCP/IP QUESTIONS

     FAQ PART SEVEN:

          5.0  OS/2 TCP/IP QUESTIONS (Continued)
          6.0  OTHER BONUS PACK SOFTWARE QUESTIONS
          7.0  IBM RESOURCES
          8.0  THIRD PARTY SOFTWARE QUESTIONS
          9.0  OTHER RESOURCES

     FAQ PART EIGHT:

          9.0  OTHER RESOURCES (Continued)

     FAQ PART NINE:

          APPENDIX A - INSTRUCTIONS FOR INSTALLING FIXPACK 5

     FAQ PART TEN:

          APPENDIX B - SLIP CONFIGURATION EXAMPLE

     FAQ PART ELEVEN:

          APPENDIX C - PPP CONFIGURATION EXAMPLE

     FAQ PART TWELVE:

          APPENDIX D - ABBREVIATED SENDMAIL DOCUMENTATION

EDITOR'S NOTE:  This document is very much a work in process.  In fact,
I have not yet completed editing it.  However, because there is so
much useful information available herein, I have decided to go ahead
and post it anyway.  This should result in some comments from all of
you which might save me the trouble of editing this further. (i.e., if
nobody thinks this is a good idea, or that it is way too long. ;-)

4.3.2  SLIP SPECIFIC QUESTIONS

From: thomasja@sgate.com
Newsgroups: comp.os.os2.networking.tcp-ip
Subject: Re: SLIP scripts
Date: 2 Apr 1995 04:03:48 GMT
Message-ID: <3ll7n4$4bs@holmes.sgate.com>
References: <3kkvcc$jdn@usenet.rpi.edu> <CxuSlizOU3zK078yn@io.org>
Reply-To: thomasja@sgate.com

In <CxuSlizOU3zK078yn@io.org>, trebla@io.org (Albert Y.C. Lai) writes:
>In article <3kkvcc$jdn@usenet.rpi.edu>,
>hillt2@goya.its.rpi.edu (Trevor Hill) wrote:
>> I have been monitoring this group for about a week.  It seems that 
about 10% 
>> of the postings are asking about how to establish a SLIP connection.  
I have 
>> not seen any answers (this may be because many of the answers are 
given 
>> "person to person" via mail)
>
>Exactly.  A while ago I also posted a request for teaching me how
>to make use of slip.exe.  No one answered up to now.  No one sent
>me email, no one posted followups.
>
>It seems to me that those who know how to do it ain't talking!  They
>want novices to always stay as novices!
>
>--
>Albert Y.C. Lai                     trebla@io.org
>00Laiyuc@wave.scar.utoronto.ca      Lai@titania.scar.utoronto.ca

Having struggled with this myself, here's what finally worked for me--

1.  use a text editor to view and update to suit your situation the 
following 
REXX script in directory TCPIP\BIN  :  annex.cmd.  This script 
accommodates
the dynamic SLIP address situation.  I had to add a couple of lines 
after the password
entry to handle an extra prompt my ISP uses before accepting the 
command to 
start SLIP.

2.  After you have your REXX script ready to go, open up an OS/2 
command line
window and enter the following :  (I haven't been able to get SLIPPM to 
work, but 
was able to use slip.exe.

slip -nocfg -com2 (or whichever com port you're using) -speed 38400 -vj
-connect "annex.cmd atdt999-9999 logonid * "  

where 999-9999 is your ISP's phone number and logonid is your userid 
with 
your provider.   The "*" will cause the script to prompt you for your 
password.

I had to use the nocfg option since I too have been unable to figure 
out what 
an acceptable format is for slip.cfg.


Hope this helps!

Jim Thomas
Clifton, Virginia

=====

[See FAQ Part 5, Appendix B, for a very long sample SLIP script.]

This example should be self-explanatory.

=====

From: jimenez@gaus90.chem.yale.edu
Newsgroups: comp.os.os2.networking.tcp-ip
Subject: Re: Using SLIPTERM.EXE, Anyone? <Answer?>
Date: 5 Apr 1995 01:05:13 GMT
Message-ID: <3lsqc9$j96@news.ycc.yale.edu>
References: <D6Ar5J.E3D@eskimo.com> <3lks8r$hmh@news1.best.com> 
<3ln5kn$pkd@pulsar.sky.net> <3lp6qi$dqg@news1.best.com>
Reply-To: jimenez@gaus90.chem.yale.edu

In <3lp6qi$dqg@news1.best.com>, pcguido@best.com writes:
: In <3ln5kn$pkd@pulsar.sky.net>, Bob Handley <bhandley@sky.net> 
writes:
: |pcguido@best.com wrote:
: ||
: || In <D6Ar5J.E3D@eskimo.com>, calvin@eskimo.com (Jimmie R. Farmer) 
writes:
: || |
: || | Hi there!  I was wondering if there was a way to MANUALLY log in
: || |and start a SLIP session in Warp's IAK?
: || |
: || | I was nosing around in the tcpip\bin dir recently, and saw the
: || |aformentioned SLIPTERM.EXE.  I tried to run it, but all I got was
: || |
: || |[C:\]slipterm
: || |Unable to locate configuration file slip.cfg (rc=2).
: || |
: || | Any suggestions on this one? What needs to go in the file
: || |'slip.cgf'? Am I on the right track here, or is there no way to 
manually
: || |log in?  Thanks in advance!
: || |
: || | Jimmie Farmer
: || |
: |[some text deleted]
: ||
: || Yes, you've found the commandline version of SLIP; but, without
: || the full TCP/IP doc, it's unlikely you're going to get very far.
: || Even with the doc, it took me several hours to get commandline
: || SLIP working just so I could trace my REXX script properly.
: || Turned out the problem wasn't even with my script! I advise you
: || stick to SLIPPM (the alternate dialer) unless you already KNOW
: || exactly why you want to do otherwise.
: ||
: || Phil "Guido" Cava   TeamOS/2
: |[some text deleted]
: |
: |It it possible for someone to post the TCP/IP doc (or at least the
: |portion concerning SLIP & slipterm)? I have had many problems with
: |SLIPPM and would rather use something where I can see what's going
: |on. If it's to big I'll except it via email. Thanks alot.
: |
: |Bob Handley
: 
: First, the documentation for IBM's TCP/IP product is in Book Manager
: format; so, you would need READIBM.EXE and it's associated DLL's
: to be able to read the doc at all. Second, the doc is part of a
: licensed product and distributing it would violate the license and
: effectively be pirating. Third, there is very little advantage to
: running SLIPTERM rather than running SLIPPM (the alternate dialer).
: The biggest advantage is being able to see the results of a TRACE
: statement in your REXX script, which, unless you are already familiar
: with REXX would be very little help.
: 
: Phil "Guido" Cava   TeamOS/2
: Help, PC!
: Let us help you achieve Warp Speed today!
: email at: pcguido@helppc.com
: ****  Say it LOUD: I'm WARPED and I'm PROUD!

There IS some documentation freely available in plain text format. By
now it's somewhat outdated, but it allowed me to play with the command
line forms of slip, slipterm, slcfg, and other stuff. I connect to my
slip server using the command line slip (slippm is not as flexible, and
i don't like it anyway). The documentation is contained within the
original slip driver for ibm's tcp/ip that was written by David Bolen.
Most of the things there still apply.

I believe the name of the package is slip2xv1.zip, in the
/pub/os2/32bit/network directory of hobbes.cdrom.com. If it's not 
there,
let me know and i'll try to look for it.

Additional information about the parameters that slip.cfg file can use,
can be obtained by just creating the file with the following lines in
it:

-------cut here for slip.cfg
interface sl0 {
	device comx,
	}
---------cut here

where x is the number of the port where your modem is located. Then you
can type at the command line:

[E:\] slcfg slip.cfg
Parsing file:
  INTERFACE:
    Name = sl0
    Device = com3
    MTU = 296
    RTT (rtt,var,min) = 0, 0, 0
    Pipe (send, recv) = 0, 4096
    SSThresh = 0
    MaxQueue = 12
    MaxFastQ = 24
    UseFastQ = 1
    Compression = 0
    Attachcmd = '(None)'
    Attachparms = '(None)'
    IPaddress = '(Not Assigned)'
    IPdest    = '(Not Assigned)'
[E:\]

So, with slcfg.exe you can get information on the configuration of
slip.exe from the slip.cfg file (i have my modem in com3). As the above
slip.cfg only contains the line specifying the port, all the other
parameters have default values within slip.exe. You can also get more
information about the command line parameters that slip.exe takes by
typing "slip -?". Most of the parameters in slip.cfg can be introduced
by switches (for example "slip -com3".

 This is what my actual slip.cfg file looks like:

interface sl0 {
   device=com3,
   compression=on,
   mtu=1006,
   SSThresh = 966,
   attachcmd="yale.cmd"
   }

Where yale.cmd is the rexx script that carries out the connection.
Otherwise, once you create a working slip.cfg file (which by the way
must go in the \tcpip\etc directory), you start it, and then you can 
run
slipterm. Within slipterm you can carry out the connection, start the
slip software in your server, and when you're done, you press the ESC
key which closes slipterm and returns control of the port to the
slipdriver. You can use the latest version of C-Kermit (still in beta)
as your "slipterm" as well.

I almost forgot. It's also a good idea to initialize the port before 
you
attempt any use. If it is set up incorrectly, slip won't work :(

I have this in my config.sys, although it could be typed at the command
line, or called within the rexx script itself.

CALL=E:\OS2\MODE.COM 
COM3:38400,n,8,1,idsr=on,xon=off,octs=on,odsr=on,dtr=on,buffer=on,to=of
f,rts=hs

Good luck,




--
 Hugo Jimenez-Vazquez
 jimenez@gaus90.chem.yale.edu
 Yale University
 Department of Chemistry

=====

Newsgroups: comp.os.os2.networking.tcp-ip
From: blogan@crash.cts.com (Barry Logan)
Subject: Re: SLIP/PPP from command line??
Reply-To: blogan@cts.com
Date: Thu, 6 Apr 1995 23:13:01 GMT
Message-ID: <9VHhvMTh6lnG083yn@crash.cts.com>
References: <3ls729$eae@news.tamu.edu> <3luhso$rth@homer.alpha.net>

In article <3luhso$rth@homer.alpha.net>, tomh@execpc.com (Tom Hansen) 
wrote:
 
> Stupid question: exactly how do you get PPP/SLIP to dial from the 
command 
> line? 

Not a stupid question. Neither the instructions nor all the files
necessary to start SLIP from the command line are included with Warp.

Here is one method.

Create the file \tcpip\etc\slip.cfg  which points at annex.cmd. The 
line attachcmd = annex.cmd tells Slip.exe which dialer script to use.
Slip.cfg looks like this:

interface sl0
   {
         device=COM2
         mtu=1006
         compression=on
         attachcmd = annex.cmd

   }


Create the file \tcpip\etc\resolv file with the following two lines: 

domain somehost.com
nameserver nnn.nnn.nn.nn


Modify the \tcpip\bin\annex.cmd file for your provider. You might want 
to
add a redial module to it.

Create a REXX script to start the process. Here is an example:

/* SLIP.CMD starts SLIP.exe with window title */
'mode com2:38400,N,8,1'
'start "SLIP" /c  c:\tcpip\bin\slip.exe -idle 10'

/* end */

NOTE - if the script is named slip.cmd and called from the command 
line,
it must be in the path BEFORE slip.exe.

To use the above technique to start POPClient or PMMail after 
the connection is made, use slipwait.exe. Here is an example:

/* CHKMAIL.CMD */
/* starts slip connection, waits for slip, calls POPCLient.cmd */

'mode com2:38400,N,8,1'

'start "slip" c:\tcpip\bin\slip.exe'    /* start slip */

'c:\tcpip\bin\slipwait.exe 360'   /* start slipwait 360 secs. */
if rc = 1 then exit          /* exit program when slipwait times out */
else do
     'call c:\os2\util\popclid.cmd'   /* check mail */
     call beep 1000,150             /* notify when done */
     'c:\tcpip\bin\go.exe k slip'  /* [k]ill SLIP connect */
     end
exit
/* end */


The kill program go.exe is available on hobbes.
ftp://hobbes.nmsu.edu:/os2/textutil/go_15.zip


Regards,


------
Barry Logan    blogan@crash.cts.com

=====

From: abbas@houston.geco-prakla.slb.com
Newsgroups: comp.os.os2.networking.tcp-ip
Subject: Re: Writing REXX scripts for SlipPm
Date: 31 Mar 1995 22:52:12 GMT
Distribution: world
Message-ID: <3li12s$747@gorgon.gatwick.Geco-Prakla.slb.com>
References: <3lbrba$3a9@news-rocq.inria.fr>
Reply-To: abbas@houston.geco-prakla.slb.com

In article 3a9@news-rocq.inria.fr, soulard@inria.fr writes:

> I'm trying to connect to another provider than IBM and I need to 
write
> a REXX script to do this. I've had a look to annexe.cmd and others 
but
> it does not work at all (for example, the slip_com_input function 
does
> not exist).
> 
> Can somebody post an example that works ?

Well, I had the same problem. Set up your Other Internet Dialer with 
proper
info and make sure that you have the latest dialer from ibm updates. 
then
on login area type in 

annex.cmd  atdt999-9999  loginid  password

and then try to dial it. Make sure your password dose not have any 
special
characters, if it does set it inside the annex.cmd manually.

Another problem is that I have to do manual setting for ifconfig and 
route
and I don't know why. You can use the same sample in annex.cmd.

Following is the note that I received from 

jon
--
The Warp Pharmacy
Tonics for Warp, via the Web
http://www.zeta.org.au/~jon/WarpPharmacy.html

    This is your problem. You need to configure a non-zero number in 
"Your IP Address" +
a number for "netmask". 

If the IP address is dynamically assigned by the provider, then you 
need to:

   a) Use ANNEX.CMD (instead of a .RSP file) to parse "Your IP address" 
      + "netmask" from the Internet provider

      Read about using ANNEX.CMD in the IAK documentation. I have
      never used it so, I have no other advice about this

   b) manually configure "Your IP address" + "netmask" to the correct 
value

      You can do this with:

        ifconfig sl0 yy.yy.yy.yy 163.xx.xx.xx netmask zz.zz.zz.zz

      where:
         yy.yy.yy.yy is your IP address
        163.xx.xx.xx is your the IP address on the providers side
         zz.zz.zz.zz is the  netmask


Diagnostic procedure:
.. check the interface

       [C:\]ifconfig sl0

       sl0: flags=11<UP,POINTOPOINT>
           inet 163.xx.xx.xx --> yy.yy.yy.yy netmask zhzhzhzh

       Note: zhzhzhzh is the hex representation of the netmask. If the
       netmask is 255.255.255.0 the hex version will be ffffff00


    2. check the routing

       [C:\]netstat -r 

       destination         router    refcnt        use flags     snmp  
intrf
                                                                metric
          163.xx.xx.xx    yy.yy.yy.yy     0           0    U       -1   
sl0
            default      163.xx.xx.xx     1         220    U       -1   
sl0


    3. ping the other end of the link 

       [C:\]ping 163.xx.xx.xx

       (Note: if your service provider gives you SLIP via the TIA
        program, ping will never work so don't bother trying it)

        
    4. check that name resolution works

       [C:\] host www.ibm.com
       www.ibm.com is 165.87.194.133

       If not, ping the domain name server using its IP address. 
       Check that the "Domain Nameserver" field has been configured
       correctly.

The Warp Pharmacy has pointers to several pages which explain this
better than I can. Have you looked at them?


> 
> Thanks.
> 
> 		Herve Soulard.
> 
> PS: Is there any documentation for Warp IAK program (slip.exe, 
ppp.exe, ...) ?

NO and that is  ....... !

I think Book Stop sells a book about IBM TCP/IP and networking on OS/2 
try it.

Abbas

=====

From: jpe@algonet.se (Jonas Eckerman)
Newsgroups: comp.os.os2.networking.tcp-ip
Subject: PPP Script to Dial IP, Get Mail/News, Logoff
Date: Tue, 21 Mar 1995 01:39:52 -0500
Message-ID: <19950321013952.2f7006dc@algonet.se>
Reply-To: jpe@algonet.se (Jonas Eckerman)


orosz@connix.com:

 o> Anyone know of a script I can use to dial my IP, use SOUPER to get 
my
 o> mail and newsgroups and then disconnect from the IP when finished? 
In
 o> other words, run an unattended session.

I suggest you use the start and slipwait commands.

Something like this maybe (the @eval is a 4OS2 variable function).


NightDial.Cmd (Starts NightSoup in a separate session and then trys 10 
times to 
connect.):

start NightSoup.cmd
set R=0
:Try
slip <lotsa parameters to get you connected>
set R=%@eval[%R+1]%
if "%R%"=="10" goto End
if errorlevel 1 goto Try
:End

NightSoup.Cmd (Waits for a connection, starts souper if succesful and 
terminates the connection.):

slipwait 3600
if errorlevel 1 goto End
Let souper do its work.
:End
slipkill


If something's wrong it's probably 'cause I'm writing from memory, but 
I think 
it's OK.


Mvh /Jonas
______________________________
Jonas Eckerman          FSDB
jpe@algonet.se           IIS

---
 * Origin: IIS (0:0/0)

=====

Newsgroups: comp.os.os2.networking.tcp-ip
From: matt@toaster.hna.com.au (Matt McLeod)
Subject: Re: IBM Software Is Feature Poor
Message-ID: <1995Apr1.084429.17053@scorch.hna.com.au>
Date: Sat, 1 Apr 1995 08:44:29 GMT
References: <aschlemmD5yHr7.46q@netcom.com> 
<3kvr15$cen@news.primenet.com> <aschlemmD63znx.DED@netcom.com> 
<3l8irc$mt1@kaiwan.kaiwan.com>

Bill Schultz (guru@kaiwan.com) wrote:
: In <>, aschlemm@netcom.com (Anthony Schlemmer) writes:

: [discussion of "quick and dirty" *.CMD file deleted]
: >Yes for quick and dirty yours is fine but I think that many users 
will 
: >want to have auto-redial which your method can't give. My campus 
dial-in 
: >is so busy that I have to redial about 10 times before I get a 
: >connection. No one wants to sit in front of their machine and have 
to keep
: >running the script time and time again until they get a connection.
: >

: In general, my feeling about the IBM software is that it is feature 
poor, which
: means to me that IBM did not research what the other software 
providers
: were giving their users in order to be friendly to said users. ;-)

: Automatic re-dial is one feature which is a "must" if you are not 
using one
: of the "big" Internet providers who has plenty of dial-up ports (and 
who
: charges accordingly).

Doing auto-redial with IAK is easy.  A few slight modifications
to my dialing script, and off it goes.  If anyone's interested,
just take the ANNEX.CMD script that IBM supplies, and replace
the:

	send dialcmd || cr
	waitfor 'CONNECT'; waitfor crlf

bit with something like this:

	do while waitfor_buffer <> 'CONNECt'
		send dialcmd || cr
		waitfor 'CONNECT', 30
	end

Simple as that.

Matt

--
Matt McLeod                       "Bonvolu alsendi la pordiston
Freelance General-Purpose Geek     lausajne estas rano en mia bideo."
matt@scorch.hna.com.au                   - AJ Rimmer

************  END OF PART TWO OF TWELVE PART WARP/IAK FAQ  ************
