Here are my delayed replies to some of the previous posts.
Does "the same problem" mean that the InCD Format window doesn't come up upon inserting a blank disc, with "Autorun on" and Autoplay properties set as in my former advice
http://www.cdrlabs.com/phpBB/viewtopic. ... 6950#66950
If yes, does it also fail when you subsequently press the burner's button to eject the disc, and press it again to load the disc for the second time?
As for your second observation, C:\Program Files\Ahead\InCd contains Error.log and SrvError.log. Apparently each file has a fixed size of 127746 bytes, and they list SCSI error messages which may assist Ahead in debugging InCD problems.
At this stage, instead of troubleshooting your Autoplay problems, it's better to wait for input from other users. If more people complain, Ahead will have to respond, sooner or later.
As for testing InCD speed, ideally you should time how long it takes to copy about 400 MB of data from your HD to an InCD disc (both for classic UDF 1.50 and MRW formats). My latest experiment with a 10x disc on LTR-48125W indicates about 4x.
The memory consumption on XP seems to be complex. In Task Manager, incdsrv.exe starts from 3356 KB on my box, going up to 6928 KB after formatting and copying. On the other hand, InCD.exe starts from 646 KB, but goes up to 7136 KB in my latest experiments (and 16584 KB occured in my earlier trials). Maybe this is just due to the way committed memory is reported, but I don't recall seeing anything similar with InCD 3.x.
The "timestamping bug" occurs if files copied to InCD discs get the current date instead of inheriting their source dates. I can now confirm that the bug occurs also for source files from an HDD (in addition to an InCD disc inserted in a DVD-ROM drive as I reported earlier). Namely, after copying 4422 files, I checked that 2156 files got the current date. This is a really serious bug, as it precludes any synchronizing backups.
In case of problems with a CD-RW disc, before formatting you should try "InCD Erase..." in Windows Explorer (right-click on the burner's drive). For InCD 4.x, this should be equivalent to calling Nero | Recorder |
EraseReWritable for "full-erase". Thus in your case I would try InCD's erase, and then Nero's full-erase. If this doesn't help, you could try other burners as suggested by LiteOnGuy, but I would reject such discs for backups.