Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!INDYVAX.IUPUI.EDU!IJAH400 From: IJAH400@INDYVAX.IUPUI.EDU ("James A. Harvey") Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: 3c503 packet driver lockup problem Message-ID: Date: 14 Feb 90 19:00:00 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 30 I have found a way to consistently reproduce the lock-up problem with the 3C503 packet driver on a NCS 286 PC (the same problem has also been seen on PS/2 model 30s with the same card, but I haven't checked this on one of those yet). This was done bringing the system up with a bare-bones AUTOEXEC.BAT. The symptoms are the same whether I setup the packet driver initialization with any of the hardware interrupts 2, 4 or 5 (ones that the 3COM diagnositics claim are free on the machine), and either of software interrupts 61 or 62 hex (I'm using software interrupt 62 hex now on the advice of a technical support person from FTP Software). The following sequence *always* causes the machine to lock up: 1. Do a cold boot. Note the time on the second hand on your watch when the PC finishes it's diagnostic tests (it beeps). 2. Install the packet driver using 3C503.COM. Don't run any network applications (TN3270 or TELBIN). Just install the driver. 3. The PC locks up exactly 60 seconds after the time noted in (1). After experiencing the problem at least once, a warm boot (Ctrl/Alt/Del) followed by driver installation seems to work (er, not work) similarly except that you get 60 seconds from the time of the driver installation rather than the boot. Not being a PC "systems" wizard, I don't know the significance of the magical 60 second mark on the 286... - James Harvey IUPUI Computing Services, DEC Systems Group Internet: ijah400@indyvax.iupui.edu BITNET:ijah400@indyvax Disclaimer: Opinions expressed here are mine, not necessarily those of Indiana University