Xref: utzoo comp.protocols.tcp-ip.ibmpc:4020 comp.protocols.tcp-ip:13437
Path: utzoo!attcan!uunet!wuarchive!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!rsiatl!jgd
From: jgd@rsiatl.UUCP (John G. DeArmond)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.protocols.tcp-ip
Subject: Re: 3c523 packet drivers -- what's the trick?
Message-ID: <4409@rsiatl.UUCP>
Date: 21 Oct 90 08:11:55 GMT
References: <1990Oct21.051918.5813@naitc.naitc.com>
Followup-To: comp.protocols.tcp-ip.ibmpc
Organization: Radiation Systems, Inc. (a thinktank, motorcycle, car and gun works facility)
Lines: 26

karl@naitc.naitc.com (Karl Denninger) writes:

>HELP!

>We're trying to get a few PS/2s running with the packet drivers, and are
>having no luck at all.  All we get is a "Timed out initializing board"
>message...... and no function!

I had the same problem last year.  I stumbled onto a work-around that
you probably won't like. :-)  I found that if an old beta version of
the driver was loaded, the machine warm booted and then the new version
loaded, everything worked OK.  Great, eh?

One must assume that some memory location is getting twiddled by one
or the other but I never had time to run this one down.  If you find
out what it takes to make the new ones work, I'd appreciate hearing.
Since terminal emulation is about all a PS/2 is good for, I expect
to run into a couple more someday.

John

-- 
John De Armond, WD4OQC  | "The truly ignorant in our society are those people 
Radiation Systems, Inc. | who would throw away the parts of the Constitution 
Atlanta, Ga             | they find inconvenient."  -me   Defend the 2nd
{emory,uunet}!rsiatl!jgd| with the same fervor as you do the 1st.