[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

1262.0. "Big Problems with DEFEA-UB in DECPC 466d2MTE" by VNABRW::BOECK_P (Peter BOECK @AUI) Fri Mar 04 1994 04:55

For a test on customer-site I want to setup a TP-PMD connection between 2 PC's
The first one is OK (DEC PC 420 ST), but I am not able to install the DEFA in the 
DECPC466d2 MTE:

Instver (version from DECWRL::/.../defeaV23.zip) reports following errors:

DMA loopback tests 4,8,16 LW Burst   FAILED
DMA Bus loading Test 1 to 3          PASSED
DMA Bus loading Test 3 to 9          FAILED

Error code is always (without leading Zeros): 9   606   b0    400

Instver is also not able to Read Ethernet-adress and Firmware version.

Loopback Test fails.


I have tried this with different IRQ's and Memory-ranges: Same result or more
errors in instver.


Further Info:

Phoenix E486 Bios Ver. 1.00
ROM-Shadowing disabled (D0000 and further).
S3 Video adapter (Standard 466 MTE Hardware configuration).


A fast help is required, because tests should start at March, 9th.


Peter Boeck @AUI
Building Integration Services vienna
VNABRW::BOECK_P

T.RTitleUserPersonal
Name
DateLines
1262.1Problem is DEFEASCHOOL::PAQUETTEFri Mar 04 1994 08:2733
Hi,
	There is a recently discovered problem with the DEFEA module.  The
problem is a timing bug.  Recent revs of the DECpc 466d2 MTE apparently have
a new EISA chip set that has more crisp timing than the old ones  (still well
within spec, though.)  This new timing causes the DEFEA bug to show up via 
the failing diagnostic DMA loopback test.  

This DEFEA/MTE problem is well understood and fixes have been developed
for both DEFEA Rev A01 boards, and DEFEA Rev B01 boards.  An ECO is currently
being written and modified boards are being tested as we write.  

I expect that the ECO will be written in the next few days.

The DECpc 466d2 MTE is the ONLY system in which we have seen this problem.
Has anyone seen this failure in a different system?  DEC or otherwise?

Now to solve your problem for the March 9th testing:
REAL SOLUTIONS:
 - You will NOT be able to get an ECO'd board from manufacturing in this 
   timeframe. 
 - All fixed boards that engineering has are currently in testing, but 
   contact me via email to see if we can work something out.
EMERGENCY HACK FIXES:
 - Get another ST class machine to replace the MTE
 - We have been able to make failing modules pass in the '466d2 MTE by 
   simply adding another EISA card (any type) to the system.  Is the DEFEA 
   the only EISA card in the machine?
 - Do you have a competent technician with soldering iron?  The fix is 
   straightforward; one pin cut and one wire add.  Contact me if this is
   an option.

	Mike Paquette
	High Performance Networks Adapters Group
1262.2Changed from 466MTE to JENSEN -> Another problemVNABRW::BOECK_PPeter BOECK @AUIFri Mar 04 1994 10:2918
Thank you very much for your prompt answer.
In the meantime we have "captured" a JENSEN.

But there is another problem:

When installing the driver, NT always asks for "Windows NT Setup Disk 1" in
Drive A:.
We only have the kit on CD-ROM.

Is there a solution ? Or bug in OEMSETUP.INF.

This is valid for Driver version 2.3

When using the driver-diskette, encluded with the DEFEA (Ver. 2.2) WinNT can
not find OEMSETUP.INF.

Many regards
Peter
1262.3Get latest kit, then specify pathQUIVER::STEFANIHave the # for the Mars Observer?Fri Mar 04 1994 14:2020
>>This is valid for Driver version 2.3
>>
>>When using the driver-diskette, encluded with the DEFEA (Ver. 2.2) WinNT can
>>not find OEMSETUP.INF.
    
    Two things.  First, grab the latest DEFEA driver diskette (V2.3) off
    any of the following places:
    
    	KALI::PCDRIVERS:FEAV23.ZIP
    	OS2LAN::OS2:[PUBLIC.COMPUSRV.LANCONTR]FEAV23.ZIP
    	DECWRL::"/pub/DEC/FDDI/EISA/defeav23.zip"
    
    Next, when installing the Windows NT driver for Alpha AXP, change the
    directory path from A:\ to A:\WINNT\ALPHA\.  Windows NT should then find
    the proper OEMSETUP.INF file and the DEFEA.SYS driver for Alpha.
    
    Please let us know if this works by replying to this note.  Thanks!
    
    Larry Stefani
    FDDI/ATM Adapters Engineering
1262.4Happens after installing driver from diskette!VNABRW::BOECK_PPeter BOECK @AUIMon Mar 07 1994 02:4518
Sorry, I did not describe the error correctly in my Reply 2!

When installing the driver, NT is doing this from diskette correctly, but after
that, NT tries to load some additional files from "Windows NT Setup Disk #1" and is
looking on drive A:.

WNT displays a Box with the Text "Insert Windows NT Setup Disk #1 in Drive A".
There is only a OK and a CANCEL-button. Therefore it is not possible to install
these files from CD-ROM.

Network is not starting up OK after a reboot.

How can we fix this, because there is no distribution Kit for WNT on diskettes in
our location.


Many regards
Peter
1262.5QUIVER::STEFANIHave the # for the Mars Observer?Mon Mar 14 1994 05:285
    re: .4
    
    Problem solved off-line.
    
       - Larry