On Tue, 11 Jul 2000 01:59:03 -0500 (CDT), Julian Aronowitz wrote:
> My restating my questions was because no one who had worked on V,
> bothered to even enumerate some of the reasons V does such a crash rou-
> tine. After all, AWeb has also crashed, but it does not seem to take
> the whole computer with it by forcing the computer to revalidate the
> harddrive that has the Cache files of the browser. This thing that V
> does makes no sense to me, which is why I posed the question and why,
> until I get some intelligle answer, I will have to refrain from using
> it, because I do not want to take a chance that I might lose everything
> I have on my harddisks. (I do back things up and I can regenerate most,
> but it is a pain in the neck and butt.)
Well, if V crashes while it's writing to disk (the cache or file downloads),
then you end up with an unvalidated partition, assuming you use FFS.
There's no crash() routine, just bugs :)
The next version will have many things changed. The layout engine is
currently being rewritten with robustness in mind. Until then, you might
want to either:
- disable the disk cache by putting a size of '0' in the prefs
- make a small partition (~30 MB or something) where to put caches (not only
Voyager, but all the programs doing caching) so that it's revalidated
quickly and you don't have important data in it
--
David Gerber
VaporWare programmer
http://www.vapor.com/
finger [EMAIL PROTECTED]
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
