Registered: Dec 2000
Location: Silicon Valley, California
Posts: 173

AAAARRRRGGGGHHHHH!!!!! I have now replaced the RAM module which never successfully "compacted." The new one did the SAME THING! The only difference was it didn't freeze first. It said it was compacting. The little bar moved a bit. Then it went to the main screen...BUT the RAM module wasn't visible. I thought this might be normal, so I turned it off and turned it back on. No dice. So I tried a soft reset. THE MESSAGE SAID THE RAM MODULE WAS CORRUPTED AND FORCED ME TO REFORMAT!!

What's the dealio? I've tried two Prisms and two modules. The only thing running was PalmThemes. I'd disable it, but I didn't get a warning.

I wouldn't care so much except you can't directly load this thing so I gotta clear out the regular memory, load the junk, etc.

ANY HELP WOULD BE GREATLY APPRECIATED!!

PurpleMD
...sittin' roun' waitin' to backup the main memory so I can clear it and load the stuff for the module...et cetera...et cetera...

Registered: Nov 2000
Location:
Posts: 714

When I went to load Noah Lite database on my ThinModem+ yesterday is compacted for the very first time, no problems whatsoever.

__________________
Matt Nichols
[email protected]

Registered: Apr 2000
Location: Inglewood, CA, USA
Posts: 390

I have two 8mb modules. One always compacted just fine, the other always crashed and forced me to reformat it. I used to think that the one that crashed was defective. After playing around with them a bit, I'm starting to think that it's a conflict between the applications and the module that is causing the problem. It's the only thing I can come up with so far...

On one module, I have only data (ebooks/static databases). That's the module that compacts OK. The other has a mixture of applications and data. After my last module crashed, I wiped the other one also. (backed-up with BackupBuddy first...) I restored them both, but switched the modules first. The one that used to compact OK has since crashed, and had to be restored. The one that used to crash hasn't needed to be compacted yet. I'll see what happens then....

Maybe one of the applications on the module is trying to "talk" to the Visor when the module goes into "compact" mode - the same as if the module was pulled out of the Visor when it was trying to read/write. (???)

----------------------
"Okay, strap yourselves in! This flight is gonna suck, and we don't serve peanuts!"
Hawkes to colonists, "...Tell Our Moms We Done Our Best". (Space: Above and Beyond)

Registered: Dec 2000
Location:
Posts: 384

good point

quote:

---

Originally posted by narnia_77
Maybe one of the applications on the module is trying to "talk" to the Visor when the module goes into "compact" mode - the same as if the module was pulled out of the Visor when it was trying to read/write. (???)

---

__________________
Fat's

Registered: Dec 2000
Location: Silicon Valley, California
Posts: 173

Re: good point

quote:

---

Originally posted by Fat_Man
What do you mostly store in you module? Applications or database? I bet one of your applications in your module is causing these corruptions.

---

Registered: Dec 2000
Location:
Posts: 384

Re: Re: good point

quote:

---

Originally posted by purplemd

Why would there be no conflict running things but only compacting them?

---

__________________
Fat's

Registered: Dec 1999
Location: Kuala Lumpur
Posts: 247

I believe the problem happens when you try to copy a file bigger than the space available on the Flash module.

I tried it out myself, copying a 350Kb file when I only had 333Kb left on the Flash module.

Sure enough, the Flash Module got corrupted, causing the Visor to hang and forcing me to reset and reformat the module.

I hope Handspring comes out with a fix for this issue.

__________________
Tan Kit Hoong,
Star Publications (M) Ltd
<img src="http://thestar.com.my/tech/images/thestar_140x45.gif">

Registered: Apr 2000
Location: Inglewood, CA, USA
Posts: 390

quote:

---

Originally posted by Tan Kit Hoong
I believe the problem happens when you try to copy a file bigger than the space available on the Flash module.

---

Registered: Dec 2000
Location: Silicon Valley, California
Posts: 173

stupid question

Stupid question...why doesn't the main memory ever compact?

Registered: Dec 1999
Location: Kuala Lumpur
Posts: 247

Narnia_77, try choosing a file that is just a little bigger than the amount of available memory on the Module.

Glad you liked the B5 guide Any suggestions on improving it?

__________________
Tan Kit Hoong,
Star Publications (M) Ltd
<img src="http://thestar.com.my/tech/images/thestar_140x45.gif">

Registered: Dec 2000
Location:
Posts: 384

quote:

---

Originally posted by purplemd
Stupid question...why doesn't the main memory ever compact?

---

__________________
Fat's

Registered: Dec 2000
Location:
Posts: 120

What ever happened to the "Gold" standard. We ARE talking about Handspring flash modules, aren't we?

Registered: Apr 2000
Location: Inglewood, CA, USA
Posts: 390

quote:

---

Originally posted by Tan Kit Hoong
Narnia_77, try choosing a file that is just a little bigger than the amount of available memory on the Module.

---

OK, I just tried to copy only 5K over what the module said it had available - same error message, no crash. (This module contains Peanut Reader w/ files, WordSmith w/ files, and a few Palm DOC files.)

quote:

---

Glad you liked the B5 guide Any suggestions on improving it?

---

Instead of short summaries, how about looong, detailed ones - just short of actual transcripts. That way, if you haven't seen an episode, you'll feel as if you had after reading it.


-----------------------
The best part about procrastination is that you are never bored, because you have all kinds of things that you should be doing.

Registered: Dec 1999
Location: Kuala Lumpur
Posts: 247

