speed47 / dvdisaster Goto Github PK

Hi, I'm completely new to this program; usually I would just use things like ImgBurn to save iso, but considering I have a lot of pretty old disc (not CD-R mind you, CD-ROM purchased ages ago--already into the "cross-finger it's still readable" territory admittedly) I found this program along with CDCheck so I thought to use this to check them out and get them into iso before they rot completely.

But it seems there is a severe bug I encountered with the last "stable" version for Windows (0.72.3pl3 that's accessible from the dead official website on the Wayback Machine archive) that seems to still be present in your latest 0.79.6pl7: a typical 700MB CD-ROM was read using the Linear strategy with all sector reported readable (all green) and the curve looking smooth and no C2 error reported, yet there are many files in the resulting ISO image that have the correct size but are unreadable; you can't open them when you mount the iso nor can you even copy them to the hard drive--Windows report them with a "Invalid MS-DOS function" error. A lot of those files don't seem to be corrupt as you can open/copy them from the disc still fine. So essentially the image made is useless. (now maybe there's thing regarding copy protection? on some disc I think, but I don't think that's the issue here as these are not some commonly bootlegged movies and big-named softwares)

Now I think some of my disc are not that dead yet so I can reimage them, but CDCheck don't make the iso while reading the disc so I'd basically be flying blind if I make a image now with Imgburn and the like (or plain copying out the files).

Personally I think this should be given the highest priority for investigation (so perhaps drop all other issues for the time being) as I think this may even affect the reputation of this program (not sure if the ecc are based on the image but it does seem like there is a connection on first thought); honestly I think if this were a commercial program there's likelihood ground for legal action even if it's a bug and not just me the user not setting the program correctly--it's this serious as data integrity seems to be compromised here, for who know how long and how many users as the last "stable" version was released ages ago.

If you need any log or such I might be able to help, but I can't use Linux and have no software development knowledge whatsoever so request have to be made with how-to-guidance if you want any settings changes for testing.

Hi,

when I tried to start the Appimage of v0.79.10-pl3 on Ubuntu 24.04 (dvdisaster worked in previous Ubuntu versions) I get the following error message:

Gtk-Message: Failed to load module "appmenu-gtk-module" Gtk-Message: Failed to load module "atk-bridge" /tmp/.mount_dvdisaJunE6x/usr/bin/dvdisaster: symbol lookup error: /usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libgail.so: undefined symbol: g_once_init_enter_pointer

Best wishes

I used the latest release version (0.79.6 patchlevel 8).

I checked the work of this program on CD-R before the clean recording and found out that the RS03 algorithm does not give full recovery for any damage (even small).

I have a CD-R 703 MB with 80% fullness was supplemented to 701 MB with 22.6% redundancy (47 roots) using the RS03 algorithm.

After that, on the working surface of the disc, I draw a small red circle with a disc marker.
The program cannot read some of the information and is forced to restore the image using ECC.

In this case, 94.9% of all sectors were successfully read. The "corruption" was in the middle of the disk, before the start of the ECC segment (I suppose), so the restore should have returned the entire image to me.
However, the data was not fully recovered!

Only 19393 sectors were damaged, but only 92.5% were recovered as a result. Redundancy - 20% of all disk space. Ultimately, 1449 sectors were not rebuilt. Because of this, I did not receive all the information that was originally recorded. Why weren't the mistakes corrected? (I assume this is a software bug.)

A software problem is also hinted at by the error correction graph (attached).
Oddly enough, recovery errors are spike-shaped and repeat at roughly equal intervals.

Please consider porting the GUI to a different toolkit. GTK 2 is end of life and Debian wants to get rid of it. The successors are GTK 3 and GTK 4.

Hi, I was wondering what it would take to make dvdisaster work on macOS.

I managed to compile it on macOS Big Sur 11.61 with a single hack (add a return; on line 103 of src/show-manual.c) to resolve this error:

src/show-manual.c: In function 'GuiShowURL':
src/show-manual.c:112:13: warning: implicit declaration of function 'pipe2'; did you mean 'pipe'? [-Wimplicit-function-declaration]
  112 |    result = pipe2(err_pipe, O_CLOEXEC);
      |             ^~~~~
      |             pipe
