home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Black Box 4
/
BlackBox.cdr
/
lan
/
lm20bfix.arj
/
PATCH2.DOC
< prev
Wrap
Text File
|
1991-02-12
|
4KB
|
119 lines
LAN Manager 2.0 Patch 2 Update
Bug Fixes
[This document describes the bugs that were fixed for the Patch 2 update
to Lan Manager 2.0B]
#1)
Bug #: 729 Title: DOS TREE on net drives
Under DOS, on remote drives, TREE recursed down the first
branch of the tree and then terminated, never popping back up,
whether it was used with the /f switch or not.
The problem was the inability of LM (2.0b) to recycle
DOS file search handles if it ran out of them. (They would
only be recycled after the 10 minute expiry time had passed).
#2)
Bug #: 831 Title: Stack switching code broken in DOS messenger
If you're in the messenger and you get another interrupt for the
messenger, the messenger will switch stacks. The common example
of this is getting a message larger than 128 characters in size.
#3)
Bug #: 1038 Title: Trap 00D using Named-pipes
When sending messages various sizes from a client to a server across
a single direction pipe, the server will take a Trap00D in ring 0
This trap (or similar ones) occurs whether HPFS386 is being used
or not. We have recreated the problem under both HPFS386 and standard
HPFS.
#4)
Bug #: 1042 Title: Named pipes bug
On a non blocking byte mode pipe, attempt two server side writes
of size > pipe buffer size with no client side reads. The first write
is correctly truncated to the pipe buffer size but the second write blocks
until a write arrives. The second write should not block but return
immediately with 0 bytes written.
#5)
Bug #: 1051 Title: Incompatability between Netpopup and graphics mode apps
Getting a popup while in graphics mode in apps like Works or Word and sub-
sequently clearing it, causes the palette to be changed.
Duplication scenario: send a popup to Works while in graphics mode. Clear it. The palette will be changed.
#6)
Bug #: 1063 Title: Trap 000D using pipes
Opening roughly 14 (I only needed 8) clients sending 55,000 byte
messages to a server will cause the server to take a Trap 000D.
Here are the registers:
Trap 000D
AX=2600 BX=163D CX=0000 DX=07A0 BP=F81C
SI=0000 DI=2108 DS=0740 ES=13A0 FLG=2246
CS=0760 IP=234C SS=0038 SP=F80A MSW=FFFD
CSLIM=5D6E SSLIM=F4EF DSLIM=3497 ESLIM=101F
CSACC=98 SSACC=97 DSACC=93 ESACC=93
ERRCD=0000 ERLIM=**** ERACC=**
Internal processing error at 0220:3606
#7)
Bug #: 1084 Title: LM 2.0 problems
Tried using edlin from DOS clients to open the same
remotefile at the same time. Make sure it's to a FAT partition
and the srvheuristic 11 bit is set to 3. After the fix
was made, they can both open it, but only one can save it
(this is expected behaviour due to a renaming attempt by edlin).
#8)
Bug #: 813 Title: Local security doesn't seem to work right on LM 2.0B
You cannot successfully start the workstation under local
security on LM 2.0B and OS/2 1.3. The NET START WKSTA command (or
NET START SERVER) from PRIVINIT.CMD keeps on printing out "." infinitely.
One workaround was to detach net start rdr in privinit. However,
one must be careful about subsequent net commands since they need to
wait for the first one to complete, and all must be detached, also,
they need to change their current scripts to use detach.
#9)
Bug #: 831 Title: NETWKSTA.EXE nmpipe (4087 byte msgmode) read hang in win/3
The Saros FileShare Windows app, when running in Windows 3.0 in 386
Enhanced mode with the lm20 winnet driver, is transferring files from
server to client via blocking, message-stream named pipes. If the file to
transfer is 3457 bytes in size, and the Saros message packet overhead of
630 bytes, the total message size of 4087 (a few bytes shy of 4096). When
the client app calls read to get the data from the server,
control never returns to the app. This failure only occurs when running in
Enhanced mode Windows, not Real or Standard.