Contents of the R210FT.TXT file
NOVELL TECHNICAL INFORMATION DOCUMENT
TITLE: v2.1 NetWare Client for OS/2 Patches
DOCUMENT ID: TID021339
DOCUMENT REVISION: E
ALERT STATUS: Yellow
INFORMATION TYPE: Symptom Solution
README FOR: R210FT.EXE
NOVELL PRODUCT and VERSION:
NetWare Client for OS/2 2.10
All current patches for the v2.1 NetWare OS/2 Client Kit. These patches have
not been submitted to Novell system test.
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL
MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE
INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL
MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
NETX.EXE displays all drives that are not NetWare drives, as Local drives,
regardless of whether they are local or mapped by another requester ( IBM's
Netx.exe will not load when using a VMB (Virtual Boot Machine) if the Dos
version is greater than v6.00.
Apply NETX.EXE, 83869 bytes, 08-05-94.
Some DOS applications (ie Norton's SI.EXE) when executed so that output is
redirected to a file on the network would give garbage in the output file.
(ie. SI > F:\TEST.TXT)
Apply NETX.EXE, 83869 bytes, 6-10-94.
The DOS calls "FindFirstFile" and "FindNextFile" do not work properly in a
Private DOS session (VDM). The problem occurs when trying to do DOS find file
calls inside a loop of DOS find files when the files are on different drives
(one network, one local). The same program, modified for the same drive (both
network or both local), works correctly.
Apply NETX.EXE, 83885 bytes, 6-6-94.
Network drives cannot be accessed in Global VDMs after the workstation is RPL
Apply NWREQ.SYS, 31764 bytes, 7-21-94.
Error SYS1039 and SYS1040 would occur and connection would be lost with Packet
Burst enabled or if using large packet size (4202). This would occur when
using a remote link product ( Lan Distance from IBM) and the NetWare Client
Apply NWREQ.SYS, 31780 bytes, 7-01-94 and PBURST.EXE From NOVLIB/05 .
When logging into a server that is not a preferred server and then loading
NWTools, the workstation will be logged out of the server it was just logged
Apply NWREQ.SYS, 31780 bytes, 7-01-94
Customer running IBM Lan Requester v3.0 and NetWare Requester v2.10. Customer
captures or redirects LPT1 to a NetWare Queue and LPT2 to a Lan Server Queue.
Then Executes "ENDCAP /ALL". This produces the following Trap in NWREQ.SYS
TRAP D NWREQ:CGROUP: DHL_DecrementFlobalLocks:
ip=3730, cmp WORD ptr es:[01fe], +00 es=0 therefore Invalid.
Apply NWREQ.SYS, 31380 bytes, 5-26-94.
Receiving errors and a loss of connection when crossing a router when the
NetWare Client is using LIP and Packet Burst. After they boot up the OS/2
workstation and run login, the following errors occur during the login
"REQ1040: Requester timed out waiting for reply from server "
"SYS2070: A program in this session encountered a problem and cannot
(more info... The system could not demand load the application's segment.
Capture is in error. For additional details type HELP SYS59244559.)"
"LOGIN-4.07 760: The utility could not execute the program CAPTURE. The
program was not found."
Apply NWREQ.SYS, 31380 bytes, 5-26-94 and NWIFS.IFS, 40036 bytes, 5-26-94.
Applications that do file and record locking may appear to run slower than
The IFS was failing to reset a lock semiphore when it received a failed
condition on a file lock attempt.
Apply NWIFS.IFS, 40084 bytes, 08-31-94.
The NWIFS.IFS would match search queries even on files which do not contain
attributes required by the search. For instance, specifying
"directories-only" in the REXX function SysFileTree did not exclude ordinary
files from the list.
NWIFS.IFS would prematurely close file handles inherited by a child process
when the parent process exits. For instance, redirecting a child process's
output to a file and calling the 'C' function execv() would cause the child
process to get an invalid file handle error because the parent process had
Apply NWIFS.IFS, 40084 bytes, 6-17-94.
The first network drive (default L:) is not available until the PMSHELL.EXE is
NWDAEMON.EXE was changed to be a PM application and the first network drive
was not made available until PMSHELL.EXE loads.
Apply NWDAEMON.EXE, 36269 bytes, 5-26-94.
SPX applications would hang.
Previous revisions of SPX did not check for an illegal datastream type in an
ECB submitted to SendSequencedPacket(). SPX now returns the SPX_BAD_PACKET
error code in this situation.
SPX was sending duplicate data frames on wide area or slower networks, the SPX
parameter SEND TIMEOUT used in the NET.CFG did not function.
The SEND TIMEOUT parameter in NET.CFG now defaults to 500 milliseconds, with a
minimum of 100 msec and a maximum of 6000 msec. This is added to the round
trip time and averaged with the current retry delay if no timeout occurs.
When sending a retry, the current retry delay is increased by 50% for each
retry up to a maximum of 6 seconds. Send retries are now always dynamic.
Instead of returning an A400h error without aborting the connection, a send
timeout now returns A3EDh (connection aborted) and aborts the connection.
Apply SPX.SYS, 15540 bytes, 09-02-94.
VDMs on RPL (Remote Program Load) workstations will only show 588k bytes of
MINI.IFS was allocating real memory and not releasing it.
Apply MINI.IFS, 8673 bytes, 6-23-94. The MINI.IFS is used ONLY with Remote
Using CX before logging in will return the following errors:
SYS3175: A program generated an access violation at 0001:09f5 CX.EXE.
SYS1811: The process has stopped.
The software diagnostic code (trap number) is 000D.
Apply CX.EXE, 45408 bytes, 5-13-94.
WINOS2 SPX Database client application "Forest & Trees" would get sys3176
errors after multiple queries. NWIPXSPX.DLL was not freeing resources
properly. In WINOS2 session if an attempt was made to make an SPX connection
to a database server that was not available the WINOS2 session would hang.
Apply NWIPXSPX DLL, 38736 bytes, 6-21-94.
Version 3.77 of Syscon will generate a SYS1811: Trap 000d if you delete a
user ID that is logged in.
Apply SYSCON.EXE, 273468 bytes, 08-22-94.
1. Error "NWTOOLS-4.10-62 : The send command has failed" occurs if you try to
send a message to more that 64 users.
2. Nwtools will setup or capture ports LPT4-LPT9, but will not reload or
setup these ports when loading the *.NWS files.
Apply NWTOOLS.EXE 565909 bytes, 7-05-94.
LOGIN.EXE exhibited problems including files using the INCLUDE command.
LOGIN.EXE would execute some lines inconsistently. If the login script had a
variety of #CMD commands, along with INCLUDE's, etc. some lines would execute
normally, some would not.
LOGIN.EXE did not correctly pass login environment variables to spawned
processes. For example, if a CMD file was called from the login script, the
CMD file could not make use of variables that had been set in the login
Apply LOGIN.EXE 138784 bytes, 6-01-94 & LOGIN.MSG 12086 bytes, 4-13-94.
Versions of OS/2 NCOPY prior to this patch would cause extended attribute
corruption and also would fail to release resources back to the alloc short
term memory pool on v3.x NetWare servers.
Prior versions of DOS NCOPY would fail to process extended attribute
For OS/2 apply NCOPY.EXE 67008 bytes, 11-03-93.
For DOS apply NCOPY.EXE 249555 bytes, 10-28-93.
For both DOS & OS/2 use NCOPY.MSG (See installation instructons)
Error: CAPTURE-4.03-700: The mode, of device, , cannot be found
in the PRINTDEF database. Either specify a valid mode or create a new mode
with the specified name. This occurs when using an NDS queue object that is
set up to redirect a print job through the 4.x queue object to a 3.x print
server queue. To duplicate the error you need to define and use a Device and
Mode. This occured with capture.exe 5-05-94 that shipped with NetWare v4.02.
Apply CAPTURE.4X, 105149 bytes, 09-02-94 and CAPTURE.MSG, 30953 bytes,
05-05-94. (See Installation Instructions)
The included version of CAPTURE.3X addresses issues of running login.exe from
a CALL statement in the OS/2 config.sys and hanging if a #capture existed in
the OS/2 login script. This problem occurs with the CAPTURE.EXE that ships
with NetWare 3.1x, including CAPTURE.EXE v3.75, dated 5-20-93, that ships with
Apply CAPTURE.3X, 37103 bytes, 1-22-91. This version of capture should NOT be
used with 4.X NetWare. (See Installation Instructions)
Self-Extracting File Name: R210FT.EXE Revision: E
Files Included Size Date Time
R210FT.TXT (This File)
CX.EXE 45408 05-13-94 10:26a
SPX.SYS 15540 09-02-94 10:47a
MINI.IFS 8673 06-23-94 3:13p
NETX.EXE 83898 08-05-94 9:17a
LOGIN.EXE 138784 06-01-94 9:08a
LOGIN.MSG 12086 04-13-94 3:59p
NCOPY.DOS 249555 10-28-93 10:02a
NCOPY.MSG 7255 01-29-93 10:31a
NCOPY.OS2 67008 11-03-93 10:40a
NWIFS.IFS 40084 08-31-94 1:25p
NWREQ.SYS 31764 07-21-94 11:13a
CAPTURE.3X 37103 01-22-91 4:31p
CAPTURE.4X 105149 09-02-94 3:15p
SYSCON.EXE 273468 08-22-94 3:12p
CAPTURE.MSG 30953 05-05-94 4:28p
NWTOOLS.EXE 565909 07-05-94 2:45p
NWDAEMON.EXE 36269 05-26-94 3:10p
NWIPXSPX.DLL 38736 06-21-94 3:02p
* Create a directory called INSTALL$.NEW under \NETWARE. Copy all files into
\NETWARE\ INSTALL$.NEW and reboot.
* NWIPXSPX.DLL will need to be manually copied to C:\OS2\MDOS\WINOS2\SYSTEM.
* MINI.IFS should be manually copied to the SYS:RPL2 subdir on your NetWare
server if you are using Remote Program Load.
* If you are running on NetWare version 3.1x, make the following subdirectory
path and place NCOPY.MSG & LOGIN.MSG in it: SYS:PUBLIC\NLS\ENGLISH. Next copy
the new versions of ncopy into their respective areas as designated by the dot
extension on the file.
NCOPY.OS2 is renamed to NCOPY.EXE and copied to SYS:PUBLIC\OS2.
NCOPY.DOS is renamed to NCOPY.EXE and copied to SYS:PUBLIC.
Copy LOGIN.EXE to SYS:LOGIN\OS2 & SYS:PUBLIC\OS2 and to your local drive where
the requester is installed.
* CAPTURE.3X is renamed to CAPTURE.EXE and used only on NetWare v3.x servers.
Copy CAPTURE.EXE to SYS:PUBLIC\OS2.
* CAPTURE.4X is rename to CAPTURE.EXE and used only on NetWare v4.x servers.
Copy CAPTURE.EXE to SYS:PUBLIC\OS2. Copy CAPTURE.MSG to
* It is a good idea to make sure you have backups of all files being replaced.
Any trademarks referenced in this document are the property of their
respective owners. Consult your product manuals for complete trademark