exile183 Posted January 27, 2013 Posted January 27, 2013 Hey everyone, I'm hoping someone can offer a suggestion to a weird problem that's come up... First off, let me explain that I've burned literally thousands of discs with ImgBurn on a wide variety of PC's and burners - IDE, SATA, and external USB. It's been rock solid. But now I've run into a problem that I can't diagnose and I'm hoping someone here has seen this before and can suggest a fix. Compounding the problem is that the problem is occurring in a situation where the PC, the drives, and the USB enclosures are all brand new - so there's a lot of variables. The PC - is a Commodore 64 Extreme (yeah, cool huh?) with USB 3.0 ports The burners - are a pair of Samsung SH-224BB's with the latest firmware (SB00) The burners are in a pair of Vantec NexStar DX enclosures (USB 3.0) The media: Taiyo Yuden TYG03. These are the "Valueline" brand, meaning I get 4 or 5 bad burns out of every spindle of 100 discs. So here's what occasionally happens. 1) The ISO burn procedes normally (I usually burn at 22X) 2) During the verify (not against img file), and usually towards the outside of the disc (between 70% and 100%), the verify suddenly stops. Verify speed drops to 0%. And it just hangs there. If I do nothing, it'll just sit there forever. If I click on CANCEL, I get a message from ImgBurn saying it's waiting for a read thread to terminate - and again, this will just hang there forever. The only way out is to cut power on the external enclosure, which causes ImgBurn to freak out with several error messages. I can then turn the power back on on the enclosure and everything will work fine again. I've tried running a straight verify on these discs in another unit on another computer and I can confirm there IS a bad sector that's triggering this. But usually ImgBurn will get a message from the burner saying "hey, dude... bad sector!" and give me that error message and allow me to cancel the burn cleanly. It seems like in this case, ImgBurn and the drive just stop talking to each other, and the only way to get them talking again is to cycle power to the burner. Any thoughts?
LIGHTNING UK! Posted January 27, 2013 Posted January 27, 2013 It's your machine that's stopped processing the I/O and not really anything to do with ImgBurn. It has to wait for the Windows API function it calls for doing I/O to return control to it. All I can suggest is that you try looking for updated firmware for the enclosure chipset and the usb chipset (if it's a 3rd party one - i.e. not Intel or whatever). They obviously also have driver updates for the usb controllers (and even the hubs if you have such things on the board - mine does) - make sure you're running the latest one. Right click the drive selection box and click 'Family Tree'. Close the prompt and then copy + paste everything from the Log window please.
Recommended Posts