DiscImageCreator

[matura713]

* make small tool using SPTI Windows interface... that tries only to read the BCA

OK, I coded the test tool, the source code is attached. it should not be considered fully finished, i.e. some (small) modifications could be necessary in order to be fully functional, but it contains the essential portion of the necessary code.

P.S. One open question, at least to me, is how GC/Wii "dvd" structure in CleanRip code corresponds to "Cdb" in SPTI Windows interface, especially which parameter defines the "layer" to read.

[EDIT] more or less the code is working, because I tested it with changing "sptd.Cdb[7] = 0x03" to "sptd.Cdb[7] = 0x04", i.e. reading the Manufacturer (instead the BCA) and I can read:

Code: Select all

Nintendo NNGC Disk

on Nintendo discs. Unfortunately, even on PC drives that works for getting the "Manufacturer", I cannot get the BCA on any disc. So, it's still open question, if there is PC drive that can read the BCA...

[Cyo.the.vile]

Here is what I get using latest test DIC.  Trying to grab TOC/pre-gap with this troublesome CD

[sarami]

Here is what I get using latest test DIC.  Trying to grab TOC/pre-gap with this troublesome CD

https://github.com/saramibreak/DiscImag … /issues/86

[sarami]

on Nintendo discs. Unfortunately, even on PC drives that works for getting the "Manufacturer", I cannot get the BCA on any disc. So, it's still open question, if there is PC drive that can read the BCA...

Perhaps it's the same as PS3 compatible drive cannot get data1/data2. If we get BCA on PC, we need to get Wii optical drive emulator like 3k3yRipper of PS3.

[matura713]

@sarami

because you requested BW-16D1HT logs in the other forum thread, I have one - I don't know if it helps, but currently it's the only CD that failed for me in BW-16D1HT using DiscImageCreator. so, the log is attached. basically, it says "Cache is short. Retry 45/50" and at the end fails.

If we get BCA on PC, we need to get Wii optical drive emulator like 3k3yRipper of PS3.

maybe that's the case... BTW, I cannot get the link to your "PS3Auth" from your signature to work for me:

Bad request. The link you followed is incorrect or outdated.

It's like 10 years ago, I made such tool for myself that authenticates PS3 drive in Windows using as base the Linux source code or I don't clearly remember, maybe it was 3k3yRipper .NET code I reversed-engineered, but I guess yours do the same anyway...

[sarami]

it says "Cache is short. Retry 45/50" and at the end fails.

Change the retry count -> /mr 100 or /mr 150 or more

I cannot get the link to your "PS3Auth" from your signature to work for me:

It needs a login.

I guess yours do the same anyway...

Yes.

[matura713]

Change the retry count -> /mr 100 or /mr 150 or more

i set it at 500, but it's the same "Cache is short. Retry 500/500", logs attached.

It needs a login.

thanks, I see, I guess I need to elevate my forum credentials somehow. That probably explains why I get so many dead links in the database as well. Anyway, I will reread the forum rules and faqs, maybe, i can figure out what i have to do...

[sadikyo]

@sarami,

I noticed an issue/bug/etc that started with DIC version 20210601.  When I try to dump certain PC discs, the status reaches "Checking EXE" and crashes immediately and will not dump. 

I believe it is something to do with some file checking or version checking that DIC is doing on files on the disc, and I'm not sure why.

On my current example, I see the line:  AUTORUN.EXE: File Version 4, 0, 0, 1 and then Checking EXE     1,
and then it crashes immediately every time.

I tested dumping on DIC 20210401 and it worked perfectly fine and this file/version checking didn't happen.

The crash occurs in both 0601 and 0701.  Please let me know if you need anymore information.  I've attached logs for the unsuccessful dump on 0601.

[sarami]

I've attached logs for the unsuccessful dump on 0601.

Code: Select all

    ========== IMAGE_SECTION_HEADER (40 bytes) ==========
                    Name: UPX1
             VirtualSize: 0002e000
          VirtualAddress: 0005b000
           SizeOfRawData: 0002e000
        PointerToRawData: 00000400
    PointerToRelocations: 00000000
    PointerToLinenumbers: 00000000
     NumberOfRelocations: 0000
     NumberOfLinenumbers: 0000
         Characteristics: e0000040
                        => contains initialized data
                        => can be executed as code
                        => can be read
                        => can be written to
    ========== IMAGE_SECTION_HEADER (40 bytes) ==========
                    Name: .rsrc
             VirtualSize: 00002000
          VirtualAddress: 00089000
           SizeOfRawData: 00002000
        PointerToRawData: 0002e400
    PointerToRelocations: 00000000
    PointerToLinenumbers: 00000000
     NumberOfRelocations: 0000
     NumberOfLinenumbers: 0000
         Characteristics: c0000040
                        => contains initialized data
                        => can be read
                        => can be written to
    ========== IMAGE_EXPORT_DIRECTORY ==========
              Characteristics: 2c10227c
                TimeDateStamp: 284ef6b9 (1991-06-07T03:00:09)
                 MajorVersion: 197f
                 MinorVersion: 03b2
                         Name: dae40257 (

"UPX" is shown in IMAGE_SECTION_HEADER of SETUP.EXE. Please check if it is compressed by UPX or not.
If yes, DIC is not supported it yet. 20210401 version does not output IMAGE_EXPORT_DIRECTORY yet.

[superg]

"UPX" is shown in IMAGE_SECTION_HEADER of SETUP.EXE. Please check if it is compressed by UPX or not.
If yes, DIC is not supported it yet. 20210401 version does not output IMAGE_EXPORT_DIRECTORY yet.

Is there any way to disable this checking so DIC doesn't crash?