ON+C+Backspace -> TRM
John H Meyers
configs from executing), I invariably get a TRM
("Try To Recover Memory").
The only way I can avoid this is to rename STARTUP
(or to purge it).
Anybody else in this boat?
(you'd better have a current backup handy before trying!)
Of course, no matter what STARTUP contains, it is my opinion
that the only way to fix this potential problem is to make sure
that STARTUP is *also* bypassed when Backspace is held down;
otherwise there would exist no way to bypass STARTUP
as well as bypassing library configs, n'est ce pas?
After all, the ability to rename STARTUP can be made difficult
by not being able to regain control of the calc at all,
and by losing all of memory as well.
My startup begins by doing { 256. 257. 258. } ATTACH
and then it may recall and/or set an alarm; this is already
enough to invariably cause the TRM, but as I said, there
ought to be a way to avoid executing *anything* after ON+C --
no configs, no extprogs, and no STARTUP -- do you not think so?
A temporary work-around to prevent STARTUP from executing
is to insert the following at the beginning of STARTUP:
\<< KEY { DROP 0. DOERR } IFT ...
However, when config and STARTUP have been bypassed,
my alarm-setting procedure will still cause a subsequent TRM,
which suggests that there is something to be fixed
(does some internal ROM library fail to get set up properly?)
BTW, how does "extable" (library 258) still get
into the LIB menu if all configs are bypassed?
(note that 258 DETACH removes it from the LIB menu).
-----------------------------------------------------------
With best wishes from: John H Meyers <jhme...@mum.edu>
Sent via Deja.com http://www.deja.com/
Before you buy.
John H Meyers
with ON+A+F+No, then doing ON+C+Backspace,
any attempt to then access alarm functions
(e.g. TIME -> Browse alarms) will get you either some
garbage or a total lock-up (have paper clip handy;
a pre-made computer backup file is also advisable).
I believe that this should be called a bug,
and I still suggest having ON+C+Backspace
automatically skip STARTUP.
Homer Simpson
only does 1 MENU (the attachments and other stuff are done by a program I
call from CST once the warmstart is really over).
>Further investigation reveals that after emptying memory
>with ON+A+F+No, then doing ON+C+Backspace,
>any attempt to then access alarm functions
>will get you either some garbage or a total lock-up
And Kermit messages are messed-up too (but the transfer itself is ok).
>I believe that this should be called a bug,
Well, I don't know... BS is supposed to allow you to solve a problem (in
general, erase a bad library in port 2), and then to reboot.
>and I still suggest having ON+C+Backspace
>automatically skip STARTUP.
Yes. STARTUP may be dangerous as well.
>BTW, how does "extable" (library 258) still get
>into the LIB menu if all configs are bypassed?
Well, almost all libraries appear in the lib menu after a ON-C/BS on ver
1.17-2, although config objects don't seem to have been executed (I have one
that dispays something, and it's obviously been skipped by BS). The HP
probably attaches all libraries it finds... Somehow.
Homer Simpson
http://zap.to/hsimpson
Detlef Mueller
> [..]
> BTW, how does "extable" (library 258) still get
> into the LIB menu if all configs are bypassed?
> (note that 258 DETACH removes it from the LIB menu).
Attaching a library to a directory registers it's XNAMEs to
the uRPL editline compiler (w/in that context), most libs do
that o-matically from w/in their configuration object. The
ExtPrg mechanic isn't connected to this in any way, if it
exists in an installed library, it'll be called upon the APPS
build-up. Note that a library gets installed (aka registered,
ie. added into the ROMPTAB) when stored (that's the reason for
the "jumping" screen) or during a WS when initially building
the ROMPTAB (on the 48 this was different, it was only able to
add a lib during WS to the ROMPTAB -- this was the reason for
the o-matic WS after storing a lib and then power-cycling the
48 (unless you'd installed <-LIB->, using its STO command ;))
Ciao,
Detlef
--
`Let's get some cards and play Magic' Detlef Mueller
-- Gex detlef (@) provi (.) de
http://www.provi.de/~detlef
PGP Public Key: http://pgp.ai.mit.edu:11371/pks/lookup?op=get&search=0x524F4049
!!! ATTN !!! To reach my via e-mail, do _NOT_ auto-reply !!!
Jean-Yves Avenard
I've changed the behavior on Backspace during boot sequence in the next ROM
forthcoming (1.17-3)
Now instead of attaching all the libs without executing the config object,
it will simply load the built-in libraries..
So if you press BackSpace during the boot sequence (just when it starts) it
will install only the built-in libraries. User libraries will be skipped and
it won't be possible to use them until you reboot the calculator. It's more
like the SafeMode in Windows NT/95.
As only build-in libraries are installed in the ROMPTAB area, even if you
attach the user library manually it won't work..
It means also, that EXTPRG will be disabled during this session..
It's safer and fix all the problems reported by John.
Cheers
Jean-Yves
"Detlef Mueller" <I.h8...@dont.even.try> wrote in message
news:qrgyrscebivqr....@news.hamburg.pop.de...
Homer Simpson
>forthcoming (1.17-3)
Excellent! I already find the OS of the HP49 very stable, but it's going to
be almost bullet-proof with this change.
>It's more like the SafeMode in Windows NT/95.
Er... You're not trying to make a kind of Windows, are you?
Homer Simpson
http://zap.to/hsimpson
Matt Maurano
<aven...@epita.fr> wrote:
>I've changed the behavior on Backspace during boot sequence in the next ROM
>forthcoming (1.17-3)
>it will simply load the built-in libraries..
Could it also disable STARTUP?
>So if you press BackSpace during the boot sequence (just when it starts) it
>will install only the built-in libraries. User libraries will be skipped and
>it won't be possible to use them until you reboot the calculator. It's more
>like the SafeMode in Windows NT/95.
Let's call it single user mode, or extensions off. :-) . It won't be
safe mode until it thrashes the disk for ten minutes trying to work
around a backasswards architecture, then boots and prints "Safe Mode"
in outlined font in each corner of the screen (See, Microsoft has
learned that UI principle: put the most innane, non-functional objects
into the most useful parts of the screen).
Matt Maurano
wrote:
>Could it also disable STARTUP?
Oops! Looks like it does. Cool!
Veli-Pekka Nousiainen
They did it already (the default-mode)
and it is much worse than just Microshit-Windowz:
look at my signature !!!
--
Regards, VPN
_________________________________________________________
Veli-Pekka Nousiainen ; e-mail= v...@fcsolutions.com
Sokinsuontie 3 A 1, FIN-02760 Espoo, Finland
TEL, WORK= +358 (9) 859 2025 ; (WORK2= +358 (3) 4728 300)
Future Computing Solutions Oy ; URL= http://www.eiffel.fi
_________________________________________________________
;-) We R TiBORG - Res. is Futile - Ur 49 ~ Assimilated !
Homer Simpson <hsam...@lemel.fr> wrote in message
news:84dmgf$hsg$2...@front7.grolier.fr...
> >I've changed the behavior on Backspace during boot sequence in the next
ROM
> >forthcoming (1.17-3)
>
> Excellent! I already find the OS of the HP49 very stable, but it's going
to
> be almost bullet-proof with this change.
>
> >It's more like the SafeMode in Windows NT/95.
>