dr_ml422 Posted April 8, 2011 Posted April 8, 2011 Ok so my Sammy as described above gives me this error at about 99%. I 09:26:56 Operation Started! I 09:26:56 Source File: N:\MY ImgBurn ISO's\25TH_HOUR.iso I 09:26:56 Source File Sectors: 2,284,384 (MODE1/2048) I 09:26:56 Source File Size: 4,678,418,432 bytes I 09:26:56 Source File Volume Identifier: 25TH_HOUR I 09:26:56 Source File Volume Set Identifier: 3B28A1EF________25TH_HOUR I 09:26:56 Source File Implementation Identifier: VsoSoftware I 09:26:56 Source File File System(s): ISO9660, UDF (1.02) I 09:26:56 Destination Device: [1:0:0] TSSTcorp CDDVDW SH-S203B SB04 (D:) (SATA) I 09:26:56 Destination Media Type: DVD+R (Disc ID: SONY-D21-00) (Speeds: 4x, 6x, 8x, 12x, 16x) I 09:26:56 Destination Media Sectors: 2,295,104 I 09:26:56 Write Mode: DVD I 09:26:56 Write Type: DAO I 09:26:56 Write Speed: MAX I 09:26:56 DVD+R Reserve Track: No I 09:26:56 Link Size: Auto I 09:26:56 Lock Volume: Yes I 09:26:56 Test Mode: No I 09:26:56 OPC: No I 09:26:56 BURN-Proof: Enabled I 09:26:56 Write Speed Successfully Set! - Effective: 22,160 KB/s (16x) I 09:26:56 Book Type Setting: N/A (Reason: Incorrect function.) I 09:26:56 Filling Buffer... (40 MB) I 09:26:57 Writing LeadIn... I 09:27:14 Writing Session 1 of 1... (1 Track, LBA: 0 - 2284383) I 09:27:14 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2284383) W 09:32:28 Failed to Write Sectors 2269696 - 2269727 - Reason: Write Error W 09:32:28 Retrying (1 of 20)... W 09:32:28 Retry Failed - Reason: Invalid Address For Write W 09:32:28 Retrying (2 of 20)... W 09:32:28 Retry Failed - Reason: Invalid Address For Write W 09:32:28 Retrying (3 of 20)... W 09:32:28 Retry Failed - Reason: Invalid Address For Write W 09:32:28 Retrying (4 of 20)... W 09:32:28 Retry Failed - Reason: Invalid Address For Write W 09:32:28 Retrying (5 of 20)... W 09:32:28 Retry Failed - Reason: Invalid Address For Write W 09:32:28 Retrying (6 of 20)... W 09:32:28 Retry Failed - Reason: Invalid Address For Write W 09:32:28 Retrying (7 of 20)... W 09:32:28 Retry Failed - Reason: Invalid Address For Write W 09:32:28 Retrying (8 of 20)... W 09:32:28 Retry Failed - Reason: Invalid Address For Write W 09:32:28 Retrying (9 of 20)... W 09:32:28 Retry Failed - Reason: Invalid Address For Write W 09:32:28 Retrying (10 of 20)... W 09:32:28 Retry Failed - Reason: Invalid Address For Write W 09:32:28 Retrying (11 of 20)... W 09:32:28 Retry Failed - Reason: Invalid Address For Write W 09:32:28 Retrying (12 of 20)... W 09:32:28 Retry Failed - Reason: Invalid Address For Write W 09:32:28 Retrying (13 of 20)... W 09:32:28 Retry Failed - Reason: Invalid Address For Write W 09:32:28 Retrying (14 of 20)... W 09:32:28 Retry Failed - Reason: Invalid Address For Write W 09:32:28 Retrying (15 of 20)... W 09:32:28 Retry Failed - Reason: Invalid Address For Write W 09:32:28 Retrying (16 of 20)... W 09:32:28 Retry Failed - Reason: Invalid Address For Write W 09:32:28 Retrying (17 of 20)... W 09:32:28 Retry Failed - Reason: Invalid Address For Write W 09:32:28 Retrying (18 of 20)... W 09:32:28 Retry Failed - Reason: Invalid Address For Write W 09:32:28 Retrying (19 of 20)... W 09:32:28 Retry Failed - Reason: Invalid Address For Write W 09:32:28 Retrying (20 of 20)... W 09:32:28 Retry Failed - Reason: Invalid Address For Write W 09:34:45 Retrying (21)... W 09:34:45 Retry Failed - Reason: Invalid Address For Write W 09:34:46 Retrying (22)... W 09:34:46 Retry Failed - Reason: Invalid Address For Write E 09:34:48 Failed to Write Sectors 2269696 - 2269727 - Reason: Write Error E 09:34:48 Next Writable Address: 2269408 I 09:34:48 Synchronising Cache... W 09:35:19 User opted to skip the 'Close Track/Session/Disc' functions. E 09:35:19 Failed to Write Image! I 09:35:23 Exporting Graph Data... I 09:35:23 Graph Data File: C:\Users\DR. MFC 7-64\AppData\Roaming\ImgBurn\Graph Data Files\TSSTcorp_CDDVDW_SH-S203B_SB04_FRIDAY-APRIL-08-2011_9-26_AM_SONY-D21-00_MAX.ibg I 09:35:23 Export Successfully Completed! E 09:35:23 Operation Failed! - Duration: 00:08:23 I 09:35:23 Average Write Rate: 10,020 KB/s (7.2x) - Maximum Write Rate: 21,931 KB/s (15.8x) I 09:39:11 Operation Started! I 09:39:11 Source File: N:\MY ImgBurn ISO's\25TH_HOUR.iso I 09:39:11 Source File Sectors: 2,284,384 (MODE1/2048) I 09:39:11 Source File Size: 4,678,418,432 bytes I 09:39:11 Source File Volume Identifier: 25TH_HOUR I 09:39:11 Source File Volume Set Identifier: 3B28A1EF________25TH_HOUR I 09:39:11 Source File Implementation Identifier: VsoSoftware I 09:39:11 Source File File System(s): ISO9660, UDF (1.02) I 09:39:11 Destination Device: [1:0:0] TSSTcorp CDDVDW SH-S203B SB04 (D:) (SATA) I 09:39:11 Destination Media Type: DVD+R (Disc ID: SONY-D21-00) (Speeds: 4x, 6x, 8x, 12x, 16x) I 09:39:11 Destination Media Sectors: 2,295,104 I 09:39:11 Write Mode: DVD I 09:39:11 Write Type: DAO I 09:39:11 Write Speed: 16x I 09:39:11 DVD+R Reserve Track: No I 09:39:11 Link Size: Auto I 09:39:11 Lock Volume: Yes I 09:39:11 Test Mode: No I 09:39:11 OPC: No I 09:39:11 BURN-Proof: Enabled I 09:39:11 Write Speed Successfully Set! - Effective: 22,160 KB/s (16x) I 09:39:11 Book Type Setting: N/A (Reason: Incorrect function.) I 09:39:11 Filling Buffer... (40 MB) I 09:39:11 Writing LeadIn... I 09:39:29 Writing Session 1 of 1... (1 Track, LBA: 0 - 2284383) I 09:39:29 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2284383) W 09:44:43 Failed to Write Sectors 2273248 - 2273279 - Reason: Write Error W 09:44:43 Retrying (1 of 20)... W 09:44:43 Retry Failed - Reason: Invalid Address For Write W 09:44:43 Retrying (2 of 20)... W 09:44:43 Retry Failed - Reason: Invalid Address For Write W 09:44:43 Retrying (3 of 20)... W 09:44:43 Retry Failed - Reason: Invalid Address For Write W 09:44:43 Retrying (4 of 20)... W 09:44:43 Retry Failed - Reason: Invalid Address For Write W 09:44:43 Retrying (5 of 20)... W 09:44:43 Retry Failed - Reason: Invalid Address For Write W 09:44:43 Retrying (6 of 20)... W 09:44:43 Retry Failed - Reason: Invalid Address For Write W 09:44:43 Retrying (7 of 20)... W 09:44:43 Retry Failed - Reason: Invalid Address For Write W 09:44:43 Retrying (8 of 20)... W 09:44:43 Retry Failed - Reason: Invalid Address For Write W 09:44:43 Retrying (9 of 20)... W 09:44:43 Retry Failed - Reason: Invalid Address For Write W 09:44:43 Retrying (10 of 20)... W 09:44:43 Retry Failed - Reason: Invalid Address For Write W 09:44:43 Retrying (11 of 20)... W 09:44:43 Retry Failed - Reason: Invalid Address For Write W 09:44:43 Retrying (12 of 20)... W 09:44:43 Retry Failed - Reason: Invalid Address For Write W 09:44:43 Retrying (13 of 20)... W 09:44:43 Retry Failed - Reason: Invalid Address For Write W 09:44:43 Retrying (14 of 20)... W 09:44:43 Retry Failed - Reason: Invalid Address For Write W 09:44:43 Retrying (15 of 20)... W 09:44:43 Retry Failed - Reason: Invalid Address For Write W 09:44:43 Retrying (16 of 20)... W 09:44:43 Retry Failed - Reason: Invalid Address For Write W 09:44:43 Retrying (17 of 20)... W 09:44:43 Retry Failed - Reason: Invalid Address For Write W 09:44:43 Retrying (18 of 20)... W 09:44:43 Retry Failed - Reason: Invalid Address For Write W 09:44:43 Retrying (19 of 20)... W 09:44:43 Retry Failed - Reason: Invalid Address For Write W 09:44:43 Retrying (20 of 20)... W 09:44:43 Retry Failed - Reason: Invalid Address For Write W 09:48:27 Retrying (21)... W 09:48:27 Retry Failed - Reason: Invalid Address For Write W 09:48:28 Retrying (22)... W 09:48:28 Retry Failed - Reason: Invalid Address For Write W 09:48:29 Retrying (23)... W 09:48:29 Retry Failed - Reason: Invalid Address For Write W 09:48:29 Retrying (24)... W 09:48:29 Retry Failed - Reason: Invalid Address For Write W 09:48:30 Retrying (25)... W 09:48:30 Retry Failed - Reason: Invalid Address For Write E 09:48:32 Failed to Write Sectors 2273248 - 2273279 - Reason: Write Error E 09:48:32 Next Writable Address: 2272992 I 09:48:33 Synchronising Cache... I 09:48:50 Closing Track... I 09:48:52 Finalising Disc... E 09:49:11 Failed to Write Image! I 09:49:15 Exporting Graph Data... I 09:49:15 Graph Data File: C:\Users\DR. MFC 7-64\AppData\Roaming\ImgBurn\Graph Data Files\TSSTcorp_CDDVDW_SH-S203B_SB04_FRIDAY-APRIL-08-2011_9-39_AM_SONY-D21-00_16x.ibg I 09:49:15 Export Successfully Completed! E 09:49:15 Operation Failed! - Duration: 00:10:00 I did continue with close track/session and the burnt disc was ok. However, My ASUS burner had no issues whatsoever: I 10:54:52 Operation Started! I 10:54:52 Source File: N:\MY ImgBurn ISO's\25TH_HOUR.iso I 10:54:52 Source File Sectors: 2,284,384 (MODE1/2048) I 10:54:52 Source File Size: 4,678,418,432 bytes I 10:54:52 Source File Volume Identifier: 25TH_HOUR I 10:54:52 Source File Volume Set Identifier: 3B28A1EF________25TH_HOUR I 10:54:52 Source File Implementation Identifier: VsoSoftware I 10:54:52 Source File File System(s): ISO9660, UDF (1.02) I 10:54:52 Destination Device: [2:0:0] ASUS DRW-24B1ST 1.03 (E:) (SATA) I 10:54:52 Destination Media Type: DVD+R (Disc ID: SONY-D21-00) (Speeds: 6x, 8x, 12x, 16x) I 10:54:52 Destination Media Sectors: 2,295,104 I 10:54:52 Write Mode: DVD I 10:54:52 Write Type: DAO I 10:54:52 Write Speed: 16x I 10:54:52 DVD+R Reserve Track: No I 10:54:52 Link Size: Auto I 10:54:52 Lock Volume: Yes I 10:54:52 Test Mode: No I 10:54:52 OPC: No I 10:54:52 BURN-Proof: Enabled I 10:54:52 Write Speed Successfully Set! - Effective: 22,160 KB/s (16x) I 10:54:52 Filling Buffer... (40 MB) I 10:54:53 Writing LeadIn... I 10:55:13 Writing Session 1 of 1... (1 Track, LBA: 0 - 2284383) I 10:55:13 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2284383) I 11:00:20 Synchronising Cache... I 11:00:23 Closing Track... I 11:00:24 Finalising Disc... I 11:00:39 Exporting Graph Data... I 11:00:39 Graph Data File: C:\Users\DR. MFC 7-64\AppData\Roaming\ImgBurn\Graph Data Files\ASUS_DRW-24B1ST_1.03_FRIDAY-APRIL-08-2011_10-54_AM_SONY-D21-00_16x.ibg I 11:00:39 Export Successfully Completed! I 11:00:39 Operation Successfully Completed! - Duration: 00:05:40 I 11:00:39 Average Write Rate: 14,930 KB/s (10.8x) - Maximum Write Rate: 22,363 KB/s (16.1x) So, Sammy's about done or some other minor detail? Thnx.
LIGHTNING UK! Posted April 8, 2011 Posted April 8, 2011 Have you tried burning at 8x? Have you tried some other media? Maybe the samsung just doesn't like 'SONY-D21-00' very much.
dr_ml422 Posted April 9, 2011 Author Posted April 9, 2011 Have you tried burning at 8x? Have you tried some other media? Maybe the samsung just doesn't like 'SONY-D21-00' very much. I didn't think it would be a media compatibility issue or write speed. I haven't used Sony in a while and so the AWS was set for MAX as default. The other settings included the older TYs, Verbs and newer JVC TYs at 12x. Also some Pro-disc CD-Rs at 24x. Anyway it's working now so thanks as usual. One thing I can't get rid of is the number of copies that's set either in the queue or main write window. It continually stays at 2 copies no matter what I do. I tried refreshing the view and drives, and manually setting it back to 1, though on closing and restarting ImgBurn it goes back to 2 copies. Did you set this as default in the latest version? Guides have nothing on this, so unless there's some setting I'm totally missing my next move is a clean uninstall/install. Messes me up when using popular apps. like Fab etc... because if using a split disc function for example, I'm making a double copy of the 1st split disc instead of the 2nd split disc etc...
LIGHTNING UK! Posted April 9, 2011 Posted April 9, 2011 It doesn't remember/restore the number of copies now unless an option is enabled. As yours is defaulting to 2, you need to enable the option, change it to 1, close and reopen the program and then disable the option again. It's the 'Remember 'Copies'' one in the Settings on the 'Write' tab (Page 1).
dr_ml422 Posted April 10, 2011 Author Posted April 10, 2011 It doesn't remember/restore the number of copies now unless an option is enabled. As yours is defaulting to 2, you need to enable the option, change it to 1, close and reopen the program and then disable the option again. It's the 'Remember 'Copies'' one in the Settings on the 'Write' tab (Page 1). I got it now. Thnx. I knew something was new etc... Now I have a quick question;if I wanted to share the same image amongst all my drives in the queue to continuously make multiple copies, could the share selected images amongst drives setting work? Using the share all images amongst drives whilst trying to make multiple copies will only use the same burner, and you would have to continuously load blank media into the same drive. I figured if I used the share the selected images amongst drives, and had say the copies setting to 3, then ImgBurn would use all 3 of my burners to continuously burn said image until the desired number. Not at the same time, though at least 1 copy after another with each burner.
LIGHTNING UK! Posted April 10, 2011 Posted April 10, 2011 The 'Copies' thing only works for 1 drive. Use 'Queue Again' option to add the same image to the queue a bunch of times and then share them between drives.
dr_ml422 Posted April 11, 2011 Author Posted April 11, 2011 Ok, so I can queue the same image as many times as I want, and then select share all images amongst drives, and it will burn the number of copies I set in the queue window correct? I never thought about that for a single .ISO. It makes sens3e as each queued up file stays put until it gets burnt. I was doing it backwards. Setting say 3 copies to be burnt of 1 queued .iso in the queue. It will do it, though in 1 burner and manually feeding it blanks.
LIGHTNING UK! Posted April 11, 2011 Posted April 11, 2011 You'd leave 'Copies' set on 1 for what I said to do. Otherwise it'll still just make X copies on the 1 drive before moving onto the next image (which is actually the same as the previous image) - potentially on another drive.
dr_ml422 Posted April 13, 2011 Author Posted April 13, 2011 You'd leave 'Copies' set on 1 for what I said to do. Otherwise it'll still just make X copies on the 1 drive before moving onto the next image (which is actually the same as the previous image) - potentially on another drive. I got you. I noticed that when I checked off the Add to Queue function in Read mode, it did add it to the Queue, though the .MDS file not the .iso. Lucky I checked the file size and also went to the source to see what exactly was created in Read mode. There was 2 files. The .MDS and .iso. The .iso was the normal 4. or so GBs so I knew that's the movie. I have no idea why on some reading of DVD discs you only get a .iso, and others both the .mds and .iso. Mattere of fact I still have no clue what the .MDS is. I'll search this. Only thing I do remember is you telling me a while back that in order to burn from the queue, ImgBurn would need the smaller file to point to so it can write the larger. At least regarding .MP3 audio files. The cue function always produces 2 files for music I believe. I know it's almost always .bin and I think sometimes .mds, though not sure about this.
LIGHTNING UK! Posted April 14, 2011 Posted April 14, 2011 If the source DVD is double layer or under 1 GB in size, the program will create an MDS file too. It's correct that the MDS should be loaded when attempting to burn. If you select the ISO, the program would just tell you to select the MDS anyway.
dr_ml422 Posted April 14, 2011 Author Posted April 14, 2011 If the source DVD is double layer or under 1 GB in size, the program will create an MDS file too. It's correct that the MDS should be loaded when attempting to burn. If you select the ISO, the program would just tell you to select the MDS anyway. It didn't tell me to select the MDS file, and as I remember, whenever I did burn a MDS file it would not even be the video, just a couple of KBs of some kind of data. Here you go: http://en.wikipedia.org/wiki/MDS_file So basically you were/are one of the few who even used/uses it. Lol... I still even after reading this don't get the use for it.
LIGHTNING UK! Posted April 15, 2011 Posted April 15, 2011 If you try and burn an ISO in Write mode and there's an MDS file present with the same name, the program will tell you that you should have selected it (so long as the ISO is over 4.37GB in size). ISO files are dumb. They're just X number of sectors in a big file and don't tell you anything else about the media they came from - that's where the MDS file comes in. The MDS holds all the info about the source disc those sectors came from so that it can be faithfully reproduced or emulated (in the case of DAEMON Tools). ImgBurn really just uses it to store the layer break info.
dr_ml422 Posted April 16, 2011 Author Posted April 16, 2011 I got you and also took my sometimes lazy butt to the search/web to really find out what's the whole deal! Hence: ImgBurn doesn't attempt to burn the MDS to a disc, it looks in the MDS file to see the name of the image file it's associated with and extract other little bits of info from it. So just load the MDS and if it supports the image format, it'll load up and you can go ahead and press the 'Write' button to burn it.
dr_ml422 Posted April 17, 2011 Author Posted April 17, 2011 Lightning I just played w/a couple of .iso that had a .MDS file. One was just under 4.37GBs so ImgBurn just went ahead and burned as usual. The 2nd one was under 1GB and ImgBurn still went ahead and burned it w/no reminder of loading the >MDS file as you stated. It also didn't booktype to DVD-R as it usually does w/out any additional settings, as it's defaulted to perform this function. Maybe the burner doesn't support bitsetting? Here's the log: I 15:56:15 Operation Started! I 15:56:15 Source File: N:\MY IMgBURN .ISOs\FRAZETTA BONUS.ISO I 15:56:15 Source File Sectors: 471,552 (MODE1/2048) I 15:56:15 Source File Size: 965,738,496 bytes I 15:56:15 Source File Volume Identifier: FRAZETTA BONUS I 15:56:15 Source File Volume Set Identifier: 3AFCACF9000731FD I 15:56:15 Source File Application Identifier: IMGBURN V2.5.0.0 - THE ULTIMATE IMAGE BURNER! I 15:56:15 Source File Implementation Identifier: ImgBurn I 15:56:15 Source File File System(s): ISO9660, UDF (1.02) I 15:56:15 Destination Device: [2:0:0] ASUS DRW-24B1ST 1.03 (E:) (SATA) I 15:56:15 Destination Media Type: DVD+R (Disc ID: SONY-D21-00) (Speeds: 6x, 8x, 12x, 16x) I 15:56:15 Destination Media Sectors: 2,295,104 I 15:56:15 Write Mode: DVD I 15:56:15 Write Type: DAO I 15:56:15 Write Speed: 12x I 15:56:15 DVD+R Reserve Track: No I 15:56:15 Link Size: Auto I 15:56:15 Lock Volume: Yes I 15:56:15 Test Mode: No I 15:56:15 OPC: No I 15:56:15 BURN-Proof: Enabled I 15:56:15 Write Speed Successfully Set! - Effective: 16,620 KB/s (12x) I 15:56:15 Filling Buffer... (40 MB) I 15:56:16 Writing LeadIn... I 15:56:36 Writing Session 1 of 1... (1 Track, LBA: 0 - 471551) I 15:56:36 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 471551) I 15:58:34 Synchronising Cache... I 15:58:38 Closing Track... I 15:58:40 Finalising Disc... I 15:59:00 Exporting Graph Data... I 15:59:00 Graph Data File: C:\Users\DR. MFC 7-64\AppData\Roaming\ImgBurn\Graph Data Files\ASUS_DRW-24B1ST_1.03_SUNDAY-APRIL-17-2011_3-56_PM_SONY-D21-00_12x.ibg I 15:59:00 Export Successfully Completed! I 15:59:00 Operation Successfully Completed! - Duration: 00:02:40 I 15:59:00 Average Write Rate: 7,992 KB/s (5.8x) - Maximum Write Rate: 9,865 KB/s (7.1x) I'm always going to keep the .MDS files. I deleted all of them a while back when I transferred all my .iso files from 1HDD to another thinking they were useless. I have a thread on that too way back about 2yrs. ago. Live n Learn! Here's the 4.36GB log which is clear as it's not even 4.37Gb: I 15:33:08 ImgBurn Version 2.5.5.0 started! I 15:33:08 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1) I 15:33:08 Total Physical Memory: 4,192,440 KB - Available: 2,745,632 KB W 15:33:08 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 15:33:08 Initialising SPTI... I 15:33:08 Searching for SCSI / ATAPI devices... I 15:33:13 -> Drive 1 - Info: ASUS DRW-24B1ST 1.03 (E:) (SATA) I 15:33:13 -> Drive 2 - Info: TSSTcorp CDDVDW SH-S203B SB04 (D:) (SATA) I 15:33:13 -> Drive 3 - Info: TSSTcorp CDDVDW SH-S223F SB03 (F:) (SATA) I 15:33:13 Found 3 DVD±RW/RAMs! I 15:43:07 Operation Started! I 15:43:07 Source File: G:\MY IMgBURN .ISOs 2\310 To Yuma.iso I 15:43:07 Source File Sectors: 2,289,344 (MODE1/2048) I 15:43:07 Source File Size: 4,688,576,512 bytes I 15:43:07 Source File Volume Identifier: 310 To Yuma I 15:43:07 Source File Volume Set Identifier: 4D01DE43________310 To Yuma I 15:43:07 Source File Application Identifier: ELBY CLONEDVD I 15:43:07 Source File Implementation Identifier: ELABORATE BYTES I 15:43:07 Source File File System(s): ISO9660, UDF (1.02) I 15:43:07 Destination Device: [2:0:0] ASUS DRW-24B1ST 1.03 (E:) (SATA) I 15:43:07 Destination Media Type: DVD+R (Disc ID: SONY-D21-00) (Speeds: 6x, 8x, 12x, 16x) I 15:43:07 Destination Media Sectors: 2,295,104 I 15:43:07 Write Mode: DVD I 15:43:07 Write Type: DAO I 15:43:07 Write Speed: 12x I 15:43:07 DVD+R Reserve Track: No I 15:43:07 Link Size: Auto I 15:43:07 Lock Volume: Yes I 15:43:07 Test Mode: No I 15:43:07 OPC: No I 15:43:07 BURN-Proof: Enabled I 15:43:07 Write Speed Successfully Set! - Effective: 16,620 KB/s (12x) I 15:43:07 Filling Buffer... (40 MB) I 15:43:07 Writing LeadIn... I 15:43:30 Writing Session 1 of 1... (1 Track, LBA: 0 - 2289343) I 15:43:30 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2289343) I 15:50:31 Synchronising Cache... I 15:50:35 Closing Track... I 15:50:37 Finalising Disc... I 15:50:57 Exporting Graph Data... I 15:50:57 Graph Data File: C:\Users\DR. MFC 7-64\AppData\Roaming\ImgBurn\Graph Data Files\ASUS_DRW-24B1ST_1.03_SUNDAY-APRIL-17-2011_3-43_PM_SONY-D21-00_12x.ibg I 15:50:57 Export Successfully Completed! I 15:50:57 Operation Successfully Completed! - Duration: 00:07:46 I 15:50:57 Average Write Rate: 10,901 KB/s (7.9x) - Maximum Write Rate: 16,918 KB/s (12.2x)
LIGHTNING UK! Posted April 18, 2011 Posted April 18, 2011 The Asus drives aren't supported/handled by the auto change booktype code. Your 2 Samsung drives would be though.
dr_ml422 Posted April 18, 2011 Author Posted April 18, 2011 The Asus drives aren't supported/handled by the auto change booktype code. Your 2 Samsung drives would be though. I'm keeping this in mind and will also check out the burner thread to see what's hot and what's not. It's there for a reason for Pete's sake.
dr_ml422 Posted April 19, 2011 Author Posted April 19, 2011 The Asus drives aren't supported/handled by the auto change booktype code. Your 2 Samsung drives would be though. I'm keeping this in mind and will also check out the burner thread to see what's hot and what's not. It's there for a reason for Pete's sake. Lightning I know for sure My Sammy's booktype so why isn't it happening from what you can see here:Thanx. I 19:47:11 Source File: N:\MY IMgBURN .ISOs\BANGKOK DANGEROUS 2.ISO I 19:47:11 Source File Sectors: 2,127,168 (MODE1/2048) I 19:47:11 Source File Size: 4,356,440,064 bytes I 19:47:11 Source File Volume Identifier: Bangkok_Dangerous_2 I 19:47:11 Source File Volume Set Identifier: 3AC195520020753D I 19:47:11 Source File Application Identifier: IMGBURN V2.4.4.0 - THE ULTIMATE IMAGE BURNER! I 19:47:11 Source File Implementation Identifier: ImgBurn I 19:47:11 Source File File System(s): ISO9660, UDF (1.02) I 19:47:11 Destination Device: [1:0:0] TSSTcorp CDDVDW SH-S203B SB04 (D:) (SATA) I 19:47:11 Destination Media Type: DVD+R (Disc ID: SONY-D21-00) (Speeds: 4x, 6x, 8x, 12x, 16x) I 19:47:11 Destination Media Sectors: 2,295,104 I 19:47:11 Write Mode: DVD I 19:47:11 Write Type: DAO I 19:47:11 Write Speed: 12x I 19:47:11 DVD+R Reserve Track: No I 19:47:11 Link Size: Auto I 19:47:11 Lock Volume: Yes I 19:47:11 Test Mode: No I 19:47:12 OPC: No I 19:47:12 BURN-Proof: Enabled I 19:47:13 Write Speed Successfully Set! - Effective: 16,620 KB/s (12x) I 19:47:13 Book Type Setting: N/A (Reason: Incorrect function.) I 19:47:13 Filling Buffer... (40 MB) I 19:47:13 Writing LeadIn... I 19:47:30 Writing Session 1 of 1... (1 Track, LBA: 0 - 2127167) I 19:47:30 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2127167) I 19:53:52 Synchronising Cache... I 19:53:57 Closing Track... I 19:54:00 Finalising Disc... I 19:54:21 Exporting Graph Data... I 19:54:21 Graph Data File: C:\Users\DR. MFC 7-64\AppData\Roaming\ImgBurn\Graph Data Files\TSSTcorp_CDDVDW_SH-S203B_SB04_MONDAY-APRIL-18-2011_7-47_PM_SONY-D21-00_12x.ibg I 19:54:21 Export Successfully Completed! I 19:54:21 Operation Successfully Completed! - Duration: 00:07:05 These Sammys always booktyped.
LIGHTNING UK! Posted April 19, 2011 Posted April 19, 2011 Windows (or rather your drivers) is what's causing the problem with booktype (same issue in your first log). It's not the drive itself erroring out. The command is just erroring out and the error code being returned translates to 'Incorrect function.'. What (make/model of) controller are the Samsung drives connected to?
dr_ml422 Posted April 19, 2011 Author Posted April 19, 2011 (edited) I went to device manager and it only told me the location of the controller. I didn't see anything about make and model. Would I have to go into Bios for this, or is there another way to find this out? This just started happening recently, before everything was fine. I did notice under Drivers for the Samsung Burners that there was a windows location and a AnyDVD location as well. I got it Lightning! The Sata storage controllers were set to AHCI instead of IDE in Bios. Here's a new log with bitsetting implemented: I 10:25:20 ImgBurn Version 2.5.5.0 started! I 10:25:20 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1) I 10:25:20 Total Physical Memory: 4,192,440 KB - Available: 3,105,084 KB W 10:25:20 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 10:25:20 Initialising SPTI... I 10:25:20 Searching for SCSI / ATAPI devices... I 10:25:20 -> Drive 1 - Info: ASUS DRW-24B1ST 1.03 (D:) (ATA) I 10:25:20 -> Drive 2 - Info: TSSTcorp CDDVDW SH-S203B SB04 (E:) (ATA) I 10:25:20 -> Drive 3 - Info: TSSTcorp CDDVDW SH-S223F SB03 (F:) (ATA) I 10:25:20 Found 3 DVD±RW/RAMs! I 10:43:16 Operation Started! I 10:43:16 Source File: N:\MY IMgBURN .ISOs\DEATH RACE.ISO I 10:43:16 Source File Sectors: 2,253,216 (MODE1/2048) I 10:43:16 Source File Size: 4,614,586,368 bytes I 10:43:16 Source File Volume Identifier: DEATH_RACE I 10:43:16 Source File Volume Set Identifier: 3AC290C500226192 I 10:43:16 Source File Application Identifier: IMGBURN V2.4.4.0 - THE ULTIMATE IMAGE BURNER! I 10:43:16 Source File Implementation Identifier: ImgBurn I 10:43:16 Source File File System(s): ISO9660, UDF (1.02) I 10:43:16 Destination Device: [1:0:0] TSSTcorp CDDVDW SH-S203B SB04 (E:) (ATA) I 10:43:16 Destination Media Type: DVD+R (Disc ID: SONY-D21-00) (Speeds: 4x, 6x, 8x, 12x, 16x) I 10:43:16 Destination Media Sectors: 2,295,104 I 10:43:16 Write Mode: DVD I 10:43:16 Write Type: DAO I 10:43:16 Write Speed: 12x I 10:43:16 DVD+R Reserve Track: No I 10:43:16 Link Size: Auto I 10:43:16 Lock Volume: Yes I 10:43:16 Test Mode: No I 10:43:16 OPC: No I 10:43:16 BURN-Proof: Enabled I 10:43:18 Write Speed Successfully Set! - Effective: 16,620 KB/s (12x) I 10:43:18 Book Type Setting: DVD-ROM I 10:43:18 Filling Buffer... (40 MB) I 10:43:18 Writing LeadIn... I 10:43:33 Writing Session 1 of 1... (1 Track, LBA: 0 - 2253215) I 10:43:33 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2253215) I 10:50:11 Synchronising Cache... I 10:50:17 Closing Track... I 10:50:20 Finalising Disc... I 10:50:41 Exporting Graph Data... I 10:50:41 Graph Data File: C:\Users\DR. MFC 7-64\AppData\Roaming\ImgBurn\Graph Data Files\TSSTcorp_CDDVDW_SH-S203B_SB04_TUESDAY-APRIL-19-2011_10-43_AM_SONY-D21-00_12x.ibg I 10:50:41 Export Successfully Completed! I 10:50:41 Operation Successfully Completed! - Duration: 00:07:21 I 10:50:41 Average Write Rate: 11,351 KB/s (8.2x) - Maximum Write Rate: 16,505 KB/s (11.9x) Edited April 19, 2011 by dr_ml422
LIGHTNING UK! Posted April 19, 2011 Posted April 19, 2011 Knowing the make / model of your motherboard is usually enough. If you have an Intel chipset board, you just need the latest rapid storage tech drivers installed - then ahci should work too.
dr_ml422 Posted April 20, 2011 Author Posted April 20, 2011 (edited) My board is the M4A78T-E by ASUS. Chipset is AMD 790GX/SB750. Something's telling me that Intel might be the industry favorite/standard. I build so prolly for the heck of it I'll make my next one a Intel board. Build wise only difference I can see is the price for the CPU. I don't think Intel is making ImgBurn or any other of the popular apps. we use work any better/faster does it? Lightning just a quick update. Everything's fine and the queued .MDS files that are loaded after a Read do point to the whole .iso when burning from the queue. When using the regular write mode and selecting the .MDS file it won't point to the .iso. It will just burn the .MDS file. Edited April 23, 2011 by dr_ml422
Recommended Posts