Very Computer

by **rory ork** » Sat, 28 Feb 1998 04:00:00

I have the following system.. 200mhz pentium .. 64 meg.. Adaptec
2940uw.. Arnet smartport 16. (just returned from service for similar problem
but was ok for 2 months-- latest rev drivers.. )

xxevent (0x00000000) port 0x00000000E, cmd 0x00000080,
b00x0000001b, b10x00000019.. As I said we were having similar events &
returned the smartport & updated drivers.. This seemed to clear up the problem
for a couple of months..
Any help appreciated.

TIA

by **Robert Li** » Sat, 28 Feb 1998 04:00:00

Quote:> I have the following system.. 200mhz pentium .. 64 meg.. Adaptec
>2940uw.. Arnet smartport 16. (just returned from service for similar problem
>but was ok for 2 months-- latest rev drivers.. )
>xxevent (0x00000000) port 0x00000000E, cmd 0x00000080,
>b00x0000001b, b10x00000019.. As I said we were having similar events &
>returned the smartport & updated drivers.. This seemed to clear up the problem
>for a couple of months..

My guess is that the port that's silkscreened "15", the next to the last
one, is getting character errors or overruns somehow. This could be
cabling, line noise, or just plain bad data coming in on the port. I
fear I don't recall the exact bit patterns, but you could do worse that
to invesigate my guesses.

I think there were some driver changes recently (the last couple of quarters)
on that combination.

--

by **rory ork** » Mon, 02 Mar 1998 04:00:00

I believe that is a printer port so if it is not a cable problem then I guess
a buffer/flow control problem..

>> I have the following system.. 200mhz pentium .. 64 meg.. Adaptec
>>2940uw.. Arnet smartport 16. (just returned from service for similar problem
>>but was ok for 2 months-- latest rev drivers.. )

>>xxevent (0x00000000) port 0x00000000E, cmd 0x00000080,
>>b00x0000001b, b10x00000019.. As I said we were having similar events &
>>returned the smartport & updated drivers.. This seemed to clear up the problem

>>for a couple of months..

>My guess is that the port that's silkscreened "15", the next to the last
>one, is getting character errors or overruns somehow. This could be
>cabling, line noise, or just plain bad data coming in on the port. I
>fear I don't recall the exact bit patterns, but you could do worse that
>to invesigate my guesses.

>I think there were some driver changes recently (the last couple of quarters)
>on that combination.

Very Computer

xxevent help

xxevent help

xxevent help

xxevent help