Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!grian!alex
From: alex@grian.cps.altadena.ca.us (Alex Pournelle)
Newsgroups: comp.unix.xenix.sco
Subject: wierd 386 error
Keywords: AMI cron failure
Message-ID: <1991Mar14.085304.4906@grian.cps.altadena.ca.us>
Date: 14 Mar 91 08:53:04 GMT
Organization: Workman & Associates
Lines: 21

I ran into a really really wierd one today--thought I'd share it with
you.

System that previously worked fine, suddenly stopped --when booted up,
it wouldn't get past cron startup.  Just crashes.

Looked at it for a while -- suddenly realized that the customer had
taken the printer away, but left the parallel printer cable connected.
Removed it, rebooted, and it's fine.  What could have been a panicky
multi-hour problem turned out to be ten minutes' luck.  Damfino how a
simple cable could cause cron to hang, though.

ANY idea?  Cable seems fine, on MS-DOS systems.  You'll understand I'm
not too interested in trying it on the XENIX system!

	Alex
-- 
		Alex Pournelle, freelance thinker
		Also: Workman & Associates, Data recovery for PCs, Macs, others
		...elroy!grian!alex; BIX: alex; voice: (818) 791-7979
		fax: (818) 794-2297    bbs: 791-1013; 8N1 24/12/3