[comp.sys.handhelds] Strange happening

persol@solan.unit.no (Per Solberg) (03/05/91)

I just tried to turn off my 48SX, but accidentally hit the on-button twice 
(rapidly), thus turning it on again. Trouble is, instead of resuming normal 
operation it came up with the following screen :

        STO Error:
        Object In Use
        4:
        3:                   { HOME }
        2:                   <3A07Fh>
        1:                   0: CCYES
        CCYES CC123 ALAR USER USER

OK, I cleared the stack and got back my VAR menu by pressing HOME (pressing VAR
didn't work) and tried to turn it off again. No luck. The same thing happened
again, so all of a sudden I was unable to turn off my calculator.
I figured GATEWAY caused the trouble, so I removed (uninstalled) it. Now it was
possible to turn off the calculator, but when I tried to reinstall GATEWAY I 
got an Undefined XLIB Name error. I turned the calculator off and then on
again; now the GATEWAY library had disappeared, but my port 0 contained an 
object named CCYES which contains <3A07Fh>.

Fortunately, I didn't lose any data, so I'll just go home and download GATEWAY
again. But I would like to know what happened, so if you have any ideas I would
appreciate it.

BTW : I have never had any problems with GATEWAY before. I have a rev. A 
      machine without plug-in cards.


Thanks


Per

erikmb@etek.chalmers.se (Erik Bryntse) (03/06/91)

In article <1991Mar4.173547.9674@ugle.unit.no> persol@solan.unit.no (Per Solberg) writes:
>
>I just tried to turn off my 48SX, but accidentally hit the on-button twice 
>(rapidly), thus turning it on again. Trouble is, instead of resuming normal 
>operation it came up with the following screen :
>
>        STO Error:
>        Object In Use
>        4:
>        3:                   { HOME }
>        2:                   <3A07Fh>
>        1:                   0: CCYES
>        CCYES CC123 ALAR USER USER
>
>OK, I cleared the stack and got back my VAR menu by pressing HOME (pressing VAR
>didn't work) and tried to turn it off again. No luck. The same thing happened
>again, so all of a sudden I was unable to turn off my calculator.
>I figured GATEWAY caused the trouble, so I removed (uninstalled) it. Now it was
>possible to turn off the calculator, but when I tried to reinstall GATEWAY I 
>got an Undefined XLIB Name error. I turned the calculator off and then on
>again; now the GATEWAY library had disappeared, but my port 0 contained an 
>object named CCYES which contains <3A07Fh>.
>

Hmm, this was interesting! What happened was that the execution of OFFC
was interrupted when you pressed ON the second time. But obviously
something else also happened. 

In Gateway the 0: CCYES object is used internally. In the beginning of
the OFFC program it does 0: CCYES DUP PURGE STO. This way the STO
operation will always work (or so I beleived). But I have noticed that
sometimes (more specifically when you recover memory) the objects in the
ports are duplicated. If this somehow happened when you pressed ON the
second time, this would account for the behaviour the next time you
ran OFFC. Since there were two 0: CCYES, PURGE only purged one of them.
And STO will not work if the object already exists in the port.

If this guess is correct, OFFC would have worked if you had tried it
another time, since there would only be one 0: CCYES object this time.

To figure out why you had problems installing GATEWAY again, I need to
know exactly how you did when you tried to install it again. To install
it again you need to have the library saved somewhere in user memory,
since it is removed from port 0 when uninstalling.

I hope this has cleared some of the questions!

Erik Bryntse

akcs.scotty@hpcvbbs.UUCP (SCOTTY THOMPSON) (03/11/91)

When I was playing with the libraries, in my $CONFIG code I specifically
told the maching to do a DEPTH \->LIST 'stk' STO because I wanted to see
if I could save the stack so that the user wouldn't lose it if he/she
installed my library.  When I looked, I got the same kind of stuff on my
screen.  I think your problem appeared because GATEWAY's a library (?). 
Something weird must happen with that software, anyway, but I would guess
that this happened because your computer was trying to configure itself
and GATEWAY's code interferred with it (?)  Just guessing, since I don't
have GATEWAY and don't intend on getting it.  Scott