1,126

Re: DiscImageCreator

Any news regarding my PM about broken C2 errors rereading?

To others: if there were sector rereadings, the image is probably broken, even if DIC reports all the errors were fixed.

1,127

Re: DiscImageCreator

darksabre76 wrote:

Unfortunately, most of the logs didn't actually write out with this error, so I should have just attached the minimal set the first time... But what I got out of it, is attached here. The disc dump (that is clean) doesn't match either of the 2 existing ones, sadly, so I can't use them as baselines to compare against.

Thanks.
It looks like that the directory size of the 200204 is incorrect because 1st directory record of the next sector shows current directory. Please try the latest test version.

F1ReB4LL wrote:

Any news regarding my PM about broken C2 errors rereading?

I sent a PM to A Murder of Crows to Oct. 2, but he doesn't login for a while.

LBA[007154, 0x01bf2]: BytePos[16826208-16828559, 0x100bf60-0x100c88f] C2 error exists. Error byte num: 299
LBA[007155, 0x01bf3]: BytePos[16828560-16830911, 0x100c890-0x100d1bf] C2 error exists. Error byte num: 317
LBA[007302, 0x01c86]: BytePos[17174304-17176655, 0x1060f20-0x106184f] C2 error exists. Error byte num: 261
LBA[007303, 0x01c87]: BytePos[17176656-17179007, 0x1061850-0x106217f] C2 error exists. Error byte num: 259
LBA[007322, 0x01c9a]: BytePos[17221344-17223695, 0x106c6e0-0x106d00f] C2 error exists. Error byte num: 468
LBA[007323, 0x01c9b]: BytePos[17223696-17226047, 0x106d010-0x106d93f] C2 error exists. Error byte num: 216
LBA[007371, 0x01ccb]: BytePos[17336592-17338943, 0x1088910-0x108923f] C2 error exists. Error byte num: 1032
LBA[007372, 0x01ccc]: BytePos[17338944-17341295, 0x1089240-0x1089b6f] C2 error exists. Error byte num: 324
LBA[007391, 0x01cdf]: BytePos[17383632-17385983, 0x10940d0-0x10949ff] C2 error exists. Error byte num: 472
LBA[007392, 0x01ce0]: BytePos[17385984-17388335, 0x1094a00-0x109532f] C2 error exists. Error byte num: 408
LBA[007401, 0x01ce9]: BytePos[17407152-17409503, 0x1099cb0-0x109a5df] C2 error exists. Error byte num: 708
LBA[007402, 0x01cea]: BytePos[17409504-17411855, 0x109a5e0-0x109af0f] C2 error exists. Error byte num: 484
LBA[007421, 0x01cfd]: BytePos[17454192-17456543, 0x10a5470-0x10a5d9f] C2 error exists. Error byte num: 197
LBA[007460, 0x01d24]: BytePos[17545920-17548271, 0x10bbac0-0x10bc3ef] C2 error exists. Error byte num: 263
LBA[007461, 0x01d25]: BytePos[17548272-17550623, 0x10bc3f0-0x10bcd1f] C2 error exists. Error byte num: 281
LBA[007480, 0x01d38]: BytePos[17592960-17595311, 0x10c7280-0x10c7baf] C2 error exists. Error byte num: 299
LBA[007481, 0x01d39]: BytePos[17595312-17597663, 0x10c7bb0-0x10c84df] C2 error exists. Error byte num: 125
LBA[007500, 0x01d4c]: BytePos[17640000-17642351, 0x10d2a40-0x10d336f] C2 error exists. Error byte num: 100
LBA[007509, 0x01d55]: BytePos[17661168-17663519, 0x10d7cf0-0x10d861f] C2 error exists. Error byte num: 10
LBA[007510, 0x01d56]: BytePos[17663520-17665871, 0x10d8620-0x10d8f4f] C2 error exists. Error byte num: 90
LBA[007539, 0x01d73]: BytePos[17731728-17734079, 0x10e9090-0x10e99bf] C2 error exists. Error byte num: 264
LBA[007559, 0x01d87]: BytePos[17778768-17781119, 0x10f4850-0x10f517f] C2 error exists. Error byte num: 489
LBA[007560, 0x01d88]: BytePos[17781120-17783471, 0x10f5180-0x10f5aaf] C2 error exists. Error byte num: 415
LBA[007727, 0x01e2f]: BytePos[18173904-18176255, 0x1154fd0-0x11558ff] C2 error exists. Error byte num: 211
LBA[007728, 0x01e30]: BytePos[18176256-18178607, 0x1155900-0x115622f] C2 error exists. Error byte num: 213
LBA[007767, 0x01e57]: BytePos[18267984-18270335, 0x116bf50-0x116c87f] C2 error exists. Error byte num: 522
LBA[007768, 0x01e58]: BytePos[18270336-18272687, 0x116c880-0x116d1af] C2 error exists. Error byte num: 118
LBA[007856, 0x01eb0]: BytePos[18477312-18479663, 0x119f100-0x119fa2f] C2 error exists. Error byte num: 80
LBA[007857, 0x01eb1]: BytePos[18479664-18482015, 0x119fa30-0x11a035f] C2 error exists. Error byte num: 20
LBA[007925, 0x01ef5]: BytePos[18639600-18641951, 0x11c6af0-0x11c741f] C2 error exists. Error byte num: 43
LBA[007926, 0x01ef6]: BytePos[18641952-18644303, 0x11c7420-0x11c7d4f] C2 error exists. Error byte num: 53
LBA[007955, 0x01f13]: BytePos[18710160-18712511, 0x11d7e90-0x11d87bf] C2 error exists. Error byte num: 527
LBA[007956, 0x01f14]: BytePos[18712512-18714863, 0x11d87c0-0x11d90ef] C2 error exists. Error byte num: 401
LBA[008342, 0x02096]: BytePos[19620384-19622735, 0x12b6220-0x12b6b4f] C2 error exists. Error byte num: 50
LBA[008343, 0x02097]: BytePos[19622736-19625087, 0x12b6b50-0x12b747f] C2 error exists. Error byte num: 15
LBA[008362, 0x020aa]: BytePos[19667424-19669775, 0x12c19e0-0x12c230f] C2 error exists. Error byte num: 85
LBA[008363, 0x020ab]: BytePos[19669776-19672127, 0x12c2310-0x12c2c3f] C2 error exists. Error byte num: 15
LBA[007153, 0x01bf1]: C2 error doesn't exist. Next check 2352 byte.
LBA[007154, 0x01bf2]: C2 error doesn't exist. Next check 2352 byte.
LBA[007155, 0x01bf3]: C2 error doesn't exist. Next check 2352 byte.
LBA[007301, 0x01c85]: C2 error doesn't exist. Next check 2352 byte.
LBA[007302, 0x01c86]: C2 error doesn't exist. Next check 2352 byte.
LBA[007303, 0x01c87]: C2 error doesn't exist. Next check 2352 byte.
LBA[007321, 0x01c99]: C2 error doesn't exist. Next check 2352 byte.
LBA[007322, 0x01c9a]: C2 error doesn't exist. Next check 2352 byte.
LBA[007323, 0x01c9b]: BytePos[17223696-17226047, 0x106d010-0x106d93f] C2 error exists. Error byte num: 70
LBA[007370, 0x01cca]: C2 error doesn't exist. Next check 2352 byte.
LBA[007371, 0x01ccb]: BytePos[17336592-17338943, 0x1088910-0x108923f] C2 error exists. Error byte num: 1032
LBA[007372, 0x01ccc]: BytePos[17338944-17341295, 0x1089240-0x1089b6f] C2 error exists. Error byte num: 324
LBA[007390, 0x01cde]: C2 error doesn't exist. Next check 2352 byte.
LBA[007391, 0x01cdf]: C2 error doesn't exist. Next check 2352 byte.
LBA[007392, 0x01ce0]: BytePos[17385984-17388335, 0x1094a00-0x109532f] C2 error exists. Error byte num: 387
LBA[007400, 0x01ce8]: C2 error doesn't exist. Next check 2352 byte.
LBA[007401, 0x01ce9]: BytePos[17407152-17409503, 0x1099cb0-0x109a5df] C2 error exists. Error byte num: 348
LBA[007402, 0x01cea]: C2 error doesn't exist. Next check 2352 byte.
LBA[007420, 0x01cfc]: C2 error doesn't exist. Next check 2352 byte.
LBA[007421, 0x01cfd]: C2 error doesn't exist. Next check 2352 byte.
LBA[007459, 0x01d23]: C2 error doesn't exist. Next check 2352 byte.
LBA[007460, 0x01d24]: C2 error doesn't exist. Next check 2352 byte.
LBA[007461, 0x01d25]: BytePos[17548272-17550623, 0x10bc3f0-0x10bcd1f] C2 error exists. Error byte num: 49
LBA[007479, 0x01d37]: C2 error doesn't exist. Next check 2352 byte.
LBA[007480, 0x01d38]: C2 error doesn't exist. Next check 2352 byte.
LBA[007481, 0x01d39]: C2 error doesn't exist. Next check 2352 byte.
LBA[007499, 0x01d4b]: C2 error doesn't exist. Next check 2352 byte.
LBA[007500, 0x01d4c]: C2 error doesn't exist. Next check 2352 byte.
LBA[007508, 0x01d54]: C2 error doesn't exist. Next check 2352 byte.
LBA[007509, 0x01d55]: BytePos[17661168-17663519, 0x10d7cf0-0x10d861f] C2 error exists. Error byte num: 60
LBA[007510, 0x01d56]: BytePos[17663520-17665871, 0x10d8620-0x10d8f4f] C2 error exists. Error byte num: 516
LBA[007538, 0x01d72]: C2 error doesn't exist. Next check 2352 byte.
LBA[007539, 0x01d73]: BytePos[17731728-17734079, 0x10e9090-0x10e99bf] C2 error exists. Error byte num: 540
LBA[007153, 0x01bf1]: BytePos[16823856-16826207, 0x100b630-0x100bf5f] Reread data matched. Rewrote from [16822848, 0x100b240] to [16825199, 0x100bb6f]
LBA[007154, 0x01bf2]: BytePos[16826208-16828559, 0x100bf60-0x100c88f] Reread data matched. Rewrote from [16825200, 0x100bb70] to [16827551, 0x100c49f]
LBA[007155, 0x01bf3]: BytePos[16828560-16830911, 0x100c890-0x100d1bf] Reread data matched. Rewrote from [16827552, 0x100c4a0] to [16829903, 0x100cdcf]
LBA[007301, 0x01c85]: C2 error doesn't exist. But byte doesn't match
LBA[007302, 0x01c86]: BytePos[17174304-17176655, 0x1060f20-0x106184f] C2 error exists. Error byte num: 648
LBA[007303, 0x01c87]: BytePos[17176656-17179007, 0x1061850-0x106217f] C2 error exists. Error byte num: 768
LBA[007301, 0x01c85]: C2 error doesn't exist. Next check 2352 byte.
LBA[007302, 0x01c86]: C2 error doesn't exist. Next check 2352 byte.
LBA[007303, 0x01c87]: BytePos[17176656-17179007, 0x1061850-0x106217f] C2 error exists. Error byte num: 768
C2 errors was fixed at all
But please dump at least twice (if possible, using different drives)

