[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

1782.0. "Win95 DEFPA install problem" by CGOOA::VAOP05::Szostak (Am I NIS or NAC ?) Thu Aug 17 1995 01:32

We are having trouble installing the DEFPA driver into Windows95.
We are using the drivers from the FPKIT242.ZIP KIT in the WIN95 
directory. The installation appears to go fine, at initial install 
we sellected only NETBEUI and restarted.  Could not see NT server.
We tried installing TCP/IP and the same results occur.  We then 
removed the adapter and reinstalled this time selecting the 
default directory a:\.  Installation appeared normal but when 
configuring adapter we only have 16 BIT real mode driver availble, 
but low and behold the network works.  Any ideas

Richard
NIS VAO
T.RTitleUserPersonal
Name
DateLines
1782.1NETCAD::STEFANIMachines to humanizeThu Aug 17 1995 12:0128
    Hi Richard,
    
>>We are having trouble installing the DEFPA driver into Windows95.
>>We are using the drivers from the FPKIT242.ZIP KIT in the WIN95 
>>directory. The installation appears to go fine, at initial install 
>>we sellected only NETBEUI and restarted.  Could not see NT server.
    
    As documented in the on-line release notes (A:\RELEASE.NOT), the
    NetBEUI and IPX/SPX protocol stacks that ship with Windows 95 do not
    currently support native FDDI NDIS 3.0 drivers.  We have repeatedly
    mentioned this to Microsoft, but feel free to post a bug report
    requesting this support.  It may help having customers (and not
    developers) asking.
    
>>We tried installing TCP/IP and the same results occur.  We then 
    
    TCP/IP is the only protocol supported and it does work over the DEFPA
    driver included in the FPKIT242.ZIP file.  Please reconfigure your
    system for TCP/IP only, and make sure that you add the IP address,
    subnet mask, and DNS addresses under TCP/IP properties.
    
    Finally, we are working with the PATHWORKS for Windows 95 development
    team to ensure that Digital's DECnet and LAT protocols are supported
    over the native FDDI NDIS 3.0 driver.
    
    Regards,
       Larry
    
1782.2Still no JoyCGOOA::VAOP05::SzostakAm I NIS or NAC ?Thu Aug 17 1995 21:308
Larry We have seen the release note but the problem we 
are seeing is the driver does not load the DEFPA LED 
remains flashing and we never get the Domain login screen 
in WIN95 startup.  The performance monitor on the NT server 
does not show any activity what so ever and yes the LED 
is flashing on the NT Server DEFPA card.  Any Ideas!!!

Richard
1782.3NETCAD::STEFANIMachines to humanizeThu Aug 17 1995 23:5732
>>Larry We have seen the release note but the problem we 
>>are seeing is the driver does not load the DEFPA LED 
>>remains flashing and we never get the Domain login screen 
>>in WIN95 startup.  The performance monitor on the NT server 
>>does not show any activity what so ever and yes the LED 
>>is flashing on the NT Server DEFPA card.  Any Ideas!!!
    
    I'm sorry, but if the LED is flashing or solid green, then the driver
    has indeed loaded.  The LED sequence for our adapters is such that the
    LED will *not* go to blinking/solid green unless the driver has
    initialized the adapter and issued the START command to the adapter.
    
    So, the driver is loaded.  Now, in Chapter 1 of the DEFPA owner's
    manual Table 1-2 describes the LED States.  A blinking green LED
    indicates a connection in progress or the cable is not attached.
    If you're connected point-to-point with the NT server and *both*
    adapters have a blinking green LED, then it means that you don't have a
    proper cross-over FDDI cable.
    
    Please check the cable.  If it's UTP, make sure the pinouts crossover
    as described in "UTP SAS Controller Pin Assignments" on page A-4 of the
    manual.  If it's multi-mode fiber, make sure the receive port of one
    adapter transceiver connects to the transmit port of the adapter
    transceiver, and vice-versa.  If the cable is a "straight-through",
    then you're connecting receive to receive and transmit to transmit. 
    Obviously, this will not work and the LED's will continue to blink
    green.
    
    A proper FDDI connection on our adapters would be indicated by a solid
    green LED.
    
       - Larry
1782.4NETCAD::STEFANIMachines to humanizeFri Aug 18 1995 00:1217
    I reread your original note and I'm assuming that you have removed the
    NDIS 2.01 16-bit driver (DEFPA.DOS) from your Windows 95 configuration,
    rebooted the system, then installed the NDIS 3.0 32-bit driver
    (DEFPA.SYS) from the A:\WIN95 directory.
    
    Unlike the NDIS 3.0 driver, the NDIS 2.01 driver doesn't shutdown the
    adapter (turn off the LED) during soft-reset (CTRL-ALT-DEL).  If you
    have the 32-bit driver (DEFPA.SYS) configured right now, please
    shutdown your Windows 95 station, then hit the reset button or power
    cycle to hard reset the adapter and turn off the LED.  On reboot, if
    the LED goes solid/flashing green, then we know for sure that the
    DEFPA.SYS driver loaded and issued the START command to the adapter.
    
    Once you're at this point, you need to get the FDDI connection secure
    and verify that the LED is solid green.
    
    - Larry
1782.5NETCAD::STEFANIMachines to humanizeThu Aug 31 1995 20:259
    re: .0
    
    Richard,
    
    Haven't heard from you in awhile.  Are your DEFPA/Windows 95 install
    problems fixed?
    
    Thanks,
       Larry