Voyager 3.3.126 working!!

[redrumloa]

Wow I am stunned! I could never get 3.3 working on my real
miggy, yet I got it working under WinUAE right
out of the box! So far it's acting just about perfect which is
incredible considering how bad Aweb started crashing!
So far so good!

Time to dust off the key file? Maybe!!

[odin]

Eeeeeeeeeeerm.....WinUAE->runs on windows,  right? =)

Opera/Mozilla runs on windoze, right? =)

May I ask* WHY* :crazy: you'd wanna use V then? Apart from the gimmick maybe.

[Vincent]

Lol, another alternative browser to IE on the PC :-D

I like it! :-D
 :roflmao:

[blobrana]

Yea , i got my voyager to be quite stable as well.
Very strange...Could it be winuae?

Still,  i use my ibrowse as my prefered browser.

[redrumloa]

May I ask* WHY*  you'd wanna use V then?

Because I paid ~$45USD for the keyfile and hardly ever got to use it!!!!!!! If I pay for something, gosh darnit I want my money's worth;-)

[Argo]

So, what your saying is "What's the point of UAE?"

[Castellen]

Odd that V 3.3.126 won't run well on your real Amiga.
I use it here on this A4000T/060 as my main browser.
It only ever gives problems on certain websites, quite often ones with lots of wacky flash anims and Javascript.

All of the sites of the sites I use frequently such as Google, A.org, Amibench, etc, work perfectly, never crashes.
Got an uptime of around 3 weeks at the moment, V has been running 90% of the time.

It's still far from perfect, but it does most of what I want to do.

[Targhan]

Why not find out what those with stable Voyager3.3.126 are running configuration wise?

Those that have it working under UAE, are you using the "native" screenmodes or one of the P96 derivatives?  Same question for the guy with the 060 up there :-?

[BADHead]

i had no problem running version 3.3126 on my
amiga (060 version) i had been using AWeb up
untill now because i had trouble with previous
versions so i deleted the whole drawer and
re-installed it  :-)  :-)  :-)  :-)

[redrumloa]

Targhan wrote:
Why not find out what those with stable Voyager3.3.126 are running configuration wise?

Those that have it working under UAE, are you using the "native" screenmodes or one of the P96 derivatives?  Same question for the guy with the 060 up there :-?

Well it looks like everyone here currently has it working. In the past my problems with Voyager was well documented here. I had alot of people giving me suggestions yet not a single one worked:-( Back then a few people came out of the woodwork to say they had the exact same problem. It was never resolved. I'd point you to those old threads but they were purged in the big cleanup:-(

Working under UAE now, P96-UAE screenmode. Previous problems were with both P96-Prometheus/Voodoo3 AND with ECS on a 060 machine.

[ikir]

The last Voyager is very good. It support javascripts and flash, and it is quite stable. Good job Vapor

[Castellen]

I presume I'm "the guy with the 060 up there"??

The guts of my current config is:
AT A4000T, Cyberstorm mkII+128Mb fast mem
OS3.9+BB2
PicassoIV GFX with Picasso96 V2.0(?)
Miami
DOpus Magellan

Patches include:
Cyberpatcher
Magic menu
MCP
Executive
ReqAttack
Powersnap
Env-handler(HappyENV)
AltTabber
Newchange

to list just a few.

I run V in an 800x600 16 bit (64k colour) screenmode.

Some people suggest increasing V's stack size helps a lot.  Got mine set to 800k.
Having lots of fast mem and using GFX card screenmodes seem to make a difference too.  Check you're using the latest version of P96/CyberGFX.

Also making sure your MUI system contains current versions of bug-free MCCs also help.
I keep a current archive of these if anyone needs them:
ftp://mp3:mp3@amiga.serveftp.net/Uploads_here/FullMUIsetup.lha

Read the included manual install instructions to tidy, repair and update your current MUI system.

I do not much like your choice of avater my friend.

BADhead, do you know or fully understand what the person concerned who's picture you are using for an avater went through, if you do not. Then may I suggest you find out.

[KennyR]

I'm afraid V3 still does all its old tricks here. Hits, gurus, hangs, reboots, memory list trashing, system freezes, failure to close the screen when I close V3, crashing on close, bring up weird requesters ("Please insert volume iµµ¡°ø¡µðøµ¤°å"), flash crashing, etc. Often a crash happens within 30s of loading v3. It also can happen if I leave it alone for ages, so it's not something I'm doing. I also have a system that can run all day without a crash, so I'm not running hacks either.

It's an unregistered copy, so not a crack either. I never got around to register it because it has never, ever worked here. I'll continue to try new betas, but as far as I'm concerned IB2.3 is the only Amiga browser to use.

[AmiDelf]

Voyager crashes a lot.. To much for me.. Not my browser.. Go for Ibrowse.. its much faster and much more stable...

Regards,
AmiDelf