DiscImageCreator

[sarami]

but why put a limit?

Format of a Path Table Record

BP Field name Content
1 Length of Directory Identifier (LEN_DI) numerical value
2 Extended Attribute Record Length numerical value
3 to 6 Location of Extent numerical value
7 to 8 Parent Directory Number numerical value
9 to (8 +
LEN_DI)

Directory Identifier d-characters, d1-characters,
(00) byte
(9 + LEN_DI) Padding Field (00) byte

Parent Directory Number (BP 7 to 8)
This field shall specify as a 16-bit number the record number in the Path Table for the parent directory of the
directory.

16-bit = 0xffff = 65535

Added the code for flushing log. (Because almost all files are 0 size)

EDIT
improved: PS2 cheat disc (support the sub-channel of huge Lead-out )

EDIT (5/2)
added: check the region of PSX if /nl is used. Because Libcrypt is only used by PAL.

[Kurems]

Dizzy replied to my question about possible compatible USB Plextor drives.
So, it's a no-go.

Thanks.

[F1ReB4LL]

https://mega.nz/#!RZkWxACJ!gllef6IbSF3_ … gL5j5TGbqo
https://mega.nz/#!sMFiRaAR!bpSobINe4Co6 … _bgfP_G-js

Sarami, why does it happen? Same drive, same command, lots of suberrors in the first case case (every sector is "fixed" due to sector shift?), 10 times less in the 2nd case. Maybe DIC should restart the dumping process when that happens? Or does it need to eject/insert the tray and swap again for a chance of a better dump?

[number78]

Sarami, is there a command line option to probe cd/dvd drive for available drive speeds and then report to console?

would be useful for DIC-gui purposes (probe drive / populate gui with real usable drive speeds). currently seems like trial/error?
perhaps a "discimagecreator -ls" for list speeds option?

[sarami]

With the test version "Apr 29 2018" continue to fail.

Found a bug and fixed it perhaps.

DIC should restart the dumping process when that happens?

Do you want to restart when how many errors are counted?

is there a command line option to probe cd/dvd drive for available drive speeds and then report to console?

Is this OK?

Code: Select all

C:DiscImageCreator.exe ls f
AppVersion
        x86, AnsiBuild, May  2 2018 13:26:55
Start time: 2018-05-02(Wed) 13:37:16
ReadSpeedMaximum: 8468KB/sec (48x)
End time: 2018-05-02(Wed) 13:37:16

[user7]

Is this OK?

Code: Select all

C:DiscImageCreator.exe ls f
AppVersion
        x86, AnsiBuild, May  2 2018 13:26:55
Start time: 2018-05-02(Wed) 13:37:16
ReadSpeedMaximum: 8468KB/sec (48x)
End time: 2018-05-02(Wed) 13:37:16

Very cool. What about for dvd and bd? That max read looks like it's for CD-Rom. It would be great to report the other max speeds to the GUI so they know which ones are available for selection depending on the disc detected.

[number78]

Is this OK?

Code: Select all

C:DiscImageCreator.exe ls f
AppVersion
        x86, AnsiBuild, May  2 2018 13:26:55
Start time: 2018-05-02(Wed) 13:37:16
ReadSpeedMaximum: 8468KB/sec (48x)
End time: 2018-05-02(Wed) 13:37:16

Very cool. What about for dvd and bd? That max read looks like it's for CD-Rom. It would be great to report the other max speeds to the GUI so they know which ones are available for selection depending on the disc detected.

awesome! thanks sarami!

[jhmiller]

Silver (Spain) continues to fail with the May 2 2018 version.

[sarami]

Silver (Spain) continues to fail with the May 2 2018 version.

Same error?

What about for dvd and bd?

Updated.

[jhmiller]

Silver (Spain) continues to fail with the May 2 2018 version.

Same error?

Yes.
Sometimes it shows the "Directory Record is over 65535" and crash, and sometimes it does not show it and crash after the "Checking SubRtoW (Track)  3/ 3".