> The new 'reset' code in the NE2000 driver is causing some 'not-so-100%'
> NE2000's to not be recoqnized.. if you remove/#if 0 the reset code, they
> work great, like they did under 1.2.??, but under 1.3.??, they fail.
That reset code causes an even larger number of 'not-so-100%' NE2000's to
work that wouldn't work before, which is why it is there. You don't say how
yours fails. Does it give a "no reset ack" message, or what?
> It would be nice if it were a definable option.. much like NE_BAD_CLONES..
Yes, having it as a local user-defineable #ifdef option is reasonable.
I will add that sometime in the near future.
Paul.