Upgrading an HP 50g Calculator ROM (to 2.15), Using a SD Card

Post by lacro37
Followed thoroughly the method explained in the PDF instructions
included with the 2.14-2 upgrade*, BUT for the 2.15 Release.
After the last Step #4, and the few seconds of the UPDATE routine, a
message ended the 0X0003*FF0 sequence with the message,
READ CARD TIMEOUT
WAIT RESET OR ENTER
Tried these three (3) last options without success, even the paperclip
method to RESET, but after it the previous screen keeps stating,
FLASH NEED UPDATE
1 USB
2 CARD
BOOT V4.01.03.03
Serial CNA 6202070
I pressed Option #2 only to get the Calculator in an endless loop that
kept it on, all night long and can't find the way out (even removing
the batteries). As a matter of fact I can't even turn it off...!!!
That's why I'm eager to find a solution to the situation.
Noticed >the UPDATE Process took much more time (# screens)< in the
uploaded / published videos I watched here, http://youtu.be/QttezbbytsM
as well as thehttp://hpcalc.gaak.org/?id=vid
After so many tryouts, could a new set of batteries make the trick?
They were almost new in the beginning.
Any comments are welcome! Tks in advance.
The last procedure step of the (ON F4) (ON F3) (+-) Sequence was not
easy to achieve.
Couldn't find this exact situation situation anywhere else.

Is your SD card >2GB? If so, it isn't an SD card but an SDHC. This
won't work.

TW

lacro37

2010-11-02 21:18:30 UTC

Is your SD card >2GB? If so, it isn't an SD card but an SDHC. This
won't work.
TW- Ocultar texto de la cita -
- Mostrar texto de la cita -

Tks for your Input feedback, Tim. Sorry, forgot to comment on that
issue. It's a regular SD Transcend 512 MB, FAT-formatted as instructed
in the PDF, by the way. Though I somehow solved it, I think that was
not the issue. Besides I've replaced the 4 batteries with a new set of
4 Alkaline AAA Duracell and tried to proceed again, that didn't make
the trick also. (See Comments below)

Strange though, my new issue is that I can't delete the EqnData.lib in
the root of the SD Card from the File Mgr within the Calculator
itself, (in order to copy the newer proper files in the Card from the
PC again). What is going on now, here? Any clues? When the system asks
me if I'm sure to Purge the file, and I press Yes, it freezes... (Have
to reset it, couldn't delete it, not even from the Card/PC
connection).

Comments,

The paperclip method was the only other way -besides batteries
removal*- to reset it back to the FLASH NEED UPDATE state, at which it
remained... until I executed the 2nd Option (Card) -because I couldn't
even try the USB Option-, and then it began to update for only a
couple of screens with that Hexadecimal code ? instead of the many
more (almost 6 screens for almost a minute of time period) I watched
in the videos... (That was the hint) In the end I could see something
about the ROM File format...? You can Imagine I double checked every
step of these issues before this risky procedure (let alone the
backups).

That is why I took the (new) batteries out, and COPIED both files
(4950_215.bin and update.scp) again to the SD Card from the PC, in
order to see if somehow they corrupted?, and finally that was the
mystery solved. Will never know what happened to that 4950_215.bin
file earlier.

For the record, never had any issues regarding the Port 2. That's why
I didn't even mention the 2MB_215f.bin file I already deleted from the
SD Root.

I've decided to upgrade not only for the sake of it, but because
lately my previous ROM release installed kept on resetting the
calculator for no reason, and began to feel annoying.

Tks, Regards, C

lacro37

2010-11-03 14:47:15 UTC

Is your SD card >2GB? If so, it isn't an SD card but an SDHC. This
won't work.
TW- Ocultar texto de la cita -
- Mostrar texto de la cita -

