RLN40UP1.TXT

Readme for Remote LAN Node (RLN) 4.0 Updates

Contents:

	1) Listing of files included in this update
	2) Installation instructions
	3) Obtaining compressed versions of the updated files
	4) Description of problems addressed in this update

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

1) Listing of files included in this update

	rln40up1 txt (this file)

CLIENT\DOSWIN

	rlnapi   dll         7,680 08-18-95  11:28a
	rlnui    dll        37,376 08-18-95  11:30a
	rln      exe        58,485 12-14-95   9:19a
	rlnasync exe        22,027 11-30-95  10:16a
	rlnuser  exe       237,779 10-11-95   6:08p
	rlnuserw exe       115,200 10-11-95   6:09p
	rlnvxd   exe         9,860 11-26-95   7:11p
	rlnuser  res        18,216 10-11-95   6:08p

CLIENT\DOSWIN\ODI

	rlnodi-e com        20,895 07-21-95   9:43a
	rlnodi-t com        21,679 07-21-95   9:43a

CLIENT\DOSWIN\SPM

	xfaxspm  exe        10,384 08-18-95  11:44a

CLIENT\OS2

	rlnos2   exe       117,840 12-14-95   9:25a

RLNNASI

	rlnnasi  exe        24,806 08-17-95  10:53a

SERVER

	rlnserv  exe     1,192,806 12-04-95  12:43p
	dbcnvt   exe       213,988 10-11-95   6:51p
	dbcnvt   txt         1,108 12-12-95  11:50a

=============================================================================
2) Installation instructions

The updated files in this archive should be applied to RLN 4.0 installations
only.

When RLN40UP1.EXE is executed, it will uncompress in the current directory 
and create the following subdirectories:

 - CLIENT\DOSWIN
 - CLIENT\DOSWIN\ODI
 - CLIENT\DOSWIN\SPM
 - CLIENT\OS2
 - SERVER

Updating an RLN Server installation:

 Pick a time when no users are currently on the server. Go to the server 
 console and shut it down. Copy the files from the "SERVER" directory to the 
 directory where the RLN server is installed.

Updating an RLN DOS/Windows Client installation:

 Copy the files from the "CLIENT\DOSWIN" directory to the directory where the 
 RLN client is installed. Also copy the files from the "CLIENT\DOSWIN\ODI" 
 and "CLIENT\DOSWIN\SPM" directory to their equivalent subdirectories.

Updating an RLN OS/2 Client installation:

 Copy the files from the "OS2" directory to the directory where the RLN OS/2 
 client is installed.

Updating an RLNNASI client installation:

 Copy the files from the "RLNNASI" directory to the directory where the RLN 
 NASI client is installed.

=============================================================================
3) Obtaining compressed versions of the updated files

Compressed versions of appropriate files are provided in the a file called 
"RLN40U1C.EXE" on the BBS, FTP Server and WWW server.
These files can be copied into the "RLNFILES" subdirectory of the RLN Client 
Builder so disks built with the Client Builder will already have the updated 
files on them. Compressed versions of the files can also be copied to the 
Quick Install disks so any future installs done from those disks will already
have the updated files on them.

=============================================================================
4) Description of problems addressed in this update

Internal Reference Number: PDA 14928

Symptom Description:
When using RLN with Chameleon's Netmanage over NDIS, a successful connection 
could be made with RLN but ping would fail. In addition, bringing up RLNUSERW 
and looking at statistics while the TCP kernel (a DLL) was loaded would show 
invalid statistics. Closing RLNUSERW after the TCP kernel was loaded would 
cause a GPF. Other stacks that are implemented in a DLL could potentially 
have the same problem.

Solution:
RLNAPI.DLL v4.0.1 dated 8/18/95
RLNUI.DLL v4.0.1 dated 8/18/95

-----------------------------------------------------------------------------
Internal Reference Number: PDA 18763

Symptom Description:
Error 203 occurs when attempting to re-connect in Windows. Under certain 
circumstances, after connecting with RLN, doing some type of network access, 
disconnecting, then attempting to reconnect with RLN, error 203 occurs.

Solution:
RLNAPI.DLL v4.0.1 dated 8/18/95
RLNUI.DLL v4.0.1 dated 8/18/95

-----------------------------------------------------------------------------
Internal Reference Number: PDA 16032

Symptom Description:
Assigning a node address (in net.cfg) causes RLNUSER to hang when attempting 
to connect. Appears most often in a Token Ring configuration.

Solution:
RLNODI-T.COM v4.0.1 dated 7/21/95
RLNODI-E.COM v4.0.1 dated 7/21/95

-----------------------------------------------------------------------------
Internal Reference Number: PDA 18403

Symptom Description:
Error 202, Script time-out. No characters sent to the COM
port.

Solution:
RLNASYNC.EXE v4.0.2 dated 11/30/95

-----------------------------------------------------------------------------
Internal Reference Number: PDA 25605

Symptom Description:
Windows locks up when coming up while RLN is in memory.

Solution:
RLNASYNC.EXE v4.0.2 dated 11/30/95
RLNVXD.EXE v4.0.2 dated 11/26/95

