Conference noted::etherworks

    
    Are they running the most recent version of the DEFPA.LAN driver
    (v3.30)?
    
    -Brenda

    yes for sure
    
     thanks
    
     JYP

>> my customer claims about Compatibility problem between Compaq Proliant
>> 1500 running Netware V4.1 and DEFPA Firmare 2.80 or 2.81, just SPX
>> doesnt work correctly in this configuration, replacing DEFPA with Compaq
>> FDDI board solved the problem or replace Proliant by Priorix Too.

Just FYI - The Compaq FDDI controllers are actually OEM'd SysKonnect FDDI
adapters.

"Compatibility problems" is not being specific.  Does the driver load
successfully?  If so, does the green LED come on on the back of the adapter. 
If so, is the green LED solid which indicates that you have a valid FDDI
connection?  If so, can you get a client to connect at all?  We need details.

We do know of a hardware incompatibility with DEFPA and Intel Triton
motherboards.  That specific hardware issue only affects original DEFPA-AA,
DEFPA-DA, and DEFPA-UA adapters (Rev. C or D etch).  Does the 1500 use Triton
host-chip set?

- Larry

  Thanks  larry for your reply,

  in fact it's an intermittent problem, all seems ok including leds on
  board and loading of drivers , IPX works but sometimes customer looses
  some services running with SPX protocol like Rconsole.

  i don't known about the chipset on 1500 but i try to find the information
  which should be the symptom if we are faced to this incompatibility issue ?


  thanks

  Jean-Yves 

>>  in fact it's an intermittent problem, all seems ok including leds on
>>  board and loading of drivers , IPX works but sometimes customer looses
>>  some services running with SPX protocol like Rconsole.
>>
>>  i don't known about the chipset on 1500 but i try to find the information
>>  which should be the symptom if we are faced to this incompatibility issue ?

From your symptoms, it doesn't sound like the Triton-chipset problem.  That
particular problem would present itself as a bus lockup or overall failure of
the card.  What you're describing definitely sounds like a higher-layer SW
issue since the driver and adapter are providing you with some level of
connectivity.

You should verify that you've set the MAXIMUM PHYSICAL RECEIVE PACKET SIZE
setting to at least 4500 bytes.  Beyond that, you should make sure that you
have installed all of the latest NetWare patch kits including LANDRx.EXE. 
RCONSOLE should definitely work over DEFPA.  The driver and card don't care
what kind of packets are sent, so I don't see an immediate reason why SPX
should have trouble, but not other protocols.

- Larry

    thanks larry,
    
    did you test defpa with proliant series ?
    
    i'll check your ideas,but since it's work great with compaq FDDI
    adapters customer won't go back to Dec FDDI board

>>    did you test defpa with proliant series ?

Not explicitly.  However, we've had a good working relationship with COMPAQ in
the past and they have let us know when interoperability problems have come up
between our controllers and their systems.  For example, if you check out the
Novell Labs certification bulletins you'll find many COMPAQ systems that were
certified under NetWare SFT III using Digital FDDI adapters for the MSL link.

>>    i'll check your ideas,but since it's work great with compaq FDDI
>>    adapters customer won't go back to Dec FDDI board

Well, that's their loss.  It's certainly a fact that the DEFPA outshines the
SysKonnect PCI FDDI boards and having them relabeled to COMPAQ won't change
that.

Regards,
   Larry