Tks for your Input feedback, Tim. Sorry, forgot to comment on that
issue. It's a regular SD Transcend 512 MB, FAT-formatted as instructed
in the PDF, by the way. Though I somehow solved it, I think that was
not the issue. Besides I've replaced the 4 batteries with a new set of
4 Alkaline AAA Duracell and tried to proceed again, that didn't make
the trick also. (See Comments below)
Strange though, my new issue is that I can't delete the EqnData.lib in
the root of the SD Card from the File Mgr within the Calculator
itself, (in order to copy the newer proper files in the Card from the
PC again). What is going on now, here? Any clues? When the system asks
me if I'm sure to Purge the file, and I press Yes, it freezes... (Have
to reset it, couldn't delete it, not even from the Card/PC
connection).
Comments,
The paperclip method was the only other way -besides batteries
removal*- to reset it back to the FLASH NEED UPDATE state, at which it
remained... until I executed the 2nd Option (Card) -because I couldn't
even try the USB Option-, and then it began to update for only a
couple of screens with that Hexadecimal code ? instead of the many
more (almost 6 screens for almost a minute of time period) I watched
in the videos... (That was the hint) In the end I could see something
about the ROM File format...? You can Imagine I double checked every
step of these issues before this risky procedure (let alone the
backups).
That is why I took the (new) batteries out, and COPIED both files
(4950_215.bin and update.scp) again to the SD Card from the PC, in
order to see if somehow they corrupted?, and finally that was the
mystery solved. Will never know what happened to that 4950_215.bin
file earlier.
For the record, never had any issues regarding the Port 2. That's why
I didn't even mention the 2MB_215f.bin file I already deleted from the
SD Root.
I've decided to upgrade not only for the sake of it, but because
lately my previous ROM release installed kept on resetting the
calculator for no reason, and began to feel annoying.
Tks, Regards, C- Ocultar texto de la cita -
- Mostrar texto de la cita -

Still with the new ROM, when I try a simple task like to VIEW a big
LIB (of ~ > 20 K I must add), in the File App Mgr*, the message I
receive states "Insufficient Memory" and/or eventually freezes in such
a way I must make a full RESET with the paperclip method.

Is this machine so sensitive? Though I had a recent full backup, it is
still very annoying having to restore it back fro whatever reason.

Any feedback is welcome.

2010-11-03 15:19:47 UTC

Is your SD card >2GB? If so, it isn't an SD card but an SDHC. This
won't work.
TW- Ocultar texto de la cita -
- Mostrar texto de la cita -

Tks for your Input feedback, Tim. Sorry, forgot to comment on that
issue. It's a regular SD Transcend 512 MB, FAT-formatted as instructed
in the PDF, by the way. Though I somehow solved it, I think that was
not the issue. Besides I've replaced the 4 batteries with a new set of
4 Alkaline AAA Duracell and tried to proceed again, that didn't make
the trick also. (See Comments below)
Strange though, my new issue is that I can't delete the EqnData.lib in
the root of the SD Card from the File Mgr within the Calculator
itself, (in order to copy the newer proper files in the Card from the
PC again). What is going on now, here? Any clues? When the system asks
me if I'm sure to Purge the file, and I press Yes, it freezes... (Have
to reset it, couldn't delete it, not even from the Card/PC
connection).
Comments,
The paperclip method was the only other way -besides batteries
removal*- to reset it back to the FLASH NEED UPDATE state, at which it
remained... until I executed the 2nd Option (Card) -because I couldn't
even try the USB Option-, and then it began to update for only a
couple of screens with that Hexadecimal code ? instead of the many
more (almost 6 screens for almost a minute of time period) I watched
in the videos... (That was the hint) In the end I could see something
about the ROM File format...? You can Imagine I double checked every
step of these issues before this risky procedure (let alone the
backups).
That is why I took the (new) batteries out, and COPIED both files
(4950_215.bin and update.scp) again to the SD Card from the PC, in
order to see if somehow they corrupted?, and finally that was the
mystery solved. Will never know what happened to that 4950_215.bin
file earlier.
For the record, never had any issues regarding the Port 2. That's why
I didn't even mention the 2MB_215f.bin file I already deleted from the
SD Root.
I've decided to upgrade not only for the sake of it, but because
lately my previous ROM release installed kept on resetting the
calculator for no reason, and began to feel annoying.
Tks, Regards, C- Ocultar texto de la cita -
- Mostrar texto de la cita -

Still with the new ROM, when I try a simple task like to VIEW a big
LIB (of ~ > 20 K I must add), in the File App Mgr*, the message I
receive states "Insufficient Memory" and/or eventually freezes in such
a way I must make a full RESET with the paperclip method.
Is this machine so sensitive? Though I had a recent full backup, it is
still very annoying having to restore it back fro whatever reason.
Any feedback is welcome.

Sounds like you have some serious issues with your unit. . . have you
run hardware checks to see if it passes things?

TW

Han

2010-11-03 15:34:01 UTC

Post by TW
Sounds like you have some serious issues with your unit. . . have you
run hardware checks to see if it passes things?
TW

From what he wrote earlier, I'd say the first thing to check is if the
SD card is not corrupt. If it is, you probably have a corrupted ROM
update. Then run the ROM check to see if your calculator actually
passes the ROM test.