-----------------------------------------------------------------------------
Internal Reference Number: PDA 19028

Symptom Description:
Using a Windows communications package causes a GPF in XFAXSPM.EXE.
With COM port sharing enabled, connecting with RLN, disconnecting, then 
attempting to connect with another Windows COM package will cause a Windows 
GPF in XFAXSPM.EXE usually at address 0004:00E2.

Solution:
XFAXSPM.EXE v4.0.1 dated 8/18/95
RLNVXD.EXE v4.0.2 dated 11/26/95

-----------------------------------------------------------------------------
Internal Reference Number: PDA 24868

Symptom Description:
DOS client - Lines scroll out of the TTY window. Once the number of lines 
displayed in the TTY window exceeds the height of the window, all previous 
lines get scrolled off the screen.

Solution:
RLNUSER.EXE v4.0.1 dated 10/11/95
RLNUSER.RES dated 10/11/95
RLNUSERW.EXE v4.0.1 dated 10/11/95

-----------------------------------------------------------------------------
Internal Reference Number: PDA 21535

Symptom Description:
Limit of 5 site definitions.

Solution:
RLNUSER.EXE v4.0.1 dated 10/11/95
RLNUSERW.EXE v4.0.1 dated 10/11/95

Note: The limit on sites is now 30.

-----------------------------------------------------------------------------
Internal Reference Number: PDA 30750

Symptom Description:
Intermittent file transfer failures. The transferring of certain (rare) 
files can fail for no apparent reason. Typically FCS errors will be logged on
the RLN Server and/or Client.

Solution:
RLN.EXE v4.0.1 dated 12/14/95
RLNOS2.EXE v4.0.1 dated 12/14/95

-----------------------------------------------------------------------------
Internal Reference Number: PDA 18171

Symptom Description:
Problems connecting to a BBS that uses 7 bit communications over RLNNASI. 
When attempting to connect to a BBS set for E71, the RLN NASI client was 
unable to set the RLN Server modem for E71.

Solution:
RLNNASI.EXE v4.0.1 dated 8/17/95

-----------------------------------------------------------------------------
Internal Reference Number: PDA 17586

Symptom Description:
Crosstalk version 2.3 doesn't find the RLN NASI Server.

Solution:
RLNNASI.EXE v4.0.1 dated 8/17/95

Note: An update to Crosstalk version 2.3.1 is also required.

-----------------------------------------------------------------------------
Internal Reference Number: PDA 14567

Symptom Description:
Users getting MAC address overwritten warning when dialing into a secondary 
server. When a primary server backs up the secondary server, the MAC 
address assigned to the user when validated by the secondary (secondary can't
validate from primary) is different than when validated by the primary.

Solution:
RLNSERV.EXE v4.0.1 dated 12/04/95

-----------------------------------------------------------------------------
Internal Reference Number: PDA 15668

Symptom Description:
Intermittent inability to connect to ports with leased line modems.
Can't re-negotiate PPP after an ungraceful disconnect. If an ungraceful 
disconnect occurs (rebooting PC without using RLNUser to disconnect), and 
the server modem forces Carrier Detect (leased line modems), you can't get 
back in on that port without bringing down the server and bringing it back 
up.

Solution:
RLNSERV.EXE v4.0.1 dated 12/04/95

-----------------------------------------------------------------------------
Internal Reference Number: PDA 18682

Symptom Description:
Intermittent inability to manager an RLN Server from the RLN Manager. When 
trying to manage the server from the RLN Manager, the Manager will send a 
SNMP request to the server and the server will respond with an ICMP port 
unreachable message.

Solution:
RLNSERV.EXE v4.0.1 dated 12/04/95

-----------------------------------------------------------------------------
Internal Reference Number: PDA 22412

Symptom Description:
X.25 ports drop out intermittently. After some period of time, PPP ports 
associated with X.25 ports will go into a state where users will connect to 
the RLN Server and get the login dialog box but will not be validated.

Solution:
RLNSERV.EXE v4.0.1 dated 12/04/95

-----------------------------------------------------------------------------
Internal Reference Number: PDA 24269

Symptom Description:
Users can't connect to the RLN Server on some ports. Under certain 
circumstances, if an inactivity timer is set on a port, it can time-out after 
a "disconnect without authentication" error message is logged for that port. 
This can create a state where users are unable to connect to that port.

Solution:
RLNSERV.EXE v4.0.1 dated 12/04/95

-----------------------------------------------------------------------------
Internal Reference Number: PDA 17126

Symptom Description:
Using a Macintosh ARA client, when performing data intensive operations such 
as downloading a large GIF file with a Web Browser (such as Netscape or 
Mosaic) the ARA client would disconnect.

Solution:
RLNSERV.EXE v4.0.1 dated 12/04/95

-----------------------------------------------------------------------------
Internal Reference Number: PDA 20946

Symptom Description:
Users get "MAC address overwritten" warning message after upgrading an RLN 
server from 3.x to 4.0. Deleted user records are purged during the upgrade 
process, which can result in assignments of new MAC addresses to users.

Solution:
DBCNVT.EXE dated 10/11/95

Note: See DBCNVT.TXT for documentation on how to use this utility.

