Hello Matt
On 26-Nov-01, you wrote:
>
>
>> This does seem to happen to AGA users. It might be due to low or
>> fragmented chip RAM. Matt will correct me if I'm wrong.
>
> It could be anything.
>
>> I see on the CSV
>
> CVS :)
>
>> that Olli has been fixing some low memory bugs, which is probably a
>> very tough job, so these problems may be less in the next
>> update.
>
> I hope Len is using the latest beta and not 3.2 (which I'm sure he's
> asked about before), since image decoders that work for the 3.2.x line
> aren't exactly going to be developed or fixed.
>
> Len, can you check as to which version of Voyager you're running, and
> also which version of the image decoders? If you type "about:" in the
> URL bar, you'll get all the information we need.
>
> If it's 3.2, I'm afraid you'll have to live with the bug until you
> upgrade to the latest beta version, where it may not appear - and if
> it does appear then at least you can be sure that there'll be a next
> beta of this particular line of the browser ;)
>
Regards
Hello Matt,Yes you are correct I am on v 3.2 because I have always felt
comfortable with it,I've been on since it came out but it's only very
recently started playing up.
After last June I have not been able to handle complications too well and my
short term memory is very short.
The details are as follows.....Version 3.2
Image decoder 68040 fpu 11.1
SSL Voyager_ssl.vlib 8.6
At first it only happened on one Amiga but today it appeared on the second
one.
At the moment I have an Appolo acc' and 2.11gig hard drive in my main Amiga.
Hoping you can help,Regards,Len.
_____________________________________________________________________
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
