Jump to content

_Greg_

Members
  • Content Count

    13
  • Joined

  • Last visited

About _Greg_

  • Rank
    ISF Newbie
  1. _Greg_

    Suggestions

    It can be done over multiple sittings. A common use of IsoPuzzle is to read as much as possible from a single bad disc using multiple different drives. The rip/dump status is stored in an .flg file which allows recovery over multiple sittings. It cannot use existing images since those are not accompanied by any information about what portions were and weren't read successfully from the DVD. 2048-byte sectors read from DVDs don't have checksums, so sector-level error-checking of existing images isn't possible. The A/V streams on the discs may include optional checksums, but that is far beyond the scope of what IsoPuzzle considers. How were the images created in the first place? Are they the full size of the disc, or are they smaller due to aborting the reading process? This info would have an impact on how practical it would be to merge the existing images successfully in the absence of checksums. As far as I remember, you only get the image file from IsoPuzle, no MDS. Is having the discs professionally resurfaced out of the question?
  2. _Greg_

    Suggestions

    There isn't really any swapping out of sectors, just filling in of blanks. IsoPuzzle keeps track of which sectors have and haven't been read successfully as you use it. You would first use the program to create a new image from one of the bad discs. You would then switch to the second disc and the program would try to read the previously unreadable sectors again. If the process is successful, you should have a single good image as the output.
  3. _Greg_

    Suggestions

    IsoPuzzle may be helpful for merging two DVDs into one image if the source discs are identical. ImgBurn can tell you the sector count for a minimal indicator of if the discs are likely to be the same, but IsoBuster (free version) would be more informative. IsoBuster shows the volume timestamp info, sector numbers where files start, and other details. If the DVDs are copy-protected a product such as AnyDVD will be needed as well. IsoPuzzle doesn't do decryption, so something like AnyDVD is needed to ensure that the data is decrypted before IsoPuzzle sees it.
  4. _Greg_

    Automatically Verify after Read?

    It's certainly the case that a properly functioning drive will only return the data from a sector if its integrity has been verified, but there are many points at which corruption can occur after that verification. I've encountered mysterious corruption in a number of different disc images in the past that were eventually traced back to causes including: - A slightly faulty or loose IDE cable in an external drive enclosure - An occasionally malfunctioning USB controller - Failing RAM (very infrequently flipping a single bit, not yet causing any OS/system instability) - Failing memory controller on a CPU (only malfunctioning a few times monthly) Other causes of corruption are of course possible. Corruption caused by intermittent problems is likely to be detected by verifying after reading. I always manually verify after reading to avoid ending up with more bad images, so I would naturally consider an option to automatically verify after reading to be very handy. Such an option would be especially valuable for automatic (robotic) batch/bulk reading since it's more likely that infrequent corruption will show up when tons of data is moving around. Thank you very much for considering this for a future version of ImgBurn.
  5. _Greg_

    Unique Disc Identifier for DVD-R discs

    That would certainly be handy, thank you very much sir.
  6. _Greg_

    Unique Disc Identifier for DVD-R discs

    Thank you very much for the clarification on this and for taking the time to answer all of my questions.
  7. _Greg_

    Unique Disc Identifier for DVD-R discs

    Thank you very much for responding so quickly. Out of curiosity, is there any particular reason that ImgBurn doesn't write the date and time into the UID? The MMC specs suggest that setting the date properly may have an impact on OPC results. Quoting MMC-4 rev. 5a below: This may have changed at some point since MMC-5 and MMC-6 have removed this text. My understanding is that the volume creation date (or for UDF the "recording date and time" field) is part of the file system. The date and time that the burning process begins certainly seems to be what ImgBurn stores there. I have layouts from years ago that are still used today. It makes a big difference that ImgBurn burns the current date and time for each new disc instead of the very inaccurate creation date of the layout/project like Nero did.
  8. While making backup copies of old DVD-R discs I made a point of reading the RMD (Recording Management Data) sectors. For each disc I copied the burner make/model/serial, disc MID, and the UID (Unique Disc Identifier) into a text file. Since the UID is supposed to contain the date and time that the disc was burned, I decided to set the modified date for that text file to match the disc's burn date and time. This makes it easy to search and sort disc images by their burn dates which can be quite handy. Most of the discs burned with various versions of Nero have the correct date+time in the UID. This is important since Nero burned the layout creation date, not the burn date, to the file system (at least for ISO+Joliet layouts). Some versions of Nero had problems with the UID though. One version I used made the month in the UID one month before the actual burn date. A later version unconditionally set the date and time as September 18th, 2003 @ 19:00:00. For all of the DVD-R discs that I burned with ImgBurn, the date and time fields of the UID are all set to 0. This is generally fine since ImgBurn writes the burn date into the file system. However, when burning a disc from an image there is no record of the burn date and time since only the original dates/times in the file system are placed onto the disc. Is there currently any way to use ImgBurn to set the contents of the UID? I'm interested in being able to set the burn date and time as defined in the MMC specs. Additionally, I'm interested in being able to set the UID to other values such as the date/time stored in an image's file system and the date/time stored in a backup of RMD sectors (16-sector / 32KB block). Thanks ahead for your reponse and thoughts on this.
  9. I also wouldn't mind seeing a feature like this. It is probably not possible in many cases to generate the parity data in real-time during the burning process, but the single build-adding-parity process described by geno would be quite useful. In cases where sufficient disc capacity is available, it may be simplest to calculate RS codes on a frame-by-frame (32KB) basis and then span each byte of the codes across different frames (so that loss of a frame minimizes the loss of ECC data for another particular frame). This would probably work well for discs with scratches or scuffs not covering the majority of the surface. Burned discs tend to go bad from the outside-in, but some go bad from other areas first. For that issue, the user could opt to specify a general preference for where the ECC data goes into the ISO relative to the data. The ECC data could be ordered different ways from sequentially (to match the order of the corresponding frames) to random (to attempt to maximize the probability that at least some ECC data will be readable). Of course, this could all be made a hell of a lot more efficient and useful if standard drive firmware weren't rigged to disallow reading of data from bad frames on DVDs.
  10. Wow, that was quite the prompt and positive response. Don't think you can buy service that good these days. Thank you very much.
  11. I would certainly appreciate it, thanks. I know, I could probably just try to be more careful where I click, but when in a rush that isn't always possible. I can't be the only person this happens to though since Nero has supported hiding/disabling the shutdown checkbox for at least a few major versions now. Thanks for all the prompt replies.
  12. blutach: Thanks for responding, but the existing options you referred to do not do what I am asking about. Under the "Tools --> Settings --> General" tab there is only the ability to enable/disable the 'Shutdown' window when a shutdown event is triggered and to change the shutdown action. The option under the "Tools --> Settings --> Read/Write/Verify" tabs only sets the default selection of the Shutdown checkbox during a verify operation. It does not disallow clicking on the checkbox I am looking for the ability to do one of the following so that I can't click on the shutdown checkbox by accident: - Block the shutdown checkbox from appearing completely during a read/write/verify operation (as is possible in Nero) - Gray out the shutdown checkbox for make it impossible to accidentally click on it during a read/write/verify operation - Change the shutdown action to "None" or "Close ImgBurn" or something else that won't have an impact on the rest of the system. Thanks again. Greg
  13. Can you please add the ability to disable the "Shutdown Computer" checkbox, or at least add "None" as a shutdown action? I have a bad tendency to not notice where I'm clicking sometimes, and it's a nightmare when I accidentally hit that checkbox right before heading out the door and don't realize it until later. Thank you. - Greg -
×

Important Information

By using this site, you agree to our Terms of Use.