LinuxBR

2010-11-03 21:40:52 UTC

Post by Han

Post by TW
Sounds like you have some serious issues with your unit. . . have you
run hardware checks to see if it passes things?
TW

HI Lacro37

Try the comand PINIT repeat it 3 or 4 time. After reset the calc
with ON+F3
D.L.

LinuxBR

2010-11-03 22:07:32 UTC

Post by LinuxBR

Post by Han

Post by TW
Sounds like you have some serious issues with your unit. . . have you
run hardware checks to see if it passes things?
TW

HI Lacro37
Try the comand PINIT repeat it 3 or 4 time. After reset the calc
with ON+F3
D.L.

Hi...

In the ROM UPDATE has a file 2MB FIX you can try update you rom using
this file, may be it can solve your problem in port 2

D.L.

lacro37

2010-11-04 16:30:57 UTC

Post by LinuxBR

Post by Han

Post by TW
Sounds like you have some serious issues with your unit. . . have you
run hardware checks to see if it passes things?
TW

HI Lacro37
Try the comand PINIT repeat it 3 or 4 time. After reset the calc
with ON+F3
D.L.

Hi...
In the ROM UPDATE has a file 2MB FIX you can try update you rom using
this file, may be it can solve your problem in port 2
D.L.- Ocultar texto de la cita -
- Mostrar texto de la cita -

Tks all for your answers. I will try to leave the record straight
here.

May be I didn't express correctly before.

As told then, I managed to update the ROM 2.15 by copying the files
again to the SD Card, and repeating the procedure. Frankly don't know
how the 4950_215.bin got corrupted in the first place. My current
Version-Revison is now the # 2.15.

Anyhow, after that I still couldn't delete the EQNDATA.lib file from
the root of the SD Card. Not from within the Calculator itself, with
the File Mgr, and not from the very SD Card through the notebook card
reader where it figures with 0 Bytes size... and don't let me erase
it.

While this file figures as STRNG Type in the File Mgr list, and
without SIZE like all the rest fo the files, it freezes when I confirm
that I want to PURGE it ... Used paperclip.

I expect to solve this issue soon, and avoid future random crashes
with this new ROM.

Don't know what hardware check I might use, but tried to run the
TEST49.lib and it stopped before ending the report, with this message,
PVARS Error: Invalid Date.

Any other method? Is there any other specific application to check the
situation?

Han,
how can I know for sure if the SD Card is corrupt?
how can I test the corruption of the ROM Update?
How would I run and check the ROM test?

LinuxBR,
For using the PINIT command 3 or 4 times, I should have access to the
Calculator, which I don't when it freezes (when trying to purge the
EQNDATA.LIB). By the way, the "ON+F3" procedure and others, didnt work
while at the same situation.

As written earlier, never had issues with Port 2. That's why I didn't
even mention the 2MB_215f.bin file I already deleted from the SD
Root.

Tks, Regards, C

Han

2010-11-04 18:34:51 UTC

Press [ON] [F4] simultaneously (I press and hold [ON], then press [F4]
while holding [ON], and release both). This should enter the
interactive test suite on the calculator. You can test the FLASH and
the SD card from here. I recommend connecting the calculator up to a
PC with the USB cable so that it runs off of the USB power. The FLASH
test can take a while if you do an in-depth test.

To exit, press [ON] [F3].

Han

lacro37

2010-11-05 03:11:23 UTC

Post by Han
Press [ON] [F4] simultaneously (I press and hold [ON], then press [F4]
while holding [ON], and release both). This should enter the
interactive test suite on the calculator. You can test the FLASH and
the SD card from here. I recommend connecting the calculator up to a
PC with the USB cable so that it runs off of the USB power. The FLASH
test can take a while if you do an in-depth test.
To exit, press [ON] [F3].
Han

Full Flash Write Test = OK
Card Test = OK
AutoTest = OK

C

John H Meyers

2010-11-05 02:51:54 UTC

Post by lacro37
As told then, I managed to update the ROM 2.15 by copying the files
again to the SD Card, and repeating the procedure. Frankly don't know
how the 4950_215.bin got corrupted in the first place. My current
Version-Revison is now the # 2.15.
Anyhow, after that I still couldn't delete the EQNDATA.lib file from
the root of the SD Card. Not from within the Calculator itself, with
the File Mgr, and not from the very SD Card through the notebook card
reader where it figures with 0 Bytes size... and don't let me erase
it.
While this file figures as STRNG Type in the File Mgr list, and
without SIZE like all the rest fo the files, it freezes when I confirm
that I want to PURGE it ... Used paperclip.

