bloort Posted May 29, 2012 Share Posted May 29, 2012 (edited) edit. to save you reading further, what i thought was a bug, i has turned out to be hardware failure on two of my drives. no fault of imgburn whatsoever. LONG time user, man i love this software so much! XP sp3, burn ISO to disk. ver 2.5.6.0 , 2.5.7.0 I have two XP boxes burning ISOs to DVD from 2.5.6.0. Box one started failing with a power calibration area error, failed to write sectors 0-31. This drive has high milage so i suspected a hardware failure. So i shifted burning duty over to my secondary box, but the same error shortly appeared. with 5 and 6 year old burners, with the most up to date firmware that i can find, i chalked it up to old hardware and a coincidental simultaneous hardware failure. Newly purchased box3 (win7 2.5.7.0) burns succesfully. With fleeting hope that it may have been a bug or oversight, i patiently awaited a new version to try on the erroring boxes . Alas, 2.5.7.0 arrives, but the PCAError persisted. In being thorough, i located an earlier version 2.5.3.0 to try, which just this moment has finished verifying a burn on the same drive, to which 20 minutes ago, and on 2570, i only recieved the error, and could not burn. The drives are optiarc, and sony, and write speeds were succesfully set according to both error and success log files. In short summary, i have possibly two (one confirmed) XPsp3 boxes which cannot burn ISO using 2560 or 2570. PCAErrors persist. Version 2530 works fine. I can certainly perform further testing on various versions if need be, or provide any more info you might need. Anyhow, i'm very happy to find my drives are still burning fine. I've tried fresh installs with 2570, and reset the setting to no avail. that's about all i can think of to say. So thank you very much for this awesome software, and i hope my contribution is of service. peace. Bloort. Edited May 31, 2012 by bloort Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted May 29, 2012 Share Posted May 29, 2012 Can you post a log from each version? The way data is written is the same in all versions, there's only 1 command that does it! That command being sent from 1 version is no more/less likely to complete successfully (or fail) than if it's sent from another version, so there must be something else coming into play here. Link to comment Share on other sites More sharing options...
bloort Posted May 29, 2012 Author Share Posted May 29, 2012 (edited) Handy help menu! here is the log from box2. Please find a log file containing successful burn w 2530, and then error burn w 2570 (also know to occur in some versions in between, i haven't drilled it down yet but i'm quite sure 2560 errs also for me) I see a difference in the log files: 2530 filling buffer 40 MB 2570 filling buffer 80 MB ImgBurn_box2.log Edited May 29, 2012 by bloort Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted May 30, 2012 Share Posted May 30, 2012 The buffer size being used isn't going to make any difference so it's not that. I think it's just fluke that sometimes it works and sometimes it doesn't. You'd have to burn something like 20 discs, alternating between program versions and always having a successful burn in one and failure in the other for me to take a report like this even remotely seriously. (no offence) It's more likely that your ageing (and probably dirty) drive just has a problem with trying to burn at max speed on those discs. Even if I tried, I couldn't make the program cause the problem you're having, and as such, it can't possibly be a bug in it. Link to comment Share on other sites More sharing options...
bloort Posted May 30, 2012 Author Share Posted May 30, 2012 I humbly accept the 20 disk challenge, as that is about the size of my upcoming burn, of cloning identical ISO DVD video i have made for the sailing clubs regatta. I agree with you entirely, as my situation does appear to be unique to the forum. In hindsight, I should have tested further before bothering you! I have 4 boxes to burn from, 3 old on XP, and one brand new but win7. So the game is afoot! Thanks for your time and consideration and awesome software over the years. I'll get right to testing today, using multiple machines. Thankfully, the error does not render blanks unusable! Peace. Bloort. Link to comment Share on other sites More sharing options...
bloort Posted May 31, 2012 Author Share Posted May 31, 2012 (edited) With blushing red face, i humbly report, that it's starting to look like a simultaneous hardware failure on two separate burners, at nearly the same time, just as you have described. A rather bizarre coincidence in my experiences. I apologise for jumping the gun like that, but it was strange to have two go down like that simultaneously. I should have researched much further before raising an alarm. My bad. This thread should now be deleted to save my posterity! I'll report any anomolies if found, as i humbly replace both drives and carry on. thank you for your time. Edited May 31, 2012 by bloort Link to comment Share on other sites More sharing options...
Recommended Posts