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. The initial mail was as follows: The most annoying thing about that is that I was able to place 3 orders on Amazon.de, but now Voyager loads the HTML-data of the main document ( about 30k ), takes 1 minute ( as before ), and crashes my whole system with different Guru`s ( see at end of mail ). Any suggestions ? Don`t tell me to use a different browser, because I need the SSL - capabilities of Voyager. And since I do not yet have a registered version of Miami I can`t use the SSL - plugin for it in connection with a different browser. And, to be honest, I like Voyager and would appreciate to use it instead of IBrowse with Amazon.de and other e-commerce sites. So, any help will be appreciated, now my system specs: A500 68020 CPU @ 33 MHz 8 MB Fast-RAM 1 MB Chip-RAM Seagate IDE HD 1.2 GB WD IDE HD 2.5 GB Acer IDE 20x CD-ROM Voyager 2.95 Miami 3.0 WB 3.0 ( 39.106 ) KS 3.0 ( 39.29 ) Setpatch 43.6 I have some other tools running, but I tested Voyager on a clean installation of WB on a spare partition and encountered the same problems. I`m using the following settings in Voyager: Toolbar buttons = text only Hide transfer anim icon = yes Use double buffered blits for transparent images = no Dithering = none Color quantization = Simple DCT processing = Simple Cache = 500MB / Verify = once per session / Maximum size = 2048 / Cache Images = No Nothing = yes in security The following Gurus are caused by the crashes: 8...003 / 8...006 / 8...004 / 8...00B According to DaLastAlert those are ACPU_Errors and Line F Emulation_Errors, but sometimes I get some Corrupt memory-adresses detected in free-mem errors, too. I think the problem is something with Voyager itself, because I tested it without everything else. I tried it with in the WB - Window in PAL:HighRes 640x256 and Overscan, on a clean installation with WB, MUI and Voyager on the partition and my knowledge is at the point of no return. Help me, please. Best regards, [EMAIL PROTECTED] Direct replys to [EMAIL PROTECTED] would be fine. End of initial mail: H E L P . I ` M S T U C K . Regards, [EMAIL PROTECTED] ____________________________________________________________ Voyager Mailing List - Info & Archive: http://www.vapor.com/ For Listserver Help: <[EMAIL PROTECTED]>, "HELP" To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"