Wrong file type and no size?

Sounds corrupted, so no wonder you can't delete it on calc.

What size is the file when examined on a computer?

What are the first 8 characters of the file, on a computer?

Can you delete the file using a computer?

What does a "disk check" (of the card) say on a computer?

If disk check fails, perhaps reformat the card on computer and try again.

[r->] [OFF]

lacro37

2010-11-05 03:43:16 UTC

Wrong file type and no size?
Sounds corrupted, so no wonder you can't delete it on calc.
What size is the file when examined on a computer?
What are the first 8 characters of the file, on a computer?
Can you delete the file using a computer?
What does a "disk check" (of the card) say on a computer?
If disk check fails, perhaps reformat the card on computer and try again.
[r->] [OFF]

Hi, John!

The "EqnData.lib" file from the SD Card in the Notebook Card Reader
figures with 0 bytes

As soon as I delete it, I refresh my Windows Explorer and then it
appears again!

As instructed, I executed > chkdsk /f h:\ < in the CMD window,
twice.

The 1st time, I could see the report I'm copying below.

I'm afraid the Win XP-Pro+SP3 Report is in spanish, but I'll translate
the important statements.

The File System is FAT (OK)
The SD Card SN...
Might not be a Win XP Disk...
Do you want to continue? Yes
Windows is checking Files and Folders

It seems there were MANY corrupted files, explained by
1st asignated unit is not valid, the entrance gate? is TRUNCATED (as
many other files and folders), and many crossed links,

Almost 200 lost chains (?) with corssed link in group # XXX. Truncated
orphan.
Do you wish to convert (them) in files? Yes

After this action, in the 2nd CHKDSK I couldn't leave the CMD Window
Open, and seems the CHKDSK was allright.

I will try to avoid reformatting the card at least for now, cleaning/
wiping/ deleting every single file which appeared in the list below.

I'll keep you all posted. Tks again, once more. Bullseye!

Best Regards, C

-----------------------------------------------------------------------------------------
El tipo del sistema de archivos es FAT.
El número de serie del volumen es FC30-3DA9
Probablemente no sea un disco de Windows XP
¿Desea continuar (S/N)? s
Windows está comprobando archivos y carpetas...

\RED2.DIR.HP La primera unidad de asignación no es válida. La entrada
estará truncada.
El tamaño de la entrada \TuberiasV106.HP no es válido.
\ESPFUN tiene un vínculo cruzado en la unidad de asignación 287
La carpeta ha sido truncada.
\EqnData.lib La primera unidad de asignación no es válida. La entrada
estará truncada.
Eliminando entrada larga de carpeta no válida de \...
\4950_215.bin tiene un vínculo cruzado en la unidad de asignación 286
El vínculo cruzado se ha resuelto copiando.
\BtMon.hp tiene un vínculo cruzado en la unidad de asignación 73
El vínculo cruzado se ha resuelto copiando.
\AreaXPv2lib tiene un vínculo cruzado en la unidad de asignación 283
El vínculo cruzado se ha resuelto copiando.
\LIBS\L1042 tiene un vínculo cruzado en la unidad de asignación 72
El vínculo cruzado se ha resuelto copiando.
Comprobación de archivo y carpeta completa.
Cadena perdida con vínculo cruzado en grupo 770. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 771. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 772. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 773. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 774. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 775. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 776. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 777. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 778. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 781. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 786. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 789. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 791. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 795. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 796. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 832. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 833. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 834. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 835. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 836. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 837. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 838. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 839. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 840. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 841. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 842. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 843. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 844. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 845. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 846. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 847. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 848. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 849. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 850. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 851. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 852. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 853. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 854. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 855. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 856. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 857. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 858. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 859. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 860. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 861. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 862. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 863. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 864. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 865. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 866. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 867. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 868. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 869. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 870. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 871. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 872. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 873. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 874. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 875. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 876. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 877. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 878. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 879. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 880. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 881. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 882. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 883. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 884. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 885. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 886. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 887. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 888. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 889. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 890. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 891. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 892. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 893. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 894. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 895. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 896. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 897. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 898. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 899. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 900. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 901. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 902. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 903. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 904. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 905. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 906. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 907. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 908. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 909. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 910. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 911. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 912. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 913. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 914. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 915. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 916. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 917. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 918. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 919. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 920. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 921. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 922. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 923. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 924. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 925. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 926. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 927. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 928. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 929. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 930. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 931. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 932. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 933. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 934. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 935. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 936. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 937. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 938. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 939. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 940. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 941. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 942. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 943. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 944. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 945. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 946. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 947. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 948. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 949. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 950. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 951. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 952. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 953. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 954. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 955. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 956. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 957. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 959. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 960. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 961. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 962. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 963. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 964. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 965. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 966. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 967. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 968. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 969. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 970. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 971. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 972. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 973. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 974. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 975. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 976. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 977. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 978. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 979. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 980. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 981. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 982. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 983. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 984. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 985. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 986. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 987. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 988. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 989. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 990. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 991. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 992. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 993. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 994. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 995. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 996. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 997. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 998. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 999. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1000. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1001. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1002. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1003. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1004. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1005. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1006. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1007. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1008. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1009. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1010. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1011. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1012. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1013. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1014. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1015. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1016. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1017. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1018. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1019. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1020. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1021. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1022. Huérfano truncado.
Cadena perdida con vínculo cruzado en grupo 1023. Huérfano truncado.
¿Desea convertir cadenas perdidas en archivos (S/N)? s

