Registered: Mar 2000
Location: Hacienda Heights, Ca
Posts: 302

Are the cache files you are referring to named:

FfsTempDbCache - 327k
and
FfsTempDirCache - 5k

I have been wondering what these file are.

__________________
Bret Snyder<BR>If you don't know where you're going,<BR>You'll probably end up somewhere else.

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

quote:

---

Originally posted by Bret Snyder
Are the cache files you are referring to named:

FfsTempDbCache - 327k
and
FfsTempDirCache - 5k

I have been wondering what these file are.

---

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

quote:

---

Originally posted by purplemd


HHHEEEYYYY why would the files be the same size as on MY visor???????

---

Ditto - same size as mine (that I deleted some time ago)

TKH: Still no crashing on copying 1K more - same message as before. (Re: B5 - tell all, tell all! )


---------------
Sorry - yesterday was the deadline for all complaints.

Registered: Nov 2000
Location:
Posts: 56

This is more of a "me too" message than anything new but I'm pretty sure that I had the same size cache files appear on my RAM as well. I think the compacting freeze problem is closely related to these cache files and RAM in one way or another.

A couple questions readily come to mind:

-Has everyone that saw these cache files on the RAM gone through at least one Compacting session with their module?

-Same question as above but have you had a Compacting freeze?

-What is this file? Is 327kb some predetermined memory block to be used as scratch when defragmenting files on the module? Or does this file contain information on where to put the files on the module?

-Are the file sizes the same when an 8mb Compacts/crashes compared to the 16mb module?


Also, I doubt that 3rd party programs running in the background are the cause (or at least not the only cause) of this problem as I had no Hacks or 3rd party launchers even installed when I had any of the compacting freezes I experienced. I later had 4 Hacks and SilverScreen running and had a successful Compacting with less than 10kb on the module.

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

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

Okay, so bottom line...we think the compacting failure is caused by a lack of free memory on the handheld. There is no evidence of conflicts caused by software, program files on the module, size of transferring file to the module OR hacks.

In short, ALWAYS make sure you have at least ~ 500 k free on the Visor before entering the FAF application?

Does this sum it up? Is it accurate? We can polish it up and email it to Handspring technical support.

Registered: Dec 2000
Location:
Posts: 384

Hmm...

FfsTempDbCache - 327k
and
FfsTempDirCache - 5k

I don't remember ever seeing these two files. Are they on the module or on internal memory? Come to think of it, I do remember seeing an unfamilar file on my internal memory once, it was about 300k. I have stayed under 300k of free memory for almost 6 months without any corruption errors.

__________________
Fat's

Registered: Aug 2000
Location: Cincinnati, OH USA
Posts: 107

Let's do --- Enough info in this thread to keep them busy and useful

quote:

---

Originally posted by purplemd
Okay, so bottom line...we think the compacting failure is caused by a lack of free memory on the handheld. There is no evidence of conflicts caused by software, program files on the module, size of transferring file to the module OR hacks.

In short, ALWAYS make sure you have at least ~ 500 k free on the Visor before entering the FAF application?

Does this sum it up? Is it accurate? We can polish it up and email it to Handspring technical support.

---

__________________
MANY BLESSINGS!
Peace and Every Good!


Michael W. Cristiani
[email protected]

Registered: Nov 2000
Location:
Posts: 56

Running hypothesis

quote:

---

Originally posted by purplemd
Okay, so bottom line...we think the compacting failure is caused by a lack of free memory on the handheld. There is no evidence of conflicts caused by software, program files on the module, size of transferring file to the module OR hacks.

In short, ALWAYS make sure you have at least ~ 500 k free on the Visor before entering the FAF application?

Does this sum it up? Is it accurate? We can polish it up and email it to Handspring technical support.

---

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

Registered: Jun 2000
Location:
Posts: 17

Ok a slight twist to the same problem.I have multiple databases on Think DB2 and Mobile Dblt. In order to free up memory on the visor I have transfered the Apps and the databsasses to the 8MB flash module. Once there I cannot access them even to just view a database. Now I Understand that I will not be able to edit the databases directly on the flash module. But I was expecting to be able to just view them. When I try to access them I get the infamous "Fatal Error". I also have tried leaving the Apps on the Visor and just transfering the databases and that too causes the crash.Any help or input would be greatly appreciated.
Thanks.

Registered: Nov 2000
Location:
Posts: 56

3rd party software issue not related to "Compacting"

quote:

---

Originally posted by katavia
...slight twist to the same problem....databases on Think DB2 and Mobile Dblt...I have transfered the Apps and the databsasses to the 8MB flash module...try to access them I get the infamous "Fatal Error".

---

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

Registered: Dec 2000
Location:
Posts: 1

Ive experienced 2 flash freezes, loosing all data on flash module,
both times happened when the batteries were slightly low, and the freezes were initialized by a low batteries message
(compacting exerts a large drain on batteries)
had about 10 compacts since these problems without incident,
as i do all file transfers shortly after inserting new batteries,

also place all files regulary updated to end of module to reduce need for compacting.

hope this helps.

topcat