rjbarker Posted January 20, 2009 Share Posted January 20, 2009 Hey all, Its been a very long time since I've been on these (old DVD Shrink Forums)?...Cynthia seems to ring a bell. we're talking a few years...basically because I have had no issues at all backing up my DVD's, until now. I now have a newer PC, and am having issues Burning my .ISO files with ImageBurn. I thought it may have been an issues with my Sammy, but I was able to burn an Image File using Nero with no issues at all. I would simply use Nero, but cannot figure out how to change the Burning Speed from 22X to 4X. Anyhow, at the Lead-in, I get the error and my DVD Drive does not respond at all...completely frozen. I can continue to use my PC, but I will have to do a "Re-Boot" to get that Drive to respond again. I have noticed other folks having this same problem. I will include my Log. Also, System specs: E8400 @ 4.05 Ghz Evga 780i nForce Chipset (w latest Chipset Drivers) 2 x 2GB Mushkin Redlines @ 1 Ghz 2 x GTX 280 GPU's Corsair 1 kW PSU 1 - Samsung DVD RW (SATA) 1 - LG DVD RW (IDE) 1 - 74 GB Raptor (SATA) 1 - 320 GB Barracuda XP SP3 Just a note, everything works fine with the IDE Drive, not the SATA Drive. As mentioned, Nero works fine burning .ISO I did update the Firmware about a month ago. Log: ; ImgBurn Version 2.4.2.0 - Log ; Monday, 19 January 2009, 22:23:12 ; \\****************************************// ; ; I 22:22:10 ImgBurn Version 2.4.2.0 started! I 22:22:10 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 3) I 22:22:10 Total Physical Memory: 2,619,868 KB - Available: 2,225,916 KB I 22:22:10 Initialising SPTI... I 22:22:10 Searching for SCSI / ATAPI devices... I 22:22:10 Found 2 DVD Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 20, 2009 Share Posted January 20, 2009 This looks like another nvidia chipset driver issue to me. The drivers misreport the errors being returned by the drive (when asking for more than 18 bytes of sense area data - which ImgBurn does) and ImgBurn is unable to then deal with the ones it expects to see - meaning you (the end user) sees problems that don't really exist. Burning at 4x doesn't mean you'll get a better burn, it could actually be worse depending on how the firmware has been tweaked. You should burn a disc at each speed and then test them via DVDInfoPro / CD Speed to check the PIPO error levels. Link to comment Share on other sites More sharing options...
rjbarker Posted January 20, 2009 Author Share Posted January 20, 2009 This looks like another nvidia chipset driver issue to me. Yes I believe you're likely right. Their have been a number of "issues" with the nVidia Chipset and SATA Optical Drives of which I have not been able to find a solution to. I have tried rolling back my Chipset Drivers to the original which shipped with the Board a year ago and have also tried the latest Chipset Drivers....all to no avail. Anyhow, reading this Forum I noticed other folks with the same problem that had success rolling back ImageBurn to previous version.....should I consider this or simply Burn with my IDE Drive? Also, I will be recieving my X58 Board and I7 components this week, installing Vista 64 Bit, so hopefully ImageBurn will perform properly on the new System. Regards Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 20, 2009 Share Posted January 20, 2009 I don't recall anyone having rolled back ImgBurn and there's no reason for this particular problem to be solved by them doing that anyway. ImgBurn has always requested more than 18 bytes of sense area data and that's where the bug in the drivers comes into play. The easiest fix is to switch to a different I/O interface in the settings. ASPI (when using the Nero WNASPI32.DLL) will limit it to 18 so that works fine and the ElbyCDIO one does the same. I haven't tried it with the patin couffin one so I can't comment on that. Link to comment Share on other sites More sharing options...
rjbarker Posted January 20, 2009 Author Share Posted January 20, 2009 The easiest fix is to switch to a different I/O interface in the settings. ASPI (when using the Nero WNASPI32.DLL) will limit it to 18 so that works fine and the ElbyCDIO one does the same. Can you provide some "detail" as where / how to try this? Thanks for your time. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 20, 2009 Share Posted January 20, 2009 Go into the settings and look on the I/O tab. Just change it to one of the others (i.e. away from SPTI). The main website (on the download page) tells you how/where to download the programs that give you the other I/O interfaces if you don't already have them available / installed. Link to comment Share on other sites More sharing options...
Recommended Posts