-----------------------------------------------------------------------------------------

John H Meyers

2010-11-05 03:52:02 UTC

I executed > chkdsk /f h:\ < in the CMD window, twice.
It seems there were MANY corrupted files, explained by
1st asignated unit is not valid, the entrance gate? is TRUNCATED
(as many other files and folders), and many crossed links,...

Sounds just like my mind ;-)

Wishing it a good recovery.

[r->] [OFF]

lacro37

2010-11-05 10:37:29 UTC

Sounds just like my mind ;-)
Wishing it a good recovery.
[r->] [OFF]

THANKS, John, and to all the inputs I had.

At least, for the time being, I assume the mistery, solved.

Cheers, C

lacro37

2010-11-05 14:35:21 UTC

Sounds just like my mind ;-)
Wishing it a good recovery.
[r->] [OFF]

THANKS, John, and to all the inputs I had.
At least, for the time being, I assume the mistery, solved.
Cheers, C

Don't panic with this never ending story. It's only for the record for
the next guy.

After some more iissues, I re-formatted the entire card as suggested.

Almost 14 libraries (files) appeared again to be broken, truncated, re-
assigned, whatever... That was enough.

John was right once more, and I'm afraid I should consider tossing
away my curret one, and buying a new SD Card all together.

Don't need any bigger than 512 MB... Is there any other restriction
besides the 2 GB size, regarding speed ? e.g. SD-HC or SD-XC ?

Eric Rechlin

2010-11-05 15:59:25 UTC

Post by lacro37
Don't need any bigger than 512 MB... Is there any other restriction
besides the 2 GB size, regarding speed ? e.g. SD-HC or SD-XC ?

It must be an SD card. SD-HC and SD-XC will not work. That effectively
limits you to 2GB (yes, I realize 4GB SD cards existed at some point, but
they are very very very rare, and I am not sure how well they would work in
the calculator).

Speed doesn't matter much. The slowest, oldest cards will definitely be
slower in the calculator, but any recent card should max out the
calculator's performance abilities. As long as you format the card to FAT16
(do not use the calculator to format it, or you will be forced to use FAT32)
it should perform well.

Cards under 2GB are becoming difficult to find, so just buy any 2GB card.
Hopefully you can find one for under 40 pesos locally; if not, let me know
and I can help.

Regards,

Eric Rechlin

lacro37

2010-11-05 18:56:40 UTC

Post by lacro37
Don't need any bigger than 512 MB... Is there any other restriction
besides the 2 GB size, regarding speed ? e.g. SD-HC or SD-XC ?

It must be an SD card. SD-HC and SD-XC will not work. That effectively
limits you to 2GB (yes, I realize 4GB SD cards existed at some point, but
they are very very very rare, and I am not sure how well they would work in
the calculator).
Speed doesn't matter much. The slowest, oldest cards will definitely be
slower in the calculator, but any recent card should max out the
calculator's performance abilities. As long as you format the card to FAT16
(do not use the calculator to format it, or you will be forced to use FAT32)
it should perform well.
Cards under 2GB are becoming difficult to find, so just buy any 2GB card.
Hopefully you can find one for under 40 pesos locally; if not, let me know
and I can help.
Regards,
Eric Rechlin