It clearly looks like that there is little number of the reading times, but in case of my bad condition disc, reading times was correct. I don't know why now.

1,128

Re: DiscImageCreator

Not many rereadings is OK, because the disc isn't heavily damaged, a few rereadings is enough. The question is why the final dump is bad.

Re: DiscImageCreator

sarami wrote:

It looks like that the directory size of the 200204 is incorrect because 1st directory record of the next sector shows current directory. Please try the latest test version.

Running the newest version, it gets to the same "Reading DirectoryRecord 34/ 68" and just cycles forever. It appears to be using both CPU and a lot of hard drive time. I left it running for about 15 minutes at that state, and managed to create a 19.5GB text file for "SimCity 3000 (USA)_volDesc.txt". Using glogg to open it, the last few billion lines (slight hyperbole) they all say the same thing:

Direcory record size of the prev sector maybe incorrect. Skip reading this sector
========== LBA[200205, 0x30e0d]: Directory Record ==========

I can't exactly compress this in a reasonable way and upload unfortunately.

1,130 (edited by user7 2017-10-08 21:22:39)

Re: DiscImageCreator

PS2 DVDs not generating hash.


[F:OutputHash][L:303] GetLastError: 2, The system cannot find the file specified.


Nothing in the .dat file. Is this fixable? I plan to update the guide pointing people to HashCalc if there's no solution right now.

