Sharon Posted March 29, 2008 Share Posted March 29, 2008 Hi All- When verifying a DVD+R against its .iso image file after recording with IMGBurn 2.4.0.0, running under Vista64 or XP64, there several miss-compare errors; however, after a *reboot* verification is perfect--no errors. I boot among: XP32, XP64 and Vista64, recording and verifying, as above, with XP32 *doesn't* exhibit the same variation. I suspect this is a configuration issue. Any suggestions? A response would be greatly appreciated. TiA Link to comment Share on other sites More sharing options...
blutach Posted March 29, 2008 Share Posted March 29, 2008 Dunno why you think this is an ImgBurn bug - your own analysis suggests memory issues (have you run a memtest?) or a rogue driver/software conflict. Please also post a log. Regards Link to comment Share on other sites More sharing options...
Sharon Posted March 30, 2008 Author Share Posted March 30, 2008 Thanks for the prompt response blutach-- 1. Memtest86+2.00 indicates memory is working fine. Given that everything else remained the same before and after the reboot that software conflicts are unlikely. I did check Software Explorer, and nothing else is running. 2. I did not imply a bug in Imgburn, but requested recommendations for configuration changes, given the endless number of setting interdependencies. I was hoping for a simple solution perhaps tweaking the Read tab's settings for: Software Retries Hardware Retries I am speculating, but because much of the architecture differs between MS's 32 and 64-bit OSes, that someone might know what causes the difference. Again, it's not XP versus Vista, but 32 versus 64-bit. The mis-compare differences also occur with XP64 bit but not with XP32. 3. If necessary, on Tuesday, I will duplicate the test and send the Imgburn log files. Is there any other information that might help? Like OS Event Viewer log data? Again TiA. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted March 30, 2008 Share Posted March 30, 2008 There's no setting to tweak to avoid a miscompare. Either the data matches the source or it doesn't. When the verify fails, repeat the process a couple more times and see if the miscompares are always in the same place. Maybe its a dodgy driver messing things up. Link to comment Share on other sites More sharing options...
Sharon Posted April 2, 2008 Author Share Posted April 2, 2008 Thanks for responding LUK. Found the solution! LUK's code is idiot proof under win32, in other words DVDD or IMGBurn works fine without changing the default settings; however, the syswow64 subsystem is a different beast and at least for this idiot requires some changes. The problem was that any Win32 app that *locks* the drive during any operation *doesn't release* the drive, or it appears. So DVDD and IMGBurn has to be configured *without locking* the optical drive for any operation. I don't know if this is SATA or specific to my setup, but once I changed the defaults, everything works perfectly!! As a side note, if DVDShrink is used with XP or Vista x64 it has to be configured with DEP. Link to comment Share on other sites More sharing options...
Recommended Posts