WimAMP Crashes in WinXP Pro
 

PS: Other then tweaking WinAMP Buffers,I will attempt to use an Older
Windows driver First as "eviltechie" suggests

SafeMode :o))

Well it's 4 hours Later

I Over-Wrote the SBA2_WEBUP_PCWDRV_1-84-40 driver with the SBA2_EAX4DRV_031031 Driver and it not only Sounds better but WinAMP has not crashed.

One thing I did do different on this TEST was to leave "CTHelper" Enabled in HKLM\RUN.

Now I can't say if CTHelper being Disabled was the Culpert or Creative Lab's Last WEB Driver SBA2_WEBUP_PCWDRV_1-84-40 .

I'm NOT Saying the Older WEB Driver did the trick but the problem may be related to whether you have CTHelper ENABLED in HKLM\RUN.

Any I've narrowed it down as WinAMP has NOT Crashed.

Good Luck! SafeMode :o))

CTHelper may have to be Enabled in HKLM\RUN

Process File : cthelper or cthelper.exe

Process Name: Plug-in manager

Description : Background task that works as a plug-in
manager for Creative drivers. It helps the
third party manufacturers to produce drivers,
add-on features, and fixes that will
integrate with a tighter fit with Creative
sound drivers and utilities.

Company: Creative Technology Ltd

System Process: No

What do you think? Should I run another 4 hours Test with CTHelper
Disabled then Load SBA2_WEBUP_PCWDRV_1-84-40 and run another
4 hr Test with CTHepler Enabled - lol

Episode 954 "A day in the Life of a Geek"

SafeMode :o))

btw, for people experiencing slowness with winamp, try out foobar. It's much more capable, if not as pretty, as winamp, and OSS and uses much less memory and CPU, and has higher quality I/O

thats what i noticed first too...
maybe reformat in NTFS?


*i like iTunes - but it eats your processor and doesnt read WM created files

Yea i tried itunes.. but it's too big of a pig for me.. I even "bought" a song (tipsy.. from one of those caps that give you a free song)

It's Me Again:

I Sent SB a Msg - Seems he forgot to Disable his OnBoard Sound :o))

AnyWay Gotta thank James - I had Forgotten about FooBar.

Downloaded and Installed v8.1 Special -> Very Impressive.
They sure have the Filters covered and Kernel OutPut WOW!

I rather prefer FooBar's STD GUI Window as it is faster to Navigate then WinAMP's Skin.

So Far NO CRASHES with WinAMP using Creative's Latest Audigy2 WEB Driver, account WinAMP is no longer on my System :o))

Really haven't had the Time to give FooBar a Full Work out yet but from looking at its components looks promising; however, I might do something about them UnGodly File association Icons - ROLF

If I ever get Replies from Creative Labs and WinAMP Techs, I will Post the Info and Let you know how FooBar fairs out for me.

That's one Impressive RIG you got DRAGON - I'm lookng to UpGrade to N Force 2 MCPT - either Asus or Abit shortly - why not this will be last chance to use the Best that 32Bit can offer while 64bit powers up.

Thanks for the InPut Guys.

SafeMode :o))

Here's a thread over at WinAMP Forums regarding WinAMP compatability with latest Creative WEB Driver UpDate for the Audigy2

Maybe we can Find a Solution for Audigy2 Users to use WinAMP effectively:
http://forums.winamp.com/showthread....17#post1351417

I'm am NOT Choosing FooBar over WinAMP or Vsa Versa, it just that Users should not be excluded from using software because of the Hardware they have.

SafeMode :o))

FooBar has worked flawlessly with Creative's Last WEB Driver SBA2_WEBUP_PCWDRV_1-84-40 for the Aufigy2.

Direct Sound v2 and Kernel Streaming has been most effective, STD Direct Sound did not fail but does not Sound as Good, I had one incident with WavOut were FooBar stumpled but it picked up - probably because I had to many too many apps on the go.

It's really too Bad WinAMP can NOT handle these Drivers because they FIX issues associated with the Audigy2's THX, EAX,OpenGL and ASIO Tracks.

I'm Impressed - Thanks James