Registered: Dec 2000
Location:
Posts: 90

This is the second time that my Hawigara 16mg card appeared to be locked in a "necessary" compression. I was attempting to move the 2mg Noah Dictionary and I received the message that my Hawigara 16mg card needed to compress and not to remove the module. The problem was that after 15 minutes of so called compression, the progress bar had not moved past the letter "r" (near the begining ). Of course I was out of the office all day, which meant that I lost all of my reference materials.

#1 Is the compacting or compression typically a long procedure?

#2 What causes this to occur? I had 8mg free on my board but only 300K on my VPR Ram.

#3 Can I run this compression on my own?

I am now faced with piece meal restoring apps and data to the VPR internal, move to the card, repeat!

USB File Mover needs to work in both directions. At least I know everything on the card from BackupBuddy

__________________

[email protected]

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

quote:

---

Originally posted by PDACPA
...I had 8mg free on my board but only 300K on my VPR Ram.

---

You might want to do a search on "compact" - a lot of people have had this problem before. Different people have different reasons/solutions - here is mine. (I'm stealing from one of my other posts in another thread here...)

quote:

---

The only problem I had was the corrupting flash modules when they compacted. I've since learned to leave available space in internal memory, so the module has somewhere to temporarily house information while it's moving stuff around on the module. (If I'm full up, I delete my AvantGo channels before moving items from internal to flash - just in case it needs to compact.) Since then, I've compacted modules over a dozen times, with no crashes. And these were same ones that gave me problems before.

---

Oh, and I usually keep around 2 mb free...

__________________
"Attitudes are contagious... Is YOURS worth catching?"

Registered: Dec 2000
Location:
Posts: 90

Sounds like thats it

That was my major guess, not enough internal memory. It was not by choice that I let it run low, but Noah was taking up the space. I knew I was going to move it, but had not had the chance the night before.

I too usually keep around 2-3mg internal free (depending on my Avantgo). I should have dumped Avantgo before that move. A mistake I will not make again.

I still wish there was a way to run the compact/defrag on both my VPR internal and module. Sort of like some housekeeping utility programs.

I had a defrag with my Palm Pro but have not heard of any recently!

__________________

[email protected]

Registered: Dec 1999
Location:
Posts: 47

An Old Time Problem

Same thing used to happen frequently on pre-Windows 95 PCs - [and still can] - while trying to re-index or duplicate dBase or other database files, and lots of accounting programs which were db-based.
- The apps needed free RAM to cache & index in. Fill up RAM, and BOOM! Corrputed databases, trashed links & files. Bye bye data. Could even happen during Reoprt generation while output indexing was taking place. An ugly event!
- The fix, from tech suport, was typically "in the future, make sure there's enough free RAM before starting certain operations."
- More recently, some better-written programs would check available RAM before letting certain operations occur. Not enough free RAM: you'd get a warning message instead of a corrupted file!

Sounds as if whoever programmed this particular application took the easy way out and didn't check available free space - assuming there is such a function in the Palm OS - although I assume there must be.

My guess is that it was written by a newer programmer who never had encountered this sort of problem in the past! Once again - "Those who forget the past, are doomed to re-live it."