![](https://forum.imgburn.com/uploads/set_resources_1/84c1e40ea0e759e3f1505eb1788ddf3c_pattern.png)
laserfan
-
Posts
169 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by laserfan
-
-
Well, yes. I was asking if it was possible to verify miscellaneous files, NOT an image, after a burn. From a 2nd drive. It does a verify now, knowing the list of files & their locations that it just burned. Why not an option to change the "compare from drive X" or something....you can only verify against an image file (eg ISO).I've used WinMerge to do binary compares and it works well enough, but of course one has to load the app and select all the files on the freshly burned disk, then find all the originals of those burned files on the hard disk drives' locations for comparison. Do-able yes, trivial no...
Just a suggestion...
-
You can do it, if you are prepared to ignore the invevitable file system date and time errors in certain sectors (16/32/261/269 and some others).
Sorry, but...what are you talking about? "Inevitable errors"? Do tell, or give a link????
-
Today I realized ImgBurn only allows switching of drives for Verify mode when burning from an image file, not from miscellaneous files that one might be burning to a disc.
Is there a way to do this i.e. that ImgBurn would remember the files I've just burned and verify the disk against the hdd originals?
-
Sure, of course, now that I see how easy Verify mode is to use, I completely agree. And I also found the "eject tray after Write" checkbox in Device options as well...how easy is that. Burn, eject, replace, verify...I've got it.Because it's already possible via Verify mode.I think it will take me a little while to get the hang of the extraordinarily rich ImgBurn feature set!
-
Thanks Cynthia, I am relatively new to ImgBurn and didn't know one could do this!You can already do this. Don't delete the image after the write and skip the verify option. When the disc is done in the 'Write' mode - move it to your other device and use the 'Verify' mode and select the image you used for the 'Write' operation, to do the verify.Not sure LUK why you'd say "never" but I am happy w/Cynthia's suggestion.
-
I've always thought that (if it were technically feasible) that it would be nice to include among the "Verify" options to cycle the disk to another drive. That is, after burning is complete, instead of cycling the disk out-and-back-in and continuing w/Verify, to present the disk and allow the "Verify" stage to complete from a second drive.
Part of this is the "anal" in me that wants to preserve the (more expensive) burner drive that's gotten heated-up over the burn cycle, and is getting worn-down by all the activity. Another part says "It'd be nice to actually verify that the burned disc is readable on a 2nd drive" in the same operation w/Burn.
I did a search and couldn't find any discussion of this before...
-
I must say for all my visits to the UK I did enjoy the food! Though I must admit I still find the word "bangers" pretty funny!McDonalds, Burger King, KFC... they're all goodThanks again for fretting along with me and my tribulations. I have edited the thread title to look less panicky--there are many things in life which look alot better in the rear-view mirror...
-
If you have ever worked in a (good) restaurant, you know that they APPRECIATE when customers tell them the food tastes bad
Wow, obviously no one here knows what a good restaurant is!!!!
#39;(
Well, I'm sure LUK understands the analogy...
-
I appreciate the advice, but the drive's 3 yrs old (almost to the day). Only paid $25+ for it so I'm not losing any sleep.
Whatever the "Setting High Speed" command did certainly hung the thing-up somehow, though it is possible if-not-likely that my CTL-ALT-DEL and then shutdown efforts are what actually killed it. In any case I felt I had to post to get LUK's attention, and he has responded exactly the way I'd have expected and hoped (to not make that command a default).
If you have ever worked in a (good) restaurant, you know that they APPRECIATE when customers tell them the food tastes bad, so they can pull it and not make anyone sick!
-
I do appreciate that you trusted my report and will change the default--this particular model (firmware TS05 btw) must have a thin skin. I've already substituted an old(er) Pio DVR103 in that position so I'm back in business, my main drive being a 109. But I think the Sammy's dead given the BIOS doesn't see it (even keeps the Master from being "seen" if it's plugged-in).
No hard feelings--I never contributed to that "other" piece of software of yours I (still) have around here someplace (!) so I'm still ahead of the game I think.
-
Sending a command to a drive shouldn't kill it, it should just reject it if it's not supported. I'm not familiar with that particular model but I've seen a fair few other mentioned in the forums and nobody else has come forward with a problem like that.
Well then I'm the first. At the least I would strongly suggest that you disable as Default the Enable High Speed Mode (Samsung) setting in the Read Settings menu, to save anyone else a similar fate.
While I agree that it *shouldn't* have killed my drive, but I am certainly convinced that somehow it *did*. I've built a fair number of computers and worked on many many more and this just did not have the look of coincidence. At least it was a cheap drive, but still...
-
I attempted a "make iso from disc" for a CD in my Samsung TS-H352A and ImgBurn immediately stuck on "Setting Samsung High Speed Mode..." and after a minute or two of doing nothing that I could see, or placing anything in the log, I aborted (or tried to abort) but nothing happened then either. I finally did CTL-ALT-DEL and tried to kill the imgburn.exe process and that didn't work either. Tried restarting the PC and it wouldn't shut-down normally.
Powered-off, and on re-starting the computer the drive is no longer detected in BIOS.
Dunno what "Setting Samsung High Speed mode" is supposed to do but I have a dead drive (with a CD stuck inside) as a result. I'll come back here and report if I'm able to revive it; so far no good.
-
Thanks dontasciime, I appreciate your attention to this.Just to make sure I tried with latest Beta.I still don't understand why ImgBurn didn't like my ACTIVEBOOT disk (different certainly from yours) but I just had occasion to make another ISO file from another disk here and it worked & verified fine.
I will wait for the next version and try my ACTIVEBOOT disk that fails with 2.32 again, as a test. Thanks again for replying!!!
-
The next version of ImgBurn has fixed this.
At present it's the same with A couple of bootable ISO I have, for instance the ghost2003.ISO I have gets to 99% and errors.
Omigosh that was fast--I was tweaking my post when you replied!!!
Is there a beta available somewhere? Guess I will go look for it...
-
Tried to make an .iso file on hdd from a CD, and when ImgBurn got to the very end, I started getting Read errors and so eventually I aborted. Tried it again with a different reader and same thing: at the very end Retries that I decide to abort. I left both .isos on the hard disk.
Then I tried RecordNow 7.3 to make an .iso of this same CD, and it completed without any errors, suggesting to me that the CD I was reading from is just fine.
Curious, I went back to ImgBurn and attempted a Verify of one of the "defective" ISOs ImgBurn had created, and the original CD verified against the "defective" aborted .iso just fine!!!??? Surprise!!??!!
Finally, I noticed in the ImgBurn logfile a note about "AnyDVD can affect Verify" and sure enough I have AnyDVD installed so I Disabled it and tried again to make a good .iso using ImgBurn. No dice, same problem, ImgBurn goes into Retry mode at the very end; apparently it doesn't like sector 53440 out of a total of 53442?
What do you suppose could be at issue with the CD that ImgBurn fails to read at the very end? But then even the aborted .iso verifies just fine!?
FIRST ATTEMPT TO MAKE ISO, GOT READ ERRORS AND ABORTED, LEAVING THE "FAILED" ISO IN PLACE:
; //****************************************\\ ; ImgBurn Version 2.3.2.0 - Log ; Saturday, 05 January 2008, 10:46:13 ; \\****************************************// ; ; I 10:36:29 ImgBurn Version 2.3.2.0 started! I 10:36:29 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 10:36:29 Total Physical Memory: 1,048,044 KB - Available: 590,672 KB W 10:36:29 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 10:36:29 Initialising SPTI... I 10:36:29 Searching for SCSI / ATAPI devices... I 10:36:29 Found 1 DVD-ROM, 1 DVD±RW and 1 HD DVD-ROM! I 10:37:20 Operation Started! I 10:37:20 Source Device: [1:1:0] TSSTcorp DVD-ROM TS-H352A TS05 (G:) (ATA) I 10:37:20 Source Media Type: CD-ROM I 10:37:20 Source Media Sectors: 53,442 I 10:37:20 Source Media Volume Identifier: ACTIVEBOOTDISK I 10:37:20 Source Media Application Identifier: OSCDIMG 2.45 (10/12/2000 TM) I 10:37:20 Source Media File System(s): ISO9660 (Bootable) I 10:37:20 Destination File: E:\ACTIVEBOOTDISK.ISO I 10:37:20 Destination Free Space: 105,980,674,048 bytes (103,496,752 KB) (101,071 MB) (98 GB) I 10:37:20 Destination File System: NTFS I 10:37:20 File Splitting: Auto I 10:37:20 Reading Sectors... (LBA: 0 - 53441) I 10:40:15 Abort Request Acknowledged E 10:40:20 Failed to Read Sector 53440 - Unrecovered Read Error E 10:40:20 Failed to Read Sectors! E 10:40:20 Operation Aborted! - Duration: 00:03:00 E 10:40:20 Average Read Rate: 593 KB/s (4.0x) - Maximum Read Rate: 1,496 KB/s (10.0x) I 10:41:09 Operation Started! I 10:41:09 Source Device: [1:0:0] PIONEER DVD-RW DVR-109 8.58 (F:) (ATA) I 10:41:09 Source Media Type: CD-RW (Disc ID: 97m27s00f) I 10:41:09 Source Media Sectors: 53,442 I 10:41:09 Source Media Volume Identifier: ACTIVEBOOTDISK I 10:41:09 Source Media Application Identifier: OSCDIMG 2.45 (10/12/2000 TM) I 10:41:09 Source Media File System(s): ISO9660 (Bootable) I 10:41:09 Destination File: E:\ACTIVEBOOTDISK.ISO I 10:41:09 Destination Free Space: 105,871,228,928 bytes (103,389,872 KB) (100,966 MB) (98 GB) I 10:41:09 Destination File System: NTFS I 10:41:09 File Splitting: Auto I 10:41:09 Reading Sectors... (LBA: 0 - 53441) I 10:42:20 Abort Request Acknowledged E 10:42:20 Failed to Read Sector 53441 - L-EC Uncorrectable Error E 10:42:22 Failed to Read Sectors! E 10:42:22 Operation Aborted! - Duration: 00:01:12 E 10:42:22 Average Read Rate: 1,484 KB/s (9.9x) - Maximum Read Rate: 2,888 KB/s (19.3x) I 10:46:12 Close Request Acknowledged I 10:46:12 Closing Down... I 10:46:12 Shutting down SPTI... I 10:46:12 ImgBurn closed!
I THEN VERIFIED MY RN7.3 ISO W/IMGBURN, AND DECIDED TO VERIFY IMGBURN'S "FAILED" ISO, AND IT VERIFIED JUST FINE!?:
; //****************************************\\ ; ImgBurn Version 2.3.2.0 - Log ; Saturday, 05 January 2008, 10:58:00 ; \\****************************************// ; ; I 10:51:30 ImgBurn Version 2.3.2.0 started! I 10:51:30 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 10:51:30 Total Physical Memory: 1,048,044 KB - Available: 576,880 KB W 10:51:30 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 10:51:30 Initialising SPTI... I 10:51:30 Searching for SCSI / ATAPI devices... I 10:51:31 Found 1 DVD-ROM, 1 DVD±RW and 1 HD DVD-ROM! I 10:52:30 Operation Started! I 10:52:30 Source Device: [1:1:0] TSSTcorp DVD-ROM TS-H352A TS05 (G:) (ATA) I 10:52:30 Source Media Type: CD-ROM I 10:52:30 Image File: E:\ACTIVEBOOT.iso I 10:52:30 Image File Sectors: 53,440 (MODE1/2048) I 10:52:30 Image File Size: 109,445,120 bytes I 10:52:30 Image File Volume Identifier: ACTIVEBOOTDISK I 10:52:30 Image File Application Identifier: OSCDIMG 2.45 (10/12/2000 TM) I 10:52:30 Image File File System(s): ISO9660 (Bootable) I 10:52:30 Verifying Sectors... (LBA: 0 - 53439) I 10:53:53 Device MD5: 943f858047b07f3d52fed5d9b8c81290 I 10:53:53 Image MD5: 943f858047b07f3d52fed5d9b8c81290 I 10:53:53 Operation Successfully Completed! - Duration: 00:01:22 I 10:53:53 Average Verify Rate: 1,303 KB/s (8.7x) - Maximum Verify Rate: 1,496 KB/s (10.0x) I 10:54:08 Operation Started! I 10:54:08 Source Device: [1:1:0] TSSTcorp DVD-ROM TS-H352A TS05 (G:) (ATA) I 10:54:08 Source Media Type: CD-ROM I 10:54:08 Image File: E:\ACTIVEBOOTDISK.ISO I 10:54:08 Image File Sectors: 53,440 (MODE1/2048) I 10:54:08 Image File Size: 109,445,120 bytes I 10:54:08 Image File Volume Identifier: ACTIVEBOOTDISK I 10:54:08 Image File Application Identifier: OSCDIMG 2.45 (10/12/2000 TM) I 10:54:08 Image File File System(s): ISO9660 (Bootable) I 10:54:08 Verifying Sectors... (LBA: 0 - 53439) I 10:55:31 Device MD5: 943f858047b07f3d52fed5d9b8c81290 I 10:55:31 Image MD5: 943f858047b07f3d52fed5d9b8c81290 I 10:55:31 Operation Successfully Completed! - Duration: 00:01:22 I 10:55:31 Average Verify Rate: 1,303 KB/s (8.7x) - Maximum Verify Rate: 1,496 KB/s (10.0x) I 10:58:00 Close Request Acknowledged I 10:58:00 Closing Down... I 10:58:00 Shutting down SPTI... I 10:58:00 ImgBurn closed!
FINALLY I DISABLED ANYDVD AND TRIED AGAIN TO MAKE AN .ISO, BUT FAILED.
; //****************************************\\ ; ImgBurn Version 2.3.2.0 - Log ; Saturday, 05 January 2008, 11:07:08 ; \\****************************************// ; ; I 11:04:42 ImgBurn Version 2.3.2.0 started! I 11:04:42 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 11:04:42 Total Physical Memory: 1,048,044 KB - Available: 522,696 KB W 11:04:42 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 11:04:42 Initialising SPTI... I 11:04:42 Searching for SCSI / ATAPI devices... I 11:04:43 Found 1 DVD-ROM, 1 DVD±RW and 1 HD DVD-ROM! I 11:05:07 Operation Started! I 11:05:07 Source Device: [1:1:0] TSSTcorp DVD-ROM TS-H352A TS05 (G:) (ATA) I 11:05:07 Source Media Type: CD-ROM I 11:05:07 Source Media Sectors: 53,442 I 11:05:07 Source Media Volume Identifier: ACTIVEBOOTDISK I 11:05:07 Source Media Application Identifier: OSCDIMG 2.45 (10/12/2000 TM) I 11:05:07 Source Media File System(s): ISO9660 (Bootable) I 11:05:07 Destination File: D:\ACTIVEBOOTDISK.ISO I 11:05:07 Destination Free Space: 52,118,319,104 bytes (50,896,796 KB) (49,703 MB) (48 GB) I 11:05:07 Destination File System: NTFS I 11:05:07 File Splitting: Auto I 11:05:07 Reading Sectors... (LBA: 0 - 53441) I 11:06:58 Abort Request Acknowledged E 11:06:59 Failed to Read Sector 53440 - Unrecovered Read Error E 11:06:59 Failed to Read Sectors! E 11:06:59 Operation Aborted! - Duration: 00:01:52 E 11:06:59 Average Read Rate: 954 KB/s (6.4x) - Maximum Read Rate: 1,496 KB/s (10.0x) I 11:07:08 Close Request Acknowledged I 11:07:08 Closing Down... I 11:07:08 Shutting down SPTI... I 11:07:08 ImgBurn closed!
-
I think you were just unlucky with that disc.
The drive returned a 'write error' so basically it had the problem, not ImgBurn.
Thanks LUK, that's the answer I was looking for. I knew there was always a chance I'd get a bad disc, but posted the log hoping for someone to "lift the fog".
For the record, while I *am* using Buffalo's firmware for my 109, it is not to my knowledge "hacked" in any way; at least I dl'ed it from their official website...
-
Well, although that's what the packaging says, it also says "compatible w/8x burners" (look here) and apparently 2.4x, 4x, and 6x are commonly expected to work.I think those MKM-001s are, in fact, rated at 2.4x. That's what I burn them at.I can't honestly say what RecordNow records them at (I have *it* set to MAX also) as it doesn't have any sort of logfile or useable progress info (which is why I was attracted to ImgBurn in the first place). Afraid these are too expensive to "experiment" with--I'll stick w/RN7.3 for DL media...
-
Having used ImgBurn successfully with DVD-5s, and liking its log function, I tried today to make a DL backup of a DVD-9 iso (ripped w/our fave ripper
no errors with *it*) and it failed. Two dollar coaster resulted (Verbatims I've had 100% success with in the past). I loaded-up another DL disc and successfully made my copy using my usual RecordNow 7.3.
I suppose I could have found a bad blank, but I looked at it closely w/my lighted magnifying glass and I could see no visual glitches. Here's the log--I think I used all defaults; if anyone can see something that I might have done wrong by all means let me know:
I 11:41:00 ImgBurn Version 2.1.0.0 started!
I 11:41:00 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)
I 11:41:00 Initialising SPTI...
I 11:41:00 Searching for SCSI / ATAPI devices...
I 11:41:00 Found 2 DVD-ROMs and 1 DVD?RW!
I 11:43:41 Operation Started!
I 11:43:41 Source File: D:\CONCERT.MDS
I 11:43:41 Source File Sectors: 3,909,952 (MODE1/2048)
I 11:43:41 Source File Size: 8,007,581,696 bytes
I 11:43:41 Source File Volume Identifier: CONCERT
I 11:43:41 Source File Implementation Identifier: Daikin U.S. Comtec Lab
I 11:43:41 Source File File System(s): ISO9660, UDF (1.02)
I 11:43:41 Destination Device: [1:0:0] PIONEER DVD-RW DVR-109 8.58 (F:) (ATA)
I 11:43:41 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x, 6x)
I 11:43:41 Destination Media Sectors: 4,173,824
I 11:43:41 Write Mode: DVD
I 11:43:41 Write Type: DAO
I 11:43:41 Write Speed: MAX
I 11:43:41 Link Size: Auto
I 11:43:41 Test Mode: No
I 11:43:41 BURN-Proof: Enabled
I 11:43:41 Optimal L0 Data Zone Capacity: 2,021,632
I 11:43:41 Optimal L0 Data Zone Method: Copied From Original Disc
I 11:43:57 Filling Buffer...
I 11:43:59 Writing LeadIn...
I 11:44:09 Writing Image...
I 11:44:09 Writing Layer 0... (LBA: 0 - 2021631)
W 11:44:28 Failed to Write Sectors 71840 - 71871 - Write Error
W 11:44:28 Retrying (1 of 20)...
W 11:44:32 Retry Failed - Invalid Address For Write
W 11:44:32 Retrying (2 of 20)...
W 11:44:32 Retry Failed - Invalid Address For Write
W 11:44:32 Retrying (3 of 20)...
W 11:44:32 Retry Failed - Invalid Address For Write
W 11:44:32 Retrying (4 of 20)...
W 11:44:32 Retry Failed - Invalid Address For Write
W 11:44:32 Retrying (5 of 20)...
W 11:44:32 Retry Failed - Invalid Address For Write
W 11:44:32 Retrying (6 of 20)...
W 11:44:32 Retry Failed - Invalid Address For Write
W 11:44:32 Retrying (7 of 20)...
W 11:44:32 Retry Failed - Invalid Address For Write
W 11:44:32 Retrying (8 of 20)...
W 11:44:32 Retry Failed - Invalid Address For Write
W 11:44:32 Retrying (9 of 20)...
W 11:44:32 Retry Failed - Invalid Address For Write
W 11:44:32 Retrying (10 of 20)...
W 11:44:32 Retry Failed - Invalid Address For Write
W 11:44:32 Retrying (11 of 20)...
W 11:44:32 Retry Failed - Invalid Address For Write
W 11:44:32 Retrying (12 of 20)...
W 11:44:32 Retry Failed - Invalid Address For Write
W 11:44:32 Retrying (13 of 20)...
W 11:44:32 Retry Failed - Invalid Address For Write
W 11:44:32 Retrying (14 of 20)...
W 11:44:32 Retry Failed - Invalid Address For Write
W 11:44:32 Retrying (15 of 20)...
W 11:44:32 Retry Failed - Invalid Address For Write
W 11:44:32 Retrying (16 of 20)...
W 11:44:32 Retry Failed - Invalid Address For Write
W 11:44:32 Retrying (17 of 20)...
W 11:44:32 Retry Failed - Invalid Address For Write
W 11:44:32 Retrying (18 of 20)...
W 11:44:32 Retry Failed - Invalid Address For Write
W 11:44:32 Retrying (19 of 20)...
W 11:44:32 Retry Failed - Invalid Address For Write
W 11:44:32 Retrying (20 of 20)...
W 11:44:32 Retry Failed - Invalid Address For Write
W 11:44:48 Retrying (21)...
W 11:44:48 Retry Failed - Invalid Address For Write
E 11:44:50 Failed to Write Sectors 71840 - 71871 - Write Error
I 11:44:50 Synchronising Cache...
I 11:44:51 Closing Track...
I 11:44:53 Finalising Disc...
W 11:47:42 Potential 'WaitImmediateIO' Deferred Error - (1/2) - Positioning Error Detected by Read of Medium
E 11:47:49 Finalise Disc Failed! - Reason: Positioning Error Detected by Read of Medium
E 11:47:49 Failed to Write Image!
E 11:47:49 Operation Failed! - Duration: 00:04:08
I 11:47:49 Average Write Rate: 3,592 KB/s (2.6x) - Maximum Write Rate: 8,346 KB/s (6.0x)
Largest single file to split-to for DVD+5?
in ImgBurn Support
Posted
Not talking about DVD Video i.e. VIDEO_TS here, but instead very large >4.x High Def transport stream/mpeg2 files, or AVI files where I've made Hi-Def Xvids for example, that exceed the size of a single-layer DVD. I want to split-and-archive them.
If I use exclusively Verbatim MCC-004-00 DVD+Rs, which purport to size-out at 4.7Gb, what should I choose if I want to use a program like HJsplit which asks for Mbytes to split to? Wondering how much "overhead" I should allow for to write the directory info or whatever else the UDF mode needs.
Yeah I know I could start at 4700 and work backward to see what works, but this would be a lot of error-and-trial and I'm hoping someone here already knows the ideal size. Maybe too if others know of a nicer splitter program than HJSplit please let me know.