home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 35 Internet
/
35-Internet.zip
/
tcphints.faq
< prev
next >
Wrap
Text File
|
1995-03-26
|
15KB
|
360 lines
@BEGIN
Getting the Most out of your Internet Access Kit (IAK), V 1.5
-------------------------------------------------------------
by Matthew S. Staben
mstaben@us.net
3-22-95
OS/2 Warp (3.0) provides a hacked subset of the TCP/IP 2.0 package
available for purchase. This subset is known as the Warp Internet
Access Kit (IAK). It includes utilities allowing a user to read
and post to newsgroups, utilize electronic mail, and much more.
This article is designed to help the user get on-line with as
little difficulty as possible -- and suggests replacement programs
which are quite useful, either as a supplement to IBM's programs or
a replacement. The supplementary programs are:
TIN 1.22, a newsreader that can be set up as a NNTP
(on-line, real-time) newsreader. TIN 1.22 is
a Unix port which behaves in exactly the same
manner as TIN does on other operating systems.
ELM 2.3, a mail reader that can even spool off mailing
into the background so when sending those
700,000 byte UUENCODED segments -- it doesn't
interfere with reading the rest of, or
replying to other pieces of mail. ELM is also
a Unix port, and utilizes the POP protocol
which will require a client. This document
describes the setup of the POP client as well.
Before you begin, you must have installed the Internet Access Kit
or the TCP/IP 2.0 package, and have obtained the following files:
TIN122.ZIP Unix port of the TIN newsreader.
ELM23-2.ZIP Unix port of the ELM mail program.
POPCL221.ZIP Allows one to set up a POP client for ELM.
DO NOT USE POPCL221A.ZIP, until you are comfortable with the
version contained in POPCL221.ZIP.
PPPFK101.ZIP PPP fake, pretends to be the dialer.
EMXRT.ZIP The EMX runtime files. You may already have
them.
These files are available by ftp'ing hobbes.nmsu.edu or
ftp-os2.cdrom.com.
You must also have obtained the PPP Gamma update from IBM. This
file can be installed automatically by use of the Software Updates
ICON or, while connected to your provider; from the command prompt
type "UPDATES -H UPDATES.GOPHER.IBM.COM". Even if you do not
intend to use PPP, this update provides a better SLIP interface as
well.
* NOTE: When UNZIPPING files, always unzip
with directories. InfoZIP's UNZIP utility
does not require any parameters, but PKUNZIP
requires that the -d parameter be supplied.
You MUST use HPFS partitions for both TIN and
ELM as long filenames are used, as well as the
temporary directory to where you unzip these
files. The reason for this is that TIN and
ELM are ports from the Unix operating system
which utilizes long filenames. DOS is
incapable of handling this type of filename.
Additionally, you cannot use the DOS version
of PKUNZIP -- you must use OS/2's because of
long filename compatibility.
Step 1: Installing the EMX Dynamic Link Libraries
The first step which must be taken is to set up the EMX DLLs. The
EMX library is continuously updated, so even if you already have
one version in your environment -- you should get the latest
version and replace the one you have each time you install software
requiring the EMX DLLs. If you have never installed the EMX DLLs,
you must first provide a permanent location for them as follows:
Unzip the ELM23-2.ZIP file which you obtained into its own,
permanent directory. Remember to use the -d option if you are
using PKWare's PKUNZIP utility. This will break out several files.
For example, following the following sequence might be usable:
[H:\] md ELM23
[H:\EMX] cd ELM23
[H:\EMX] PKUNZIP2 -d E:\HA5\FILES\EMXRT.ZIP
CONFIG.SYS will then need to have the EMX path appended to the SET
PATH statement. In this case, add <;H:\EMX\BIN> while omitting the
brackets. It is important to remember the location of your EMX
DLLs as they it will be needed again to complete step 3.
While still modifying the CONFIG.SYS files, you can place remark
(REM) statements in front of several of the DOS drivers if you
don't plan on using Windows or DOS software to access the Internet.
If not, then loading them on startup is a waste of memory. This is
done by remarking out the significant lines:
rem DEVICE=h:\tcpip\bin\vdostcp.vdd
rem DEVICE=h:\tcpip\bin\vdostcp.sys
rem RUN=h:\tcpip\bin\vdosctl.exe
Even if you do so now, you can always remove the REMark statements
and the drivers will load the next time you boot your machine.
Step 2: Install TIN 1.22
Unzip the TIN122.ZIP file which you obtained into its own,
temporary directory. Remember to use the -d option if you are
using PKWare's PKUNZIP utility. This will break out several files.
delete README.OS2, or store it in another location.
delete TCPIPDLL.ZIP.
rename TIN.EXE to RTIN.EXE. By doing this, you are causing
TIN 1.22 to use NNTP
news-server mode. See
README.OS2 for more
information.
create TIN.CMD -- Here's mine.
----------------BEGIN----------------
@echo off
set USER=mstaben
set REALNAME=Matthew S. Staben
set HOME=H:/tcpip/home
set TMP=H:/tcpip/tmp
set NNTPSERVER=news.us.net
set HOSTNAME=usnet.us.net
set TIN_SPOOLDIR=H:/TCPIP/TIN
set TIN_LIBDIR=H:/TCPIP/TIN
set TIN_NOVROOTDIR=H:/TCPIP/TIN
set LINES=25 // WANT 50 lines?
set COLS=80
rem MODE CO80,25 // YOU CAN SET YOUR VIDEO
set EDITOR=T32.EXE // TO YOUR PREFERENCE
set VISUAL=T32.EXE
RTIN
-----------------END-----------------
You may have noticed that I use the T32.EXE program as my editor.
If this field is left blank, the default editor (EPM.EXE) will be
used. Copy all three of the remaining files, RTIN.EXE, TIN.CMD, to
the \TCPIP\BIN directory. TIN.MAN can be copied to your manuals
directory, deleted, or saved along with the other files. Delete
the files (copy source) and remove the temporary directory. TIN
1.22 is now installed.
Step 3: Install ELM 2.3
Unzip the ELM23-2.ZIP file which you obtained into its own,
permanent directory. Remember to use the -d option if you are
using PKWare's PKUNZIP utility. This will break out several files.
Unlike the TIN installation, there are many files including source
code which is unnecessary for our purposes. In fact, for this
installation, only the files contained in the BIN directory and the
DOC directory will be used. You may delete all other files and
their associated directories without adverse effect. For example,
following the following sequence might be usable:
[H:\TCPIP] md ELM23
[H:\TCPIP] cd ELM23
[H:\TCPIP\ELM23] PKUNZIP2 -d E:\HA5\FILES\ELM23-2
[H:\TCPIP\ELM23] cd BIN
[H:\TCPIP\ELM23\BIN]
In the BIN directory, along with other files, is a file named
ELM-TCP.RC. This file is the resource file for ELM and contains
the basic setup of ELM and needs to be changed as I did mine.
Comments are preceded with a pound (#) sign and do not need to be
removed.
----------------BEGIN----------------
Rmail=sendmail
Options=background
NodeName=mstaben
Domain=us.net
FromDomain=us.net
ReplyTo=mstaben@us.net
ConfDir=H:/tcpip/etc
MailDir=H:/tcpip/mail
TempDir=H:/tcpip/tmp
Mailbox=mstaben
Name=Matthew S. Staben
Home=H:/tcpip/home
Editor=T32.EXE %s
Pager=T32.EXE %s
-----------------END-----------------
CONFIG.SYS must be updated to contain the following lines:
----------------BEGIN----------------
SET HOSTNAME=usnet.us.net
SET TERM=mono
SET TERMCAP=H:\EMX\ETC\TERMCAP.DAT
SET UUPCSYSRC=H:\TCPIP\ELM\BIN\ELM-TCP.RC
SET UUPCUSRRC=H:\TCPIP\ELM\BIN\ELM-TCP.RC
-----------------END-----------------
Note the SET TERMCAP setting above. This path should reflect the
path used when installing the EMX DLLs as described in step one (1)
of this document.
Additionally, CONFIG.SYS needs to have the path appended to the SET
PATH statement. In this case, add <;H:\TCPIP\ELM\BIN> while
omitting the brackets. Please note that the EMX runtime DLL's set
by the SET TERMCAP label may differ for your installation. Please
refer to step 1 in this document. ELM requires that a file,
SENDMAIL.CF, exist. Unfortunately, the IAK supplies this file as
SENDMAIL.UML to work with Ultimail lite. SENDMAIL.UML should be
copied to SENDMAIL.CF, and can be found in your \TCPIP\ETC
directory. Once copied, it will need to be modified through use
of, and only of, the "E.EXE" editor. The relevant lines are shown
with my changes. Following the DV, the mail server's relay should
be named. Following the DH, the domain name of the mail hub should
be used. My mail server is actually "mail.us.net" and is broken
into two here.
(( The E.EXE editor does not expand tabs, as other editors do. ))
----------------BEGIN----------------
# The unqualified (domain-less) name of the mail relay
DVmail
# The fully-qualified domain name of the mail hub
DHus.net
# Version # of this file
DZ1.0um
-----------------END-----------------
When this is complete, your installation of ELM is complete except
for the POP client which serves as the mail grabber -- in that it
repeatedly checks the POP server on the mail relay for incoming
mail and downloads it to the remote location. ELM then notices
that this mail has arrived and updates its screen.
Step 4: Install the POP Client
Unzip the POPCL221.ZIP file which you obtained into its own,
temporary directory. Remember to use the -d option if you are
using PKWare's PKUNZIP utility. This will break out several files.
Edit the POPCLID.CMD file on the relevant lines, as I've done here.
It doesn't matter which editor you use. Again, the settings should
be tailored to your particular Internet provider:
----------------BEGIN----------------
host = 'us.net'
loginname = 'mstaben'
password = 'dontwork'
delay = 120
mda_path = 'filter.exe'
mda_args = '-v -u mstaben'
-----------------END-----------------
And then, you should copy POPCLIENT.EXE, POPCLID.CMD, LAMAILER.CMD
to the \TCPIP\BIN directory.
Step 5: Set up your Dialer.
The Internet Access Kit (IAK) offers two methods of accessing the
Internet. You can purchase access through IBM's advantis network,
which is a costly but easy way to get started, or you can get
access through one of many other access providers. Either way,
both methods of accessing the Internet utilize underlying
command-line files which handle the grunt work. In the file,
PPPFK101.ZIP are two replacement files, SLIP.EXE and PPP.EXE
(depending on your connect option) which temporarily replace the
original SLIP or PPP executable and write the received parameters
out to a file so that the command-line executable can be used
without the graphical front end. So, assuming a working connection
already exists, you can unzip the PPPFK101.ZIP file and follow the
instructions. They are straightforward -- except they do not
mention where the files it creates will be placed. I found mine in
the root directory of the [C:\] directory.
Even if you do not wish to use the faker package, I have included
the necessary listing of parameters so that you may simply cut it
out and use it as a batch file. It is in fact, the .CMD file I use
to dial out. Where the comment ((SAME LINE)), simply have the
information given all on one single line with no carriage returns.
The .CMD file below will redial if the line is busy, no answer, or
the connection is lost during connect. It will exit if either
SLIPKILL, PPPKILL, or the CONTROL-C option is used to terminate the
connection.
** NOTE: The only change I made was to change my password to
"dontknow," and the phone number. This command file will
also redial if there is no answer or busy, a very handy
ability. I also placed this .CMD file in H:\TCPIP\BIN as
I did everything else.
----------------BEGIN----------------
:begin
rem
rem THIS IS THE SLIP.EXE PARAMETER LISTING
rem slip.exe -p3 -hangup ath -com2 -speed 57600 -mtu 1006
rem -nocfg -exit 0 -notify -rtscts -idle 120 -connect
rem "h:\tcpip\bin\usnet.cmd atdt3018471102 mstaben dontknow"
rem
REM ** BEGINNING HERE, PLACE ALL PARAMETERS ON ONE LINE **
ppp.exe com2 57600 mru 1500 rtscts modem defaultroute
netmask 255.255.0.0 priority 1 notify exit user mstaben
name mstaben secret dontknow -vj idle 120 connect "slattach
ATZ OK AT&C1&D2&K3&Q5S11=55S95=47 OK ATDT301-555-1212 NNECT
\r login: mstaben ssword: dontknow usnet ppp\r"
REM ** THE ABOVE SHOULD BE ONE SINGLE LINE **
if errorlevel 4 goto 4
if errorlevel 3 goto 3
if errorlevel 2 goto 2
if errorlevel 1 goto 1
if errorlevel 0 goto 0
echo NONE
goto exit
:0
echo LOST CONNECTION
goto exit
:1
echo BUSY/FAILED DIAL
goto begin
:2
echo TWO
goto exit
:3
echo THREE
goto exit
:4
echo NORMAL EXIT BY KEY
goto exit
:exit
-----------------END-----------------
Step 6: Make your directories.
For the last, and most simple step, you need to make the
directories that ELM and TIN will need. These are the:
H:\TCPIP\TMP
H:\TCPIP\HOME
H:\TCPIP\MAIL
H:\TCPIP\HOME\.TIN (yes, that's a DOT)
H:\TCPIP\HOME\ELM
The signature file can be placed here, as .signature and signature,
one for each of the packages.
GOOD LUCK, and HAPPY SURFING! If you have any questions, please
feel free to contact me at mstaben@us.net. I check my mail every
time I walk up to the computer (by starting STARTPPP.CMD which
starts the dialer, ELM 2.3, and POPCLIENT). I can also be reached
at 11MSTABEN@GALLUA.GALLAUDET.EDU. This mailbox is checked more
frequently.
@END