Hi,
The main reason I know this happens is because of poor designing of a
state machine, a source of common error in digital systems. Oftentimes,
the machine starts off in a so called "unused state"...and it is the
responsibilty of the designer that an unused state advances to a normal
one automatically. As reality goes...this doesn't happen always.
peace...
Adit
================================================================
"...if you smack the ball hard enough, then you don't have to run."
================================================================
On Wed, 16 Dec 1998, holotko wrote:
> "James [on his mailserver]" wrote:
> >
> > A bit off topic, but interesting nontheless;
> >
> > i crashed my mobile phone!
> >
> > Panasonic G450, UK Vodafone
> >
> > it said Lo Battery, i pressed a key (probably 5) and the backlight came
> > on, then the battery ran out and it said Phone Shutting Down and stayed
> > that way until i removed it's battery! when i tried to power it up it
> > didn't, had to plug the charger in...
> >
> > anyone else had any weird experiences with embedded programs like this?
> > (i seem to have a knack at making things fail, it's happened to my Atari
> > Lynx, Personal CD Player (i could make the backlight flash patterns!) and
> > my MD recorder killed a disc for no good reason)
> >
>
> Yeah, they do some wierd things every now and then for a wide variety
> of reasons. Sometimes just shutting the device off for a while &
> removing the power supply or a battery, letting it sit for awhile and
> then power it up again and they seem to work fine again. I've had
> several such devices fail and after a breif "cooling off period", of a
> few hours to a day or so, they all started working fine again.
>
>
> --
> email: [EMAIL PROTECTED]
> Local mailserver <landreau.ruffe.edu> , remote <ns.computer.net>
>
> Smoke a Lucky Strike!
