| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 506.1 | | STAR::GAGNE | David Gagne - VMS/LAN Development | Wed Mar 18 1992 09:09 | 16 |
| The NETACP you have has the new code for FDDI network management. The
FXDRIVER you have does not have the new FDDI network management code.
This means that either you have copied a NETACP from a new version of
VMS to your V5.5 system or some kit you've installed is supplying
you with a version of NETACP that is not compatible with the VMS V5.5
FXDRIVER.
Note that I used "NETACP" above. Not being an expert in DECnet-VAX,
I believe that it's NETACP that makes the QIO requests on behalf of
NCP. If not, then the problem is in whatever piece of DECnet-VAX
that makes the QIO startup requests to the FDDI driver.
If all you did was install DNVEXT, then you should file a QAR/SPR
against that product stating that the image(s) they are shipping are
not compatible with VMS V5.5.
|
| 506.2 | It was NETACP. | EWBV06::IDO | | Wed Mar 18 1992 22:48 | 59 |
|
Thank you for your reply, David. The problem caused NETACP.EXE I used.
The following is the ID list of related images. I used NETACP.EXE (X-13A2) I
copied from NET_VOID.
I could run DEMFA properly under DECnet after I replaced the NETACP to
original one from VMS V5.5.
So, All CSC should not provide X-13A2 NTACP.EXE for customer using DEMFA,
until FXDRIVER supports new NETACP. Is there any plan for FXDRIVER??
Thanks again,
Naoki
-----------------------------------------------------------------------------
NETACP.EXE I copied from NET_VOID(DVAX$patch13_V5x.A)
Image Identification Information
image name: "NETACP"
image file identification: "X-13A2"
link date/time: 25-FEB-1992 17:15:20.59
linker identification: "05-09"
Patch Information
There are no patches at this time.
Here is the original NETACP.EXE in VMS V5.5 SSB
Image Identification Information
image name: "NETACP"
image file identification: "X-51"
link date/time: 12-OCT-1991 05:08:32.39
linker identification: "05-09"
Patch Information
There are no patches at this time.
Here is FXDRIVER.EXE from VMS V5.5
Image Identification Information
image name: "FXDRIVER"
image file identification: "X-16"
link date/time: 12-OCT-1991 05:12:10.56
linker identification: "05-09"
Patch Information
There are no patches at this time.
|
| 506.3 | Start with the correct sources | STAR::GAGNE | David Gagne - VMS/LAN Development | Thu Mar 19 1992 12:33 | 7 |
| FXDRIVER in the AMBER release of VMS (probably called V5.5-2) works
with the new NETACP. I expect that the NETACP you got was not from
V5.5 The person that supplied the NETACP to CSC should have used V5.5
as the base; not AMBER.
The development of the new features in NETACP/NCP/FXDRIVER was done in
AMBER; all at the same time.
|