Thomas is correct. The only limit on number of files in cache that Michael has in the software is a top limit of 256 on the *report* of number of files in cache. <G> It's fun ... hit F8 and the percentage starts moving over the green bar ... but then it disappears as your HDD deletes more and more files. <MG> I've even had my Norton Commander politely tell me "Not enough memory to show more than 550 files ..." in the cache directory. <G> A full cache has never caused me to crash. Lots of *other* things have, over the dozen or so versions I've run [or attempted to run in the earlier days], but never the cache being too full. Superfull cache can slow things down, with software having to sort through the index to find what it's looking for. l.d. ==== On Thu, 24 Feb 2000 03:58:55 -0500 (EST), Thomas Mueller wrote: > .... Michael P. has set a limit on 256 items in the cache and when it reaches > that limit, Arachne just stops! Clearing the cache (and CACHE.IDX) with the > F8 key will usually get Arachne zipping along again. On one of my computers > I have Cache and CACHE.IDX on a resizeable RAM drive that clears every time I > leave Arachne; on another computer, I hit F8 after I hang up. The "sleep" > problem has not really been a problem with 1.6b1. > When did Arachne start having a limit of 256 items in the cache? I have > exceeded 1000 and could tell, from the DOS prompt, by typing 'dir cache' when in > the Arachne directory. > Support the International Alliance for Compatible Technology > http://pages.cthome.net/iact/ -- Arachne V1.60;b1, NON-COMMERCIAL copy, http://arachne.cz/
