home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
wpfaq001.zip
/
T_FAQ6.TXT
< prev
next >
Wrap
Text File
|
1995-04-29
|
27KB
|
728 lines
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 6 of 12. It contains the sixth 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. ;-)
5.0 OS/2 TCP/IP QUESTIONS
IBM Supplied FAQ:
This note is an answer to some frequently asked questions about OS/2
Warp, Internet Access, and TCP/IP 2.0.
(1) Does TCP/IP 2.0 work on WARP?
We are testing this, and we haven't found any problems yet. This is a
supported combination, meaning that we will fix any problems that do
arise.
(2) Does the Internet Connection kit work with OS/2 2.1?
No. The Internet Connection kit can only be installed on OS/2 Warp.
(3) I have OS/2 2.1 and TCP/IP 2.0. Can I run Web Explorer and Gopher?
Yes. You must have CSD UN64092 installed. Web Explorer can be
downloaded from the Internet, via anonymous FTP from
ftp01.ny.us.ibm.net, where it is in the subdirectory /pub/WebExporer.
Gopher can be downloaded from the Internet, via anonymous FTP from
software.watson.ibm.com, where it is in the subdirectory /pub/os2/ews.
The version of Gopher on software.watson.ibm.com is not current, but it
will be updated soon.
(4) I have OS/2 Warp. Can I use the Internet Connection kit for TCP/IP
LAN access?
No, the Internet Connection kit only supports dial access. You must
install TCP/IP 2.0 for LAN based TCP/IP access. A follow-on to OS/2
Warp is in the works that will include full LAN enablement. (There
will
be an upgrade charge.)
(5) Can I install both TCP/IP 2.0 (for LAN access) and the Internet
Connection kit?
Yes. This combination is not tested or supported, but it does work.
You
must install TCP/IP 2.0 first. Then you install CSD UN64092. Then you
install the Internet Connection, in the same directory where TCP/IP 2.0
is installed. You will see a warning message that the combination is
not
supported. There are some problems:
5a. The icons of the Internet Connection kit are configured to use a
dial connection. How do I use these applications on the LAN?
Create program objects for Web Explorer (explore.exe) and Gopher
(gopher.exe) in your TCP/IP folder.
5b. The UltiMedia Mail Lite package included with the Internet
Connection kit is configured to be used with an Internet mail box. How
do I use it on the LAN?
For LAN based mail, use the LaMail package that ships with TCP/IP 2.0.
Questions 5c and 5d come up when a user tries to use Internet and LAN
TCP/IP access simultaneously. These problems do not occur unless you
try
to access TCP/IP hosts on a LAN at the same time that you have an
active
dial connection to the Internet.
5c. I want to access TCP/IP hosts on the LAN and via a dial connection
to the Internet simultaneously. When I dial the Internet, I can no
longer get to the LAN TCP/IP hosts. The error message is "host
unknown".
What do I do about this?
While you are connected to the Internet, TCP/IP name resolution queries
a
host name server on the Internet to look up host addresses. The
Internet
name server will not know the names of your local hosts. You can use
the
TCP/IP configuration notebook to create a hosts file (page 3 of the
services section) for hosts on your LAN. Or you can access hosts on
your
LAN by IP address instead of by name.
5d. I have a default route to a router on my LAN. When I dial the
Internet, the LAN default route is inactivated, and I can no longer
access TCP/IP hosts through my LAN router until I hang up the Internet
connection. What do I do about this?
While you are connected to the Internet, your default route is to the
Internet. You can create host, network, or subnet routes for TCP/IP
hosts that you access through your LAN router, so that these hosts
remain
accessible while you are connected to the Internet. You use the
routing
page of the TCP/IP Configuration Notebook.
=====
From: daveh@csn.net (Dave Hughes)
Newsgroups: comp.os.os2.networking.tcp-ip
Subject: Re: Slip -> Os2 -> Net?
Date: 31 Mar 1995 04:41:16 GMT
Message-ID: <3lg15c$np7@news-2.csn.net>
References: <3ktl2j$b7i@news-2.csn.net> <3kvoss$r13@kelso.abbott.com>
<3l5cr5$fiq@fox.almaden.ibm.com>
Thanks all, for the leads. I will study and apply - and holllar when
it works.
Tony Rall (trall@trall.almaden.ibm.com) wrote:
: The typical problem is not so that the system on the lan side of the
: slip link knows about the other end of the link - it certainly does
: or you wouldn't be able to ping it. It's that the other systems on
: the lan don't know about the remote slip system. One of the setups
: described below should do what you want.
: Routing for OS/2 TCP/IP
:
: (Wherever "SLIP" is indicated below, any supported point-to-point
: protocol could be substituted. From the routing standpoint, it makes
: no difference.)
:
: In the examples below, IP addresses are shown using the following
: shorthand:
:
: L1 = IP address for interface 1 on subnet L. For example, if the
: subnet address is 128.1.2.0 (subnet mask = 255.255.255.0), the IP
: address would be 128.1.2.1.
: Interfaces and addresses
: ------------------------
: Machines don't have IP addresses - interfaces do. If you have a
: machine with two LAN interfaces, you should have two IP addresses.
: Normally these addresses would be on different subnets.
: Point-to-point interfaces are an exception to this addressing rule -
: the address used can match one of the machine's other addresses. And
: the address of the other end of the link doesn't even have to be on
: the same "subnet".
: Also, you do not need to add routes for destinations that are defined
: by your interfaces. For example, if you have a SLIP connection
: defined as:
: ifconfig sl0 S1 S2
: no routing definition (a "route add" command) is needed for S2.
: Some SLIP routers do not have IP addresses for their SLIP interface.
: They do, however, have addresses for any LAN interfaces that they
: have. Remote OS/2 machines require that their SLIP interfaces be
: configured with a target address; thus it is necessary to either find
: out the router's LAN address or make up an address. In the latter
: case, I suggest an address like 172.1.1.1 (which will not be used by
: anyone on the connected Internet); also, you will not be able to send
: packets with the router as the destination (i.e., you won't be able
to
: ping the router), but you will be able to send packets through the
: router to some distant destination.
: Names and addresses
: -------------------
: Routing is only concerned with IP addresses (such as 198.79.74.5) and
: not IP names (such as www.ibm.com). Nameservers (or HOSTS files) are
: used to translate between names and addresses. If you start with an
: IP name, it will always have to be converted to an address (since
that
: is what routing requires). If you start with an address, the name
may
: not be required, but some applications require that it be possible to
: perform the reverse translation from address to name. But again,
that
: isn't a routing issue, and names will not be mentioned in the rest of
: this discussion.
: Where routing is configured
: ---------------------------
: Most, if not all, of the changes suggested below for SETUP.CMD and
: TCPSTART.CMD (these are in the TCPIP\BIN directory) can be
: accomplished by completing the Network, Routing, and Autostart
: sections of the TCP/IP configuration notebook (TCPIPCFG.EXE) rather
: than simply editing the indicated files.
:
: Routing on a machine with a single interface
: --------------------------------------------
:
: --------------- LAN
: | | |
: L1 L2 L3-----other subnets
: router
:
: * Static routing
: Simple, cheap, but no recovery from router failure. In
SETUP.CMD,
: for machines such as L1 and L2, add:
: route -f add default L3 1
: The network administrator should provide you with the router's
IP
: address.
: * Dynamic routing
: Not very complicated, some cost (requires another process
(demon)
: running on your machine that listens for certain broadcast
: packets), can provide automatic recovery from router failure
and
: configuration changes. To use this, at least one router on
your
: network must also support RIP, a routing protocol most commonly
: used on end-user networks. In TCPSTART.CMD, add (or
uncomment):
: start routed -q
: or (to avoid having the demon's window appear on your screen):
: start /min routed -q
: or (to avoid routed even showing up in your window list):
: detach routed -q
: You don't need any route statements in SETUP.CMD.
:
: Routing a LAN via SLIP to the internet
: --------------------------------------
:
: --------------- LAN
: | | | SLIP link
: L1 L2 L3/S1-------------------S2/I1---(the internet)
:
: In this setup, the administrator of the S2/I1 machine (usually a
: commercial Internet provider) must be aware that you have a
"network"
: at your end of the SLIP link and not simply a single machine. That
: administrator usually must assign you the local network address (L)
: that you will be using (as well as the SLIP addresses (S1 and S2).
In
: some cases, the SLIP addresses will be handled dynamically; this
would
: usually be handled in SLIPUP.CMD, rather than in SETUP.CMD, on
L3/S1.
: (I hope that the LAN addresses, L1, L2, and L3, are not dynamic - I
: wouldn't know how to handle that.)
:
: * The non-SLIP LAN machines (L1, L2)
: In SETUP.CMD, add:
: route -f add default L3 1
: * The SLIP-LAN machine (two IP addresses: L3 and S1)
: In SETUP.CMD, add:
: route -f add default S2 1
: In TCPSTART.CMD, you may need to start routed (but without the
: "-q" option) - see below:
: start routed
: * Routing required on the "internet" side
: The S2/I1 machine must do something to enable itself and other
: internet machines to be aware of the L network:
: - Use dynamic routing. If L3/S1 runs routed (without the -q
: (quiet) option), S2/I1 can run routed or gated (preferably
: quietly) to listen for the routing broadcasts from L3/S1.
: - Use static routing. L3/S1 need not run routed (and some
: traffic on the SLIP link is avoided). A network route (on
: S2/I1) is needed to the LAN:
: route add net L S1 1
:
: Routing a LAN machine via SLIP to a home machine
: ------------------------------------------------
:
: SLIP link
: S1-------------------S2/I1---(the office network)
: home office
:
: In this setup, the administrator of the office network must provide
: you with your IP addresses. You need at least 3 of them: S1, S2,
and
: I1. Ideally S1 and S2 will be on a different subnet than I1 - ask
for
: this configuration. If your network administrator will only
provide
: addresses in the same network, you must use the "proxy arp"
solution
: below.
:
: * The home machine
: In SETUP.CMD, add:
: route -f add default S2 1
: * The office (SLIP-LAN) machine
: * Routing to a SLIP subnet
: You simply must be running a routing protocol out the LAN (I1)
: interface. In TCPSTART.CMD, you need to start routed (but
without
: the "-q" option):
: start routed
: * Proxy arp solution - no separate SLIP subnet
: In this case, all of the IP addresses (S1, S2, I1) that you've
: been assigned are on the same subnet. Normal routing
techniques
: will not work because the S1 address (no other LAN machine
needs
: to talk to S2) is not physically on the same network as I1. So
: we try to use a technique called "proxy arp": the office
machine
: will respond on the I network to arp queries for S1 with its
own
: adapter address.
:
: First you have to determine the LAN adapter address of the I1
: interface. Issue "netstat -n" and copy the displayed "physical
: address" for the I1 interface. In SETUP.CMD, after the "arp -
f"
: statement add:
: arp -s S1 12:34:56:78:90:12 pub
: where 12:34:56:78:90:12 is the adapter address of I1.
:
: This tells TCP/IP that when it receives an arp message for IP
: address S1, that it should respond with its own adapter
address.
: Thus other machines on the I subnet, when wanting to send to
S1,
: will actually transmit to I1. The S2/I1 machine should forward
: the packet over the SLIP link to S1.
: --
: Tony Rall trall@almaden.ibm.com
=====
From: trall@trall.almaden.ibm.com (Tony Rall)
Newsgroups: comp.os.os2.networking.tcp-ip
Subject: Re: Need Help with TCPIP routing/addressing
Date: 1 Apr 1995 07:26:04 GMT
Message-ID: <3liv6c$l2q@fox.almaden.ibm.com>
References: <3lbtki$ovi@superb.csc.ti.com> <3lekth$tj@news3.digex.net>
Reply-To: trall@almaden.ibm.com (Tony Rall)
Jake Coughlin's reply was right on the mark. Here's a post I made
recently elsewhere on this same subject:
If TCP/IP 2.0 and the IAK (or simply slippm.exe) are both installed,
it is possible to run both lan and serial stuff simultaneously.
However starting the slip or ppp link using the supplied aids (such as
slippm and annex.cmd) will mess up your default route and probably
your nameserver address (in etc\resolv). These things can be
corrected manually or you can write a different slip startup script
that doesn't screw things up in the first place.
Exactly what has to be done after the serial connection is configured
depends on how you want things to work. In any case, running ppp
should not cause you to lose the route to your local lan subnet. In
other words, you should still be able to talk to others on your
subnet by IP address (but perhaps not by name).
If you have other lans connected via one or more other routers, you
might not be able to reach them after starting ppp (because your
default route may now point to the ppp connection).
Name resolution
---------------
As for name resolution, this can be tough. The way this is designed,
the first name server that responds to you must be able to resolve
any name you're going to use (or the name must be in your own
etc\hosts).
If you have a company nameserver that only knows the names on your
local
lans, and a service provider nameserver that knows Internet names but
not your local names, you've got a problem with no easy solution.
When slippm runs, it replaces your etc\resolv file (where your
nameserver is specified) with one that points to the nameserver
you configure for your serial connection. This is the reason that
none of your lan names are likely to work after starting ppp.
Assuming you can't get the server function centralized, you're left
with the following choices:
* Don't use local names while connected via PPP (and re-establish
your lan etc\resolv file after dropping the PPP connection).
* Put all of your local names in etc\hosts. (Keeping this current
can be a royal pain if you have more than a few machines). Erase
etc\resolv when not connected to your provider.
Routing
-------
There's many possibilities depending on how you want it to work.
I'll discuss a single example. Let's say you have 2 subnets on
your lan:
1.1.1.0 1.1.2.0
-------------------- ----------------
|.7 |.1 |.1 .9| ppp 2.5.5.0
A ----R---- os2--------------ISP
.10 .1
The interesting configuration is the OS/2 machine. Before the ppp
link was added, he may have been configured like this (in
tcpip\bin\setup.cmd):
ifconfig lan0 1.1.2.9 netmask 255.255.255.0
route add default 1.1.2.1 1
Running slippm will add another default route and tend to mess
things up. Change the setup.cmd to the following for a static
routing solution:
ifconfig lan0 1.1.2.9 netmask 255.255.255.0
route add subnet 1.1.1.0 1.1.2.1 1
This will solve the routing for this simple configuration.
As a gateway to the Internet
----------------------------
The OS/2 machine will do this as already described (unless you
put "ipgate off" in setup.cmd). But the rest of the setup won't
cooperate unless you make provision for it.
In particular, your lan partners won't know to route stuff destined to
the Internet to you. In my example, the machines on 1.1.1.0 need a
default route to 1.1.1.1 (which they would probably already have), and
the other machines on 1.1.2.0 need a default route to you, 1.1.2.9
(which they probably don't have). They would also need the same
subnet route that you use (route add subnet 1.1.1.0 1.1.2.1 1) to your
other lan.
And your ISP must know about your subnets - so that they will route
everything destined to your machines via your OS/2 machine. On top of
that, your network address (1.0.0.0 in the example) will have to be an
officially registered address. It takes some time to set this up.
You may have to change all your lan addresses to match what you're
assigned. Your ISP may charge you extra for the additional routing
and nameservice functions.
--
Tony Rall trall@almaden.ibm.com
=====
Newsgroups: comp.os.os2.networking.tcp-ip
From: bdelima@novell.com (Bob DeLima)
Subject: Getting TCPIP 2.0 and NW to coexist
Message-ID: <1995Mar31.162511.6412@novell.com>
Date: Fri, 31 Mar 1995 16:25:11 GMT
I use Warp exclusively now but this should also apply to 2.11, so I'll
share
with you my observations.
1. Install Warp and the IAK
2. Install 2.11 requester, DON'T reboot yet
3. Install the rt211.exe Requester patch
4. Verify that you DON'T have CONNECTIONS in the SET AUTOSTART line of
the
config.sys and reboot OS/2. Make sure Netware is working OK before
proceeding
any further.
5. Install TCPIP into the same directory as the IAK, don't
worry configuring LAPS. DON'T reboot yet
6. Install TCPIP CSDs
7. Reboot - you may get some errors
8. Open the Netware Requester Install utility and select Utilities-
>ODINSUP
setup
9. Run the TCPIP Configuration applet in your TCPIP folder to
configure TCPIP.
10. Your NET.CFG file should look something like this:
Link Driver NE2000
frame ethernet_802.2
frame ethernet_802.3
frame ethernet_ii
frame ethernet_snap
INT #1 10
PORT #1 360
Link Support
Buffers 38 1514
MemPool 4096
Max stacks 5
Protocol stack ipx
bind NE2000
sockets 128
Protocol stack spx
bind NE2000
sessions 64
netware requester
cache buffers 30
sessions 20
preferred server=my_server
default login drive f:
display hard errors off
DATA ECB COUNT = 90
ECB COUNT = 20
USE MAX PACKET = ON
Protocol TCPIP
Bind NE2000
ip_address xxx.xx.xxx.xxx
ip_netmask xxx.xxx.xxx.x
ip_router xxx.xx.xxx.xxx
tcp_buffer 10240
tcp_sockets 16
udp_sockets 8
raw_sockets 1
nb_sessions 4
nb_commands 8
protocol odinsup
bind NE2000
11. Your protocol.ini file should look like this:
[PROT_MAN]
DRIVERNAME = PROTMAN$
[IBMLXCFG]
tcpip_nif = tcpip.nif
ibmtok_nif = ibmtok.nif
[tcpip_nif]
DriverName = TCPIP$
Bindings = NE2000
[NE2000]
DriverName = NE2000$
12. Your config.sys should have the following for the TCPIP and
Netware
stuff. Be careful of ordering:
SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS
LIBPATH=.;C:\OS2\DLL;C:\OS2\MDOS;C:\;C:\OS2\APPS\DLL;C:\MMOS2\DLL;C:\IB
MCOM\DLL;C:\TCPIP\DLL;C:\TCPIP\UMAIL;C:\VIEWER\DLL;C:\NETWARE;C:\NETWAR
E\NLS\ENGLISH;L:\OS2;P:\OS2;
SET
PATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;C:\;C:\OS2\
MDOS;C:\OS2\APPS;C:\MMOS2;C:\TCPIP\BIN;C:\TCPIP\UMAIL;C:\VIEWER\BIN;C:\
NETWARE;L:\OS2;P:\OS2;
SET
DPATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;C:\;C:\OS2
\BITMAP;C:\OS2\DOS;C:\OS2\APPS;C:\IBMCOM;C:\MMOS2;C:\MMOS2\INSTALL;C:\V
IEWER\DATA;C:\NETWARE;C:\
ETWARE\NLS;C:\NETWARE\NLS\ENGLISH;L:\NLS;P:\NLS;
SET
HELP=C:\OS2\HELP;C:\OS2\HELP\TUTORIAL;C:\MMOS2\HELP;c:\tcpip\help;C:\TC
PIP\UMAIL;C:\VIEWER\HELP;C:\NETWARE\NLS\ENGLISH;
DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM
DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM
SET BOOKSHELF=C:\OS2\BOOK;C:\MMOS2;C:\TCPIP\DOC;C:\APPS\OS2\TCPIP\HELP;
DEVICE=C:\NETWARE\VIPX.SYS
DEVICE=C:\NETWARE\VSHELL.SYS GLOBAL
REM --- NetWare Requester statements BEGIN ---
SET NWLANGUAGE=ENGLISH
DEVICE=C:\NETWARE\LSL.SYS
RUN=C:\NETWARE\DDAEMON.EXE
REM -- ODI-Driver Files
BEGIN --DEVICE=C:\NETWARE\NE2000.SYS
REM -- ODI-Driver Files END --REM
DEVICE=C:\NETWARE\ROUTE.SYS
DEVICE=C:\NETWARE\ODINSUP.SYS
DEVICE=C:\NETWARE\IPX.SYS
DEVICE=C:\NETWARE\SPX.SYS
RUN=C:\NETWARE\SPDAEMON.EXE
rem DEVICE=C:\NETWARE\NMPIPE.SYS
rem DEVICE=C:\NETWARE\NPSERVER.SYS
rem RUN=C:\NETWARE\NPDAEMON.EXE
DEVICE=C:\NETWARE\NWREQ.SYS
IFS=C:\NETWARE\NWIFS.IFS
RUN=C:\NETWARE\NWDAEMON.EXE
rem DEVICE=C:\NETWARE\NETBIOS.SYS
rem RUN=C:\NETWARE\NBDAEMON.EXE
DEVICEHIGH=C:\OS2\MDOS\LPTDD.SYS
REM --- NetWare Requester statements END ---
RUN=C:\IBMCOM\PROTOCOL\NETBIND.EXE
RUN=C:\IBMCOM\LANMSGEX.EXE
SET ETC=c:\tcpip\etc
SET TMP=c:\tcpip\tmp
SET READIBM=C:\TCPIP\DOC
SET HOSTNAME=your_pc
SET NEWSSERVER=your newsserver ip address
DEVICE=C:\IBMCOM\PROTOCOL\INET.SYS
DEVICE=C:\IBMCOM\PROTOCOL\IFNDIS.SYS
DEVICE=c:\tcpip\bin\vdostcp.vdd
DEVICEHIGH=c:\tcpip\bin\vdostcp.sys
RUN=c:\tcpip\bin\cntrl.exe
RUN=c:\tcpip\bin\vdosctl.exe
SET TELNET.PASSWORD.ID=password
13. Go into the IAK folder and change the program objects to remove
LINKUP.EXE. For example, open settings for the Retreive Software
Updates
Icon. Delete LINKUP.EXE from program name and put in UPDATE.EXE from
the line
below(parmaeters). In the parameters field, remove the UPDATE.EXE from
the
box, but leave the rest. change the /h to -h. You will now be able to
use
this applet to retreive and install the latest newsreader, webexplorer,
PPP,
archie, Ultimail, and whatever else IBM release for the IAK. You can
also
remove LINKUP.EXE from the other program objects as well.
Good luck and let me know how it goes.
Regards-
Bob DeLima
Novell Inc
************* END OF PART SIX OF TWELVE PART WARP/IAK FAQ ***********