|
|
|
Imgburn "command sequence error" when attempting to burn wii iso's
|
|
|
cnalley87
Newbie
|
4. September 2009 @ 13:58 |
Link to this message
|
Imgburn's giving me hell (i think). Imgburn works fine until it says writing sectors. It gets to about 23 percent, no matter what iso im trying to burn (wii iso's) and then i watch the write speed jump ridiculously between 2,000 k/b per second and 0 kb per sec until it eventually stalls on 0 kb per sec and gives me an error.This started 2 days ago with elebits, then i successfully burned a excite truck and now im getting errors again, wtf? So if someone can help, I'd really be thankful. here's my log...
I 07:43:34 ImgBurn Version 2.5.0.0 started!
I 07:43:34 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3)
I 07:43:34 Total Physical Memory: 752,048 KB - Available: 413,052 KB
I 07:43:34 Initialising SPTI...
I 07:43:34 Searching for SCSI / ATAPI devices...
I 07:43:34 Found 1 DVD-ROM, 1 DVD-ROM/CD-RW and 1 DVD±RW!
I 07:45:44 Operation Started!
I 07:45:44 Source File: C:\Program Files\BitLord\Downloads\Call_of_Duty_3_(NTSC)_(WII)\vortex-cod3\Call_of_Duty_3_Wii.iso
I 07:45:44 Source File Sectors: 2,294,912 (MODE1/2048)
I 07:45:44 Source File Size: 4,699,979,776 bytes
I 07:45:44 Source File Volume Identifier: COD3 US
I 07:45:44 Source File File System(s): Special
I 07:45:44 Destination Device: [3:1:0] LITE-ON DVDRW SOHW-1693S KS09 (J:) (ATA)
I 07:45:45 Destination Media Type: DVD-R (Disc ID: CMC MAG. AM3) (Speeds: 6x, 8x, 12x, 16x)
I 07:45:45 Destination Media Sectors: 2,298,496
I 07:45:45 Write Mode: DVD
I 07:45:45 Write Type: DAO
I 07:45:45 Write Speed: 2x
I 07:45:45 Link Size: Auto
I 07:45:45 Lock Volume: Yes
I 07:45:45 Test Mode: No
I 07:45:45 OPC: No
I 07:45:45 BURN-Proof: Enabled
W 07:45:45 Write Speed Miscompare! - Wanted: 2,770 KB/s (2x), Got: 8,864 KB/s (6.6x)
I 07:45:45 Advanced Settings - Force HT: N/A, Online HT: N/A, OverSpeed: N/A, SmartBurn: Yes
I 07:45:45 Filling Buffer... (20 MB)
I 07:45:45 Writing LeadIn...
I 07:46:53 Writing Session 1 of 1... (1 Track, LBA: 0 - 2294911)
I 07:46:53 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2294911)
W 08:09:19 Failed to Write Sectors 625696 - 625727 - Reason: Command Sequence Error
W 08:09:19 Retrying (1 of 20)...
W 08:09:19 Retry Failed - Reason: Command Sequence Error
W 08:09:19 Retrying (2 of 20)...
W 08:09:20 Retry Failed - Reason: Command Sequence Error
W 08:09:20 Retrying (3 of 20)...
W 08:09:20 Retry Failed - Reason: Command Sequence Error
W 08:09:20 Retrying (4 of 20)...
W 08:09:20 Retry Failed - Reason: Command Sequence Error
W 08:09:20 Retrying (5 of 20)...
W 08:09:20 Retry Failed - Reason: Command Sequence Error
W 08:09:20 Retrying (6 of 20)...
W 08:09:20 Retry Failed - Reason: Command Sequence Error
W 08:09:20 Retrying (7 of 20)...
W 08:09:20 Retry Failed - Reason: Command Sequence Error
W 08:09:20 Retrying (8 of 20)...
W 08:09:20 Retry Failed - Reason: Command Sequence Error
W 08:09:20 Retrying (9 of 20)...
W 08:09:20 Retry Failed - Reason: Command Sequence Error
W 08:09:20 Retrying (10 of 20)...
W 08:09:20 Retry Failed - Reason: Command Sequence Error
W 08:09:20 Retrying (11 of 20)...
W 08:09:20 Retry Failed - Reason: Command Sequence Error
W 08:09:20 Retrying (12 of 20)...
W 08:09:20 Retry Failed - Reason: Command Sequence Error
W 08:09:20 Retrying (13 of 20)...
W 08:09:20 Retry Failed - Reason: Command Sequence Error
W 08:09:20 Retrying (14 of 20)...
W 08:09:20 Retry Failed - Reason: Command Sequence Error
W 08:09:20 Retrying (15 of 20)...
W 08:09:20 Retry Failed - Reason: Command Sequence Error
W 08:09:20 Retrying (16 of 20)...
W 08:09:20 Retry Failed - Reason: Command Sequence Error
W 08:09:20 Retrying (17 of 20)...
W 08:09:20 Retry Failed - Reason: Command Sequence Error
W 08:09:20 Retrying (18 of 20)...
W 08:09:20 Retry Failed - Reason: Command Sequence Error
W 08:09:20 Retrying (19 of 20)...
W 08:09:20 Retry Failed - Reason: Command Sequence Error
W 08:09:20 Retrying (20 of 20)...
W 08:09:20 Retry Failed - Reason: Command Sequence Error
E 08:09:37 Failed to Write Sectors 625696 - 625727 - Reason: Command Sequence Error
I 08:09:37 Synchronising Cache...
W 08:09:40 User opted to skip the 'Close Track/Session/Disc' functions.
E 08:09:40 Failed to Write Image!
I 08:09:40 Exporting Graph Data...
I 08:09:40 Graph Data File: C:\Documents and Settings\You Wish\Application Data\ImgBurn\Graph Data Files\LITE-ON_DVDRW_SOHW-1693S_KS09_FRIDAY-SEPTEMBER-04-2009_7-45_AM_CMC_MAG._AM3_2x.ibg
I 08:09:40 Export Successfully Completed!
E 08:09:40 Operation Failed! - Duration: 00:23:55
I 08:09:40 Average Write Rate: 917 KB/s (0.7x) - Maximum Write Rate: 2,704 KB/s (2.0x)
Also, after Excite truck i thought i had a couple more success's with cursed mountain and the conduit only to find out their discs cannot be read five mins into gameplay, jeez. Oh and Excite Truck works flawlessly.
|
|
Advertisement
|
|
|
|
AfterDawn Addict
|
4. September 2009 @ 15:29 |
Link to this message
|
|
|
|
cnalley87
Newbie
|
4. September 2009 @ 15:38 |
Link to this message
|
First off, Thank You. OK, so for f*#%'s sake i tried to burn Cod3 before installing the firmware. As i thought i did the same thing. Then I installed the firmware, rebooted and burnt the game again. The burn completed (YESSSSSS!) but as soon as i create a save file and choose my difficulty setting it goes to the cod3 loading screen, my wiimote shuts off and the console freezes. Im using Staples brand dvd-r's as that's all I have at hand right now. I will try using verbatim. What are some other decent brands just in case I can't find them?
|
|
cnalley87
Newbie
|
4. September 2009 @ 15:42 |
Link to this message
|
|
Also, I have Several games burnt on my staples dvd-r's(all which I have original copies for) and never had problems with them before . Why would the discs be doing this now?
|
AfterDawn Addict
|
4. September 2009 @ 16:01 |
Link to this message
|
Staples should carry Verbatim disks.
There seems to be a consensus that the only consistently reliable DVDs are Taiyo-Yuden and Verbatim.
Taiyo-Yuden are only available by mail order in North America.
Quote:
Source File Size: 4,699,979,776 bytes
You're burning to the outer edge of the disk - the edge of the disk is where problems often arise, hence better quality disks have consistently better results.
|
|
Advertisement
|
|
|
|
cnalley87
Newbie
|
4. September 2009 @ 16:07 |
Link to this message
|
|
Ok, I'll get verbatim's and post after a couple burns. Thanks for the knowledge!
|
|
