In the OpenVMS 7.3 timeframe, a patch was released to fix a hang caused by a double deletion of a network device. This was VMS73-NETACP-V0100. There was also a version for 7.3-1 called, unsurprisingly, VMS731-NETACP-V0100.
When OpenVMS 7.3-2 was kitted, this patch was not generated, but rather rolled up into VMS732-UPDATE-V0100. Unfortunately, when this was done, a minor problem was introduced.
The NETACP patch placed the corrected version of NETDRIVER.EXE in SYS$COMMON:[SYS$LDR] where it is supposed to live. The fix included in the 7.3-2 UPDATE patches however placed it in SYS$SYSTEM:
This would have been OK if we were talking about version 4.x of VMS ;)
I have confirmed with Engineering that copying the version of NETDRIVER.EXE from SYS$SYSTEM to SYS$COMMON:[SYS$LDR] and rebooting is a correct workaround until a remediated patch kit can be released.
Patch kits affected: VMS732-UPDATE-V0100, VMS732-UPDATE-V0200, VMS732-UPDATE-V0300
Posted at February 23, 2005 6:24 PMThis seems only to be relevant for DECNET IV sites. For these however it seems most relevant.
A lot of OpenVMS systems are TCP/IP only or have changed to DECNET/OSI ( and TCPIP).
Posted by: Lars Funck Jensen at March 6, 2005 3:35 AM
Comments are closed