src/show-manual.c: At top level:
cc1: note: unrecognized command-line option '-Wno-unknown-warning-option' may have been intended to silence earlier diagnostics
Linking  : dvdisaster
Undefined symbols for architecture x86_64:
  "_pipe2", referenced from:
      _GuiShowURL in show-manual.o
ld: symbol(s) not found for architecture x86_64
collect2: error: ld returned 1 exit status
make: *** [dvdisaster] Error 1

I configured and compiled with:

./configure CC=gcc-11
make -j CC=gcc-11

This resulted in a seemingly functional GUI, but with "No drives found":

Is it just missing the drive detection code for macOS, or are there other issues that you know of that make macOS support problematic?

I assume that the main reason to drop macOS support is that you could not support and test it, because you do not have a mac? Would you be willing to accept a PR that fixes the macOS support?

I can perhaps try to do it if I find the time and it turns out to be not too hard. Do you happen to have some pointers where to look?

Created a disk using version 0.79.5 (from the default repos in ubuntu 22.04 LTS)

scaning the disk and verifying the .iso file works fine on version 0.79.6 on windows 10

However using version 0.79.10 on windows 10 gives errors

This version of dvdisaster 0.79.10 cannot read any disk from my drive (Windows 10 x64). Just get error INQUIRY failed. Something is wrong with drive D:.. Official dvdisaster 0.72 pl3 works no issues.

Hi, first thank you for reviving this project :)
Today to test it, I tried to create an rs03 augmented image.

But after burning it with ImgBurn and re-read the disc with dvdisaster I found that it can't see the augmented part.

0.79.6pl4 :

0.79.6pl4 : (Recover RS03 headers enable)

Is this behaviour normal ?

on a side note with a blank cd I get this :

(The old version) :

ps: that it is the same thing with RS02 and this version.
on 0.72 the RS02 disc is detected without changing settings.

Again thank you for the git.

Hi, I am getting an error when trying to run the app image:

/tmp/.mount_dvdisaGUl8Qd/usr/bin/dvdisaster: symbol lookup error: /usr/lib/libgio-2.0.so.0: undefined symbol: g_module_open_full

Can you help please?

I am using Dvdisaster on Windows with a Pioneer BD-RW BDR-XD08 drive. I burned a BDXL 100GB disk using ImgBurn, based on an ISO generated by dvdisaster.

After burning, this disk shows up properly in windows containing all the files I expect it to. However, trying to verify the ECC data on disk using the "Scan" option from dvdisaster simply hangs, without reading anything from disk. Clicking "stop" at this point results in no change either, the program hanging.

Please see the log from verbose mode listed below:

09f0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0a00: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0a10: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0a20: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0a30: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0a40: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0a50: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0a60: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0a70: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0a80: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0a90: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0aa0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0ab0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0ac0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0ad0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0ae0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0af0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0b00: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0b10: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0b20: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0b30: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0b40: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0b50: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0b60: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0b70: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0b80: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0b90: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0ba0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0bb0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0bc0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0bd0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0be0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0bf0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0c00: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0c10: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0c20: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0c30: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0c40: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0c50: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0c60: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0c70: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0c80: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0c90: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0ca0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0cb0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0cc0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0cd0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0ce0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0cf0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0d00: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0d10: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0d20: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0d30: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0d40: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0d50: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0d60: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0d70: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0d80: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0d90: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0da0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0db0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0dc0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0dd0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0de0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0df0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0e00: 00 00 00 00 45 42 01 00  00 00 00 00 ff ff ff ff  ....EB.. ........ 
0e10: ff ff ff ff 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0e20: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0e30: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0e40: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0e50: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0e60: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0e70: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0e80: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0e90: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0ea0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0eb0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0ec0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0ed0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0ee0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0ef0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0f00: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0f10: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0f20: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0f30: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0f40: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0f50: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0f60: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0f70: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0f80: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0f90: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0fa0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0fb0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0fc0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0fd0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0fe0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
0ff0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........ 
1000: 00 00 00 00                                       ....
#BD: BD medium successfully probed, type BD-R
# query_type() returned.
# deciding reading strategy...
Using READ(10).
GetImageFingerprint(16): read & cached

