PW-OSF PWOSF_E01050F PATHWORKS V5.0F for DEC OSF/1 ECO Summary
Copyright (c) Digital Equipment Corporation 1995.
All rights reserved.
PRODUCT: PATHWORKS for DEC OSF/1 Version 5.0F
OP/SYS: DEC OSF/1 Versions 3.0, 3.2
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: PWOSF_E01050F
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: pwosf_e01050f.tar 22999040 Bytes
System Reboot Necessary: See Release Notes
ECO KIT SUMMARY:
An ECO kit exists for PATHWORKS for DEC OSF/1 V5.0F on DEC OSF/1 V3.0,3.2
This kit addresses the following problems:
- 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 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 OSF 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 OSF 5.0F ECO1 KIT:
----------------------------------------------------
Use the tar utility to unpack the kit, example:
> tar xvf PWOSF_E01050F.TAR
- the following files are in the tar file.
PWKBASE510 PWKNWTRAN3510
PWKCONFIG510 PWKRNOTE510
PWKDNA3510 PWKRPL510
PWKLIC510 PWKTCP3510
PWKNBU3510 PWKNW3SVOL510
PWKNWBASE510 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
--- MORE TO FOLLOW ---
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.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
pwosf_e01050f.README
pwosf_e01050f.CHKSUM
pwosf_e01050f.CVRLET_TXT
pwosf_e01050f.tar
|
