"Cooperative update outside range" errors NON-STOP after starting Winamp

[ClintJCL2]

Okay. I do a weird thing where I simply move my winamp folder from computer to computer when I build new computers.

Why? I depend on a lot of custom plugins, so I can't just download a new one. It's a 1-2 hour process for me to roll out a new winamp that does what I want it to do. And that's only if I kept my notes up to date.

So I got a new computer and moved winamp to it. No problem. It played music 24/7 for a month straight.

Then yesterday, after rebooting (finally caught up on windows updates), whenever it comes up, i get that error:

"COOPERATIVE UPDATE OUTSIDE RANGE"

Over and over. It won't go away. I've googled the people who have had this error in the past, and it is related to winamp's playlist generator.

Well I don't use that.

I even removed the DLL in trying to fix this problem.

It still happens!

I will update more, but I have to run tto a job interview. I'm hoping to get this resolved before work takes over my life. I don't want to have an error dialog on my screen for the rest of my life. That's no life

[Aminifu]

It sounds like 1 or more of the Windows updates is causing your problem, since Winamp was working before you added them.

Anyway, all of the Gracenote supported stuff (auto-tagging, playlist generation, etc.) is no longer working. The Gracenote support contract was with AOL, which no longer owns Winamp. You should remove all of the Gracenote related files.

Use the Winamp Info Tool (http://koopa.meggamusic.co.uk/infotool/) to make an extended report of your current installed configuration. The tool will put the report in a zip file, use the advanced reply editor to attach it to a post. This report provides detailed information that will eliminate the need for asking a lot of basic questions. The download link is on the bottom right side of the page I provided the link to above. Some antivirus apps give a false positive response, so you may need to temporarily disable your AV (or put the tool on the AV's scanning exclusion list) in order to download and run the tool (the tool is a standalone app, installation is not needed).

[ClintJCL2]

Awesome!

Whoa, there's a tool for that? Where've I been?!?! Oh, right! Busy happily using winamp

I'm on it! (didn't get the job tho)

[ClintJCL2]

That tool was fascinating to use and read, and I'm glad I also discovered this Winamp Backup Tool that those same guys make. Good finds. Thanks!

[Un?]fortunately, the problem went away simply by installing the tool.

The tool did not know where winamp was installed and said this was bad. I gave it that info. That seems to have been the most likely thing to fix the problem.

That kinda makes the tool even better than I expected! It didn't just diagnose!


You, sir, must be a grand master at this. Thank you. Best winamp support experience in 15 years.

[Aminifu]

You, sir, must be a grand master at this. Thank you. Best winamp support experience in 15 years.

Thank you. Glad things are working for you again!

I have experience, but I'm not a grandmaster at this. I have taken the time to read the stickies on how to diagnose and report problems (http://forums.winamp.com/showthread.php?t=161361 and http://forums.winamp.com/showthread.php?t=66558).

The Backup Tool is useful, but it may not be aware of all the 3rd party plug-ins you use. So you may have to continue to backup those yourself.

Too bad about the job, maybe you'll get the next one.