The problem is that when I log on in one account at my PC in WinXP, then switch to another user and finally try to log off from this "another user", InCD does not end properly. I've got a message "Ending the programme...". And also now InCD takes 70-90% of CPU resources while runing on a second account ("another user"). It looks like the programme does not work properly under multiple accounts in WinXP. Any suggestion?

I am experiencing the same thing when using Fast User Switching on XP, although I don't receive the "Ending the Program.." notification. InCD pegs the CPU at 99% until I kill the offending process. Hopefully there will be some sort of fix soon, as this is a very annoying problem.

This is because Ahead's burning programs (InCD included) require administrator access to write to a disc...

All of the accounts on my machine have admin rights, and no one tried to write to a disk. It is the background process (incd.exe) that causes the problem when it starts another copy of itself when a second user logs in with fast user switching.

I am not using "fast switching" between user accounts in XP home edition, and when someone is logging off my "visitor's" account, (limited account), the "Ending the Program....." message comes along, and INCD was not even used.

Yes, I confirm, one of our developer has broken the XP multi-user and fast user switching support of InCD! [:(!] (Someone starts running fast and far away to hide... [}:)]) Of course now that we have seen this, we have immediately work on fixing it and hopefully it will be repaired in next InCD web update. The engineer who work on resolving it is also currently checking the functionnality with limited right user account to not allow them to format or erase, but ensure they are still able to read and write already formatted media.