KgCobra Posted September 27, 2009 Posted September 27, 2009 The only thing that I can think has changed was I removed 2 virtual drives, one using UltraISO, the other BDDecryter. Otherwise, nothing has changed on my system. I was burning AVCHD discs, using Verbatium DCD+R DL discs with no issues. The drive I am using is listed in the pasted log. Any help or suggestions where to start looking for issues is greatly appreciated. This is the first issue I have ever had using the program for many years now. Thanks in advance... Log: I 22:53:51 ImgBurn Version 2.5.0.0 started! I 22:53:51 Microsoft Windows 7 Ultimate Edition (6.1, Build 7600) I 22:53:51 Total Physical Memory: 4,192,760 KB - Available: 3,319,000 KB I 22:53:51 Initialising SPTI... I 22:53:51 Searching for SCSI / ATAPI devices... I 22:53:51 Found 1 DVD
LIGHTNING UK! Posted September 27, 2009 Posted September 27, 2009 It looks like a driver issue to me. Which controller is the drive connected to? Have you tried a different cable? Copy + paste what you see in the filter drivers list (found in the tools menu).
KgCobra Posted September 27, 2009 Author Posted September 27, 2009 It looks like a driver issue to me. Which controller is the drive connected to? Have you tried a different cable? Copy + paste what you see in the filter drivers list (found in the tools menu). =============================================== Filter Driver Load Order - ImgBurn v2.5.0.0 =============================================== Upper Device Filter: [None Found] Upper Class Filter: [None Found] Device: CD/DVD-ROM Device Lower Class Filter: AnyDVD Lower Device Filter: [None Found] Filter Name: AnyDVD File Name: C:\Windows\System32\Drivers\AnyDVD.sys File Version: 6.5.7.1 File Description: AnyDVD Filter Driver Product Name: AnyDVD Product Version: 6.5.7.1 Company Name: SlySoft, Inc. Copyright: Copyright 2002 - 2009 SlySoft, Inc.
KgCobra Posted September 29, 2009 Author Posted September 29, 2009 And the other questions? Lightning, Apparently it was a bad image and NOT an I/O error as stated in the log. On a whim, I re-did the encode (5 hours worth), and the new image burnt just fine. As I had mentioned before, the program as always been solid for me and that is why I thought of trying a new image. Thanks for your help and quick responses. Keep up the great work, it is appreciated. Sincerely, KgCobra (Andrew)
Recommended Posts