ExamineUDF(Device: PIONEER BD-RW BDR-XD08 1.02)
 Examining the ISO file system...
  Sector 16:
   Volume descriptor type    = 1
   Volume descriptor version = 1
   Standard identifier       = CD001
   -> primary volume descriptor:
    System identifier         : |LINUX                           |
    Volume identifier         : |Sony Handycam                   |
    Volume space size         : 32761665 sectors
    Volume set size           : 1
    Volume sequence size      : 1
    Logical block size        : 2048
    Path table size           : 1620 bytes
    L-Path table location     : 21
    Opt L-Path table location : 0
    M-Path table location     : 23
    Opt M-Path table location : 0
    Volume creation date/time : 15-02-2024 17:28:45.01
    Volume modification d/t   : 15-02-2024 17:28:45.01
    Volume expiration d/t     : 00-00-0000 00:00:00.00
    Volume effective d/t      : 15-02-2024 17:28:45.01
    File structure version    : 1
  Sector 17:
   Volume descriptor type    = 2
   Volume descriptor version = 2
   Standard identifier       = CD001
   -> supplementary volume descriptor: *skipped*
  Sector 18:
   Volume descriptor type    = 2
   Volume descriptor version = 1
   Standard identifier       = CD001
   -> supplementary volume descriptor: *skipped*
  Sector 19:
   Volume descriptor type    = 255
   Volume descriptor version = 1
   Standard identifier       = CD001
   -> volume descriptor set terminator;
      end of ISO file system parsing.
 Examining the UDF file system...
  not yet implemented.

# *** read_capacity(PIONEER BD-RW BDR-XD08 1.02) ***
 -> 47305567
ExamineECC() started
...trying RS01
...trying RS02
RS02Recognize: medium D:
try_sector: trying sector 32761665
try_sector: no cookie, skipping current modulo
try_sector: trying sector 32761515
try_sector: read error, trying next header
RS02Recognize: skipping exhaustive RS02 search
...trying RS03
RS03RecognizeImage: medium D:
FindRS03HeaderInImage: medium D:
FindRS03HeaderInImage(): Header found at pos +0
...augmented image found
# Calling query_size()
# *** query_size(PIONEER BD-RW BDR-XD08 1.02) ***
Medium size obtained from ECC header: 47305560 sectors
# returned: 47305560 sectors
Medium "Sony Handycam": BD-R, 47305560 sectors, Ecc, created 15-02-2024, Manuf.-ID: VERBAT,IMk.

Scanning medium for read errors.
Reading CRC information from ecc data (RS03) ... Calculated layout for RS03 image:
data sectors      = 32761665
data padding      = 73957
layer size        = 185512
total sectors     = 47305560
medium capacity   = 0
header position   = 32761665
first CRC sector  = 32835624
first ECC sector  = 33021136
ndata             = 178
nroots            = 77 (43.3%)

Is there any technical possibility for this program to also fix C2 errors in sectors? I mean errors caused by the degradation of the medium. I rip a lot of game discs and I care about the highest image quality of the ripped disc
It's also nice if the program detects copy protection that deliberately damages some sectors (SafeDisc, Bitpool, LaserLock, Ring PROTECH etc), thanks to which it would be possible to save copy-protected game discs

I tried to recover a Video CD with dvdisaster and scanning marked all sectors as "illegal request: illegal mode for this track". I thought it's the disc is beyond repair in the first place, but after I tried another completely fine Video CD, it still reports all of its sectors as illegal requests.

So is Video CD being supported by dvdiaster ? If not, what makes Video CDs different than data CDs ?

OS: Windows 10
Version: v0.79.10-pl2

Settings:

With these settings, dvdisaster-enhanced .iso files consistently fail the "Verify" step before burning to disk on my end. I originally noticed this after burning a full BDXL and trying to verify the re-read iso and narrowed it down a bit.

To reproduce:

1. Create a small image .iso (I had about 170 MB with various files)
2. Use above settings to embed ECC info
3. Run "Verify" on this new image immediately. The result in my case was:
   

Workaround:
Set I/O method to read/write again

Hi all.

I understand that dvdisaster works by augmenting an image with error correction data, which is meant to be burned on the disc all at once.

I was wondering if this approach could be extended to work also on a multi-session disc, i.e., you write a first session made of the data and its error correction data, then later add further sessions of the same kind until the disc is full.

In this way, a single disc could be used as storage for an automatically backup system, which would, for example, add new data daily until the disc becomes full.

Is this "theoretically" possible?

