| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2095.1 | | NETCAD::STEFANI | | Mon Jul 29 1996 11:55 | 42 |
| Scott,
Please, please tell me who is responsible for writing these reports?
I have yet to see ONE of these reports that are DEFEA or DEFPA related
be 100% accurate.
Since you seem to be "in the know", please find out whether there's a
chance that I can be part of the review board for future DEFEA or DEFPA
related problem reports.
>>CAUSE
>>=====
>>
>>This problem occurs due to firmware problems on the network adapter.
>>Certain chipsets of the adapter causes any registered broadcast addresses
>>to clear during the adapter reset. DEFPA.SYS and DEFEA.SYS drivers reset
>>the adapter for a variety of conditions reported by the adapter during
>>normal use.
Incorrect. This is not, and never was a firmware problem. Both the
DEFEA.SYS and DEFPA.SYS drivers (v1.57) had a bug in which the
BROADCAST address (FF-FF-FF-FF-FF-FF) filter would be disabled during
software reset. When issuing a SW reset of the adapter, all of the
filters are disabled and any modified FDDI settings are returned to
their default values. The driver is responsible for maintaining the
filter settings, multicast addresses, node address override, etc. and
wasn't doing it properly for the Broadcast Address Filter.
The latest DEFEA.SYS and DEFPA.SYS driver (v1.82) that ships in the
v2.7 DEFEA and DEFPA SW kits fixes this problem. I'm sure that
Microsoft has already introduced updated drivers into the NT source
pool that does the same. However, it's likely that MS's DEFEA.SYS and
DEFPA.SYS drivers are still labeled "v1.57" which makes discovering
the new driver more difficult.
If it's possible, I'd like this report to be updated. Users shouldn't
be worried that their DEFEA or DEFPA HW or firmware is bad.
Thanks for posting this note.
- Larry
|
| 2095.2 | rptd to MS as SRZ 960729-000605 | CSC32::BINGHAM | Scott Bingham �� Windows NT / BackOffice Team, USCSC | Mon Jul 29 1996 17:51 | 15 |
| Hello Larry,
I do not know who creates the MSKB articles; I believe that it is
the PSS group in Microsoft. PSS is their software support group, not
an engineering group.
I have informed Microsoft that their article is in error, via
problem report SRZ 960729-000605.
As to a review board: I doubt that there is any such thing, in
such a formal sense.
As always, thanks for your response.
_Scott
|
| 2095.3 | | NETCAD::STEFANI | | Mon Jul 29 1996 19:35 | 16 |
| >> As to a review board: I doubt that there is any such thing, in
>>such a formal sense.
OK, then I'll suggest the following. Your group monitors the MSKB
articles and anything that is Digital NIC related gets forwarded to the
following folks:
Mike Paquette (NETCAD::PAQUETTE) - Adapter Engineering Manager
Janice Ferguson (NETCAD::FERGUSON) - EtherWORKS SW Team Leader
Larry Stefani (YESWAY::STEFANI) - FDDI SW Team Leader
We can then make sure that the articles are accurate, then report back
to you.
Thanks,
Larry
|
| 2095.4 | | CSC32::BINGHAM | Scott Bingham �� Windows NT / BackOffice Team, USCSC | Tue Jul 30 1996 13:27 | 11 |
| > OK, then I'll suggest the following. Your group monitors the MSKB
> articles and anything that is Digital NIC related gets forwarded to the
More accurately, we stumble over MSKB articles as customers bring
them to our attention. :-) But thanks for the list; I'll use it.
I have more info on this particular article that I will forward to
you.
Thanks,
_Scott
|