After months of running without probs and without changing anything on my system, this morning eJukebox (3.5) no longer works, but hangs after
starting Winamp, i.e. even before loading its own interface. It takes up 99.9% of CPU time and the system is super slow.
I uninstalled and reinstalled eJukebox. It then comes up fine, but as soon as the database is rebuilt (rebuilding itself seems to work fine), it
starts Winamp, plays one song and sits forever on "Synchronizing..." It then uses again 99.9% CPU and cannot be terminated.
After rebooting the PC, I have the initial situation that eJukebox will start Winamp but not its own screen.
Help, what can I do???
I use WINAMP 2.91
Solved...kind of:
After trying various de- and re-installs (also reinstalling Winamp, MDAC, IE etc). I finally had the great idea to try to first install 3.5 then
immediately downgrade to 3.4 and finally it works again!!!!
I can now consistently reproduce the problem: Upgrade to 3.5 - eJukebox hangs up. Reboot System, downgrade to 3.4 - eJukebox runs
again. Do the upgrade to 3.5 again: Yep, system hangs!
This means there is some kind of major bug in 3.5 and also that I am now unable to ever use 3.5 or later versions until this bug is fixed. The weird
thing is that 3.5 was running fine for 3-4 days.
Any ideas where I could look, I would really prefer to run 3.5 and future versions rather than being stuck on 3.4. forever.
I would imaging that it must be something that was introduced in 3.5 that has now been corrupted - so the obvious thing is rating - maybe one of your
mp3 has a corrupt rating that 3.4 doesnt look at or use but later versions do. Sounds logical. Maybe backup your database - reinstall 3.4 with just
one album scanned - then upgrade....
but then again im just a monkey without an organ grinder
v3.4 had ratings too so it is probally not that.
Odd that is initially worked and then stopped working....
I am not sure but, if you changed the screen resolution from what it was when eJukebox last ran it could possible cause problems when it is restarted.
As eJukebox now remembers EDV and eJukebox height and restores on startup.
How long did you wait when it was using 100% cpu? It may have been trying to download an image.
Also, when you uninstalled eJukebox did you delete the ejukebox.ini file?
Thanks for the suggestions and help. I did erase the entire program directory after uninstall, so yes, the ejukebox.ini file was also gone. I also
waited 4 hours once, so I don't think the program was doing anything.
For some strange reason, it is now working again, and I know nobody is going to believe me, but the only thing I did different this time (from the
other 4 times I tried) was to use a different directory name for the install.
Before, I always did this: eJukebox install into c:ejukeboxmyname. (Because I have another copy in c:ejukeboxwifename)
After getting the hanging system, I rebooted, did uninstall, removed c:ejukeboxmyname, then installed from the original setup files, but again into
c:ejukeboxmyname.
This time, I chose c:ejukeboxnewname and everything works.
It sounds too crazy and maybe it was just coincidence, but maybe there is some entry in a file outside of eJukebox or in the registry or in a
cache/temp file that needed to be overwritten with a new directory name? Weird.
Thanks again for helping, I'll keep an eye out if I can reproduce this again.
Interesting observation: The hanging eJukebox came back last night. And it was exactly when I selected a track from the same album where it was
hanging up last time: the album "Melody A.M." by "Röyksopp".
Since eJukebox always automatically plays the last track when the system is restarted, there was no way for me to get back into eJukebox.
Again, downgrading to 3.4 was the solution: After downgrading, eJukebox came up fine, I could then remove the offending track from the playlist and go
back to 3.53 without problems.
I played around some more and now I know it is definitely related to playing *any* track from that album: As soon as it starts playing a song from the
album, eJukebox stays forever on "Synchronizing"
The obvious thought was that it may have to do with the Band name containing an "ö" character. But that is not it, as I have another album
by Röyksopp and that one doesn't cause any problem. I'll be playing some more with the tags to see what could be wrong.