Thanks,
Giovanni

Minnor issue, but the app image icon wont present on taskbars etc with Linux Mint for example.

If the icon file could be posted here to manaully overide It would be apprachated as this is the only possible work around I've found so far.

Hello!
I have a question about dvdisaster behaviour in the presence of unrecoverable/ skipped errors.

Let's suppose the data in disc is as follows:

Data Legend: O -> Ok B -> Bad (skipped / unrecoverable)

    ID: 0 1 2 3 4
Data: O O B B O

Does dvdisaster will recover that the following way:

ID: 0 1 2 3 4
Data: O O B B O

respecting the original structure of the data.

Or will it won't write bad sectors, having the data this way:

    ID: 0 1  4
Data: O O O

I ask this because I need data to be exactly aligned as I written them to use par2 correctly and recover that data.
I wasn't aware of dvdisaster tool at the time and used par2 on this data.

I have a couple of problems.
The first problem is that all my internal SATA drives are not visible in the program (Under W10) but the internal drives are correctly recognized by other burning or ripping programs. All USB drives are recognized.
The second is the incorrect BD "automatic" RS03 Disc size. (With RS02 I can select a correct size manually)
For example if I have a 25GB BD with:
Free Sectors: 12.219.392
Free Space: 25.025.314.816 bytes
the program generate only a 11.776.657 sectors ISO, basically wasting about 805MB of free space on disc. There is a fix for that?

Difference in size:

Not tried yet with BD50-100-128GB to check if size is also not correct.
Tried with BD 50, same problem, it uses the "default" sector number. So now the image is 1803MiB smaller from the top "preview" and in the end 1451MiB smaller with final files.

For reference the numbers I have with all my bluray are:

BD25:
Free Sectors: 12.219.392
Free Space: 25.025.314.816 bytes
(default dvdisaster sector value 11826176)

BD50:
Sectors: 24.438.784
Size: 50.050.629.632 bytes
(default dvdisaster sector value 23652352)

BD100:
Sectors: 48.878.592
Size: 100.103.356.416 bytes
(default dvdisaster sector value 47305728)

BD128:
Free Sectors: 62.500.864
Free Space: 128.001.769.472 bytes
(default dvdisaster sector value 60403712)

The only BD128 ever in production is SONY-NQ1-001 (found in 3 packages: Optical disk Archive, Consumer 25 cakebox and Enterprise 25 cakebox all with the same Disc/Media ID)

Thank you

I want to build a server to rip my blu-ray iso(s) which is headless and have no cd drive. And for some reason I can't use "mount" command to mount iso, and I found a lot of archive software but they all broke on my iso. Can you add a extract feature that users can get files directly?

When calculating the RS03 layout, dvdisaster tries to find the smallest medium size that will result in at least 8 roots. However, even if the --no-bdr-defect-management CLI flag is specified, the function RS03Layout *CalcRS03Layout(Image *image, int target) still performs its checks using defect-management-enabled medium sizes:

However, I'm not sure whether this is a bug or intended behavior, as I know that using a redundancy lower than 20% triggers a warning message anyway, so maybe these redundancies of ~6.25% are too small to be useful anyway?

I'm trying to recover some HD DVDs. But unfortunately it only reports "Drive failed to report media type."
Yes, the disc is recognized by the drive and parts can be read normally using file copy.

Is there any way to support HD DVDs? Should be very similar to BDs.

.

Hi

I have latest macOS Sonoma 14.3 (Apple M1)
The macOS build doesn't open. I have also tried the CLionly build, same message

I have also tried launching the executable in the macOS folder of the .app, and the same message.

Currently, you're unable to set the ECC redundancy percentage when using RS03 in image mode. In image mode, dvdisaster seems to default to 200% redundancy which is unable to be changed. It'd be useful to be able to change this in image mode for when you're just creating an image you're not going to write immediately (or are preparing an image for other types of media).

Salut Stéphane,

I just wanted to thank you for reviving dvdisaster. It's been an invaluable tool for me in the past and will sure be in the BD-R era.

I just realized it was dropped from Debian Testing for being unfit for GCC 10. Are you planning to point the maintainers to your repository so it will be part of Bullseye again? Is there any contact with Carsten Gnörlich or any info on why he abandoned dvdisaster without making sure someone else cares about the "official" branch?

Best,
Flössie