Hmm...okay. Seems my theory is a little flawed. Near as I can tell, though, copying a larger file has something to do with the problem. Mebbe it's a mix between what hacks I have on my Visor and the fact of compacting. How about copying a file that is JUST under the amount of available space? 1K less?

Longer, more detailed summaries for the B5 Guide? That was an idea I was toying with at first, Narnia_77, but I made the Guide to go with the show, so that you can basically keep track of what to expect from week to week.

Therefore, I purposely omitted some details so that when you actually watch the show, you will still have some surprises.

__________________
Tan Kit Hoong,
Star Publications (M) Ltd
<img src="http://thestar.com.my/tech/images/thestar_140x45.gif">

Registered: Dec 2000
Location: Silicon Valley, California
Posts: 173

Okay...I have only data files on my RAM module now.

In general, I disable ALL hacks before going into the file mover program. I also turn off CruiseControl and/or QuickBits. I'm not currently using PalmThemes (fell in love with the color version of Backdrop). So, theoretically, I should have nothing to conflict with the file mover thing.

It seems that others are able to have programs on their RAM modules. Do you think that it's certain types of programs that can be on the module?

Registered: Nov 2000
Location:
Posts: 56

troubleshooting

Hey Purple,

There are possible 3 explanations (that I can think of) to explain this recurring problem:

1. Our modules have some inherent defect (ie. some fixed threshold that cannot be breached).
-I doubt this as I have crashed the module with different amounts of memory left on the module.

2. What is on the module (ie., programs vs. data)
-I doubt this too as it seems many (including myself) have experienced the problem with only data, only programs and a mix of both.

3. File size issues (File that is being moved, memory on the module and memory on the RAM)
-My money is on this one. I have seen random cache files appear on the RAM (that were not there prior to Compacting failures) after crashes. Has anyone else noticed this? I have a suspicion that temp files are being written to the RAM...at least in some cases. I assume since there is no ROM, that the files have to be put somewhere before they are deleted from their prior location during compacting. If the RAM is equally full as the module, then there may not be anywhere for the files to be written.

In any case, I have not had any problems since I have cleared my RAM when filling the module. I think at least a few other people have had success with this advice too. Regardless, it may be a good idea to keep track of the filesize of what you are moving and the memory left on both the RAM and module.

quote:

---

Originally posted by DocVisor 02-23-2001 10:35 PM


I had another compacting mishap like the ones described earlier on this thread by PurpleMD, Fat_Man and I. This time, I noticed some strange FfMg Dbcache files on the RAM after the soft reset. Based on this observation, I have a suspicion that the RAM is used, at least occasionally, as a temporary storage space during "Compacting." If the RAM is being used and is equally as full as the module, this could offer an explanation for the screen freezes: there isn't anywhere to temporarily put the files during defragmenting.

While attempting to transfer files to the module, I have since cleared the RAM of space equal to the largest file on the module. After 5 intentional compacts (all below 100kb), I have not had another freeze. In a final test, I had 12kb left on my module and I transferred a 12kb file without any problem leaving 0kb left on the module. I will add that I did this test with 7.1kb on the RAM.

This theory would tend to explain why I had prior success loading the module close to capacity by transferring the largest file last since I likely had a good portion of my RAM free.

For anyone that would like (unverified) suggestions on how to cram their modules 100% full:
-In general, move the programs/data that you do not intend to delete anytime soon to the module
-Clear your RAM as much as you can (I kept an equal amount as the largest file on the module but this may not be totally necessary)
-Load the module full incrementally by syncing data to your RAM then moving it (again, trying to keep your RAM as free as you can so as to anticipate "Compacting")
-Reload your RAM when your module is full

If anyone has an inclination to tempt fate and cram their modules 100% full, please test this tentative hypothesis and post your experiences (good or bad). Keep track of:
**The file size(s) that you are transferring
**The free RAM and
**The space left on the module

Regards,
DocVisor

---

__________________
<i> If it's worth doing, it's got to be done right now.</i>

Registered: Dec 2000
Location:
Posts: 384

Here's something interesting

I have noticed that some hacks will still remain active or partly active even after you deactivate them. I'm using Afterburner 3.0t, I noticed that when I deactivate it, my benchmark is still accelerated. The only way I can truely deactivate it is doing a soft reset.

I'm not quite sure what's causing the corruption errors with your prism and the memory module. My best guess is a systems program.

When you move stuff into the module, do you use "copy" or "move"? Not sure what this have to do with anything, but I find it faster using the "copy" method, after copying, I delete the file from the internal memory.

__________________
Fat's

Registered: Dec 2000
Location: Silicon Valley, California
Posts: 173

I have one of these funky CacheDB files of 327 kb. Can this be deleted then? I figured it was expendable since I hadn't noticed it before. Anyway, I bought Afterburner but have been afraid to use it since my RAM module always crashed. I used the non-overclocking accelerators (QuickBits, CruiseControl). I disable as much as possible before even going into the FAF application. Even if I'm just checking out what's in there.

I still say Handspring should have included some type of warning in the documentation!

Registered: Dec 1999
Location: Kuala Lumpur
Posts: 247

I deleted the ffCache DB file after the crash and reformat of the module with no problems. I believe that the file was created as a backup during the compacting process

__________________
Tan Kit Hoong,
Star Publications (M) Ltd
<img src="http://thestar.com.my/tech/images/thestar_140x45.gif">

Registered: Feb 2001
Location:
Posts: 2

crash

I delete my cache files after crash without a problem. Clearing Ram does help avoid crash.