1,131 (edited by sarami 2017-10-10 00:17:18)

Re: DiscImageCreator

dic
*2017-10-10
- changed: /r option is used only by data command
- changed: /raw option is used only by the multi-session disc
- changed: Enable multiple execution
- fixed: Getting the subchannel offsets (Resident Evil 2 Disc 2 (Eu))
- fixed: Descrambling from 00:01:00 to 00:01:74 when used /p option
- fixed: GMT of the CD log, UTC of the DVD log
- improved: Checking argument (cd, dvd)
- improved: Reading directory record (SimCity 3000 (USA))
- improved: Reading DVD structure

todo
http://forum.redump.org/post/56424/#p56424
http://forum.redump.org/post/56473/#p56473

EccEdc
*2017-10-10
added: Write MSF
added: Distinguish between zero sync and zero sync of the pregap sector

Re: DiscImageCreator

sarami wrote:

Fixed.

Confirmed fixed on my end. Thank you very much sarami!

1,133 (edited by reentrant 2017-10-20 18:48:47)

Re: DiscImageCreator

Sarami it looks like DIC after removal of /rc doesn't pick up SmartE or possibly VOB (/ss doesn't help):
http://forum.redump.org/topic/16532/ibm … um-issues/

Could you have a look at it plz?

1,134

