home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Encyclopedia 96-1
/
novell-nsepro-1996-1-cd2.iso
/
download
/
netware
/
nsd004.exe
/
NSD004.TXT
< prev
next >
Wrap
Text File
|
1994-03-22
|
22KB
|
586 lines
NOVELL TECHNICAL INFORMATION DOCUMENT
TITLE: Updated OS/2 Requester files for 1.3
DOCUMENT ID: TID000231
DOCUMENT REVISION: B
DATE: 22MAR94
ALERT STATUS: Yellow
INFORMATION TYPE: Symptom Solution
README FOR: NSD004.EXE
NOVELL PRODUCT and VERSION:
NetWare Client for OS/2 1.3
ABSTRACT:
This file is the Novell Services Diskette 4 (NSD 4). The file solves minor
problems found in NetWare Requester for OS/2 1.3. NSD 4 includes all changes
from the first and second NSD files.
──────────────────────────────────────────────────────────────────────────────
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.
──────────────────────────────────────────────────────────────────────────────
ADDITIONAL CONFIGURATION
Other:
Named Pipes
SYMPTOM
In previous versions, Named Pipes clients could appear to successfully
connect to a Named Pipes server even when no Named Pipes servers existed.
SOLUTION
With NSD004.EXE applied, this problem no longer occurs.
SYMPTOM
In previous versions, Named Pipes clients could receive "invalid handle"
errors. This occurred if two threads were both open and doing DosRead or
DosTransact requests, then the first thread closed.
SOLUTION
With NSD004.EXE applied, this problem no longer occurs.
SYMPTOM
DosWaitNmPipe was not properly notifying Named Pipes clients when a pipe
becomes available.
SOLUTION
With NSD004.EXE applied, DosWaitNmPipe will now properly notify Named
Pipes clients when a pipe becomes available.
SYMPTOM
Sending data segments close to 64 KB in size caused the Named Pipes
servers to freeze.
SOLUTION
With NSD004.EXE applied, Named Pipes clients can now use the entire 64 KB
in the API message buffer. Named Pipes no longer uses any of the space.
SYMPTOM
Opening more client and server pipes than you have available SPX sessions
would freeze the workstation.
SOLUTION
With NSD004.EXE applied, opening more client and server pipes than you
have available SPX sessions no longer freezes your workstation. Instead,
you receive an error message telling you that no SPX sessions are
available.
SYMPTOM
When many Named Pipes calls were coming to a 32-bit board (NE2-32 or
NE3200), Named Pipes connections may have been lost or frozen. This may
have occurred when a fast-CPU (such as a 486) Named Pipes server was
servicing many clients.
SOLUTION
With NSD004.EXE applied, this problem no longer occurs.
SYMPTOM
When Named Pipes clients used DosCallNmPipe to retrieve information from
Named Pipes servers, the server froze.
SOLUTION
With NSD004.EXE applied, this problem no longer occurs.
SYMPTOM
Routers, such as Cisco, that send Service Advertising Packets (SAPs) with
more than five entries would not work properly with Named Pipes.
SOLUTION
With NSD004.EXE applied, this problem no longer occurs.
SYMPTOM
When a Named Pipes machine attempted to read data from another Named
Pipes machine, random data corruption errors sometimes occurred.
SOLUTION
With NSD004.EXE applied, this problem no longer occurs.
SYMPTOM
When messages were sent that were too large for the buffer on either side
of the transmission, Named Pipes was setting the BytesRead value to zero.
This zero value sometimes caused failures in applications that check
BytesRead to determine how much data has been read.
SOLUTION
With NSD004.EXE applied, this problem no longer occurs.
SYMPTOM
Named Pipes client sessions may sometimes have been disconnected on busy
networks.
CAUSE
This symptom was occurring because Service Advertising Packets (SAPs)
were not being sent every 60 seconds; therefore, Named Pipes servers were
occasionally removed from the client server tables, causing the client to
terminate the session.
SOLUTION
With NSD004.EXE applied, SAP threads now run at Ring zero; so this
problem no longer occurs.
SYMPTOM
The Extender would not run reliably on Windows workstations.
SYMPTOM
Also, Windows Named Pipes workstations no longer lose connections over
bridges or routers.
SOLUTION
With NSD004.EXE applied, some problems with the Named Pipes Extender for
DOS/Windows have been solved. The Extender now runs more reliably on
Windows workstations. Also, Windows Named Pipes workstations no longer
lose connections over bridges or routers.
ADDITIONAL CONFIGURATION
Third-Party Product and Version:
Other:
General
SYMPTOM
When running SPX applications in a virtual DOS or Windows session, an
error stating that SPX had incorrectly terminated may have been returned.
SOLUTION
With NSD004.EXE applied, SPX now correctly terminates.
SYMPTOM
Heavy asynchronous communications coming into a machine caused the Link
Support Layer (LSL) to freeze.
SOLUTION
With NSD004.EXE applied, this problem no longer occurs.
SYMPTOM
Sometimes, applications that used Extended Attributes (EAs) did not have
worked properly.
SOLUTION
With NSD004.EXE applied, this problem no longer occurs.
SYMPTOM
Network management programs had problems functioning with a revision
indicated by a letter.
SOLUTION
With NSD004.EXE applied, the revision indicator has been changed from a
letter (F) to a number (5) to better function with network management
programs.
SYMPTOM
If you entered a number of NetWare Requester cache buffers that required
a buffer size larger than 64 KB, the Requester would disable caching.
SOLUTION
With NSD004.EXE applied, the Requester now simply uses the maximum value
allowed for cache buffers when the value you specify is too large.
SYMPTOM
When you tried to change the Extended Attributes (EAs) of a file that you
had only Read Only access to, no error message was returned; however, the
EAs never changed.
SOLUTION
With NSD004.EXE applied, the message now appears.
SYMPTOM
Each workstation booting remotely requires two server connections, an RPL
connection and a person's username connection. Applications searching
for a workstation's server connection would sometimes find the server
connection before locating the person-s username connection.
SOLUTION
With NSD004.EXE applied, the RPL connection now appears at the end of the
connection table so that applications searching for a workstation's
server connection will find the username connection first.
SYMPTOM
Some applications require information about whether the remote
workstation is booting from support NCPs and Extended Attributes.
SOLUTION
With NSD004.EXE applied, the remote workstations now check to see if the
server their booting from support NCPs and Extended Attributes.
SOLUTION
Apply NSD004.EXE
Self-Extracting File Name: NSD004.EXE Revision: A
Files Included Size Date Time
\
NSD004.TXT (This File)
IPX.SYS 10416 11-22-91 8:34a
LSL.SYS 16944 11-19-91 8:22a
NE2.SYS 20448 06-24-91 1:40p
NSD.LVL 945 04-13-92 8:31a
SPX.SYS 13120 04-09-92 12:02p
TLI.DLL 20341 07-15-91 4:03p
3C501.SYS 18320 06-24-91 1:44p
3C503.SYS 26528 06-24-91 1:30p
3C505.SYS 18736 08-15-91 9:14a
3C523.SYS 18592 07-09-91 11:18a
NWIFS.IFS 34720 04-10-92 1:15p
NWREQ.SYS 17888 04-09-92 4:09p
PCN2L.SYS 13632 10-11-91 3:46p
ROUTE.SYS 33200 06-25-91 9:53a
TOKEN.SYS 25392 12-13-91 4:54p
DOSBOX.EXE 10262 11-07-91 1:30p
NE2-32.SYS 21152 03-31-92 2:41p
NE1000.SYS 19424 06-24-91 1:41p
NE2000.SYS 21152 11-27-91 11:10a
NE2100.SYS 20992 12-13-91 9:28a
NE3200.SYS 25904 04-02-92 3:25p
NMPIPE.SYS 16176 04-02-92 11:53a
TRXNET.SYS 21856 02-19-92 4:36p
CMGRLAN.SYS 42976 03-26-91 9:32a
COEXIST.TXT 10367 03-10-92 10:57p
DDAEMON.EXE 8496 11-19-91 8:22a
EXOS205.SYS 22480 11-27-91 3:21p
EXOS215.SYS 22992 11-27-91 3:21p
INSTALL.EXE 44608 06-25-91 10:15a
INSTALL.HLP 3686 02-08-91 11:18a
NE1500T.SYS 21008 12-13-91 9:28a
NPCALLS.DLL 1040 10-01-91 10:36a
NWCALLS.DLL 67856 11-20-91 2:45p
NWSPOOL.EXE 29824 03-25-92 1:19p
ODINSUP.SYS 18720 02-27-92 8:46a
TLI_SPX.DLL 27743 08-13-91 12:22p
TLI_TCP.DLL 10875 03-19-91 9:02a
TRXNET2.SYS 21856 02-19-92 4:36p
IPXCALLS.DLL 1332 11-22-91 8:34a
NPDAEMON.EXE 22432 04-02-92 11:52a
NPSERVER.SYS 18592 04-02-92 11:52a
NSDINSTL.EXE 40400 04-16-91 10:20a
NSDINSTL.HLP 3560 04-16-91 10:13a
NWCONFIG.DLL 4005 11-20-91 2:46p
NWDAEMON.EXE 25168 04-10-92 1:16p
READCMGR.TXT 6741 06-27-91 5:13p
SPDAEMON.EXE 10560 04-09-92 12:02p
SPXCALLS.DLL 3124 04-09-92 12:01p
\DOSNPIP\
DOSNP.EXE 9971 04-02-92 11:18a
\NPRNT\
NPRINT.EXE 50727 03-06-92 1:37p
\WINDOWS\
NETAPI.DLL 7168 06-24-91 11:05a
Installation Instructions:
NOTE FOR OS/2 EXTENDED EDITION USERS:
If you have not yet installed the Requester diskette on your
workstation, copy the INSTALL.EXE file on this NSD to the Requester
diskette and install the Requester. Then install this NSD using the
instructions below. If you have already installed the Requester,
just follow the instructions below.
Step 1: Boot the workstation with OS/2 and open an "OS/2 Window" or
"OS/2 Full Screen." The command line prompt appears. NOTE:
You can press F1 or click the "Help" button for help during
this procedure.
Step 2: Insert the NSD diskette into drive A, change to drive A, and
type the following:
NSDINSTL <Enter>
NOTE: If you are running NSDINSTL from a diskette, you will
need to give the diskette a volume label of NSD.
An installation window appears.
Step 3: If you originally installed the NetWare Requester in the
default C:\NETWARE directory, skip to the next step. If you
installed the Requester in another location, click the "Specify
directories" button, type each location and click the "OK"
button.
Step 4 Click the "Copy program files" button; then click the "Start"
button.
The NSD files are copied to your hard disk. Click the "OK"
button on the "Installation complete" message.
Step 5 Click the "Exit" button. Note that you must reboot for the
changes to take effect.
Patch History:
Problem solved by NSD 3:
NSD3--1 You will now see "OS/2 Requester: V1.30 Rev. F" when you type
NVER.
NSD3--2 Previously, if your application or utility specified a UNC path
with just a server and volume name (and no directory), you
would receive a File Not Found error. This problem has been
fixed.
NSD3--3 The Requester now correctly reads directory attributes for fake
root drives.
NSD3--4 If your application issues a Named Pipes request when you are
running dual requesters with NetWare loaded first and with
NetWare Named Pipes support not loaded, the request is now
properly passed on to the non-NetWare Requester.
NSD3--5 The DOS box now supports closing and reopening file handles 0
through 4.
NSD3--6 The Requester now automatically reattaches to a server if you
lose your last connection. The Requester attaches to your
preferred server or to the nearest server if you have not
specified a preferred server. This enables you to log in again
after a connection is lost without having the LOGIN utility on
your local disk.
NSD3--7 The Requester has been enabled so that it can support Double
Byte Character Sets (DBCS).
NSD3--8 When you run the WHOAMI utility on a NetWare 2.15 or 2.2
server, you will now see the correct connection number for your
workstation.
NSD3--9 If your workstation is a Named Pipes server, do not set your
SPX connection limit higher than 255.
NSD3--10 Previously, if you were running a multithreaded program with
all threads issuing SPX commands, one or more of the threads
may have hung. This no longer occurs.
NSD3--11 Previously, you received an error if you
1. Ran a program off the network in one OS/2 session,
2. Opened a second session and ran the same program,
3. Closed the first program and exited the first session,
4. Opened a third session and tried to run the same program.
This problem no longer occurs.
NSD3--12 When using SPX applications, your workstation will no longer
run out of SPX sessions or freeze up, as may have happened
previously.
NSD3--13 In some cases, your workstation may not have attached to a
NetWare server upon booting. Your workstation will now attach
properly.
NSD3--14 Your workstation now provides diagnostic information for
network management.
NSD3--15 When using Named Pipes applications, your workstation will no
longer freeze up, as may have happened previously.
NSD3--16 Previously, when you typed CASTOFF ALL to turn off broadcast
messages from a particular server, it appeared that you no
longer had a connection to that server. This now works
properly.
NSD3--17 On a DOS workstation, you can specify the number of files that
can be open simultaneously by using the FILES= option in the
CONFIG.SYS file and the FILE HANDLES option in the SHELL.CFG
file. The total number of files specified with these two
options cannot exceed 253.
When you load the Named Pipes Extender for DOS, the SHELL.CFG
FILE HANDLES option is set to 40 by default. Therefore, the
maximum number of files you can specify in CONFIG.SYS without
adjusting the SHELL.CFG default is 213 (for a total of 253). If
you specify more than 253 total files, when the Named Pipes
Extender loads, you receive a message telling you to reduce the
total number of files.
NSD3--18 When you boot a workstation that is running both the Novell
NetWare Requester and the IBM LAN Requester on an Ethernet
network, you receive a message saying the workstation cannot
find a file server. The workstation actually does attach to a
server. Please disregard the error message.
NSD3--19 A check has been included to ensure that the NWIFS.IFS and
NWREQ.SYS files are at the same revision level. If revision
levels do not match, you will see the following error message:
MESSAGE
NWREQ.SYS version does not match NWIFS.IFS version.
If you see this error message, reinstall NSD 4.
Problem solved by NSD 2:
NSD2--1 IPX options in NET.CFG no longer need to be followed by a
space.
NSD2--2 When using NETAPI.DLL for WINDOWS, you will no longer lose the
functionality of your serial port, as may have happened
previously.
NSD2--3 Caching now works properly with any allowable size of Link
Support Layer (LSL) buffer (see the NetWare Requester for OS/2
manual for allowable sizes).
NSD2--4 Attempting to view a nonexistent file or directory by typing
the DIR command with wildcard characters now displays the
proper error message.
NSD2--5 You can now type a server and volume name using a Universal
Naming Convention (UNC) path, and if that server or volume does
not exist, the software will display the correct error message.
Problem solved by NSD 1:
NSD1--1 Applications that use NetWare routines from the NWCALLS.DLL
file when the Requester is not loaded will no longer be
terminated. Instead, they will receive the following error
message: 88ff (REQUESTER NOT LOADED).
NSD1--2 A sending and receiving error code is now properly displayed as
8805 instead of 8905.
NSD1--3 Previously, if the ring broke on a Token-Ring network when the
Requester was trying to send, the Requester would hang the
workstation. Now the send process will simply time out and the
Requester will display an error message.
NSD1--4 Occasionally, the OS/2 File Manager does not properly copy a
network directory and its accompanying subdirectories.
Previously, this error caused the system to hang. Now, because
of changes to the Requester, you simply receive an error
message.
NSD1--5 Previously, if you used the OS/2 E.EXE editor to create a new
file, the file would not save properly to your file server. An
error of 899C was returned. This problem no longer occurs.
NSD1--6 Child processes now close correctly when using Named Pipes.
NSD1--7 The installation program, INSTALL.EXE, will now install on
Extended Edition OS/2 when IBM NetBIOS is running. This was
only a problem on the Extended Edition of OS/2.
NSD1--8 Previously, if a Named Pipes server was a slower system than a
Named Pipes client connected to it, performance was very poor.
Performance has been improved in this situation.
NSD1--9 A new configuration option, called "DisplayHardErrors," has
been added to the NET.CFG file. This option allows programs to
keep running without interaction when a hard error is
displayed. This is specifically for sites with unattended
workstations. The option has the following syntax:
displayharderrors no
To display error messages, simply leave this line out of your
NET.CFG file.
NSD1--10 In certain circumstances, a NetWare server specified with
lowercase letters in a UNC path would not be recognized. This
problem has been solved.
NSD1--11 The CMGRLAN.SYS driver replaces the TOKENEE.SYS driver. Select
Communication Manager on the Modify CONFIG.SYS screen during
Requester installation.
CMGRLAN.SYS works with IBM Ethernet, IBM PC, and Token-Ring
networks using Extended Edition Communications Manager. If you
are running OS/2 Extended Edition, you should use this new
driver. For instructions on using CMGRLAN, please read the
READCMGR.TXT file in the same location as this file.
The READCMGR.TXT file also provides instructions for using
IBM's LAN Requester and Novell's NetWare Requester on the same
computer.
Solution Specifics:
NEW OR CHANGED DRIVERS
The following drivers have been updated since the NetWare Requester 1.3
was released:
TRXNET.SYS (NSD 4)
TRXNET2.SYS (NSD 4)
NE2-32.SYS (NSD 4)
3C503.SYS (NSD 3)
3C505.SYS (NSD 3)
3C523.SYS (NSD 3)
TOKEN.SYS (NSD 3)
ROUTE.SYS (NSD 3)
NE1000.SYS (NSD 2)
NE2.SYS (NSD 2)
NE2000.SYS (NSD 2)
The following drivers are new since the NetWare Requester 1.3 was
released:
NE3200.SYS (NSD 4)
EXOS205.SYS (NSD 4)
EXOS215.SYS (NSD 4)
3C501.SYS (NSD 4)
PCN2L.SYS (NSD 4)
ODINSUP.SYS (see ODINSUP.TXT--NSD 4)
NE1500T.SYS (NSD 3)
NE2100.SYS (NSD 3)
CMGRLAN.SYS (replaces TOKENEE.SYS--NSD 1)