Thanks Eric! How are you? Tell me if you come to BsAs.
Yes, I've already checked MeLi (MercadoLibre = eBay's local partner),
and those are offered around US$ 10. That''s more than ok.
It seems to be hard to find any card under 2 GB, but all those
restrictions I can even apply for a Micro SD Card with an adapter.
Currently I'm only using 15 MB of those 512 MB, and I won't need much
more. I regret that I lookd for a good brand like SanDisk, but
Trascend was very highly recommended.
I usually format the cards as FAT-Only, from the PC (Notebook).
Best rgds, Carlos

lacro37

2010-11-06 00:23:28 UTC

Post by lacro37
Don't need any bigger than 512 MB... Is there any other restriction
besides the 2 GB size, regarding speed ? e.g. SD-HC or SD-XC ?

It must be an SD card. SD-HC and SD-XC will not work. That effectively
limits you to 2GB (yes, I realize 4GB SD cards existed at some point, but
they are very very very rare, and I am not sure how well they would work in
the calculator).
Speed doesn't matter much. The slowest, oldest cards will definitely be
slower in the calculator, but any recent card should max out the
calculator's performance abilities. As long as you format the card to FAT16
(do not use the calculator to format it, or you will be forced to use FAT32)
it should perform well.
Cards under 2GB are becoming difficult to find, so just buy any 2GB card.
Hopefully you can find one for under 40 pesos locally; if not, let me know
and I can help.
Regards,
Eric Rechlin

Did I mention that after the formatting, etc. the Efficiency% from the
Test49v17.lib report, reached 20% !!! ???

According to MScan (Lib#1229) Port 2 reports 38% Free (414.448 Bytes ~
almost 415 KB), while my Port 0 / Home Dir is almost full (14075 ~
6%); though I can't load the "L935.HP" lib of 45 KB because of lack of
space memory? Am I doing my maths wrong? Which libraries may I load in
Port 1? How can I recognise which ones could I move from #2 to #1? I
recall Port 1 is not that convenient, but I have almost 50% free
(131064 Bytes) against the previous situation.

I'm eager to try the Filer6 from TW as well as others, but they are
usually huge considering the P2 size. .

lacro37

2010-11-06 16:25:40 UTC

Post by lacro37
Don't need any bigger than 512 MB... Is there any other restriction
besides the 2 GB size, regarding speed ? e.g. SD-HC or SD-XC ?

It must be an SD card. SD-HC and SD-XC will not work. That effectively
limits you to 2GB (yes, I realize 4GB SD cards existed at some point, but
they are very very very rare, and I am not sure how well they would work in
the calculator).
Speed doesn't matter much. The slowest, oldest cards will definitely be
slower in the calculator, but any recent card should max out the
calculator's performance abilities. As long as you format the card to FAT16
(do not use the calculator to format it, or you will be forced to use FAT32)
it should perform well.
Cards under 2GB are becoming difficult to find, so just buy any 2GB card.
Hopefully you can find one for under 40 pesos locally; if not, let me know
and I can help.
Regards,
Eric Rechlin

Did I mention that after the formatting, etc. the Efficiency% from the
Test49v17.lib report, reached 20% !!! ???
According to MScan (Lib#1229) Port 2 reports 38% Free (414.448 Bytes ~
almost 415 KB), while my Port 0 / Home Dir is almost full (14075 ~
6%); though I can't load the "L935.HP" lib of 45 KB because of lack of
space memory? Am I doing my maths wrong? Which libraries may I load in
Port 1? How can I recognise which ones could I move from #2 to #1? I
recall Port 1 is not that convenient, but I have almost 50% free
(131064 Bytes) against the previous situation.
I'm eager to try the Filer6 from TW as well as others, but they are
usually huge considering the P2 size. .- Ocultar texto de la cita -
- Mostrar texto de la cita -

I moved 44KB of libraries from P2-to-P1, and I still can't install a
45KB LIB in P2 with almost 459KB Free (42%Free) !?
Is this only a SD Card issue?

Dave Hayden

2010-11-06 12:57:15 UTC

As long as you format the [SD] card to FAT16
(do not use the calculator to format it, or you will be forced to use FAT32)
it should perform well.

Eric, can you elaborate on the performance difference? I always
assumed that cards for the calculator should be formatted with FAT32
to keep the cluster size small. There's no sense having a bunch of
100 byte
files stored in 16k clusters. :)

Dave

2010-11-06 15:25:07 UTC

Basically, the calculator scans the whole filesystem when you power it
on. With a large 2gb 32 fornatted card, you have a 1-2 second delay
*every* time the calc powers on. With a really slow card, it can
stretch to 3 seconds.

It is very annoying.

TW

Eric Rechlin

2010-11-12 16:33:55 UTC

