»

[Targhan]

Just in time for Christmas, Voyager3.3.125 is available from http://v3.vapor.com/

Source: Vapor Web site

[KennyR]

I keep making the same mistake each time a Voyager beta comes out - I think it's going to be stable. It never is. This new beta crashed within 30 seconds of me first running it. I'll stick to IBrowse. ;-)

[ikir]

I'm using it from hours.. and all works....
Voyager are stable on some system and not on others..... :-?

[4pLaY]

Hmm try asking what config guys who got it stable has got! and then i mean software wise also! its well known that Amiga users these days run a zillion paches to try and get missing features in the OS itself so its no wonder it works on some and others not.

[SilvrDrgn]

Funny they should put out this update now. Maybe the imminent iBrowse v2.3 release gave the Vapor guys a "push".

[KennyR]

Well, I don't run many system patches at all, and V³ has always been flakey here, while others with the same config as me say it's as stable as a rock. Not many, though. ;-)

[Castellen]

I've been using the V3.3.122 beta for months. It seems to be
completely stable on a majority of websites (E.G. Amiga.org, Aminet,
etc) but crashes every time on certain others. Not necessarily ones
with heavy use of Javascript and Flash. Seems to be the way Voyager
reacts to some HTML??

I'll see how the new version goes, I've just downloaded it.

I think having an up to date MUI setup helps a lot with V and many
other MUI apps.
If it helps anyone, I keep an updated full archive with
cleanup/install instructions. Download it from:
ftp://mp3:mp3@amiga.serveftp.net/Uploads_here/FullMUIsetup.lha

I also run MCP, MagicMenu, ENV handler (Happy Env), Cyberpatcher, etc.

Merry Christmas,
Anthony.

[Castellen]

KennyR: OK, I agree with you!! Crashed within 20 seconds of running
it here, but a second time seemed to run a *BIT* better.


In short, I wasn't overly impressed by V 3.3.125.
Aside from the fact it contains a few very minor bugfixes, it's far less stable than version 3.3.122 which I have been running since about March.

It appears to be a bit faster at image decoding/layout, but it might have been me dreaming.
It seems more willing to do more complicated Javascript things. Starts to do them, then crashes badly. So a number of detailed Javascript based sites still don't work, for example AirNZ online flight booking.
Most of the SSL encrypted online banking still works fine with my bank, though there are still the same layout errors.
It crashed without any reason on common sites I never have problems
on, such as Amiga.org as well as a number of "simpler" ones.

Haven't tried it on an 8 bit screen (I refuse to) but it had the same problem on 16 and 24 bit screenmodes.


Quoted from the Readme, the bugfixes from version 3.3.122 to 3.3.125 are:

- Imgdec: transparent images could have their background not refreshed
properly (Zapek)
- General: V wouldn't execute any external command when being started from CLI
(Zapek)
- General: disabled single window mode since it is the cause of 99% of peoples'
experienced crashes. It'll be back when it works (Neko)
- JS: fixed crash happening with some "popup" windows, thanks to Henes (Zapek)
- Layouter: pen allocation precision was slightly wrong (Zapek)
- GUI: more efficient prefspage switching (Zapek)
- Net: fixed some possible buffer overflows in POST requests (Zapek)
- General: fixed small internal memoryleak which could happen with some custom
context menus (Zapek)
- JS: fixed V.MorphOS crashing on most string from real datatype conversions,
libc bug (Zapek)
- General: no longer barfs when Busy.mcc isn't installed (Zapek)
- General: no longer barfs when Listtree.mcc isn't installed (Zapek)
- Network: added SSL support to the MorphOS version (Zapek)


The single window mode one was obvious that it never worked even slightly, so no one ever used it anyway.
Another strange thing I noticed:
Compiliation date of 3.3.122 = 9/3/2002
Compiliation date of 3.3.125 = 2/5/2002

So it's been done since about May, but only now have they released it. Could it be that since the next version of IBrowse is about to be released, the V3 team decided:
"Uh-oh, the current V3 beta has timed out, and IB are about to do a release, quick do something!"
"But we've only got this less stable version with a number of insignificant bugfixes..."
"That'll do, we'll release that!!"


Personally I reccommend sticking with 3.3.122 in the meantime, I'm
using it again now.

It's usually quite stable, even though it does have that annoying
"beta version timeout" requestor on startup. Hopefully they'll
actually make some IMPROVEMENTS on the next release!!!! I've posted a
number of detailed bug reports AGES ago which still seem to have been
ignored.

Other things frustrate me with regard to features going missing. For
example one of the earlier versions had a nice text search ability
which has been missing for a while, the "save as ASCII text"
feature doesn't work, "Save image as.." doesn't work, the printing
never has worked (I think?) or at least not properly. plus lots of
other little things.

Seriously, I know writing a prog such as V3 would be a mammoth task,
one that I could never hope to do myself. But I find it very annoying
that over so much time, that there has been so little apparent
development/improvements.

So KennyR, I really hope you are not mistaken with the next release

Anthony.

[logain]

Hi,

reports says, that the problems diappear when increasing Voyagers Stack to 200000 bytes.

[Ivan]

Well the icon has about 50k stack set up.
They ought to raise it at least.

One thing i did notice was Voyager was insanely
unstable on a pubscreen named Voyager.1 with
a screentitle the same name. Changed them both
in PSI to Vo and it seemed to crash quite a bit
less for me. Though it's still crashing far too
often for a commercial product. Sorry Vapor, i
like Voyager too but its just plain unstable
for me.

Alot of MUI based apps seem to have thier share
of querky bugs so it may be that alot of things
are out of thier control with the Voyager
crashes. MUI (which i have a number of problems
with) is supposedly going to be updated so
let's see how things pan out.

Ivan

[Targhan]

Well, the problem is not just in our heads about V125 being unstable.
I've just upgraded to V3.3.126 now. I've posted a new entry for it,
and it seems to be more stable on my system. I still have an issue
with yellow alerts, but no boom-crash since installing it. Also, you
may want to bump up the stack for Voyager.

I found a post on the V m/l that seems to indicate that some
of the MUI libs (.mcc) may have been downgraded by accident. You may
want to check the version numbers of your mui classes. I'm not
stating that this is a fact, but it's better to be safe than sorry.

[Castellen]

@Targhan:
Been running 3.3.126 for almost 3 hours now with no problems at all.
Yipee!

I think there were a few earlier MCCs in with V3.
Th best way to check is manually copy any "new" MCCs into your
MUI/LIBS/MUI directory using DOpus, which automatically does a version
check.
Decent installer scripts have automatic version checking as well.

The MUI archive of mine (see earlier posts) does contain MCCs later
than the ones included with V3.