In a message of 10-Apr-00 David Gerber wrote:

 > Well, for obvious reasons V won't calculate the size of the cache everytime
 > you start it so it stores it. Since this is a new feature it might not be set
 > correctly. Open the Cache Pruner and press the 'Start' button, it'll begin
 > scanning the cache directory then if the computed size doesn't match the
 > stored size it'll update it and tell you to press 'Start' again.

Neat.

Another cache problem. My finger slipped above the "Goto disk cache" which
as you most probably know is the same as "About:cache". IT WOULD BE VERY
NICE TO HAVE A SAFETY REQUESTER WARNING: "Scanning cache might take en
eternity and might crash your computer" "Continue | Cancel"

Well, as I have mentioned more than once, my cache is close to 200 MB, so
Voyager scanned and scanned and scanned and after around 8 minutes it
stopped scanning. Then nothing happened -- I suppose it was sorting the
entries. After another 8 minutes nothing seems to have happened. Fifteen
minutes or so later I noticed that the mouse pointer had become corrupted,
I switched to the Workbench that told me that Voyager had eaten all the
memory as well. Voyager didn't respond in any way. I decided to close
YAM and NewsRog before reboot ... this resultet in a crash which I think
neither YAM nor NewsRog is to blame for :-)))

If you add a safety requester for that damn "About:cache" I will buy you
a beer next time you are in Denmark :-)


Uffe Holst

____________________________________________________________
Voyager Mailing List - Info & Archive: http://www.vapor.com/
For Listserver Help: <[EMAIL PROTECTED]>, "HELP"
To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"

Reply via email to