Post by Dave Hayden
Eric, can you elaborate on the performance difference? I always
assumed that cards for the calculator should be formatted with FAT32
to keep the cluster size small. There's no sense having a bunch of
100 byte files stored in 16k clusters. :)

Since FAT32 uses smaller clusters, it means there are more clusters in
total. I am not sure of the internal details of it, but it seems that when
you turn on the calculator, the underlying Kinpo OS scans all the clusters
on the card. If you have more clusters it takes longer for the calculator
to be ready for use after you turn it on -- I've seen several seconds, with
FAT32 on a slow card. With FAT16 on a fast card it's pretty much
instantaneous.

Because of the ridiculous amount of space you get from a 2GB card, it's no
big deal if each file takes 32KB instead of 4KB. That's still lets you fit
65,536 of those 100 byte files. :)

I think the Filer is faster with the FAT16 format as well, but I don't
recall as it has been quite a while since I last tested this.

Regards,

Eric Rechlin

lacro

2010-11-14 00:18:56 UTC

Post by Eric Rechlin

Since FAT32 uses smaller clusters, it means there are more clusters in
total. I am not sure of the internal details of it, but it seems that when
you turn on the calculator, the underlying Kinpo OS scans all the clusters
on the card. If you have more clusters it takes longer for the calculator
to be ready for use after you turn it on -- I've seen several seconds, with
FAT32 on a slow card. With FAT16 on a fast card it's pretty much
instantaneous.
Because of the ridiculous amount of space you get from a 2GB card, it's no
big deal if each file takes 32KB instead of 4KB. That's still lets you fit
65,536 of those 100 byte files. :)
I think the Filer is faster with the FAT16 format as well, but I don't
recall as it has been quite a while since I last tested this.
Regards,
Eric Rechlin

Well, Friends, I bought, FAT(16) formatted and similar-content-
transferred my new 2GB SanDisk Mobile microSD Card with Adapter (US$
15). Couldn't find a smaller size.

Though it seems to work OK, I've already faced the same couple of
situations I experienced before.

#1) The File Mgr still states I have 861,344 KB... !? Shouldn't it
report almost the above 1.85 GB this Card really has?

#2) As before, when I want to FixSTO Lib 935 SDLIB 0.5 to Port 2, I
still get the >FixSTO Error: Insufficient Memory< Message...!? Is that
right? Am I doing something wrong here?

PS:
My 512 MB Card previously specified, was sent to its provider to check
its situation in order to get it fixed or changed by the guarantee
claim, in which case I doubt I'll get a similar sized card.

John H Meyers

2010-11-14 00:57:45 UTC

I bought, FAT(16) formatted and similar-content-transferred
my new 2GB SanDisk Mobile microSD Card with Adapter (US$15).
The File Mgr still states I have 861,344 KB... !? Shouldn't it
report almost the above 1.85 GB this Card really has?

All's well -- there just isn't room
to display the first digit on the screen.

As before, when I want to FixSTO Lib 935 SDLIB 0.5 to Port 2...

I never tried any of this "graduate level" stuff ;-)

[r->] [OFF]

lacro

2010-11-14 01:14:13 UTC

All's well -- there just isn't room
to display the first digit on the screen.

As before, when I want to FixSTO Lib 935 SDLIB 0.5 to Port 2...

I never tried any of this "graduate level" stuff ;-)
[r->] [OFF]

Tks!, John : ) It's one of the required files for the latest TW
release of his Filer, that I understand can read Directories from the
SD Card.

2010-11-14 01:47:27 UTC

Post by lacro
Tks!, John : ) It's one of the required files for the latest TW
release of his Filer, that I understand can read Directories from the
SD Card.

Hello,

That library was actually built to not need any special storing
methods unless I am remembering incorrectly. The downside is that it
needs much more RAM to run as it recalls the full C program first
before execution. I wanted to avoid having a slew of emails wondering
why it had problems and wouldn't run. . . :-)

TW

lacro

2010-11-14 15:30:49 UTC

Post by lacro
Tks!, John : ) It's one of the required files for the latest TW
release of his Filer, that I understand can read Directories from the
SD Card.

Hello,
That library was actually built to not need any special storing
methods unless I am remembering incorrectly. The downside is that it
needs much more RAM to run as it recalls the full C program first
before execution. I wanted to avoid having a slew of emails wondering
why it had problems and wouldn't run. . . :-)
TW

Hello Tim,

Don't want to upset you with explanations, BUT in that case, 2 doubts
arised to me.

