DiscImageCreator

[Savagesteel]

Hello there,

I'm dumping the Diablo 1 shareware PC CD-ROM.
I'm using:

• DiscImageCreator 20200403
• Plextor PX-712A drive
• Windows 10 x64

I dump the disc with the following command:

Code: Select all

C:\Program Files\DiscImageCreator\Release_ANSI\DiscImageCreator.exe cd E .\temp\Diablo-Shareware.bin 8 /c2

I get no C2 errors however in the mainError.txt I get the following error:

Code: Select all

LBA[031892, 0x07c94]: Track[01]: Invalid sync. Skip descrambling

I don't know how to interpret it, can you please advise?

[R00n5t3r]

Transfer length was too large.

Code: Select all

uiDirPos: 341431, TransferLength: 82

Fixed it. Test plz. http://www.mediafire.com/file/eq80y20l9 … st.7z/file

That seems to have done the trick. New logs are enclosed

[sarami]

@R00n5t3r, sadikyo
Thanks. The src was pushed.

I don't know how to interpret it, can you please advise?

All logs are needed and use the latest test version.

[Savagesteel]

@sarami
Thank you for your answer, please find below the link for the logs:
http://www.mediafire.com/file/5446vlhsb … e_logs.zip

I will redump with the test version and also post the logs.

[Savagesteel]

Below the logs with 20200517, I get the same error:
http://www.mediafire.com/file/fnwjb0xr8 … 200517.zip

[sarami]

I get the same error:

This problem can't be fixed now.
Try below.
1. Change the drive speed.
2. Resurface if scratches exist in the disc.
3. Change the disc if possible
4. Change the drive if possible.

[sadikyo]

so, I already submitted this information to DICUI for update, but I wanted to share here also.  I was talking with Enker about the layerbreak information for xbox discs, and apparently people (myself included until I discovered the issue) have been submitted the incorrect layerbreak for xbox discs, when they should essentially all be the same default one. 

Here is what Enker shared with me:

"Hey, yes the DICUI layerbreak for Xbox/Xbox360 (and also Blu-ray discs) is incorrect. It's caused by DIC reporting two layerbreaks, one for the video partition and one for the game partition (DICUI uses this one). It never logs the actual layerbreak that takes into account the video partition+middle zone that comes before the game partition. If you add the video LayerZeroSector + Middle Zone + game LayerZeroSector, then you get the default value on the disc page.

DICUI could omit the layerbreak for Xbox/Xbox360/Blu-ray discs, since we never need to enter one for those discs."

As I said, I've already sent this to DICUI to pull the correct one, but I wanted to share with you as well sarami, in case anything has to be done on the DIC side.

The correct layerbreak is apparently the default of 1913776, and not the 1715632 that often/sometimes gets reported.

[Savagesteel]

1. Change the drive speed.
2. Resurface if scratches exist in the disc.
3. Change the disc if possible
4. Change the drive if possible.

1. I tried with 2x, 4x and 20x and had the same error
2. The disc is in very good condition I cannot see any scratch or damage
3. Yes in the following weeks I will scout ebay to get one and  compare the dumps
4. Unfortunately I don't have a second drive which supports 0xC8 instructions

Also when I dump the disc with IsoBuster and the same Plextor drive the image has the same size but data is different (different hash).
When dumping the disc with IsoBuster and two different drives I get the same image file (same hash).

[sarami]

Also when I dump the disc with IsoBuster and the same Plextor drive the image has the same size but data is different (different hash).
When dumping the disc with IsoBuster and two different drives I get the same image file (same hash).

Perhaps, your disc is no problem.
Try to downgrade the firmware and test DIC with no-firmware-check build. /viewtopic.php?p=25410#p25410

The correct layerbreak

http://www.mediafire.com/file/eq80y20l9 … st.7z/file
Added: output layerbreak to _disc.txt (only xbox or xbox 360)

[F1ReB4LL]

/viewtopic.php?p=55563#p55563 - could you look at it? Why does it have a missing sector (resulting in incorrect lead-in and first pregap sizes)?

Heartbreak Diary also has a weird lead-in size, probably incorrect. And the "Subs indexes" cue is missing its lead-out/lead-in/pregap tags, bug?