|
|
|
|
|
by alternatetwo
1593 days ago
|
|
I think it was precisely your blog post (?) which I read that detailed that it was pre 5.666! Is the problem that now that the source is out you can no longer claim plausible deniability you never saw it or what exact complications does it cause by just being leaked? And one other (WinAmp related question) - I still use 5.666, but it has the weird issue that it's the one program that Windows can't get to close itself when shutting down ... why would that be? Is that fixed in WACUP? |
|
With the clear demise of 'classic' Winamp with the whole 'set the tone' & seemingly nft related crap the new lot are now going for, what was leaked still equates to what's gone to the new owners (which was one of my pre-sale tasks) so it's into the messy state of who has recourse against it being leaked.
As for the issue, I don't remember there being anything specific that is in place to make it intentionally block system closing unless it's taking too long &/or it's crashing. I don't have the Winamp core handling that aspect of the running process with the current preview build (& the beta builds barely let the Winamp core do anything with it being able to run without it with some missing features) so the best way to find out if it behaves would be to try it out as a portable install so it doesn't mess with your existing Winamp install.
-dro