Del_Usion Posted March 5, 2009 Share Posted March 5, 2009 As instructed I have started my own topic, which I did not do originally to not create something potentially redundant. The problem just started occurring since I just got around to upgrading to 2.4.2.0. I killed about 3 discs after I noticed that 1) when this happened I couldn't fully cancel out of ImgBurn (apparent crash) 2) my Liteon LH-20A1L kept blinking and wouldn't release the disc unless I rebooted and 3) the discs that were failures had a different amount of data on them despite failing at the same point. That last one got me thinking that the first two symptoms might indicate that the disc was actually still being burnt despite indications otherwise. After this started I switched to Nero to check myself and was able to burn there fine. Tonight I decided to try an experiment. I decided to let it go after the failure to see if the disc burnt. I got impatient after several minutes sitting on the first failure warning, and clicked retry, which I had tried with previous attempts but not after waiting a bit. This time it picked right up and completed the main track, but "failed" in the switch to the lead-out. I waited again, clicked retry, and the disc finished burning. Despite all of this, the disc verified okay! I don't know enough about the changeover from lead-in to main track to lead-out to know exactly what this means, but it definitely is strange. Below is my log. Some information has been obscured by asterisks intentionally. I 19:03:34 ImgBurn Version 2.4.2.0 started! I 19:03:34 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 19:03:34 Total Physical Memory: 3,144,108 KB - Available: 2,048,208 KB W 19:03:34 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 19:03:34 Initialising SPTI... I 19:03:34 Searching for SCSI / ATAPI devices... I 19:03:34 Found 1 DVD-ROM and 1 DVD Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted March 5, 2009 Share Posted March 5, 2009 It's the error codes that are wrong - are you using an NVIDIA controller by any chance? Have you tried resetting the interface back to SPTI? and if that fails, switch to ASPI and use the Nero WNASPI32.DLL. btw, your elbycdio interface is out of date. You should update whichever program you have installed so that you get the latest one. Link to comment Share on other sites More sharing options...
Del_Usion Posted March 6, 2009 Author Share Posted March 6, 2009 Yes, the the board is on an NVIDIA chipset. I have tried both the SPTI and Elby interfaces, that was just the one I had left it on. It's been a while since I used or updated CloneDVD, so that's why I had the old version. I'll take care of that. It appears that ASPI with the Nero dll is working without complaint. Thanks for the help! Is there something I should do to improve the chipset compatibility, driver update or such? I'll admit it's been about a year since I checked for chipset driver updates, but they haven't exactly updated them too quickly in the past. Link to comment Share on other sites More sharing options...
Del_Usion Posted March 6, 2009 Author Share Posted March 6, 2009 I just checked the chipset driver, and it appears I'm as up to date as it gets, which is last September. Link to comment Share on other sites More sharing options...
mmalves Posted March 6, 2009 Share Posted March 6, 2009 Update to the latest nforce drivers, even though for some people they still give bogus error messages with SPTI interface Link to comment Share on other sites More sharing options...
Recommended Posts