Hi all,
Sorry guys, but here are some other DM41X bug on HEPAX module this time...
for the record :
- I only use LIB#4 and HEPAX4H, and I am on f/w 2.1
- No syntetics just plain old FOCAL programs
Start with some programs already in HEPAX...
do a RESET (ON + Backspace) of the calculator
HEPDIR gives a "H:NO FILESYS" (normal)
Now, (re)load one of the program that was in HEPAX before reset onto the main memory using
SETUP, 1, 3 then choose the raw program (let's call it PROG)
Now try to load this program in HEPAX again using
ALPHA PROG ALPHA
HSAVEP
you get a "PACKING" + "H:NO FILESYS" (first bug?)
you can try as many time HSAVEP as you want it always says "PACKING" + "H:NO FILESYS"
Now... just shut OFF the calculator and put it back ON again
You still have PROG in alpha
do again a HSAVEP... it works this time = "PACKING" + "SAVING" + "COMPILING" (second bug or same bug?)
Now interesting part... do a HEPDIR again... and tadaaaaaa!!!
You find the all former programs that were in HEPAX memory before RESET! (second bug or third bug?)
I know that all these 3 are certainly the same bug
PS: maybe I should stop using the DM41X for a while
HEPAX module bug this time
HEPAX module bug this time
Sincèrement, Sincerely, 73,
Boubker
DM15L, DM41L, DM42 #00855 (domes upgraded), DM41X #00707
HP48SX (with dark screen), HP42s, HP32SII (1990 with fraction bug), HP41C/CV
TI-89 titanium, CASIO fx-cg50 and Numworks (to play with micropython)
Boubker
DM15L, DM41L, DM42 #00855 (domes upgraded), DM41X #00707
HP48SX (with dark screen), HP42s, HP32SII (1990 with fraction bug), HP41C/CV
TI-89 titanium, CASIO fx-cg50 and Numworks (to play with micropython)
-
- Posts: 58
- Joined: Mon Jan 13, 2020 4:49 pm
- Location: Netherlands
Re: HEPAX module bug this time
I do not think this is a DM41X bug, but rather normal HEPAX behavior. Have a look at the HEPAX Volume 1 manual page 62. It mentions there that a Memory Lost followed by a HEPAX file operation may result in the NO FILESYS message. Two OFF/ON cycles will restore the filesystem, and obviously any previous contents may still be available. Only the HEPAX module chain was broken, and the contents were not erased by the Memory Lost. If this is the case in a real HEPAX I do not know, but I would not qualify this as a DM41X bug, but as pretty good HEPAX implementation of it.
Regards from NL,
Meindert Kuipers DM41X #48
Meindert Kuipers DM41X #48
Re: HEPAX module bug this time
Thanks for that info Meindert!
I somehow missed this bug report, and just found it today; I'm glad to see the issue is not a 41X bug, but the way things should be.
So...
Thanks Boub65 for the report
Thanks Meindert for the research and explanation
Thanks Angel for the HEPAX 4H module
Thanks David for the high-fidelity 41X emulation.
I somehow missed this bug report, and just found it today; I'm glad to see the issue is not a 41X bug, but the way things should be.
So...
Thanks Boub65 for the report
Thanks Meindert for the research and explanation
Thanks Angel for the HEPAX 4H module
Thanks David for the high-fidelity 41X emulation.
--bob p
DM42: β00071 & 00282, DM41X: β00071 & 00656, DM10L: 071/100
DM42: β00071 & 00282, DM41X: β00071 & 00656, DM10L: 071/100
-
- Posts: 328
- Joined: Wed May 24, 2017 10:44 pm
- Location: Vancouver Canada
- Contact:
Re: HEPAX module bug this time
And thanks Bob!
Cheers, Geoff
Cheers, Geoff
Re: HEPAX module bug this time
Meindert explained it perfectly. (as usual)
I also confirm this behavior on Diego's NoV modules with -HEPAX 1D implementation.
I have only tested it with a NoV-64 module but it should be the same for all the others: NoVRAM, NoV-32 and NoV-64d.
Sylvain
PS: hello Geoff, nice to see you back! (I will reply to your email soon)
It is.MeinKuipers wrote: ↑Tue Aug 17, 2021 2:20 pmI do not think this is a DM41X bug, but rather normal HEPAX behavior.
Always .... well should be, I have not tested all the file functions but the ones I have tested, showed me the same message.MeinKuipers wrote: ↑Tue Aug 17, 2021 2:20 pmIt mentions there that a Memory Lost followed by a HEPAX file operation may result in the NO FILESYS message.
CorrectMeinKuipers wrote: ↑Tue Aug 17, 2021 2:20 pmTwo OFF/ON cycles will restore the filesystem, and obviously any previous contents may still be available.
Only the HEPAX module chain was broken, and the contents were not erased by the Memory Lost.
I can confirm this behavior with the original HEPAX prototype (-HEPAX 0C) module that I have. (graciously restored by Diego)
I also confirm this behavior on Diego's NoV modules with -HEPAX 1D implementation.
I have only tested it with a NoV-64 module but it should be the same for all the others: NoVRAM, NoV-32 and NoV-64d.
Sylvain
PS: hello Geoff, nice to see you back! (I will reply to your email soon)
[DM1x/DM1xL/DM41/DM41L/DM41X/DM42]
-
- Posts: 328
- Joined: Wed May 24, 2017 10:44 pm
- Location: Vancouver Canada
- Contact:
Re: HEPAX module bug this time
No rush, take care and hope to see you in October if we are allowed to travel to the US or in montreal if not. Umm Schwartz’s smoked meat sandwiches!
Re: HEPAX module bug this time
Thank you all for your replies.
So I understand that it is "normal" behavior
So I understand that it is "normal" behavior
Sincèrement, Sincerely, 73,
Boubker
DM15L, DM41L, DM42 #00855 (domes upgraded), DM41X #00707
HP48SX (with dark screen), HP42s, HP32SII (1990 with fraction bug), HP41C/CV
TI-89 titanium, CASIO fx-cg50 and Numworks (to play with micropython)
Boubker
DM15L, DM41L, DM42 #00855 (domes upgraded), DM41X #00707
HP48SX (with dark screen), HP42s, HP32SII (1990 with fraction bug), HP41C/CV
TI-89 titanium, CASIO fx-cg50 and Numworks (to play with micropython)
-
- Posts: 58
- Joined: Mon Jan 13, 2020 4:49 pm
- Location: Netherlands
Re: HEPAX module bug this time
This shows how perfect the DM41X implementation of HEPAX is!pcscote wrote: ↑Sat Sep 04, 2021 5:15 pmMeindert explained it perfectly. (as usual)
It is.MeinKuipers wrote: ↑Tue Aug 17, 2021 2:20 pmI do not think this is a DM41X bug, but rather normal HEPAX behavior.
Always .... well should be, I have not tested all the file functions but the ones I have tested, showed me the same message.MeinKuipers wrote: ↑Tue Aug 17, 2021 2:20 pmIt mentions there that a Memory Lost followed by a HEPAX file operation may result in the NO FILESYS message.
CorrectMeinKuipers wrote: ↑Tue Aug 17, 2021 2:20 pmTwo OFF/ON cycles will restore the filesystem, and obviously any previous contents may still be available.
Only the HEPAX module chain was broken, and the contents were not erased by the Memory Lost.
I can confirm this behavior with the original HEPAX prototype (-HEPAX 0C) module that I have. (graciously restored by Diego)
I also confirm this behavior on Diego's NoV modules with -HEPAX 1D implementation.
I have only tested it with a NoV-64 module but it should be the same for all the others: NoVRAM, NoV-32 and NoV-64d.
Sylvain
PS: hello Geoff, nice to see you back! (I will reply to your email soon)
Regards from NL,
Meindert Kuipers DM41X #48
Meindert Kuipers DM41X #48