Re: DiscImageCreator

I can confirm that SmartE wont be detected. I had to dump those discs using CDM.

1,135 (edited by sarami 2017-10-29 16:40:44)

Re: DiscImageCreator

Deleted?

usurper wrote:

I can confirm that SmartE wont be detected.

Please log. My smartE disc has 00002.tmp in disc and dic judges whether this file exists or not.

Detected [00002.tmp], Skip error from 979 to 1000

Re: DiscImageCreator

Trying to dump a new disc not in redump's db. Star Wars - Jedi Knight II - Jedi Outcast (USA) published by Cosmi Software. Purchased brand new.

Picture's of disc & DIC logs: https://mega.nz/#F!UP4wCJgK!4BcBoGTomFMnzuK4123Sxg

Think disc is bad but want to double check its not some kind of protection.

Was able to install & play. Tried to dump with DIC and getting c2 errors before aborts with

Created img (LBA)  76513/350592[F:ProcessReadCD][L:1489] GetLastError: 121, The semaphore timeout period has expired.

Please wait for 40000 milliseconds until the device is returned

Tried with command "DiscImageCreator.exe cd J: game.bin 2 /c2" & "DiscImageCreator.exe cd J: game.bin 2 /sf /c2 3 /d8 /ns /s 2" 2nd command found "Detected intentional subchannel in LBA -1 => SecuROM Type4 (a.k.a. NEW)" but no other program I tried found any protection, just disc is overburned (824,594,736 bytes).

