PW-OSF PWUNIX_ECO450F PATHWORKS for Digital UNIX V5.0F ECO Summary
Copyright (c) Digital Equipment Corporation 1996. All rights reserved.
PRODUCT: PATHWORKS for Digital UNIX, Version 5.0F
OP/SYS: Digital UNIX[R], Versions 3.2 through 3.2D
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: PWUNIX_ECO450F
ECO Kits Superseded by This ECO Kit: PWUNIX_ECO350F
PWOSF_ECO250F
PWOSF_E01050F
ECO Kit Approximate Size: PWUNIX_ECO450F.TAR 44920 Blocks
(22999040 Bytes)
ECO KIT SUMMARY:
An ECO kit exists for PATHWORKS for Digital UNIX V5.0F on Digital UNIX
V3.2 through V3.2D. This kit addresses the following problems:
Problem addressed in the PWUNIX_ECO450F kit:
A fix for a problem unlocking a byte range which was locked via
SMBlockread. (seen with Lotus Notes)
A fix for hung knb sessions with WinNT & Win95.
Handle duplicate change requests during replication from NT primary.
A fix for a replication problem caused by datagrams being broadcast
on just one transport.
Fix for a problem with file permissions which was happening because
of the quota support implementation.
Add an ignorequotas lanman.ini parameter (default no).
Fix for printer class list corruption in clsetup.
Fix for generation of illegal NetBIOS names (too long) for server
loopback connections on servers with long hostnames.
Fix for a panic in the knb kernel code.
Problem addressed in the PWUNIX_ECO350F kit:
A fix for the problem of the license server sometimes crashing in a
NetWare environment.
A fix for a problem of the license registrar reporting that the
client has a license when really no TSR is running on the client.
A fix for the problem of a client accessing the local CD drive
during a directory listing of a share.
A fix for a second print job sometimes hanging the print queue.
A fix for a problem translating an old revision of the license.dat
(pre-v5.0F) which caused the file to become corrupted.
Files system quotas are now supported for regular users. Quotas are
not supported for users with any operator or admin privileges.
Change error reporting for some write errors to be consistent.
Write errors which are reported in the SMB close response are now
also reported via an alert message which the user will see if the
client is running netpopup.
A fix to the SMBflush processing (for flushing all files on the
session) which would cause the lmx.srv process to loop.
A fix in knb to fix an illegal operation that caused a panic in
XTISO (xti_output) on SMP servers.
Modification to knbmon and nbemon.
A fix for the problem of NetWare users with passwords not being able
to login.
A fix for a panic when using NVT or rprinter.
Problem addressed in the PWOSF_ECO250F kit:
At times, files opened by a WfW client will not be closed. This
problem was occurring because the server incorrectly accepted an
open request with opportunistic locking.
UAS replication was sometimes failing because the server was using a
bad (long) mailslot name. This mailslot problem could also
intermittently affect other file replication, any communication
between servers in a domain, and some net commands.
The netBEUI code would panic during shutdown when embryonic session
control blocks were waiting for datalink LCBs. This problem
occurred when the DL_DATALINKS value (in dlpi_data.c) was less than
the NB_DATALINKS value (in nbdata.c)
Could not rename long file names for the Windows NT and Win95
clients. The same problem prevented the creation of a new folder
for a Win95 client.
The flush SMB had performance problems. These problems became
serious when an application frequently generated flush SMBs.
Memory leaks in the license registrar (pwlic.reg) caused logon
performance problems over time.
When the /etc/group file had a lot of users in a group, the long
line could get truncated when a lanman group was deleted from the
file.
The lmx.nbd process would not start on systems where DECnet was
running on a tu0 controller. This problem is timing-related and
could happen intermittently on systems that used other controllers.
The PATHWORKS DECnet daemon (lmx.nbd) would not start on a server
with a low Phase IV DECnet address.
When copying large files from share to share over TCP/IP, the client
would intermittently hang.
When the remote adapter is defined on a DECnet client (via ncp) the
client could not get a license.
When a write error occurred on AdvFS, either because of quotas
exceeded or a full file system, the error was not reported to the
client.
If user has NFS share exported with root access and ignoreunix is
set to yes and a directory in the share has permissions 755, a user
could not create a file in that directory even if the PATHWORKS
permissions allow it.
The NET FILES command would not completely list the open files, but
would abort with "SYSTEM ERROR 8 - OUT OF MEMORY".
For a particular application (ATTACHE), the client sends SMBlseek
for a 0 byte file with an offset of -1 and the server responded with
an error. According to the SMB definition, the server should just
set the file pointer to the beginning of the file.
NetBEUI control blocks would get into a "waiting" state and wouldn't
be recovered until system reboot. The server would gradually run
out of NetBEUI sessions.
When mail notification is sent on TCP/IP, the client program expects
an ASCII name in the source name field of the NetBIOS header. But,
the name that was used was the permanent unique name, which is
binary.
A panic could occur when the knb timer queues are corrupted.
Panic inside flushq() when an invalid queue is passed.
Problem addressed in the PWOSF_ECO150F kit:
Net error command displays incorrect SMB information.
In Windows 3.1 file manager to copy directories, an error would
occur with certain directory structures and copy was not successful.
A panic occurred when an adapter status request was received from a
V5.2 client and requested a license or when the command show astat
was executed.
The server incorrectly detected a file operation past EOF when a
lock, read or write was attempted at the last possible file
position.
When Window's print manager is active, it constantly enumerates
print queues. This caused general performance problems.
When the net session command was issued during the time when a
session is being set up or torn down, an out of memory error was
reported and the command did not succeed.
An old DOS application requests the original program disk because
the server used a media ID of zero on the diskattr SMB response,
which is allowed but not required.
When an NTAS PDC was restarted, the network serviced did not start
if a PWOSF BDC was running in the domain. This occurred because the
PWOSF server was incorrectly defending a NETBIOS group name (The
domain name).
If a print job was added to a queue where a job was already printing
to an lps printer, the job was lost and the pcsaclass process
crashed.
Licenses for DECnet clients using client-based licensing could not
be verified by the license registrar.
A home directory was not created when a user was added and
createhomedir was set to yes. The default is now no.
Pwadmin utility intermittently reported that the shared resource did
not exist when attempting to set permissions.
WFW and Windows NT clients with multiple transports configured could
only connect intermittently.
The excluded set of UID's specified in the lanman.ini file was being
ignored when a new user was created.
PWlic.reg hang occurred with OS/2 Warp clients. OS/2 Warp clients
do not respond to a Netbios session request.
A panic occurred on an SMP system when remote boot clients were in
use.
INSTALLATION NOTES:
Customers must de-install PATHWORKS for Digital UNIX Base system subset
using setld:
- If any of the subsets are not installed, setld displays a
message to the user stating that. It also prompts the user to
make sure they really want to deinstall the subsets specified.
and re-install with new kit:
> /etc/setld -l /kitdir
- /kitdir is the location of the kit. If the kit is on tape, the
most common tape drive specification is /dev/rmt0h. If the kit is
already on the system, /kitdir is the path to the kit's location.
See directions below for details on installing the kit.
Installing The PATHWORKS for Digital UNIX 5.0F ECO4 Kit:
-------------------------------------------------------
Use the tar utility to unpack the kit, example:
> tar xvf PWUNIX_ECO450F.tar
- the following files are in the tar file.
PWKBASE510 PWKLIC510 PWKNWBASE510 PWKRPL510
PWKCONFIG510 PWKNBU3510 PWKNWTRAN3510 PWKTCP3510
PWKDNA3510 PWKNW3SVOL510 PWKRNOTE510 instctrl
Change to the kit directory and use the setld utility to install the kit:
> cd
> setld -l /kitdir
- The above setld command will display a list of valid subsets that
are in the current directory in menu format and prompts the user.
Below is an example:
The subsets listed below are optional:
There may be more optional subsets than can be presented on a single
screen. If this is the case, you can choose subsets screen by screen
or all at once on the last screen. All of the choices you make will
be collected for your confirmation before any subsets are installed.
- PATHWORKS for DEC OSF/1 AXP (Common):
1) PATHWORKS for DEC OSF/1 AXP - License Server
2) PATHWORKS for DEC OSF/1 AXP - PATHWORKS Configuration
3) PATHWORKS for DEC OSF/1 AXP - Release Notes
- PATHWORKS for DEC OSF/1 AXP (LAN Manager):
4) PATHWORKS for DEC OSF/1 AXP - DECnet Driver
5) PATHWORKS for DEC OSF/1 AXP - LAN Manager Services
6) PATHWORKS for DEC OSF/1 AXP - NetBEUI Driver
Enter your choices or press RETURN to display the next screen.
Choices (for example, 1 2 4-6):
Choices (for example, 1 2 4-6):
7) PATHWORKS for DEC OSF/1 AXP - Remote Boot Service
8) PATHWORKS for DEC OSF/1 AXP - TCP/IP Driver
- PATHWORKS for DEC OSF/1 AXP (NetWare):
9) PATHWORKS for DEC OSF/1 AXP - NetWare Services
10) PATHWORKS for DEC OSF/1 AXP - NetWare System Volume
11) PATHWORKS for DEC OSF/1 AXP - NetWare Transports
Or you may choose one of the following options:
12) ALL of the above
13) CANCEL selections and redisplay menus
14) EXIT without installing any subsets
Enter your choices or press RETURN to redisplay menus.
Choices (for example, 1 2 4-6):
- the installation proceeds from here.
R] UNIX is a registered trademark in the United States and other
countries licensed exclusively through X/OPEN Company Ltd.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
pwunix_eco350f.README
pwunix_eco450f.CHKSUM
pwunix_eco450f.CVRLET_TXT
pwunix_eco450f.tar
|
