| Title: | FDDI - The Next Generation |
| Moderator: | NETCAD::STEFANI |
| Created: | Thu Apr 27 1989 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2259 |
| Total number of notes: | 8590 |
I have a customer that utilizes our ethernet interface to allow XNS to talk to the VAX. This customer is, in fact, Xerox. With VMS 5.4-3, supposedly the Ethernet driver has been changed to support FDDI. Whatever changed has broken the Xerox XNS software on the VAX. I need to identify who would know what the changes are in the ethernet device driver so I can get that information to Xerox. There are a number of internal Xerox VAX sites that are stuck at VMS 5.4-2 until this gets resolved and I'd like to do everything we can to help. Thanks. Jim Mickol Sr. Sales Support Consultant Xerox Account Group Rochester, NY DTN 252-7106
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 397.1 | MR1PST::DENISE::CARR | Tue Nov 19 1991 15:57 | 3 | ||
Try contacting Lee Leahy (STAR::L_LEAHY) in VMS. I believe he is responsible for the PEDRIVER. | |||||
| 397.2 | RCOCER::MICKOL | Greetings from Rochester, NY | Tue Nov 19 1991 16:03 | 4 | |
Thanks. Jim | |||||
| 397.3 | Contact me | STAR::GAGNE | David Gagne - VMS/LAN Development | Tue Nov 19 1991 16:57 | 22 |
PEDRIVER is the cluster driver that uses the Ethernet/FDDI drivers.
As you mentioned, there are changes to the Ethernet drivers in VMS
V5.4-3. There is about 10 man years of work in the Ethernet
drivers between VMS V5.4-2 and VMS V5.4-3. So you DON'T want a list of
changes because such a list doesn't exist and such a list would
probably be too large for anyone to go through.
I am in the VMS group that modified the Ethernet/FDDI drivers in VMS
V5.4-3. I can guarantee that no internal or external documented
interface was modified. There have been multiple third party vendors
that reverse engineered some of the internal interfaces incorrectly and
are now having problems. I am handling each of these individually.
If XEROX needs information about how a particular interface works and
IF THAT INTERFACE IS THE ALTSTART INTERFACE, then they can sign a
non-disclosure to get a document from which they can deduce how to use
the ALTSTART interface. If they are using the QIO interface, then that
is already documented in the I/O User's Manual, Part II, chapter 6.
If they are using some other interface, then they will have to convert
to one of those two interfaces.
Thank you.
| |||||