3.0b out (!)

[musicmusic]

Grab it at http://ftp15e.newaol.com/winamp/clie...mp3_0-full.exe , was uploaded several hours ago.

But what's new, except smaller download? Seems exactly the same to me, except its marked 3.0b. Its stil build #488, if that makes sense..

[Tomato Face]

[edit]Nevermind, I'm a moron[/edit]

[Electronic Punk]

Sawg: as I am unsure, would the wa2update in your sig already be in this re-release or should I still install it ?

[evil_oj]

uh, what's new about it?

[Gonzotek]

Originally posted by Sawg
Security Fix (and no AOD)

Winamp 3 (1.0.0.488) XML parser buffer overflow

No more AOL on Desktop (and everywhere else). AOL unloving people may commence rejoycement....now.

-=Gonzotek=-

[Dazog]

No more AOL crap

and

1 security Fix.

DAtz IT

[Gonzotek]

It's mostly a security fix release. The no AOD thing is for all future builds (I think). I think they just wanted to get the fix out fast, since it's a security related thing.

-=Gonzotek=-

[ctkatz8086]

found a problem

don't consider changing any options in this new version, because you simply can't. i tried turning off two winamp 2 plugins and when i restarted winamp3 they were still on. also, changing the names of playlists and adding playlists is a futile effort, it reverts back to whatever you had before. i'm not discouraging downloading it, just making you aware of these problems.

[evil_oj]

Damn, this means that a new Winamp3 release like build 490 or higher is a long way off. Why would they release a fix for an older version if they were planning on releasing a new build soon? Or is this build from months ago and people just didn't see it?

[musicmusic]

Peter said on the other forum, that 490 is (nearly?) ready, and may be a public "beta" development build, and you'll probably find it less stable than #488..

So they probably relased this one fix release as a new main page release is still a way off.

And know, believe me this hasn't been lurking around for a while, becuase the upload date was something like yesterday, 17:53GMT, and the studio.exe is dated 2nd Oct, and it fixes that security bug discovered only just over a week ago..

[Darkain]

Originally posted by musicmusic
Peter said on the other forum, that 490 is (nearly?) ready, and may be a public "beta" development build, and you'll probably find it less stable than #488..

well.. some random people claim to have b490... and these same random people claim that is in deed in fact less stable.

/me just wishes there was an update to betanews.... /me wants to know what has changed since b489.

as for it being a public beta... well, i currently dont think it will be. but i could be rong.

[Dazog]

Its not that 490 is Less stable.

its MORE stable, there are just MINOR bugs that need to be fixed before public consumption.

So wait until the NEXT public release BEFORE you say its not Stable.

These builds are meant to catch these bugs so when the Public release is close it will rock everyones world.


so yeah

[Electronic Punk]

Originally posted by musicmusic
And know, believe me this hasn't been lurking around for a while, becuase the upload date was something like yesterday, 17:53GMT, and the studio.exe is dated 2nd Oct, and it fixes that security bug discovered only just over a week ago..

Thought it was now winamp3.exe ?

[YtseJam]

3.0b is still build #488 + the security fixes.

Studio.exe is in #488, winamp.exe(or is it winamp3.exe? shrugs) is most probably in build #489 and above.

[ctkatz8086]

Re: found a problem

Originally posted by ctkatz8086
don't consider changing any options in this new version, because you simply can't. i tried turning off two winamp 2 plugins and when i restarted winamp3 they were still on. also, changing the names of playlists and adding playlists is a futile effort, it reverts back to whatever you had before. i'm not discouraging downloading it, just making you aware of these problems.

this place has strange rules about editing...
anyway, revising my statement, it looks like not being able to change options in 3.0b is a compatibility issue. apparantly it has a problem with the winamp 2 plugin manager, winamp title bar control (wa2 plugin), bluecave winamp slider (wa2 plugin) or a combination of the three.