I haven't changed anything in my playlists since upgrading to 9a a few weeks back. Am trying to catch up, but emplode keeps falling over with the above error code. I'm trying to re-organise the playlists (different logic) so I'm moving around (cut and paste) some of them. Am also replacing old MP3 files with normalised ones (delete old ones; insert new ones)

Have spent 4 or 5 hours trying to find a work-around, but it keeps falling over. Also when I keep the changes down to 4 or 5 new playlists per synch.

Am I trying something that doesn't work??

Email [email protected] for a definitive answer, but I think that code is actually a Windows file error which emplode passes on to the user.

Rob

Copy is already with support ([email protected]), together with a second report that details how empeg itself has crashed and is mimicking NASA's Mars Lander behaviour: not responding to any commands, as if they came from NASA. Last error was 0xfffffff4 during stage 5 of the synch. I didn't mention that I was playing the empeg while doing a synch. When the synch started, playback was halted though. Could that have sent it into orbit?

Henno

If Rob's guess is correct, and it's a Windows file error, you might be having hard disk or RAM problems. Run a scandisk and test your RAM.



-- Tony Fabris -- Empeg #144 --
Caution: Do not look into laser with remaining good eye.

hard disk or RAM problems

Highly unlikely that the disk or RAM is at fault. Scandisk (thorough) revealed no errors and I use ECC-RAM, so even occasional RAM glitches are corrected. Moreover, if RAM were at fault, I would expect 'blue screens' and many more programs falling over.

My guess is that emplode causes the problems. As said earlier, I am re-organising play lists and I suspect that emplode/empeg get confused when playlist are moved and/or with combined additions/deletes during a single synch.

BTW: When I connected power to the empeg this morning, it woke up as normal . May be NASA should re-connect their Mars Lander to re-vive it again too

Henno

Incase anyone was wondering.. I was right, it was a Windows error. Henno was also right - it was caused by a bug in emplode :-)

Rob