home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
os2pt2.exe
/
OS2PT2.TXT
< prev
next >
Wrap
Text File
|
1998-12-18
|
13KB
|
294 lines
NOVELL TECHNICAL INFORMATION DOCUMENT
TITLE: OS2PT2.EXE; Client v2.12 for OS/2 Patch
TID #: 2946186
README FOR: OS2PT2.EXE
SUPERSEDES:
OS2212I2.EXE
OS2IPX.EXE
os2pt1.exe
NOVELL PRODUCTS and VERSIONS:
OS/2-NW312
NetWare Client for OS/2 2.12
Requester OS/2 2.12
ABSTRACT:
This file contains the latest patches for the NetWare Client v2.12 for OS/2
(NetWare Requester for OS/2).
The 32bit libraries from SDK13 are also included.
-----------------------------------------------------------------
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO
NOVELL. NOVELL MAKES ALL REASONABLE EFFORTS 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.
-----------------------------------------------------------------
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.
Specific instructions for NWIPXSPX.DLL and TBMI2.COM:
1. Exit WinOS2 (Optional, but recommended)
2. Replace the NWIPXSPX.DLL and TBMI2.EXE file in the directory where the
Windows NetWare drivers are located (typically WINDOWS\SYSTEM or
\OS2\MDOS\WINOS2\SYSTEM).
3. Restart Windows.
Specific instructions for INSTALL.DOC:
1. Rename \NETWARE\NLS\ENGLISH\INSTALL.DOC
2. Copy the new INSTALL.DOC to \NETWARE\NLS\ENGLISH
* It is a good idea to make sure you have backups of all files being
replaced.
ISSUE:
Symptom:
Previous revisions of VIPX used a different method of determining when
an SL-enhanced 486 (and all Pentiums) had enabled interrupts in a
VDM. It was possible for a Dos or Windows application to hang OS2
because VIPX believed the VDM's interrupts were disabled when in fact they were
not. This was most often reported with (Excel) but possible with any Dos/Win
application.
Solution:
Apply VIPX.SYS and DOSVIPX.SYS dated 6-05-97 or later.
Symptom:
Revisions prior to 7-30-97 of the v2.12 IFS could halt OS2 when reading
corrupt extended attributes.
Revisions prior to 1-29-97 of the requester did not support long UNC
filenames for volumes whose server-assigned volume number was
greater than 31.
Revisions of the v2.12 IFS prior to 1-27-97 did not spool captured
print data correctly, causing kernel traps.
Revisions prior to 11-08-96 could cause preformance problems with "True
Commit". The Requester for NetWare has been fixed to commit files
to disk on the NetWare server when OS/2 requests it to do so. This can
manifest itself in slower performance depending on the circumstances.
The new NET.CFG setting as follows:
Netware Requester
True Commit 0 (0 = Off / 1 = On)
Revisons prior to 12-10-96 had problems when attempting to do a directory on a
NetWare server using UNC syntax, the user would get the following error:
SYS0003: The system cannot find the path specified.
Solution:
Apply NWIFS.IFS dated 12-10-96 or later.
Apply NWREQOS2.MSG dated 12-05-96 or later.
Symptom:
Revisions of NWREQ prior to 12-05-97 assumed that Large Internet Packets
would be delivered across routers and renegotiate a packet size if an NCP
request timed out. There is now a new NET.CFG option for the Netware
Requester section: "Large Internet Packets Negotiated". This option
causes NWREQ to "renegotiate" LIP by pinging the server after a LIP size
is agreed upon by NWREQ and the server.
Example:
NetWare Requester
Large Internet Packets Negotiated
The "Large Internet Packets" parameter can take three values: 'On', 'Off', and
'Negotiated'. They are mutually exclusive, and only one value will be used.
Whichever is specified last will be used.
Revisions of NWREQ prior to 11-24-97 would cause data corruption in two
situations with packet burst enabled. First, any burst read from the
server with overlapping data would cause data corruption. Second, if a
burst written to a server times out, but receives a successful status
after a PBurst system packet, data corruption would occur.
Revisions prior to 2-13-97 had problems when NWStop is typed the
OS/2 client continues to RIP the network and create a service connection to
anything that responds. This manifests itself in Not-Logged-In connections on
the server. One workstation can eat up all the connections on a v3.x server.
Previous revisions of NWREQ did not handle hard errors correctly. No
abort/retry/fail message was presented to the user when hard errors
occurred.
Solution:
Apply NWREQ.SYS, dated 12-18-97 or later.
Symptom:
Revisions or SPX prior to 10-27-97 left parts of SPXListenForDisconnect
unimplemented. This API was added to support NWSIPX32.DLL.
Revisions of SPX prior to 8-22-97 had a timing problem when a watchdog
event occurs while another daemon thread is aborting a connection.
Revisions of SPX prior to 6-26-97 had an incomplete method for verifying
access to memory specified by SPX applications.
Revisions of SPX (in the 2.12 requester) prior to 3-04-97 had session
table pages where table entries overlapped a control structure. This
could cause system GP faults and other undefined behaviors.
Previous revisions of SPX did not return LSL buffers when hangup
ACK packets arrive whose connection is no longer valid. This would
eventually cause the entire ODI system to stop functioning.
Revisions of SPX prior to 1-29-97 did not return LSL buffers when hangup
ACK packets arrive whose connection is no longer valid. This would
eventually cause the entire ODI system to stop functioning.
Note: OS2IT1.EXE, a previous patch file, shipped with the incorrect version of
SPX.SYS dated 2-04-97.
Solution:
Apply SPX .SYS, dated 10-27-97 or later.
Symptom:
Revisions prior to 12-18-97 of TLI_SPX did not have a thread-safe
implementation of t_sndudata(). The immediate address of sent IPX packets
could be wrong.
Revisions of TLI_SPX prior to 4-02-97 limited sent packet lengths to 576
bytes. Packet lengths are now increased to the LAN driver's maximum
packet length.
Prior revisions of TLI_SPX always responded to connection requests
with the SPXII bit (0x08) set in the connection control field. This
caused Microsoft's implementation(s) to hang.
Prior revisions of TLI_SPX ignored changes to the spxIIMinimumRetryDelay
configuration parameter.
Revisions prior to 12-11-96 had an issue with IBM's DB2.
IBM's DB2 works fine except when the client accessing it is a Win95 machine.
If that is the case, during a large query, after the OS/2 box transmits 32k
of data the connection will hang and will get a SYS3175 error in TLI_SPX.DLL at
1:a4a6. This causes the client to lose connection to the server and sometimes
causes the DB2 database to crash and can corrupt the data.
Solution:
Apply TLI_SPX.DLL, dated 12-18-97 or later.
Symptom:
Revisions of IPX prior to 12-05-97 did not deliver IPX SAP packets to VDMs
using VIPX if any OS2 applications had the SAP (452h) socket open.
Revisions of SPX prior to 1-29-97 did not return LSL buffers when hangup
ACK packets arrive whose connection is no longer valid. This would
eventually cause the entire ODI system to stop functioning.
Solution:
Apply IPX.SYS ,dated 12-05-97 or later.
Symptom:
One of the menus of the NetWare Requester install program documented and
allowed editing of the OS/2 NET.CFG. Parameters that were incorrect or not
documented at all have been included or fixed.
Solution:
Apply INSTALL.DOC dated 5-20-97 or later.
Symptom:
If you try the OS/2 help on a NetWare Requester error no help will be found.
(IE "HELP REQ0815")
Help files for the OS/2 Requester are included with this patch kit.
Solution:
Apply REQ.MSG and REQH.MSG dated 8-27-97 or later.
Symptom:
Revisions of NWWORKER prior to 10-23-97 used NWParsePath() in NWCALLS.DLL to
split the \\SERVER\PRINTQUEUENAME given to NWWORKER, and a 16-character limit
is now imposed on what appears to be a volume name in pathnames given to
NWParsePath(). A lower-level call in NWCALLS.DLL is now used to get around
this limitation.
Revisions of NWWORKER prior to 10-06-98 returned an error "SYS0059 an unknown
network error has occurred" when using the Network Folder to view the objects
in the network if the user does not have rights to the print queue. See TID
2939742.
Solution:
Apply NWWORKER.DLL dated 10-06-98 or later.
Symptom:
Revisions of NWIPXSPX prior to 7-25-97 strictly limited the packet size
requested from standard mode by IPXInitialize() and friends to the value
returned by IPX. A somewhat larger packet size may now be requested, but no
other validation is done by NWIPXSPX. Due to varying MAC header lengths, there
are situations where an IPX application (such as Lotus Notes) is configured for
smaller MAC headers and hence expects a larger packet size. A revision of
TBMI2.COM dated 7-25-97 or later is also required to accommodate this
situation.
Solution:
Apply NWIPXSPX.DLL dated 7-25-97 or later.
Symptom:
Revisions of TBMI2 prior to 7-25-97 strictly limited packets to the worst-case
packet size reported by IPX. When USE MAX PACKET ON and ADD MAX PACKET nn is
specified, TBMI2 allows nn extra bytes to be used per packet. This NET.CFG
parameter was added for use in situations where an IPX application (such as
Lotus Notes) is configured for smaller MAC headers. Revisions of TBMI2 prior to
11-25-96 did not process the USE MAX PACKET
configuration parameter, and NWIPXSPX.DLL has no way to discover this
situation. TBMI2 now processes USE MAX PACKET.
Solution:
Apply TBMI2.COM dated 7-25-97 or later.
Symptom:
Revisions of VSHELL.SYS prior to 10-16-98 could kill the current VDM when an
application made certain VLM connection management calls.
Solution:
Apply VSHELL.SYS dated 10-16-98 or later.
Symptom:
The OS/2 v2.12 Client does not have the current 32 bit SDK libraries or DLL's
for OS/2.
Solution:
The 32 bit libraries or DLL's have been included in this patch kit. They are
from Novell's Developer SDK13.
Apply:
NETOS232 DLL 253,842 07-15-97
CALOS232 DLL 139,493 07-10-97
CFGOS232 DLL 30,281 07-11-97
CLNOS232 DLL 56,932 07-10-97
CLXOS232 DLL 31,468 07-11-97
LOCOS232 DLL 102,551 07-10-97
NCPOS232 DLL 156,695 07-10-97
AUDOS232 DLL 36,953 07-11-97
Self-Extracting File Name: OS2PT2.EXE
Files Included Size Date Time
..\
OS2PT2.TXT (This file)
AUDOS232.DLL 36953 7-11-1997 6:50:12 am
CALOS232.DLL 139493 7-10-1997 3:05:44 pm
CFGOS232.DLL 30281 7-11-1997 6:48:54 am
CLNOS232.DLL 56932 7-10-1997 2:35:28 pm
CLXOS232.DLL 31468 7-11-1997 6:48:40 am
DOSVIPX.SYS 10560 6-5-1997 9:00:16 am
INSTALL.DOC 76326 5-20-1997 6:13:54 am
IPX.SYS 12340 12-5-1997 3:22:08 am
LOCOS232.DLL 102551 7-10-1997 2:33:34 pm
NCPOS232.DLL 156695 7-10-1997 2:50:26 pm
NETOS232.DLL 253842 7-15-1997 11:29:08 am
NWIFS.IFS 43988 7-30-1997 9:31:34 am
NWIPXSPX.DLL 41152 7-25-1997 9:28:28 am
NWREQ.SYS 37684 12-18-1997 10:02:18 am
NWREQOS2.MSG 16846 12-5-1997 3:05:54 am
NWWORKER.DLL 114710 10-6-1998 7:20:02 am
REQ.MSG 13771 8-27-1996 7:01:16 am
REQH.MSG 61738 8-27-1996 7:01:18 am
SPX.SYS 17220 10-27-1997 5:49:56 am
TBMI2.COM 25021 7-25-1997 5:22:12 am
TLI_SPX.DLL 55871 12-18-1997 9:15:52 am
VIPX.SYS 53248 6-5-1997 9:00:10 am
VSHELL.SYS 77824 10-16-1998 9:46:30 am
-----------------------------------------------------------------
Any trademarks referenced in this document are the property of their respective
owners. Consult your product manuals for complete trademark information.
-----------------------------------------------------------------