home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 8 Other
/
08-Other.zip
/
os2c5.exe
/
OS2C5.TXT
< prev
next >
Wrap
Text File
|
1996-07-10
|
30KB
|
903 lines
NOVELL TECHNICAL INFORMATION DOCUMENT
TITLE: Patches for v2.11 NetWare Client for OS/2
README FOR: OS2C5.EXE
NOVELL PRODUCTS and VERSIONS:
NetWare Client for OS/2 2.11
ABSTRACT:
This file contains the latest field test patches for the v2.11 NetWare OS/2
Requester as of 7-9-96. These patches have not been submitted to Novell system
test. Applying these patches will get you to the current code base.
-----------------------------------------------------------------
DISCLAIMER
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.
-----------------------------------------------------------------
ISSUE:
SYMPTOM
If the Preferred Server is a v3.x server and NetWare 4.x
servers exist on the network the Requester would not
correctly clears the connection to the first attached DS server.
SOLUTION
Apply NWREQ.SYS, 32852 bytes 6-24-96
SYMPTOM
When making record locks, the requester was putting in a timeout value when it
should not. This caused some applications such as Timberline to run slower.
SOLUTION
Apply NWIFS.IFS, 41780 bytes 06/18/96
SYMPTOM
Also when an OS/2 application set file flags the Shareable flag
would always be set to non-Shareable when it should not be changed.
SOLUTION
Apply NWIFS.IFS, 41780 bytes, 6-04-96 or later
SYMPTOM
The requester had some NCP fields byte-swapped,
causing traps to occur and invalid requests to be made.
Revisions of the IFS prior to 2-21-96 and since 1-31-95 changed
FS_FINDFROMNAME so it would report all files expected from
DosFindFirst/DosFindNext. That change also fails to report the parent
directory ".." if FS_FINDFROMNAME is called with "." as the pName
parameter. The IFS now handles file/directory deletions correctly during
FS_FINDFROMNAME calls.
Could lose drive mappings if multiple OS2 windows map the same drive
differently.
SOLUTION
Apply NWREQ.SYS, 32852 bytes 5-17-96 or later.
Apply NWIFS.IFS, 41764 bytes 5-17-96.
SYMPTOM
Previous revisions of NWREQ would cause a system GP fault when attempting to
get the default connection which is an unattached preferred server connection.
Warp Connect can cause this when it asks NWIFS to find a remote named pipe.
SOLUTION
Apply NWREQ.SYS, 32852 bytes, 9-26-95 or later.
SYMPTOM
When using the Send.exe utility set to poll for messages, (send /a=p) if
NWGetBroadcastMessage is called nothing is returned. NWDaemon.exe was
disposing of messages before they could be polled.
SOLUTION
Apply NWREQ.SYS, 32852 bytes, 8-14-95 or later.
Apply NWDAEMON.EXE, 36281 bytes, 8-14-95 or later.
SYMPTOM
Unable to browse files when using certain applications.
CAUSE
Revisions of the IFS since 1-31-95 changed FS_FINDFROMNAME so it would report
all files expected from DosFindFirst/DosFindNext. That change also fails to
report the parent directory ".." if FS_FINDFROMNAME is called with "." as the
pName parameter. This revision of the IFS corrects this problem.
SOLUTION
Apply NWIFS.IFS, 41700 bytes, 1-17-96 or later.
SYMPTOM
Alloc Short Memory on the NetWare server climbs rapidly, consumes all
available short term memory resources and abends. This symptom was seen
primarily on OS/2 application servers.
CAUSE
NWIFS.IFS was allocating extended attribute handles and not releasing them
depending on the circumstances envolved.
SOLUTION
Apply NWIFS.IFS, 41556 bytes, 6-15-95 or later.
SYMPTOM
When NVER.EXE is run it improperly identifies the v2.11 NetWare Requester as
v2.10.
SOLUTION
Apply NWREQ.SYS, 32804 bytes, 6-15-95 or later.
Apply NWIFS.IFS, 41556 bytes, 6-15-95 or later.
Apply NWDAEMON.EXE, 36267 bytes, 6-15-95 or later.
SYMPTOM
Loss of connection occurs when COPY/XCOPY files accross FRAME
RELAY on WAN with OS/2 and NetWare Requester v2.11.
CAUSE
If a 4.10 server receives a packet burst write and does not receive all of
the
fragments it will no longer respond with a missing fragment list request, this
will cause the OS/2 requester to time out and resend the entire packet. The
requester instead will send a system packet to request a missing fragment
list.
SOLUTION
Aplly NWREQ.SYS, 32804 bytes, 6-15-95 or later.
SYMPTOM
IBM is changing the way it tests for long name support on a network drive.
The current implementation in the IFS will fail. The IFS now returns
ERROR_FILENAME_EXCED_RANGE if a long filename open is attempted on a network
drive without the OS/2 namespace (OS2.NAM) loaded.
SOLUTION
Apply NWIFS.IFS, 41604 bytes, 8-14-95 or later.
SYMPTOM
Drag & drop copies in the Drives Icon View would randomly fail.
CAUSE
When a application (WP Shell) would attempt to change the creation date for
the target directory being copied, the IFS was not setting the last update for
date and time, the file server would return an error.
SOLUTION
Apply NWIFS.IFS, 41508 bytes, 5-11-95 or later.
SYMPTOM
When the NetWare console BROADCAST cammand or the command line utility
SEND.EXE is used in an RPL environment excessive broadcast traffic is created.
The first connection that each workstation makes for it's C: drive on the
server tries but can't respond to the broadcast. This results in repeated
retries by the server and diminished bandwidth.
SOLUTION
Apply NWREQ.SYS, 31940 bytes, 3-06-95 or later.
Apply NWIFS.IFS, 41476 bytes, 3-06-95 or later.
Apply NWDAEMON.EXE, 36277 bytes, 3-06-95 or later.
SYMPTOM
The Requester would randomly fail when mapping drives to NFS mounted volumes.
CAUSE
The Requester is coded to only handle volume numbers 0 - 32. Most NFS
mounted
volume numbers are > 32. This has been fixed, how ever, the included patch
will only support the DOS name space on volume numbers greater than 32. This
will be re-engineered to support the OS/2 name space in a future release of
the
Requester.
SOLUTION
Apply NWIFS.IFS, 41428 bytes, 3-1-95 or later.
SYMPTOM
Previous revisions of the IFS cause a system GP fault if DosBufReset() is
called with a remote named pipe handle.
SOLUTION
Apply, NWIFS.IFS, 41428 bytes, 2-27-95 or later.
SYMPTOM
When a OS/2 application creates a file on a network volume the Requester will
assign the shared attribute to the newly created file. This should not occur.
SOLUTION
Apply NWIFS.IFS, 41412 bytes, 2-10-95 or later.
SYMPTOM
When using Dos Login in a Global VDM the following errors could be returned:
Shell-332-69: Shell is not attached to a Server Shell-332-70: Requested Server
is not availabel Progbram aborted
SOLUTION
Apply NWREQ.SYS, 32772 bytes, 5-03-95 or later. Login.exe and Logout.exe
from NetWare 4.10 must be used along with this new NWREQ.SYS.
SYMPTOM
Saving a file while using IBM Works generates a Trap 00D.
SYMPTOM
If your network connection is lost prior to OS/2 Shutdown, Shutdown will take
3 plus minutes to complete. This is usually only manifests itself while using
remote connectivity products. IBM APAR PJ16957 is needed along with the
following files for the NetWare Requester.
SOLUTION
Apply NWREQ.SYS, 31876 bytes, 2-10-95 or later.
Apply NWIFS.IFS, 41412 bytes, 2-10-95 or later.
Apply NWWORKER.DLL, 114710 bytes, 2-10-95.
SYMPTOM
Poor performance when loading DOS/Windows applications from NetWare server.
CAUSE
In a VDM with NETWARE_RESOURCES set to NONE, reads & writes
will be burst to & from the NetWare server. If a file handle was lost during
bursting, the retry & security (signature) mechanisms exhibited problems
causing a slow down.
When loading applications, in a dual requesting environment, seamlessly from
the desktop on OS/2 v2.11, a 10-15 second delay when launching the application
will occur, this is caused by a flood of Netbeui resolve name packets. Also,
WIN/OS2 was making small 8 byte read requests, dual requesting doesn't apply
here. These are resolved by applying service pack XR_A080 from IBM.
SOLUTION
Apply NWREQ.SYS, 31780 bytes, 1-13-95 or later, and or IBM's service pack.
SYMPTOM
The commit NCP 59 was not being properly handled by the Requester. When a
DosBufReset() call was made from the application the info was not being fully
committed to disk at the file server.
SOLUTION
Apply NWIFS.IFS, 41220 bytes, 1-5-95 or later.
SYMPTOM
Cannot disable all (error) messages from appearing on workstation.
SOLUTION
Apply NWDAEMON.EXE, 36267 bytes, 12-19-94. Once installed edit the NetWare
section of your config.sys as follows:
C:\NETWARE\NWDAEMON.EXE NOMESSAGES
The NOMESSAGES parameter must be upper case and one continous
string. Using this option eliminates the need to use the Display Hard Errors
Off parameter in the NetWare Requester section of the NET.CFG.
SYMPTOM
Previous revisions of IPX don't learn their local network number(s) when
performing a GetLocalTarget for all networks. This was added so NPDAEMON could
learn it's local network number(s).
Revisions of IPX since 11-09-95 have code which allows the LSL to reclaim
buffers from VIPX when necessary. High volumes of broadcast traffic directed
at VIPX were causing problems.
SOLUTION
Apply IPX.SYS, 10292 bytes, 1-19-96.
SYMPTOM
The IPX router was causing broadcast storms by routing various types of
multicast\functional addresses back onto the same net. The IPX router has been
fixed to prevent routing of receive packets between adapters or onto the same
adatper.
SOLUTION
Apply IPX.SYS, 10292 bytes, 8-08-95 or later.
SYMPTOM
Previous revisions of IPX would generate a RIP broadcast from a call to
IpxGetLocalTarget even if the target was on the primary board. This revision
is better able to find it's local net address at boot time.
SYMPTOM
Sometimes when using IBM's ODI2NDI solution, the NetWare Requester was unable
to establish a connection causing a REQ 0815 error to occur.
CAUSE
When IPX loads it attempts to discover the network using a RIP packet, this
attempt never reaches the network because NETBIND.EXE has not yet run. IPX
would then attempt to discover the network by examining broadcast packets on
the network and sometimes finding invalid network addresses resulting in a REQ
0815 error.
SYMPTOM
Previous revisions of IPX supported only 128 sockets. This limit has been
increased to 256 sockets.
SOLUTION
Apply IPX.SYS, 10292 bytes, 5-15-95 or later.
SYMPTOM
The Requester contains a routing table that was failing to initialize
correctly. This caused IPX to do a RIP request on it's own local network to
get a network address that it already knows about. This has been fixed.
SOLUTION
Apply IPX.SYS, 10292 bytes, 2-13-95 or later.
SYMPTOM
Revisions of SPX since 2-21-95 use long-term locks instead of short-term
segment locks. 32-bit programs with SPX data in large stacks can cause
DevHlp_VMLock to fail. Short-term locks are used if long-term locks fail.
Revisions of SPX prior to 3-27-96 did not validate packet sizes when
sending sequenced packets. This could cause system GP faults or data
corruption. ECBs are now checked for this when given to SPX.
SOLUTION
Apply SPX .SYS, 15748 bytes, 5-09-96.
SYMPTOM
Lotus Notes servers using SPX would
randomly hang or Trap in Linksup$.
CAUSE
It is believed that this was caused by
Windows 95 boxes using NWLINK (IPX/SPX).
NWLINK was setting the acknowledge bit
on a terminate connection ack that was
initiated by the Notes server. It is
not proper to request an ack on a ack.
SOLUTION
Apply SPX.SYS, 15,684 bytes, 2-14-96 or later.
SYMPTOM
Previous revisions of SPX did not detect locked segments which grow and then
get used in subsequent calls. SPX still cannot handle this situation, but it
no longer causes a system GP fault.
SYMPTOM
Previous revisions of SPX allowed network buffers to be locked above 16
megabytes, which could cause problems with other protocols and certain network
drivers.
Revisions of SPX prior to 9-29-95 could potentially cause a system GP fault
when retransmitting a packet.
SOLUTION
Apply SPX.SYS, 15668 bytes, 12-18-95 or later.
SYMPTOM
Previous revisions of SPX did not allow 32-bit values to be specified for
abort, listen, and verify timeouts.
SOLUTION
Apply SPX.SYS, 15668 bytes, 2-21-95 or later.
SYMPTOM
Previous revisions of TLI_SPX could cause a GP fault when sending
data under a heavy load. The packet data area wasn't referred to
properly in these cases.
SOLUTION
Apply TLI_SPX .SYS , 55859 bytes, 4-02-96.
SYMPTOM
TLI does not support SPX Packets greater than 576 bytes. When OS/2 TLI
receives such a packet, it looks like the session gets blown away. OS/2 TLI
stops sending Keep-Alives and the session times out.
SOLUTION
Apply TLI_SPX.DLL, 55859 bytes, 12-14-95 or later.
SYMPTOM
Applications written for TLI could run into situations in high-stress
environments where they would trap in DOSCALL1 or TLI_SPX. While this
situation was rare, high stress environments could cause it.
SOLUTION
Apply TLI_SPX.DLL, 55351 bytes, 6-12-95 or later.
SYMPTOM
Possible deadlock situations could occur causing TLI SPX applications and/or
the PC to hang. TLI entered into a DOS critical section and never came back.
SOLUTION
Apply TLI.DLL, 20931 bytes, 4-13-95.
SYMPTOM
When simultaneously opening several VDMs, conflicts between VDMs can arrise
as
they attempt to open and read NET.CFG at the same time. Renaming a file that
does not exist using INT21 Function 56H on a network in a Dos session with
Netx.exe loaded would return 05H (Access Denied) instead of 02H (File not
found). Netx.exe hads been fixed to return 02H.
SOLUTION
Apply NETX.EXE, 85215 bytes, 7-21-95.
Apply TBMI2.COM, 24991 bytes, 3-13-95.
SYMPTOM
When a VDM (DOS Window) was opened on OS/2 RPL workstations,
NETX.EXE would do a reset on all floppy drives, this resulted in the floppy
drive lights turning on and or hanging the PC if OS/2 happen to be formatting
a
floppy disk at the time this occured. This reset code was implemented for DOS
RPL workstations. The reset code has been removed.
SOLUTION
Apply NETX.EXE, 85213 bytes, 3-2-95 or later.
SYMPTOM
Previous revisions of VIPX could consume all available LSL buffers and
keep them for an unbounded length of time. Inbound packets are now
discarded when a certain threshhold of inbound packets are
pending inside VIPX.
SOLUTION
VIPX.SYS , 53248 bytes05-30-96
Note: Apply DOSVIPX.SYS, 10560 bytes, 5-30-96 when VMBooting a read DOS
kernel.
SYMPTOM
Previous revisions of VIPX used an incorrect method of determining when an
SL-enhanced 486 (and all Pentiums) had enabled interrupts in a VDM. VIPX
would believe the VDM's interrupts were disabled and indefinitely postpone
calling ESRs, causing OS/2 to hang.
SOLUTION
Apply VIPX.SYS, 53248 bytes, 5-17-96 or later.
Note: Apply DOSVIPX .SYS, 10560 bytes, 5-17-96 or later when VMBooting a
real DOS
kernel.
SYMPTOM
Previous revisions of VIPX could cause a system GP fault if the number of
available system GDTs was exhausted. VIPX does not reliably support more
than 12 DOS sessions which use VIPX. This revision of VIPX includes code
which allows the LSL to reclaim its buffers if they are needed elsewhere.
SOLUTION
Apply VIPX.SYS, 53248 bytes, 1-19-96 or later.
Note: Apply DOSVIPX.SYS, 10560 bytes, 1-19-96 or later when VMBooting a real
DOS
kernel..
SYMPTOM
Abnormal termination of applications running in VDMs (DOS/WINOS2 Sessions.)
SYS3170: A program in this session encountered a problem and cannot continue.
SYS3176: A program in this session encountered a problem and cannot continue.
CAUSE
The previous versions of VIPX.SYS released for the v2.11 NetWare
Requester were fixed to work around problems envolving VME or Virtual Mode
Extentions in Intel Pentium & SL-Enhanced processors. These fixes proved
unsuccessful and have been removed. If you have one of the previously
mentioned processors and are experiencing DOS application problems you should
take one of the following courses of action:
SOLUTION
1) If you are running v3.0 (Warp) of OS/2 add VME=NO as the first line of
your
config.sys file.
Apply VIPX.SYS, 53248 bytes, 3-17-95 or later.
2) If you are running v2.11 OS/2 (XR06200) apply IBM Fix Pack XR_A092 (or
later) as per IBM APAR PJ14831. Add VME=NO to the first line of your
config.sys file.
Apply VIPX.SYS, 53248 bytes, 3-17-95 or later.
Note: Apply DOSVIPX.SYS, 10560 bytes, 3-17-95 or later, when VMBooting a real
DOS
kernel.
SYMPTOM
Under certain circumstances, if VSHELL.SYS failed when creating a connection
it would terminate the primary connection.
SYMPTOM
The previous version of VSHELL.SYS dated 12-20-94 caused DOS/Windows
applications running simultaneously to run slow. The 12-20-94 version of
VSHELL.SYS SHOULD NOT be used.
SOLUTION
Apply VSHELL.SYS, 36864 bytes, 1-18-95.
SYMPTOM
When logging into a NetWare server the first network drive could not be
mapped
when DEFAULT LOGIN DRIVE was used in the NET.CFG. A MAP DEL F: before mapping
F would work around this problem, assuming F is the default login drive.
The following error msg occurs when trying to remap the login drive:
LOGIN 4.12-890 The specified server is unknown.
NWTOOLS does not display the login drive letter as available. Login from a
script file (login /s) returns the same error msg.
SOLUTION
Apply NWCALLS.DLL, 111764 bytes, 3-14-95.
SYMPTOM
Connection wrap around problems in Windows (Groupwise connetions above 255 in
WinOS2 session)
SOLUTION
Apply NETWARE.DRV, 126432 bytes, 11-27-95.
SYMPTOM
In a WinOS2 session connection to a remote Post office on a Netware
Server
fails using Microsoft Mail.
SOLUTION
Apply NETWARE.DRV, 126384 bytes, 8-23-95 or later.
SYMPTOM
Previous revisions of INSTALL.EXE did not expect to have invalid
string values in non English versions of INSTALL.DLL. This caused
a SYS3175 GP fault when running VLMBOOT setup.
SOLUTION
Apply INSTALL.EXE, 185824 bytes, 06-12-96
SYMPTOM
Install.exe could not correctly identify different versions of OS/2, 3.x vs
2.x, full pack vs OS/2 for Windows etc. This will specifically resolve issues
involving a RIPL'd environment including the Launch Pad in v3.x and whether
Windows software in found in C:\WINDOWS or C:\OS2\MDOS\WINOS2.
SOLUTION
Apply INSTALL.EXE, 186032 bytes, 12-23-94 or later.
SYMPTOM
If a workstation has DIRECTORY SERVICES OFF, and logs into a server other
than the preferred server, and then NetWare Tools is loaded, the current
connection is terminated. If you log into your preferred server this loss of
connection does not occur.
CAUSE
Previous revisions of NWTOOLS used NWNET.NWGetPreferredDSServer(), which will
logout of all servers if there were no Directory Services connections and no
connection to the preferred server. NWGetPreferredDSServer() is called when
NWTOOLS is loaded. As a workaround, NWGetPreferredDSServer() has been fixed
and linked directly into NWTOOLS.EXE.
SOLUTION
Apply NWTOOLS.EXE, 174160 bytes, 6-30-95.
SYMPTOM
Revisions of NMPIPE prior to 12-19-94 did not lock read buffers in memory.
If
a read buffer was swapped to disk while waiting for a DosRead to complete, the
data would be written somewhere else.
SYMPTOM
Previous revisions of NMPIPE did not translate compatibility sharing mode
(from VDMs) to deny-none sharing mode.
SYMPTOM
Named Pipes communication in a VDM would fail shortly after a DOS open was
communicated to the Named Pipe server.
SOLUTION
Apply NMPIPE.SYS, 24344 bytes, 1-09-95.
SYMPTOM
Previous revisions of NPDAEMON didn't track available service threads
correctly. This could cause hangs or resource leaks. Also, we delay
replies by 55 msec to DosPeekNmPipe() requests to open pipes with no data.
SOLUTION
Apply NPDAEMON.EXE, 19378 bytes, 5-22-96.
SYMPTOM
Previous revisions of NPDAEMON assumed that IPX would know it's network
number when NPDAEMON is started. If the IPX network number is not
initialized,
NPDAEMON performs an IpxGetLocalTarget() for all networks and then gets an
updated table copied from IPX. There is an updated IPX which learns it's
network number(s) when performing a GetLocalTarget for all networks.
SOLUTION
Apply NPDAEMON.EXE, 19374 bytes, 12-11-95 or later.
Apply IPX.SYS, 10292 bytes, 1-19-95 or later.
SYMPTOM
Previous revisions of NPDAEMON contained a memory leak which would eventually
consume all available swap memory. The affected memory is now recycled to
limit the amount of memory consumed.
SOLUTION
Apply NPDAEMON.EXE, 18852 bytes, 4-5-95 or later.
SYMPTOM
Revisions of OS2 NetBIOS since 1-23-95 created a problem with the session
watchdog. It was related to verify and listen timeout NET.CFG parameters, and
is now fixed.
Revisions of OS2 NetBIOS prior to 10-27-95 did not update the internal
Datagram Net Cache when relevant NetBIOS traffic arrived. Now they do so that
a change in routers will be detected.
Previous revisions of OS2 NetBIOS returned an error 5h (command timed out) if
a hangup request times out (the smaller of 20 seconds and NCB_STO). If no
other requests are pending, the session is not completely destroyed until
another request is made which involves that session. NetBIOS now returns an
error 18h (session ended abnormally) in this situation. Both errors are legal
reports of the situation, but the changed method is easier for applications to
cope with.
SOLUTION
Apply NETBIOS.SYS, 20260 bytes, 12-20-95.
SYMPTOM
Revisions of NetBIOS starting with v2.11 aborted sessions and names when apps
using NETAPI/NETSUB exited. This included apps which performed a
spawn-with-overlay. The LM10 interface is not affected by this change.
SOLUTION
Apply NETBIOS .SYS, 20196 bytes, 3-06-95 or later.
SYMPTOM
Previous revisions of NetBIOS did not properly handle synchronous requests
generated by IBM's LAPS product which virtualizes multiple VDM sessions.
Closing VDMs with NetBIOS activity from the task list would cause unexpected
behavior in other NetBIOS VDMs.
SOLUTION
Apply NETBIOS.SYS, 20196 bytes, 1-20-95 or later.
SYMPTOM
Excess NetBIOS system traffic on network. The parameters VERIFY TIMEOUT and
LISTEN TIMEOUT now allow full 32-bit values to be specified. Previously, they
were stored as 16-bit values. ABORT TIMEOUT has always been a 32-bit value.
This increases the upper limit for these parameters considerably. It is not
advised to use the possible maximum of 4000000000 as this roughly equates to
46
days.
SYMPTOM
NetBIOS did not return adapter reset values properly with the LM10 interface
used by IBM LAN Server. NetBIOS now returns the minimum of the requested
values versus the values in NET.CFG for sessions, commands, and names.
SOLUTION
Apply NETBIOS.SYS, 20180 bytes, 1-23-95 or later.
SYMPTOM
ROUTE.SYS that shipped with the v2.11 Requester was not routing
TOKEN-RING_SNAP frames correctly causing TCP/IP protocols to fail
in source routed environments.
SYMPTOM
Source Routing load balancing was not taking place properly on a large fault
tolerant Source Routed network. ROUTE.SYS file now updates its table entries
on receives only if the destination node address in the MAC header is not
"FFFFFFFFFFFF." Extra transmit retry code was added to retry a route that has
timed out for a maximum of 2 times before sending a SR broadcast frame to
discover a new route. The number of extra transmit retries can be specified
by
a new 'XTX' parameter in the PROTOCOL ROUTE section of NET.CFG, how ever
caution should be used when tweaking this parameter. The default value for
XTX
is 2, range is 0 to 6. We also changed RxHandler to always reject broadcast
frames (MAC desttination address) for route info. This protects routes
which have timed out and are ready to be replaced from getting slow routes.
PROTOCOL ROUTE
SOURCE ROUTE XTX 2
SOLUTION
Apply ROUTE.SYS, 47504 bytes, 2-15-95.
SYMPTOM
Using login.exe to login from config.sys causes OS/2 v3.x machines to hang.
SOLUTION
Apply NWSTART.EXE, 8227 bytes, 12-6-94 in the following fashion:
CALL=C:\NETWARE\NWSTART.EXE
CALL=C:\NETWARE\LOGIN.EXE
SYMPTOM
Corrections were made so that large (greater than 64k in size) LAN drivers
could be remote loaded during the RPL process.
SOLUTION
Apply MINI.IFS, 8753 bytes, 12-21-94.
SYMPTOM
Revisions of DOSNP since 3-15-94 have included a feature which
causes named pipes requests to time out if they take longer than
960 ticks (52.7 seconds). This allows client software to recover
from named pipe server malfunctions. The default action now is to
never time out requests in this manner. A new NET.CFG parameter
"NP TIMEOUT" allows users to configure the number of ticks
(18.2/sec) for this timeout.
SOLUTION
Apply DOSNP.EXE, 10757 bytes 12-01-95
SYMPTOM
LOGIN.EXE didn't parse login scripts correctly when using "IF MEMBER
OF "GROUP1" THEN BEGIN" when the groups names only differed by
the last character.
SOLUTION
Apply NWNET.DLL, 202960 bytes 6-06-96
Apply LOGIN.EXE 128704 6-22-95 & LOGIN.MSG 11333 9-22-94.
LOGIN.EXE can be obtained from OS2Ux.EXE. LOGIN.MSG ships with NetWare v4.1.
Self-Extracting File Name: os2c5.exe
Files Included Size Date Time
..\
OS2C5.TXT (This file)
DOSNP.EXE 10757 12-1-95 10:26:18 pm
DOSVIPX.SYS 10560 5-30-96 9:50:54 pm
INSTALL.EXE 185824 6-12-96 9:16:36 pm
IPX.SYS 10292 1-19-96 4:36:54 pm
MINI.IFS 8753 12-21-94 4:15:56 pm
NETBIOS.SYS 20260 12-20-95 6:21:28 pm
NETWARE.DRV 126432 11-27-95 7:05:56 pm
NETX.EXE 85215 7-21-95 10:23:02 pm
NMPIPE.SYS 24344 1-9-95 5:15:48 pm
NPDAEMON.EXE 19378 5-22-96 11:15:00 pm
NWCALLS.DLL 111764 3-14-95 6:58:52 pm
NWDAEMON.EXE 36281 8-14-95 2:30:12 pm
NWIFS.IFS 41780 6-18-96 10:04:50 pm
NWNET.DLL 202960 6-6-96 9:30:20 pm
NWREQ.SYS 32852 6-24-96 7:26:48 pm
NWSTART.EXE 8227 12-6-94 8:02:00 pm
NWTOOLS.EXE 174160 6-30-95 7:44:40 pm
NWWORKER.DLL 114710 2-10-95 4:24:24 pm
ROUTE.SYS 47504 2-15-95 8:20:56 pm
SPX.SYS 15748 5-9-96 9:21:18 pm
TBMI2.COM 24991 3-13-95 4:48:34 pm
TLI.DLL 20931 4-13-95 10:35:10 pm
TLI_SPX.DLL 55859 4-2-96 5:50:38 pm
VIPX.SYS 53248 5-30-96 9:50:30 pm
VSHELL.SYS 36864 1-18-95 2:25:12 pm
Installation Instructions:
* Create a directory called INSTALL$.NEW under \NETWARE. Copy all files into
\NETWARE\INSTALL$.NEW and reboot. During boot up, all files in the
INSTALL$.NEW directory will be moved automatically to the \NETWARE directory.
Existing files in the \NETWARE directory will be overwritten, and the
INSTALL$.NEW directory will be removed.
* NETWARE.DRV should be manually copied to os2\mdos\winos2\system
subdirectory. If you have installed VLM Boot and you have a \NETWARE\NETXDLL
subdirectory, copy NETWARE.DRV to the NETXDLL subdirectory instead of
os2\mdos\winos2\system.
* TBMI2.COM should be manually copied to \os2\mdos\winos2\system
subdirectory.
* MINI.IFS should be manually copied to the SYS:RPL2 subdir on your NetWare
server if you are using Remote Program Load.
** 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
information.
-----------------------------------------------------------------