amitaik Posted November 1, 2013 Posted November 1, 2013 Hello everybody. First of all, I searched and searched for answers and couldnt find anything to help me. I am trying to burn a game for my XBOX. Something that had no problems a few months ago. I am using an iXtreme IATAPI iHAS524 and Verbatim DVD+R x8 DL discs. I 10:52:37 ImgBurn Version 2.5.8.0 started! I 10:52:37 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1) I 10:52:37 Total Physical Memory: 4,192,760 KiB - Available: 2,197,004 KiB I 10:52:37 Initialising SPTI... I 10:52:37 Searching for SCSI / ATAPI devices... I 10:52:37 -> Drive 1 - Info: DTSOFT BDROM 1.05 (F:) (Virtual) I 10:52:38 -> Drive 2 - Info: ATAPI iHAS524 B AL2A (E:) (ATA) I 10:52:38 Found 1 DVD±RW/RAM and 1 BD-ROM! No matter what I try, the burning icon is grayed out and below it says "Device not ready (Medium not present - tray closed)". Thank you so much!
Henderson Posted November 1, 2013 Posted November 1, 2013 Greetings. amitaik, same problem here. Used ImgBurn for over one year, never a glitch. Backing up a commercially purchased DVD just now. Original burned as always to dedicated video HDD. Fails to see blank 8.5GB Verbatim DVD +R DL in either Pioneer Drive. See ImgBurn Log below: I 11:36:38 ImgBurn Version 2.5.8.0 started!I 11:36:38 Microsoft Windows 7 Professional x64 Edition (6.1, Build 7601 : Service Pack 1)I 11:36:38 Total Physical Memory: 12,573,812 KiB - Available: 8,934,916 KiBI 11:36:38 Initialising SPTI...I 11:36:38 Searching for SCSI / ATAPI devices...I 11:36:39 -> Drive 1 - Info: PIONEER DVD-RW DVR-216D 1.07-GENERAL (D:) (ATA)I 11:36:40 -> Drive 2 - Info: PIONEER DVD-RW DVR-216D 1.08-GENERAL (H:) (ATAPI)I 11:36:40 Found 2 DVD±RWs! As with above compadre, my file to disc burn icon is greyed out. Below that is banner message that reads: "Device Not Ready (Medium Not Present - Tray Closed)"
LIGHTNING UK! Posted November 1, 2013 Posted November 1, 2013 That status come from the drive, this is nothing to do with ImgBurn. If your drive can't see the disc then it's a hardware issue or you've got a problem on your system whereby the drive's real status is being misreported. Try in safe mode.
Recommended Posts