Other programes that I tried to dump disc are:
Alcohol 120 (found no protection, so used default copy option) - 0 errors per edccchk-v1.26-win32
CloneCD with recommended settings - 3486 errors
CdManipulator with recommended settings - 2176 errors.

1,137 (edited by sarami 2017-10-29 16:43:07)

Re: DiscImageCreator

antimatter wrote:

"Detected intentional subchannel in LBA -1 => SecuROM Type4 (a.k.a. NEW)" but no other program I tried found any protection, just disc is overburned (824,594,736 bytes).

This is misdetection. I'll fix it if possible.

antimatter wrote:

The semaphore timeout period has expired.

I don't know now why this error occurred.


EDIT:

F1ReB4LL wrote:

Any news regarding my PM about broken C2 errors rereading?

Uploaded test version.
- improved: Rewrote the C2 error recovering logic

        /c2     Continue reading CD to recover C2 error existing sector
                        val1    value to reread (default: 10, min: 2, max: 255)
                        val2    first LBA to reread (default: 0)
                        val3    last LBA to reread (default: end-of-sector)

1,138

Re: DiscImageCreator

Have you fixed the "/f" parameter? FUA should be enabled only when "/f" is used, not always.

1,139

Re: DiscImageCreator

FUA is not matter. Reading speed is down when reads minus from current. It is the same as /r (reverse reading)

1,140

Re: DiscImageCreator

I have a bug to report about DIC.

I have two disc drives, a Plextor and a Blu-Ray drive.  I use the Plextor to dump CDs and the Blu-Ray drive to dump DVDs.

However, I have never had any sucess in trying to use two instances of DIC at once.

To be extra careful, I downloaded an extra copy of DIC and placed it in a different directory, and tried to run it while the original DIC was dumping a disc.

I got the error "[F:main][L:1077] GetLastError: 183, Cannot create file when that file already exists."

Do you think you could fix this?

1,141

Re: DiscImageCreator

sarami wrote:

Uploaded test version.
- improved: Rewrote the C2 error recovering logic

        /c2     Continue reading CD to recover C2 error existing sector
                        val1    value to reread (default: 10, min: 2, max: 255)
                        val2    first LBA to reread (default: 0)
                        val3    last LBA to reread (default: end-of-sector)

I don't understand the current logic, it rereads all the sectors now, not only the ones with C2 errors? Works very slow and ineffective. Took 6 hours, ended with the same bad results as before. DIC from 2013 dumps the same disc in 30 minutes with no errors. Why not to rollback to the old error correction, if it works fast and gives better results?

Post's attachments

Pocket Fighter (Japan)_DIC20171029.7z 7.2 mb, 1 downloads since 2017-10-31 

You don't have the permssions to download the attachments of this post.

1,142 (edited by sarami 2017-11-06 17:05:11)

Re: DiscImageCreator

Updated.

        /c2     Continue reading CD to recover C2 error existing sector
                        val1    value to reread (default: 255)
                        val2    0: reread sector c2 error is reported (default)
                                1: reread all (or from first to last) sector
                        val3    first LBA to reread (default: 0)
                        val4    last LBA to reread (default: end-of-sector)
                                val3, 4 is used when val2 is 1

----

it rereads all the sectors now, not only the ones with C2 errors?

As I already said in PM, the c2 error report of the drive isn't completely reliable as far as I see the log of A Murder of Crows, so I check all sectors if even one c2 error exists. But when val2 is "0", only rereads sector c2 error is reported.

Why not to rollback to the old error correction

The old logic saw the sector all-bytes matched for two consecutive as the correct sector, but it could get the incorrect sector all-bytes matched for two consecutive.
So my bad disc couldn't get the all recovered sector. Your disc is nothing but getting the correct sector by accident.


