mrg Posted September 14, 2006 Posted September 14, 2006 (edited) I want burn a DVD-Video with my Plextor 716A on a TDK 16x DVD+R (Taiyo Yuden) and get a error-window (ImgBurn 2.1.0.0): I/O Error! Device: [1:0:0] Plextor DVDR PX-716A 1.08 (M:) (ATA) ScsiStatus: 0x02 Interpretation: Check Condition CDB: 25 00 00 00 00 00 00 00 00 00 Interpretation: Read Capacity Sence Area: 70 00 05 00 00 00 00 0A 00 00 00 00 2C 00 00 00 00 00 Interpretation: Command Sequence Error but the burned DVD seems OK. I used ImgBurn with CLI: "C:\Programme\ImgBurn\ImgBurn.exe" /MODE ISOBUILD /BUILDMODE DEVICE /DEST M: /SRC "E:\DVD\VIDEO_TS" /FILESYSTEM "ISO9660 + UDF" /copies 1 /VOLUMELABEL "1" /SPEED 4x /ERASE /VERIFY YES /START /WAITFORMEDIA /CLOSESUCCESS /IBG "ibg" /LOG "<imgburn.log>" What's wrong and why is the imgburn.log not saved? Edited September 14, 2006 by mrg
LIGHTNING UK! Posted September 14, 2006 Posted September 14, 2006 The CLI log stuff isn't working because the GUI one currently takes preference - and it now defaults to saving all the time, but in a different folder. If you disable auto saving of the log your CLI version will work again. It's impossible to work out exactly what's going on by just looking at that I/O error. Normally that sort of thing comes up if you have the program open twice and they're using the same drive. So dig out the log (you can find the folder if you look in the settings) and then copy + paste it. (or just copy + paste it while the program is still open).
mrg Posted September 14, 2006 Author Posted September 14, 2006 If you disable auto saving of the log your CLI version will work again. ...So dig out the log (you can find the folder if you look in the settings) Thanks for the answer, but in the 'Settings' under 'Events', 'Save the Log' was not aktivatet.
LIGHTNING UK! Posted September 14, 2006 Posted September 14, 2006 Oh sorry, I missed that you'd called your file "" '' characters are not allowed in folder / file names.
mrg Posted September 28, 2006 Author Posted September 28, 2006 (edited) The same error appeared now 3 times again and also again with TDK 16x DVD+R (Disc ID: YUDEN000-T03-00). This time the error appeared after '14:14:35 BURN-Proof: Enabled' and before '14:14:44 Filling Buffer...' The log: I 14:14:19 Initialising SPTI... I 14:14:19 Searching for SCSI / ATAPI devices... I 14:14:20 Found 2 DVD-ROMs and 1 DVD?RW! I 14:14:20 Operation Started! I 14:14:20 Building Image Tree... I 14:14:20 Checking Directory Depth... I 14:14:20 Calculating Totals... I 14:14:20 Preparing Image... I 14:14:20 Checking Path Length... I 14:14:20 Image Size: 3.167.649.792 bytes I 14:14:20 Image Sectors: 1.546.704 I 14:14:35 Operation Successfully Completed! - Duration: 00:00:14 I 14:14:35 Operation Started! I 14:14:35 Source File: -==/\/[BUILD IMAGE]\/\==- I 14:14:35 Source File Sectors: 1.546.704 (MODE1/2048) I 14:14:35 Source File Size: 3.167.649.792 bytes I 14:14:35 Source File Volume Identifier: X I 14:14:35 Source File Application Identifier: IMGBURN V2.1.0.0 - THE ULTIMATE IMAGE BURNER! I 14:14:35 Source File Implementation Identifier: ImgBurn I 14:14:35 Source File File System(s): ISO9660; UDF (1.02) I 14:14:35 Destination Device: [1:0:0] PLEXTOR DVDR PX-716A 1.08 (M:) (ATA) I 14:14:35 Destination Media Type: DVD+R (Disc ID: YUDEN000-T03-00) (Speeds: 4x; 6x; 8x; 12x; 16x) I 14:14:35 Destination Media Sectors: 2.295.104 I 14:14:35 Write Mode: DVD I 14:14:35 Write Type: DAO I 14:14:35 Write Speed: 4x I 14:14:35 Link Size: Auto I 14:14:35 Test Mode: No I 14:14:35 BURN-Proof: Enabled I 14:14:44 Filling Buffer... I 14:14:45 Writing LeadIn... I 14:15:07 Writing Image... I 14:24:37 Synchronising Cache... I 14:24:41 Closing Track... I 14:24:42 Finalising Disc... I 14:24:58 Image MD5: 0727251c2c4c3e33d78fe886c97eb8f5 I 14:24:59 Exporting Graph Data... I 14:24:59 Graph Data File: imgburn.ibg I 14:24:59 Export Successfully Completed! I 14:24:59 Operation Successfully Completed! - Duration: 00:10:23 I 14:24:59 Average Write Rate: 5.427 KB/s (3.9x) - Maximum Write Rate: 6.193 KB/s (4.5x) I 14:24:59 Cycling Tray before Verify... I 14:25:26 Device Ready! I 14:25:27 Operation Started! I 14:25:27 Source Device: [1:0:0] PLEXTOR DVDR PX-716A 1.08 (M:) (ATA) I 14:25:27 Source Media Type: DVD+R (Book Type: DVD-ROM) (Disc ID: YUDEN000-T03-00) (Speeds: 4x; 6x; 8x; 12x; 16x) I 14:25:27 Image File: -==/\/[BUILD IMAGE]\/\==- I 14:25:27 Image File Sectors: 1.546.704 (MODE1/2048) I 14:25:27 Image File Size: 3.167.649.792 bytes I 14:25:27 Image File Volume Identifier: X I 14:25:27 Image File Application Identifier: IMGBURN V2.1.0.0 - THE ULTIMATE IMAGE BURNER! I 14:25:27 Image File Implementation Identifier: ImgBurn I 14:25:27 Image File File System(s): ISO9660; UDF (1.02) I 14:25:27 Verifying Sectors... I 14:30:27 Device MD5: 0727251c2c4c3e33d78fe886c97eb8f5 I 14:30:27 Image MD5: 0727251c2c4c3e33d78fe886c97eb8f5 I 14:30:27 Exporting Graph Data... I 14:30:27 Graph Data File: imgburn.ibg I 14:30:27 Export Successfully Completed! I 14:30:27 Operation Successfully Completed! - Duration: 00:04:59 I 14:30:27 Average Verify Rate: 10.345 KB/s (7.5x) - Maximum Verify Rate: 14.324 KB/s (10.3x) I 14:30:27 Close Request Acknowledged I 14:30:27 Closing Down... I 14:31:19 Shutting down SPTI... I 14:31:19 ImgBurn closed! I wrote the same content also to a DVD-R and DVD+RW but without this error message. Should I use another interface like ASPI - WNASOI32.DLL? Edited September 28, 2006 by mrg
LIGHTNING UK! Posted September 28, 2006 Posted September 28, 2006 In a normal system there's no reason at all for a read capacity command to fail in the 'pre-burn' stage. The 'read capacity' command should only really fail with that error when it's issued mid burn, so I suspect your drive is being interfered with by another program or it's not finishing a previous burn properly. Having just turned on the pc from scratch, can you burn an image without getting the error?
mrg Posted September 29, 2006 Author Posted September 29, 2006 (edited) Having just turned on the pc from scratch, can you burn an image without getting the error? Yes, you are right. The error comes only starting from the second start of imgburn by cli and also not in the 'pre-burn' stage. I have test it with /TESTMODE YES on a dvd-r and the first run was successfully, the second not! I made of it a video (xvid / 800x600 px / 1:41 min / 2 MB) [EDIT] Link removed. Log: I 11:52:30 Initialising SPTI... I 11:52:30 Searching for SCSI / ATAPI devices... I 11:52:30 Found 2 DVD-ROMs and 1 DVD?RW! I 11:52:31 Operation Started! I 11:52:31 Building Image Tree... I 11:52:31 Checking Directory Depth... I 11:52:31 Calculating Totals... I 11:52:31 Preparing Image... I 11:52:32 Checking Path Length... I 11:52:32 Image Size: 86.835.200 bytes I 11:52:32 Image Sectors: 42.400 I 11:52:34 Operation Successfully Completed! - Duration: 00:00:03 I 11:52:35 Operation Started! I 11:52:35 Source File: -==/\/[bUILD IMAGE]\/\==- I 11:52:35 Source File Sectors: 42.400 (MODE1/2048) I 11:52:35 Source File Size: 86.835.200 bytes I 11:52:35 Source File Volume Identifier: X I 11:52:35 Source File Application Identifier: IMGBURN V2.1.0.0 - THE ULTIMATE IMAGE BURNER! I 11:52:35 Source File Implementation Identifier: ImgBurn I 11:52:35 Source File File System(s): ISO9660; UDF (1.02) I 11:52:35 Destination Device: [1:0:0] PLEXTOR DVDR PX-716A 1.10 (M:) (ATA) I 11:52:35 Destination Media Type: DVD-R (Disc ID: SONY08D1) (Speeds: 4x; 6x; 8x) I 11:52:35 Destination Media Sectors: 2.298.496 I 11:52:35 Write Mode: DVD I 11:52:35 Write Type: DAO I 11:52:35 Write Speed: 4x I 11:52:35 Link Size: Auto I 11:52:35 Test Mode: Yes I 11:52:35 BURN-Proof: Enabled I 11:52:50 Filling Buffer... I 11:52:50 Writing LeadIn... I 11:53:14 Writing Image... I 11:53:29 Synchronising Cache... I 11:53:31 Cycling Tray after Test Write... I 11:53:52 Image MD5: 289972df04a66ed95f77382f67a60234 I 11:53:52 Operation Successfully Completed! - Duration: 00:01:17 I 11:53:52 Average Write Rate: 6.057 KB/s (4.4x) - Maximum Write Rate: 6.057 KB/s (4.4x) I 11:53:52 Close Request Acknowledged I 11:53:52 Closing Down... I 11:54:08 Shutting down SPTI... I 11:54:08 ImgBurn closed! Edited March 22, 2007 by mrg
LIGHTNING UK! Posted September 29, 2006 Posted September 29, 2006 Ok I'll chuck my 716 in an external enclosure and test it with your command line, as stated in your first post. I call the 'pre-burn' stage anything up until it says 'Writing LeadIn...' in the log. Am I correct in assuming you only get this error once you've hit the burn button? i.e. it doesn't just pop up the second you load the program normally for the 2nd time? (perhaps not via CLI)
mrg Posted September 30, 2006 Author Posted September 30, 2006 I have isolate the problem. The error appears only if by the last run of ImgBurn the Checkbox 'Close Program' was checked respectively the cli argument /CLOSESUCCESS was used. So if ImgBurn is closed manual, the next time i can burn without getting the error. What's the meaning of 'Device Not Ready (Logical Unit not ready, Long Write in progress)' thats shown in the video and are the dvd's nonetheless burn accurate?
LIGHTNING UK! Posted September 30, 2006 Posted September 30, 2006 It means the drive is still busy finishing the previous write. If that's show in the statusbar then it would explain why the read capacity command is failing.
mrg Posted September 30, 2006 Author Posted September 30, 2006 @ LIGHTNING UK Didn't you see the video from post #7? It show the cli-arguments and imgburn (include the statusbar) from beginning to end.
LIGHTNING UK! Posted September 30, 2006 Posted September 30, 2006 I hadn't noticed it, no. I've look at it now though and I see where the problem is coming from - I'll look into it. The CLI stuff undergoes no/very little testing so weird thing do and can happen.
LIGHTNING UK! Posted October 1, 2006 Posted October 1, 2006 Just a bit of an update... It was clear from your video that the autoinsert thread was being created/run (by another thread) AFTER I'd tried to terminated it at the start of the write process. So, it was running in the background during a 'Write' operation. As the drive goes between 'ready' and 'not ready' states when you're burning, the autoinsert thread thinks you've inserted a disc and so will try to initialise it. That's where the error was coming from and it's why you could have the error box up on the screen and yet the burn still carried on regardless - had the burn have been erroring out, that would not have been the case. I think I've fixed this now.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now