[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:VAX and Alpha VMS
Notice:This is a new VMSnotes, please read note 2.1
Moderator:VAXAXP::BERNARDO
Created:Wed Jan 22 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:703
Total number of notes:3722

583.0. "PFDRIVER.EXE?" by CHR27::YEUNG (im2bz2p,ru?) Mon May 12 1997 21:22

My customer recently added a turbochannel adapter (DWCTX) and a FDDI
adapter (DEFTA) to a VAXstation 4000/96.
After powering the system back up, the FCA0 device did not exist.
So I ran SYSGEN AUTO ALL, and it complained that the
	SYS$COMMON:[SYSEXE]PFDRIVER.EXE file could be found.

I also found the same error message in STARTUP.LOG.  The older versions
of STARTUP.LOG (prior to installation of DWCTX and DEFTA) did not
have the PFDRIVER %SYSGEN-E-FNF error.

What is the PFDRIVER?

Thanks

Tim
T.RTitleUserPersonal
Name		DateLines
583.1Error MessageCHR27::YEUNGim2bz2p,ru?Mon May 12 1997 21:259
Error message mentioned in .0 is:

SYSGEN> AUTO ALL
%SYSGEN-W-OPENIN, error opening SYS$COMMON:[SYSEXE]PFDRIVER.EXE; as input
%SYSGEN-E-FNF, file not found

Thanks
Tim
583.2UTRTSC::utoras-198-48-122.uto.dec.com::JurVanDerBurgChange mode to Panic!Tue May 13 1997 04:0010
This is from my devicedriver list:

PF    DRQ3-B    Y   PRESTON GMAD I/O SUBSYSTEM
                    VAXLAB SOFTWARE LIBRARY

I guess that there's something wrong with the config and that sysgen
mistakingly selects this driver.

Jur.
583.3STAR::STOCKDALETue May 13 1997 15:4216
>>      SYS$COMMON:[SYSEXE]PFDRIVER.EXE file could be found.

I assume you are running V6.2 or earlier.  The error is because the DEFTA
is not a DEFTA-FA so SYSLOA doesn't recognize the device type.  You need
to patch SYSLOA to recognize the device so that the correct driver gets
loaded.

I'll send you a patch command file via mail.  Note that some care is needed
to ensure that the DEFTA is up-to-rev.  You'll have to inspect the module
to verify this.  The patch command file describes this.

Just out of curiosity, why did the customer go with FDDI?  I hope not because
of any expectation of high performance (on a VAX 4000 that is)?

- Dick
583.4FixedCHR27::YEUNGim2bz2p,ru?Wed May 14 1997 00:2913
>Just out of curiosity, why did the customer go with FDDI?  I hope not because
>of any expectation of high performance (on a VAX 4000 that is)?

They're adding another network segment that's FDDI and they need to connect
five VAX 4000/96 systems to it.  The 4000/96 systems are satellite nodes and
the MSCP server is reachable via FDDI.  They'll still boot over Ethernet.

Thanks John, the patch worked.
BTW, the customer is running V6.2 and the DEFTA boards are up to rev.

Thanks

Tim