iR0b0t wrote:

I will recheck --- b) Dump with "/c2 /q /p" parameters --- later again.

I confirmed that 0xd8 with 08(Main+C2+Sub) couldn't get the pregap sector properly if first track is the data.
If resolves this, when reads the pregap sector of the first track, it has to use 0xd8 with 02(Main+Sub).


EDIT:
Sorry. 20171102 version wasn't uploaded. Uploaded as 20171106. I confirmed my damaged disc is recovered all using this version.


EDIT2:

ajshell1 wrote:

However, I have never had any sucess in trying to use two instances of DIC at once.

Please tell me the procedure in detail.

1,143 (edited by battosai121 2017-11-15 05:48:45)

Re: DiscImageCreator

Not Really sure what the problem is but on the newer version of this including the test version it errors out on dumping discs for me, but older version do work.

LBA[268743, 0x419c7]: [F:GetLBAForSubChannelOffset][L:58]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-21-00 = ILLEGAL_REQUEST - LOGICAL BLOCK ADDRESS OUT OF RANGE
lpCmd: be, 04, 00, 04, 19, c7, 00, 00, 01, f8, 04, 00
dwBufSize: 2448
OK
Checking SubQ adr (Track)  1/ 1
Checking SubRtoW (Track)  1/ 1
Reading DirectoryRecord    5/   5

Set OpCode: 0xbe, SubCode: 1(Raw)
Checking SubQ ctl (Track)  1/ 1
[F:ProcessReadCD][L:1462] GetLastError: 87, The parameter is incorrect.

Please wait for 40000 milliseconds until the device is returned
History is much like an endless waltz. The three beats of war, peace and revolution continue on forever.

1,144

Re: DiscImageCreator

Updated test version. Test and upload the log please.

Re: DiscImageCreator

I want to start off by giving sarami and all contributors to DiscImageCreator kudos and a warm thank you for all the work you do! big_smile

I've experienced a bug, tested with the latest version and test version (no idea if it's present in earlier versions).
DIC doesn't recognize that The Elder Scrolls III: Tribunal has a SafeDisc 2.xx.xxx protection, and therefor it cannot get dumped properly (it founds a load of C2 errors, naturally).
I'll include the compressed archive with the files from the latest test version of DIC before I canceled the dumping of that disc.
Cheers! smile

Post's attachments

Tribunal_to_sarami.7z 16.36 kb, 1 downloads since 2017-11-15 

You don't have the permssions to download the attachments of this post.
Main ODDs: QEMU (MSWinXPSP3): PLEXTOR - CD-R PREMIUM 1.07 (+30) | PLEXTOR DVDR PX-760A 1.07 (+30) | HL-DT-ST DVD-ROM GDR-8163B 0L15 (+102) | LITE-ON COMBO SOHC-4832K OQKB (+6).
I've got access to approx. 100 different ODDs and a scanner supporting 3 200 x 6 400 DPI.

1,146

Re: DiscImageCreator

Thx.
_volDesc.txt

                                   :
              Length of Directory Record: 34
        Extended Attribute Record Length: 0
                      Location of Extent: 335260
                             Data Length: 2048
                 Recording Date and Time: 2002-10-31 16:31:47 -05:00
                              File Flags: 2 (Visible, Directory, Disassociated, File has't record format, Owner/Group ID has't, Final Directory Record)
                          File Unit Size: 0
                                    :
========== LBA[000020, 0x00014]: Path Table Record ==========
         Length of Directory Identifier: 1
    Length of Extended Attribute Record: 0
                     Position of Extent: 335260
              Number of Upper Directory: 1
                   Directory Identifier: 
                                 :

This disc points 335260 sector as the position of root directory, but this sector is all zero byte, so dic can't read the directory record and can't detect the protect.
I think the correct position of root dir is 21 or 22 or 23 or 24.

Can Isobuster read the directory correctly?

