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

Conference 7.286::fddi

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

1515.0. "DEFPA board and Windows NT v3.1??" by VAXSPO::ARRONQUE () Thu Dec 01 1994 11:17

    Hello,
    
    I read in topic 1423.2 that DEFPA board requires Windows NT v3.5 to
    work. Any chance to make it work under NT v3.1 ?
    
    
    
    Thank you,
    Marco Arronque
    NIS - Brazil
T.RTitleUserPersonal
Name
DateLines
1515.1LURE::CERLINGIXOYEThu Dec 01 1994 13:025
	Since the DEFPA is PCI-based, and since I think PCI support is
	not provided in 3.1, I don't think so.

tgc
1515.2NETCAD::STEFANILook Ma, I'm drinking my oatmeal!Thu Dec 01 1994 14:2432
    >>	Since the DEFPA is PCI-based, and since I think PCI support is
    >>	not provided in 3.1, I don't think so.
    
    That's more or less true.  There are really two problems:
    
    1.  The PCI-specific driver and HAL calls do not exist in the NDIS
        wrapper that shipped with Windows NT 3.1.
    2.  Microsoft strongly recommended (and we listened) that developers
        create NDIS 3.0 miniport drivers for Windows NT 3.5, Windows 95,
        and beyond.  The Windows NT 3.1 NDIS wrapper does not support
        miniport network drivers.
    
    The final Premium SDK/DDK that Microsoft shipped out to developers
    included an NDIS 3.0 wrapper for Windows NT 3.1 that (in theory)
    includes the API's for miniports.  Developers can then use their
    existing code base to build Windows NT 3.1 compatible drivers, then
    install the new wrapper and get it to work.
    
    Did Microsoft include FDDI miniport driver support in this special
    wrapper?
    Did Microsoft include the PCI-specific driver and HAL calls?
    
    I don't really know the answer to either question at this point.  In
    any event, it may become a lot of extra work on our part to find out.

    I'm hoping that the majority of Windows NT 3.1 customers will upgrade
    to Windows NT 3.5 and make the issue moot.  So far this seems to be
    holding true.
    
    Larry Stefani
    Network Driver Development
    Networks Engineering