#1) Where does that RAM come from? in order to get it to make it work,
by making/ erasing space from which Port... 0, 1 or/ and 2.
I've already tried to make it work by resetting it, just before the
FixSTO procedure (Must I add, w/o success?)

#2) Which of your latest releases (2006 and 2008), should I consider
then?

I'm eager to manage files from my SD Card, and think your application
is the only one who can handle that issue.
I also want to add WR's HeadMan to improve the experience, regarding
your ReadMe files.

Cheers, C

2010-11-14 16:45:58 UTC

Post by lacro

Post by lacro
Tks!, John : ) It's one of the required files for the latest TW
release of his Filer, that I understand can read Directories from the
SD Card.

Hello,
That library was actually built to not need any special storing
methods unless I am remembering incorrectly. The downside is that it
needs much more RAM to run as it recalls the full C program first
before execution. I wanted to avoid having a slew of emails wondering
why it had problems and wouldn't run. . . :-)
TW

You should just store both libraries into port2 and then reboot (ON-
C). Then you can access it either through APPS, or the Lib menu. I
don't remember how I did it.

Post by lacro
#2) Which of your latest releases (2006 and 2008), should I consider
then?

The later one probably.

Post by lacro
I'm eager to manage files from my SD Card, and think your application
is the only one who can handle that issue.
I also want to add WR's HeadMan to improve the experience, regarding
your ReadMe files.

I had someone request this. I think all it does it add a READ button
into the menu so you can call that ebook reader thing from the WR
program.

TW

lacro

2010-11-15 19:08:42 UTC

Post by lacro

Post by lacro
Tks!, John : ) It's one of the required files for the latest TW
release of his Filer, that I understand can read Directories from the
SD Card.

Hello,
That library was actually built to not need any special storing
methods unless I am remembering incorrectly. The downside is that it
needs much more RAM to run as it recalls the full C program first
before execution. I wanted to avoid having a slew of emails wondering
why it had problems and wouldn't run. . . :-)
TW

You should just store both libraries into port2 and then reboot (ON-
C). Then you can access it either through APPS, or the Lib menu. I
don't remember how I did it.

Post by lacro
#2) Which of your latest releases (2006 and 2008), should I consider
then?

The later one probably.

I had someone request this. I think all it does it add a READ button
into the menu so you can call that ebook reader thing from the WR
program.
TW- Ocultar texto de la cita -
- Mostrar texto de la cita -

Thnak you for your time. I wiil try that.

Regards, C

Joe Horn

2010-11-14 12:42:23 UTC

Post by lacro
#1) The File Mgr still states I have 861,344 KB... !? Shouldn't it
report almost the above 1.85 GB this Card really has?

They only allocated six digits for the display. Fear not: your
leading digit is there, just not displayed.

-Joe-

lacro

2010-11-14 13:18:32 UTC

Post by lacro
#1) The File Mgr still states I have 861,344 KB... !? Shouldn't it
report almost the above 1.85 GB this Card really has?

They only allocated six digits for the display. Fear not: your
leading digit is there, just not displayed.
-Joe-

Tks, Joe
Excuse my ignorance.
Good Sunday!
C

John H Meyers

2010-11-05 03:43:28 UTC

Post by John H Meyers
Wrong file type and no size?
Sounds corrupted, so no wonder you can't delete it on calc.
What size is the file when examined on a computer?
What are the first 8 characters of the file, on a computer?
Can you delete the file using a computer?

It seems you've already said that the computer thinks
the file size is zero, and that it can't be deleted.

So _both_ calculator and computer seem to agree
that this "file" is corrupted, and if "disk check"
can't restore sanity, surely you must re-format the card, no?

An SD card is not guaranteed to be free of defect,
so if even "re-formatting" leaves a flaky card,
the (physical) trash bin would seem to be
the best place to toss it.

[r->] [OFF]

lacro37

2010-11-05 03:49:34 UTC

It seems you've already said that the computer thinks
the file size is zero, and that it can't be deleted.
So _both_ calculator and computer seem to agree
that this "file" is corrupted, and if "disk check"
can't restore sanity, surely you must re-format the card, no?
An SD card is not guaranteed to be free of defect,
so if even "re-formatting" leaves a flaky card,
the (physical) trash bin would seem to be
the best place to toss it.
[r->] [OFF]

I will try to verify how the card is behaving in the next few days.
Any doubt, I will re-format it as suggested, and in the worst scenario
I will toss it away. However, remember good old cards are not as cheap
down here, than over there (in the US).

My very best 2 u all!

lacro37

2010-11-05 03:54:37 UTC