bekkys Posted February 10, 2011 Posted February 10, 2011 Hi, I use imgburn all the time to write to dvd, but when I try and burn downloaded trial software from adobe and write it to dvd, after I compare the checksums they are different. I can't install the software from the dvd because the checksums are different and get errors. I am using a Pioneer DVD-RW DVR-111D 1.29 (ATA) and from searching the forums I think the drive is adding padding or sectors to the DVD. How can I stop the drive adding padding or sectors to the DVD? Thanks, bekky
LIGHTNING UK! Posted February 11, 2011 Posted February 11, 2011 Post the log of you burning and verifying that image please.
bekkys Posted February 11, 2011 Author Posted February 11, 2011 Hi, The fastsum image shows the checksums for the files. The first file is the checksum of the image before it is written. The second file which matches the first file is the original file source. The third file with a different checksum is after the file has been written. Is this what you wanted? Thanks, bekky
bekkys Posted February 11, 2011 Author Posted February 11, 2011 here is the information after creating the image and then after is has been written to cd.
mmalves Posted February 11, 2011 Posted February 11, 2011 We need the log from when you burned the disc.
bekkys Posted February 11, 2011 Author Posted February 11, 2011 Hi, The source file checksum is 7411CEE779D62FB82B64015C59B9862B and the written file checksum is 6C32DC3F1344A3A281985B0ACD662ADF. The log is below: I 23:00:25 ImgBurn Version 2.5.5.0 started! I 23:00:25 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 23:00:25 Total Physical Memory: 3,407,340 KB - Available: 2,340,444 KB I 23:00:25 Initialising SPTI... I 23:00:25 Searching for SCSI / ATAPI devices... I 23:00:25 -> Drive 1 - Info: PIONEER DVD-RW DVR-111D 1.29 (D:) (ATA) I 23:00:25 -> Drive 2 - Info: PIONEER DVD-RW DVR-111D 1.29 (E:) (ATA) I 23:00:25 Found 2 DVD±RWs! I 23:01:01 Operation Started! I 23:01:01 Building Image Tree... I 23:01:07 Checking Directory Depth... I 23:01:07 Calculating Totals... I 23:01:07 Preparing Image... I 23:01:07 Checking Path Length... I 23:01:07 Contents: 1 File, 0 Folders I 23:01:07 Content Type: Data I 23:01:07 Data Type: MODE1/2048 I 23:01:07 File System(s): ISO9660, UDF (1.02) I 23:01:07 Volume Label: Acrobat I 23:01:07 Size: 487,666,616 bytes I 23:01:07 Sectors: 238,119 I 23:01:07 Image Size: 488,243,200 bytes I 23:01:07 Image Sectors: 238,400 I 23:01:09 Operation Successfully Completed! - Duration: 00:00:08 I 23:01:09 Operation Started! I 23:01:09 Image Contents: 1 File, 0 Folders I 23:01:09 Image Sectors: 238,400 (MODE1/2048) I 23:01:09 Image Size: 488,243,200 bytes I 23:01:09 Image Volume Identifier: Acrobat I 23:01:09 Image Volume Set Identifier: 3E4B68200003A330 I 23:01:09 Image Application Identifier: IMGBURN V2.5.5.0 - THE ULTIMATE IMAGE BURNER! I 23:01:09 Image Implementation Identifier: ImgBurn I 23:01:09 Image File System(s): ISO9660, UDF (1.02) I 23:01:09 Destination File: C:\acrobat.iso I 23:01:09 Destination Free Space: 2,394,484,736 Bytes (2,338,364 KB) (2,283 MB) (2 GB) I 23:01:09 Destination File System: NTFS I 23:01:09 File Splitting: Auto I 23:01:09 Writing Image... I 23:01:32 Image MD5: 2ed2eaa541fc259a88072d821569b3a0 I 23:01:32 Operation Successfully Completed! - Duration: 00:00:23 I 23:01:32 Average Write Rate: 20,730 KB/s (138.2x) - Maximum Write Rate: 26,732 KB/s (178.2x) I 23:01:50 Operation Started! I 23:01:50 Source File: C:\acrobat.mds I 23:01:50 Source File Sectors: 238,400 (MODE1/2048) I 23:01:50 Source File Size: 488,243,200 bytes I 23:01:50 Source File Volume Identifier: Acrobat I 23:01:50 Source File Volume Set Identifier: 3E4B68200003A330 I 23:01:50 Source File Application Identifier: IMGBURN V2.5.5.0 - THE ULTIMATE IMAGE BURNER! I 23:01:50 Source File Implementation Identifier: ImgBurn I 23:01:50 Source File File System(s): ISO9660, UDF (1.02) I 23:01:50 Destination Device: [0:1:0] PIONEER DVD-RW DVR-111D 1.29 (F:) (ATA) I 23:01:50 Destination Media Type: CD-R (Disc ID: 97m26s66f, CMC Magnetics Corp.) (Speeds: 4x, 10x, 16x, 24x, 32x, 40x) I 23:01:50 Destination Media Sectors: 359,844 I 23:01:50 Write Mode: CD I 23:01:50 Write Type: SAO I 23:01:50 Write Speed: MAX I 23:01:50 Lock Volume: Yes I 23:01:50 Test Mode: No I 23:01:50 OPC: No I 23:01:50 BURN-Proof: Enabled I 23:01:50 Write Speed Successfully Set! - Effective: 7,056 KB/s (40x) I 23:01:50 Advanced Settings - Optimal Writing Speed: No I 23:01:50 Filling Buffer... (40 MB) I 23:01:51 Writing LeadIn... I 23:02:15 Writing Session 1 of 1... (1 Track, LBA: 0 - 238399) I 23:02:15 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 238399) I 23:04:19 Synchronising Cache... I 23:04:24 Image MD5: 2ed2eaa541fc259a88072d821569b3a0 I 23:04:24 Exporting Graph Data... I 23:04:24 Graph Data File: C:\PIONEER_DVD-RW_DVR-111D_1.29_FRIDAY-10-FEBRUARY-2011_1-01_PM_97m26s66f_MAX.ibg I 23:04:24 Export Successfully Completed! I 23:04:24 Operation Successfully Completed! - Duration: 00:02:34 I 23:04:24 Average Write Rate: 3,876 KB/s (25.8x) - Maximum Write Rate: 5,128 KB/s (34.2x) I 23:04:24 Cycling Tray before Verify... W 23:04:33 Waiting for device to become ready... I 23:04:48 Device Ready! I 23:04:49 Operation Started! I 23:04:49 Source Device: [0:1:0] PIONEER DVD-RW DVR-111D 1.29 (F:) (ATA) I 23:04:49 Source Media Type: CD-ROM (Speeds: 4x, 10x, 16x, 24x, 32x, 40x) I 23:04:49 Image File: C:\acrobat.mds I 23:04:49 Image File Sectors: 238,400 (MODE1/2048) I 23:04:49 Image File Size: 488,243,200 bytes I 23:04:49 Image File Volume Identifier: Acrobat I 23:04:49 Image File Volume Set Identifier: 3E4B68200003A330 I 23:04:49 Image File Application Identifier: IMGBURN V2.5.5.0 - THE ULTIMATE IMAGE BURNER! I 23:04:49 Image File Implementation Identifier: ImgBurn I 23:04:49 Image File File System(s): ISO9660, UDF (1.02) I 23:04:49 Read Speed (Data/Audio): MAX / MAX I 23:04:49 Verifying Session 1 of 1... (1 Track, LBA: 0 - 238399) I 23:04:49 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 238399) I 23:06:55 Device MD5: 2ed2eaa541fc259a88072d821569b3a0 I 23:06:55 Image MD5: 2ed2eaa541fc259a88072d821569b3a0 I 23:06:55 Exporting Graph Data... I 23:06:55 Graph Data File: C:\PIONEER_DVD-RW_DVR-111D_1.29_FRIDAY-10-FEBRUARY-2011_1-01_PM_97m26s66f_MAX.ibg I 23:06:55 Export Successfully Completed! I 23:06:55 Operation Successfully Completed! - Duration: 00:02:06 I 23:06:55 Average Verify Rate: 3,814 KB/s (25.4x) - Maximum Verify Rate: 5,356 KB/s (35.7x) I 23:06:59 Close Request Acknowledged I 23:06:59 Closing Down... I 23:06:59 Shutting down SPTI... I 23:06:59 ImgBurn closed! Thanks, bekky
LIGHTNING UK! Posted February 11, 2011 Posted February 11, 2011 Once you've made your ISO, mount it in a virtual drive program (i.e. Virtual CloneDrive) and then do a hex compare between the source file on your hdd and the on on the virtual drive. I'd be interested to see exactly where in the file things are going wrong. I've just built and burnt an image here using that same source exe and mine works fine.
bekkys Posted February 11, 2011 Author Posted February 11, 2011 (edited) Hi, I mounted and compared it and the hex compare matches. When I hex compare the written dvd file with hex compare these are the results. Thanks, bekky Edited February 12, 2011 by bekkys
bekkys Posted February 12, 2011 Author Posted February 12, 2011 (edited) Does this help? Thanks, bekky Edited February 12, 2011 by bekkys
LIGHTNING UK! Posted February 12, 2011 Posted February 12, 2011 It doesn't make much sense really. The image on your hdd is fine - yeah? You mounted that and it checked out ok. Your initial log shows the md5 of the image when it was built and when you'd burn/verified the disc... all of them match. So where are these errors being introduced?! To me, it looks like memory corruption or something. Run Memtest86+ for a few passes and see if it picks anything up.
bekkys Posted February 13, 2011 Author Posted February 13, 2011 Hi, I ran Memtest86+ and there were no errors at all. I also tried to write the same file on a different computer and it had the same problem with the checksum. What else could this be? I have used dvd+r and dvd-r discs and this didnt help. I have wasted about 20 discs. When i copy the file to a usb drive it works and the checksums match. Thanks, bekky
ianymaty Posted February 13, 2011 Posted February 13, 2011 Just a hunch, couldn't be some antivirus or other protection software interfere?
bekkys Posted February 13, 2011 Author Posted February 13, 2011 Hi, I disabled the antivirus software as well.
bekkys Posted February 14, 2011 Author Posted February 14, 2011 Has anyone got any other ideas how I can prevent this? Is imgburn faulty? Thanks, bekky
LIGHTNING UK! Posted February 14, 2011 Posted February 14, 2011 I suggest you go right back to the start. Take your exe, make an ISO using Build mode. Make a note of the MD5 ImgBurn shows you in the log (or MD5 the entire ISO yourself manually - actually, do both and make sure they match). Mount the ISO and double check the exe file is still ok. Now burn the ISO and double check the MD5s in the log after the Write phase and the Verify phase still match the one you noted down earlier. Now check the exe on the burnt disc. The hex compare screenshots show that something very odd is going on. The few bytes that have been changed (12 in total) have only really had 1 bit changed in the byte (11 out of 12 times, it's bit 0) - that's why I said it looked like memory corruption. If ImgBurn had a problem causing a global issue like that, we'd have heard about it by now because nothing would ever work! And like I said earlier, I can burn the same file without any problem.
bekkys Posted February 15, 2011 Author Posted February 15, 2011 I suggest you go right back to the start. Take your exe, make an ISO using Build mode. Make a note of the MD5 ImgBurn shows you in the log (or MD5 the entire ISO yourself manually - actually, do both and make sure they match). Mount the ISO and double check the exe file is still ok. Now burn the ISO and double check the MD5s in the log after the Write phase and the Verify phase still match the one you noted down earlier. Now check the exe on the burnt disc. The hex compare screenshots show that something very odd is going on. The few bytes that have been changed (12 in total) have only really had 1 bit changed in the byte (11 out of 12 times, it's bit 0) - that's why I said it looked like memory corruption. If ImgBurn had a problem causing a global issue like that, we'd have heard about it by now because nothing would ever work! And like I said earlier, I can burn the same file without any problem. Hi, I tried everything you said and did the same on another computer with the same result. They are running xp and vista. I also tried it with the verbatim +r discs and the same problem. What else can i try? this is so frustrating Thanks, bekky
LIGHTNING UK! Posted February 15, 2011 Posted February 15, 2011 Ok so what happened when you did all that exactly? Was the ISO ok? (the exe was still ok once mounted) Did the MD5 in ImgBurn's log match each time? Post the new logs after each stage of what I said in my previous post.
bekkys Posted February 15, 2011 Author Posted February 15, 2011 Ok so what happened when you did all that exactly? Was the ISO ok? (the exe was still ok once mounted) Did the MD5 in ImgBurn's log match each time? Post the new logs after each stage of what I said in my previous post. Hi, The log file is too big and confusing because i have been trying so many things, but this is what has happened. The md5 of the file using FastSum is 7411CEE779D62FB82B64015C59B9862B and the Image MD5 from imgburn is 7514325a56dcdccad8bc8d47523b541b. When I write to dvd imgburn verifies the md5 and the logs show the Image MD5 and Device MD5 both match. When I run FastSum on the source file and the dvd file there is mismatch. If I open the imgburn iso and run FastSum on the source file and the file in the imgburn iso the md5 both match. It is only when I write to dvb that md5 of the file inside the iso is changing. I tried the same on another computer and the results are identical. thanks, becky
LIGHTNING UK! Posted February 15, 2011 Posted February 15, 2011 You only have to copy + paste all the info from the Log window itself after performing the specific thing I mentioned. Close the program after each step (well, there are only 2 really) so you can start a fresh. At this point, I simply can't help you and have pretty much lost the will to live (where your issue is concerned).
bekkys Posted February 26, 2011 Author Posted February 26, 2011 You only have to copy + paste all the info from the Log window itself after performing the specific thing I mentioned. Close the program after each step (well, there are only 2 really) so you can start a fresh. At this point, I simply can't help you and have pretty much lost the will to live (where your issue is concerned). Hi, I formatted my computer and everything seems to be working properly. Thanks for your help. Thanks, bekky
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