Hi.

Now I'm replying to my own post. As for the new drive, I was able to solve the issue:
The player software seems to have a problem if /etc/mtab exists (I usually link it to /proc/mounts when using the shell, to make df and others work ok, and usually remove it again before exiting.). I know I had a similar problem before, where the player software would show even more problems. However, I really would like to know why the player software exits the connection to emplode after or during "controlling disk" stage if /etc/mtab is linked like I stated above.

An even more interesting question is how did /etc/mtab survive drive initialization using the drive builder image?
Answer: It looks as it didn't. I now get a stage 4 error 0xfffffffe with my old drive. DAMN, what's going on here?

cu,
sven
(proud owner of a MkII 12GB blue now green, #080000113)