> Anyway, even corrupted cache files shouldn't make V unstable. If yes it means
> there's a bug (although the code didn't change from 3.1 to 3.2).
It was reported numerous times by a few people on the NCML, since the V3.2
release, that 'V3.2 crashed all the time...until I deleted the cache and
then restarted V. Now it works fine!', so it was a suggestion based on their
comments.
Chris.
--
Chris Wiles
Active Technologies - http://www.active-net.co.uk
____________________________________________________________
Voyager Mailing List - Info & Archive: http://www.vapor.com/
For Listserver Help: <[EMAIL PROTECTED]>, "HELP"
To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"
