Path: utzoo!attcan!uunet!lll-winken!ames!xanth!nic.MR.NET!shamash!com50!bungia!orbit!pnet51!steve
From: steve@pnet51.cts.com (Steve Yelvington)
Newsgroups: comp.sys.atari.st
Subject: Infinite reboots
Message-ID: <452@orbit.UUCP>
Date: 7 Jan 89 19:25:08 GMT
Sender: root@orbit.UUCP
Organization: People-Net [pnet51], Minneapolis, MN.
Lines: 29


 
My ST seems to have gone insane. I received a new unit the day after
Christmas, replacing my trusty 520 that had blown a disk controller. It worked
just fine until last night, when I was working on writing a desk accessory
startup module for Sozobon C. I got a demonstration DA up and running to the
point that it had registered in the DA menu, but I couldn't "wake it up."
After two or three clicks on the menu item, my ST rebooted itself.
 
I gave up and went to bed after first setting up the event-scheduler that runs
UUMAIL. But instead of finding mail this morning, I found a "keyboard
interrupt" message from the event-scheduler -- 60 seconds before it was to
call, when nobody in the house was up -- and a nice little row of bombs.
 
Now I find that I can't even get the system to boot in a stable fashion. I can
get the Desktop to come up, but ANY mouse event -- just bumping the mouse --
causes a reboot. Keystrokes do not appear to cause a problem unless they're
the alt-key combinations that move the mouse.
 
What the heck is going on? And do Atari's replacement units come with a
warranty?

UUCP: {rosevax, crash}!orbit!pnet51!steve
ARPA: crash!orbit!pnet51!steve@nosc.mil
INET: steve@pnet51.cts.com
  -----------
  -or-
  stag!thelake!steve@pwcs.StPaul.GOV
  "A member of STdNET -- the ST Developers' Network"