> Hi there,
>
> I still have the same problems. Everytime I try to access
> http://www.amazon.de
> or http://wuarchive.wustl.edu Voyager crashes my machine. I
>
> - raised the stack from 52000 to 104000
> - switched off image and background loading
> - set the image cache to 512 kB
> - deleted the cookie.1 file
>
> I have about 4MB of free FastRAM and about 800kB of free
> ChipRAM when Voyager attempts to load the sites. Today I
> received a ...6 and some ...3 Guru`s and I don`t know
> what else I should try.
Have you got a spare 8Mb SIMM to put in your accelerator?
I've got this hideous feeling that this is a hardware
problem. Most of the guru's you mention are caused by
memory access violations of some sort.
Either the CPU has accessed data and tried to execute it
(0x80000004), is accessing data starting with 0x0A or 0x0F
in which case it's passing it to the FPU/MMU which either
isn't there or doesn't understand you (0x800000B etc. IIRC)
Or 0x80000003 which is accessing data at odd addresses.
Or 0x80000006 which I think I now remember as being a bus
error. My A1200 did this for years until I replaced the SIMM
for a bigger one. Then it stopped. The SIMM flatly refused
to work in a PC, because the memory count failed, or if
unlucky, himem.sys checked the memory and failed it.
Either way, something on your system is either corrupting
memory, messing with pointers to data and code, or you're
running out of stack and popping rubbish into your registers
for the CPU to execute.
Can you try the SIMM in a PC at all?
Can anyone recommend a memory scanning program? :)
--
Matt Sealey [EMAIL PROTECTED]
Distributed Systems Support
Computer Centre
University of Leicester
____________________________________________________________
Voyager Mailing List - Info & Archive: http://www.vapor.com/
For Listserver Help: <[EMAIL PROTECTED]>, "HELP"
To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"