Re: DiscImageCreator

sarami wrote:

Thx.
_volDesc.txt

                                   :
              Length of Directory Record: 34
        Extended Attribute Record Length: 0
                      Location of Extent: 335260
                             Data Length: 2048
                 Recording Date and Time: 2002-10-31 16:31:47 -05:00
                              File Flags: 2 (Visible, Directory, Disassociated, File has't record format, Owner/Group ID has't, Final Directory Record)
                          File Unit Size: 0
                                    :
========== LBA[000020, 0x00014]: Path Table Record ==========
         Length of Directory Identifier: 1
    Length of Extended Attribute Record: 0
                     Position of Extent: 335260
              Number of Upper Directory: 1
                   Directory Identifier: 
                                 :

This disc points 335260 sector as the position of root directory, but this sector is all zero byte, so dic can't read the directory record and can't detect the protect.
I think the correct position of root dir is 21 or 22 or 23 or 24.

Can Isobuster read the directory correctly?

IsoBuster doesn't show any directory record at sector 335260, it's all zero byte.
I can see the start of a directory record from sector 20-->23.
If you need any screenshots or anything else, just ask for it smile

Main ODDs: QEMU (MSWinXPSP3): PLEXTOR - CD-R PREMIUM 1.07 (+30) | PLEXTOR DVDR PX-760A 1.07 (+30) | HL-DT-ST DVD-ROM GDR-8163B 0L15 (+102) | LITE-ON COMBO SOHC-4832K OQKB (+6).
I've got access to approx. 100 different ODDs and a scanner supporting 3 200 x 6 400 DPI.

1,148

Re: DiscImageCreator

http://redump.org/disc/45930/ and http://redump.org/disc/45931/ are undumpable with DIC (including the recent versions, as I understand) - https://www.sendspace.com/file/31jg9r
Digital Pinball: Necronomicon: Revelations was already reported before, though.

Also, please fix the .dat file generator for Subs Indexes dumps. It doesn't add Subs Indexes .bin files into the .dat anymore, that's not correct. Maybe worth to make a normal dat for normal bins and additional (Subs Indexes).dat for (Subs Indexes).bin files, then?

1,149

Re: DiscImageCreator

Digital Pinball: Necronomicon: Revelations was already reported before, though.

I showed the way to deal to him at that time. (try to use "/s 2" and/or "/f" or change the reading speed or change the drive)

This is definitely the problem of the drive(or disc) that returns the corrupted subchannel, but I don't know why the drive(or disc) returns such the corrupted those.
So I consider these options are enabled if there are some corrupted those.


It doesn't add Subs Indexes .bin files into the .dat anymore

Firstly, are "Subs Indexes" needed? I know that this is used for some pc-engine CDROM^2, but redump'org adopts "TOC Indexes".


BTW, is your pocket fighter recovered using the latest test version? If there is any of the problem, plz tell me.
I asked A Murder of Crows for testing too about ten days ago, but it seems he is busy, haven't reported yet.

1,150

Re: DiscImageCreator

sarami wrote:

Digital Pinball: Necronomicon: Revelations was already reported before, though.

I showed the way to deal to him at that time. (try to use "/s 2" and/or "/f" or change the reading speed or change the drive)

This is definitely the problem of the drive(or disc) that returns the corrupted subchannel, but I don't know why the drive(or disc) returns such the corrupted those.
So I consider these options are enabled if there are some corrupted those.

While I could agree about Wangan here, Pinball subdump is errorless, so it's not the disc's fault.

sarami wrote:

It doesn't add Subs Indexes .bin files into the .dat anymore

Firstly, are "Subs Indexes" needed? I know that this is used for some pc-engine CDROM^2, but redump'org adopts "TOC Indexes".

I'm adding all the PCE (Subs Indexes) dumps as hidden entries, so these are needed. Will probably make them yellow/visible later, dunno, need to consult with iR0b0t.