mholmes234 Posted December 31, 2010 Share Posted December 31, 2010 The program gets stuck on 'Searching for SCSI/ATAPI Devices' Windows 7 64bit Clean windows install I have read the FAQ. Here is the logfile. Please let me know any suggestions. I 13:52:34 ImgBurn Version 2.5.4.0 started! I 13:52:34 Microsoft Windows 7 Professional x64 Edition (6.1, Build 7600) I 13:52:34 Total Physical Memory: 12,573,808 KB - Available: 8,978,100 KB W 13:52:34 I/O Interface 'Debug Mode' Enabled! I 13:52:34 Initialising SPTI... I 13:52:34 Searching for SCSI / ATAPI devices... I 13:52:34 Initialising Device (\\?\scsi#cdrom&ven_asus&prod_drw-24b1lt&rev_1.03#5&1dc749fb&0&000100#{53f56308-b6bf-11d0-94f2-00a0c91efb8b})... Thank you! Mark Link to comment Share on other sites More sharing options...
cornholio7 Posted December 31, 2010 Share Posted December 31, 2010 are you running as administrator? Link to comment Share on other sites More sharing options...
mholmes234 Posted December 31, 2010 Author Share Posted December 31, 2010 are you running as administrator? Yes, my user account is administrator. Link to comment Share on other sites More sharing options...
mholmes234 Posted December 31, 2010 Author Share Posted December 31, 2010 Problem resolved. I have an Asus P6X58D Premium motherboard. This motherboard has two different SATA controllers - the standard SATA motherboard controller which is ICH10R and a Marvell Controller 9123. The Marvell controller supports two SATA III or 6Gb/s ports. When the DVD drive is connected to the Marvell controller it is not recognized. I tried both AHCI and IDE settings in the bios for the Marvell controller and both failed. When I moved the DVD drive to the standard SATA controller it worked right away. Is there an incompatibility with third party SATA controllers or specifically the Marvell chip? Thanks, Mark Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted January 1, 2011 Share Posted January 1, 2011 ImgBurn isn't even really doing anything in your log, it's all Windows. Optical drives have never worked very well on 3rd party chipsets (with the exception of Silicon Image ones). Newer Marvell drivers may have fixed your issue but they're not very good at releasing them - that controller is meant for HDDs. Link to comment Share on other sites More sharing options...
Recommended Posts