DiscImageCreator

[sarami]

Attached.

- fixed: checking of the directory record length
https://www.mediafire.com/file/eq80y20l … st.7z/file

[TheMechasaur]

Attached.

- fixed: checking of the directory record length
https://www.mediafire.com/file/eq80y20l … st.7z/file

Both discs dumped successfully. Thx

[max]

There seems to be a fault regarding the new /rr argument: https://github.com/saramibreak/DiscImag … issues/117

[NovaAurora]

Latest DIC produces an unusable multisession .img and data track, tried several mounting tools, data track appears empty in Isobuster.
Alcohol 120 creates a working image. Isobuster dump also fails.
Issue present since at least Nov 2021 build, haven't tested older.

Logs: https://mega.nz/file/bBc2XIrD#6CP-ddLxn … Jl5hj2JtQA

[F1ReB4LL]

Check the last non-zero byte -> Detected in 0x7ad(1965) of LBA 288285 + -1
Check the 1st non-zero byte -> Detected in 0(0) of LBA -75
Non-zero byte position is over the -10,000 samples. Not fix the offset

Does it mean the leadout has non-zero data? If yes, it should change the offset according to the leadout + dump the first pregap separately.

[sarami]

Does it mean the leadout has non-zero data?

No, LBA 288285 is the 1st lead-out sector, therefore "LBA 288285 + -1" indicates the last sector.

[F1ReB4LL]

Does it mean the leadout has non-zero data?

No, LBA 288285 is the 1st lead-out sector, therefore "LBA 288285 + -1" indicates the last sector.

Ok. But, again, if the first pregap is "over the -10,000 samples", why not to dump it separately as Pregap.bin or Track 00.bin?

[sarami]

why not to dump it separately as Pregap.bin or Track 00.bin?

Is there .pre file? If yes, it's the pregap sector of the track 1.

[F1ReB4LL]

why not to dump it separately as Pregap.bin or Track 00.bin?

Is there .pre file? If yes, it's the pregap sector of the track 1.

It's there, but its size is 0 bytes. Plextor Premium was used.

[sarami]

It's there, but its size is 0 bytes.

fixed.
https://www.mediafire.com/file/eq80y20l … st.7z/file