engine Posted October 2, 2010 Posted October 2, 2010 Dear forum users, I am getting an error at the end of some of my burns when I am using Patin-Coufin. When I use SPTI this error doesn't show up. When I use other media and Patin-Couffin I don't get this error. I am getting this error with Patin-Couffin and this media in particular. Please see the log and image attached. ImgBurn.log Thanks.
LIGHTNING UK! Posted October 2, 2010 Posted October 2, 2010 Don't use Patin Couffin. The bug is in the driver, not ImgBurn. I did tell the guys at VSO about it but they basically said Patin Couffin is dead (they use SPTI too now for Vista / 7) and they won't do anything else to it.
engine Posted October 2, 2010 Author Posted October 2, 2010 (edited) Thanks LIGHTNING UK! I will do that. Can you point me to that Burn rights tool? Or should I try ElbyCDIO instead? Thanks again. Edited October 2, 2010 by engine
LIGHTNING UK! Posted October 2, 2010 Posted October 2, 2010 A quick Google of 'BurnRights' will find you what you need. Basically, you can get the Nero version here - http://www.nero.com/enu/support-nero6-tools-utilities.html and the Poikosoft version here - http://www.softpedia.com/get/System/OS-Enhancements/BurnRights.shtml
engine Posted October 2, 2010 Author Posted October 2, 2010 (edited) Thanks for the links. I would like to report my findings. I switched to ElbyCDIO DLL while Patin-Couffin was still installed and I got the same type of error while trying to quick erase a DVD+RW. After that I uninstalled Patin-Couffin and restarted the system. Tried to quick erase the same DVD+RW while using ElbyCDIO DLL and I didn't got any kind of error. I am now burning the same DVD+RW to check if the same type of error appears at the end of the burn. Kind regards. PS: ElbyCDIO DLL appears to be fine. Edited October 2, 2010 by engine
engine Posted October 3, 2010 Author Posted October 3, 2010 (edited) I think this error didn't happen back when I was using nVidia and Silicon Image controllers. Now I am using a single Intel controller exclusively. This might be an Intel Patin-Couffin issue. Kind regards. Edited October 3, 2010 by engine
Recommended Posts