Strange ROM / RAM behavior

[Marshall]

FYI -

I have not seen this posted, but I may have missed many things.

In the process of trying to test out moving applications to my memory stick in my NZ, and trying out things like MemHack, I have at times accidentially duplicated applications in RAM. Or really the operating system has duplicated them. I did not intend to copy them in ram.

This uses that much more ram for the apps that are duplicated.

I have then used FILEZ to determine which file(s) to delete, the ones not copy protected, delete them, and then what seems like a usual memory error comes up. I then have to manually reset and then all is OK.

I suppose this is normal in the "testing" / trying out phase of using palm devices. I also suppose it might drive developers crazy, and might have driven some of the later releases of palmos.

I imagine this relates to the "natural" reload of software that must happen with a hard reset... but I suppose there is some utility that will make this all transparent. ;-)

Is there some more sensible way to approach this stuff?

- Marshall

[jettie1767]

This usually happens if you have the same app on ram and rom as when you get an update from Sony. Zlauncher or even the Clie Launcher usually keeps this transparent to the user.

[n2ifp]

You can't do things haphazardly and not expect problems, Never willy-nilly delete files. I always use the delete in the pull down menu in the default launcher.

The same procedures you do on a desktop PC apply to a Palm PDA.

You can always verify the creator ID's

http://dev.palmos.com/creatorid/

[Marshall]

FYI -

I think "jettie1767" got my meaning, but I doubt "n2ifp" did. I'm sorry I was not clear.

This is a peculiar behavior where the normal "protected" app is on ram and another accidental copy is on memory stick and with running of the app from the stick causes a second copy of the app to show in ram, most IDs are identical including the creator id. (I will check again but I am pretty sure it was when last this happened.)

This may be something that Megalauncher causes or shows inappropriately, but I doubt it. It shows in FileMan and Filez. The ram seem to be used up until I delete the duplicate of the app.

Strange... interesting... but strange.

- Marshall

[Marshall]

FYI -

I did check for the creatorid and they are all the same in this strange copy behaviour.

I guess it servers me right for backing-up with BB and by simple FileMan copy.

- Marshall