Julian Aronowitz said,
> One person, on the Voyager list stated that, one of the reasons that
> MS Windows does not crash when deluged by intense graphics is because it
> does a virtual memory routine in using the disk drives for extra storage
Nah.. Windows crashes plenty often enough. As far as browsers go, V
is being developed by a handful of gifted people in their spare time,
whereas MS can put 500 people on it 24-7 if need be. Also, if a site
crashes Explorer the person creating it will notice and change the
problem so it doesn't. In the unlikely event they make it truly
compliant with the standards it will likely work ok with V too.
> This brought to mind a program/package called, "GigaMEM."
Or VMM was another one...
> recall whether this was a hardware/software combo or just a hardware or
You need an MMU, but after that its software.
> just a software setup. If it is only a software setup, then, will it
> work on an Amiga running AmigaOS 3.5? And, would it solve the problem?
Yes, they "ought" to work ok under OS3.5. (Neither program has been
updated in years though.) No, it wont solve the problem. In fact,
since AmigaOS was never designed with VM in mind it can increase the
number of crashes quite a lot until you set it up right.
> the reviews and comments). I am more interested in whether this is a
> plausible alternative to getting a graphics card with eight megs of RAM,
> for itself?
The virtual memory system will not increase the amount of chipram you
have. If you have a gfx card in the first place, or are running FBlit
or similar, VM *might* put off the crashes for a bit. Ultimately,
though, you can and will run out of ram, regardless of how much you've
got (real or virtual) and the crash will happen again.
As someone else pointed out, the program is supposed to check whether
it got the ram it wanted and fail gracefully if it didn't.
Unfortunately this isn't as easy as it sounds in a program as complex
as V and the best approach would be to narrow down the exact
circumstances under which the crash occurs and tell the authors about
it in as much detail as possible. The problem is not as simple as
just "running out of chipram" because I've had that several times and
it simply fails to display the image (which is fine). In V2.95 it used
to nuke every time.
The best compromise is to use something like FBlit. This will avoid
the use of chipram where possible (and where the application software
was done right). V3 supports it fine and runs faster for it too. You
can never replace a true graphics card though.
Regards,
Ian
===
_____________________________________________________________________
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
