Hi Mark & Trevor

I put the following "hack" into the kernel in /fs/super.c :

	if (!strcmp(dev_name, "/dev/hdc4")) {

		printk("Skipping mount of /dev/hdc4\n");

		free_mount_page(page);

		retval = 0;

		goto out;

I decided just to check for any attempt to mount /dev/hdc4 as I will not be needing this device at all.
It does the trick of silently ignoring any attempts to mount the filesystem.

But now it seems to me, as if it is the fsck.ext2 following the mount that makes the synchronization fail. This is probably built into the player application as you suggested. I have tried a lot of fiddling around with using scripts to intercept the fsck.ext2 call but with no luck.

I also tried returning another value than 0 in the mount system call, to tell the system that the mount went wrong, but apparently this doesn't stop the player app from trying to run an fsck on it...

In the meantime I also found out that Jemplode apparently synch's ok - while Emplode still fails.
As I can just use Jemplode, I have decided to just ignore the "problem"...
But at least I had a lot of fun poking around in the kernel

Thank you both for your suggestions...

/Nicolai