DBCacheTool useful on the TX?

[snark]

Hi,

I wonder if DBCacheTool, which can be found at http://www.jade.dti.ne.jp/~imazeki/palm/DBcT/ (http://www.jade.dti.ne.jp/%7Eimazeki/palm/DBcT/) can be useful on the TX. I installed it but I'm not sure which settings to activate and if it'll help the TX or not?

[Cyker]

DBcache and it's opposite, SharkCache will help on any NVFS device. Assuming they're compatible ;)

[snark]

DBcache and it's opposite, SharkCache will help on any NVFS device. Assuming they're compatible ;) What's the difference between SharkCache and DBCacheTool? I thought SharkCache was only for the Lifedrive's particular memory configuration.

[Cyker]

AFAIK (Disclaimer: I don't have a fakeRAM NVFS device anymore so this is semi-2nd hand info)...

DBcache clears out the realRAM on an NVFS device: NVFS Palms do not clear out their hidden realRAM (aka the DBcache?) properly, and lots of people were having "Out of memory"-type errors despite having 200MBs or whatever of storage space left. The only way to clear it is to soft-reset, which was a PITA, so this tool was made.

SharkCache does the opposite - It 'loads' apps into the DBcache so that they start up as fast as pre-NVFS Palms when you actually go to load them: This was made primarily for the LifeDrive because that has the slowest initial/first-load times of any PDA currently in existance (Aside from early PPC's possibly), but is applicable to all NVFS Palms because they all experience this two-stage load lag.
The Flash-based NVFS devices have much lower access times 'tho so the lag is small enough that most people can get used to it eventually, although for people like me who demand near-instant loads it still drives us nuts :D