A "Stop" GUI button to abort dumping.

See if we can find a way to get the current maximum drive speed from within C# instead of relying on DIC to do that. It would make it simpler than trying to run DIC and then parsing the output with regex.

See https://msdn.microsoft.com/en-us/library/windows/desktop/aa394081(v=vs.85).aspx

Disc Tools & DICUI/DICUI_1.06/etc

If the DICUI folder is within a folder with an "&" in the title, it will dump the game, but won't generate a dat or some other files.

HD-DVD should be removed from the XBOX360 format list because no games ever came out on it. However, since movies did, it's technically good to keep them their own format, similar to DVD-Video. Additionally, adding currently undumpable formats such as Laserdisc to the list may be fun to do, as long as the implementer makes sure to have the status of those formats be undumpable. See current implementation for HD-DVD and UMD.

Internal change to update DiscType to MediaType to more accurately reflect what the enumeration stands for.

If/when we get an updating framework for the main program, it would be good to get an automatic updater for the internal version of DIC. This would also entail removing the ability to customize the location of DIC since we would need to have a fairly concrete idea of what is being used. Not that users couldn't use a different version themselves, this just makes it easier for most people.

At some point, it may be worthwhile to figure out how to combine the single- and dual-layer entries for the disc formats that support them so there's less confusion for end users. Maybe have the output say which it ended up being.

Ideas:

• Use the GetLayerbreak method to see if any layerbreak is returned. If one is returned, then it's dual layer, otherwise, single layer. This could be THE key.
• Keep both internal options but only expose one of them at any given time to end users (not sure if I like this idea, but it's possible). It would also be one of those "if both exist, only show one"... which could run into potential issues

This is currently implemented in PSX, but should be used for all CD-Rom formats :3

Currently, the best course of action for people to get the copy protection field for their discs is to run ProtectionID. This is good, but it is not scriptable. It would be better if we had internal checking for copy protection that can slowly add more over time.

Possibly look at BurnOut, since that's OSS and EOL;

just tried in DICUI 1.02 - puts an additional slash if you leave the auto-filled directory setting.

cmd line (fails) C:\DICUI_1.02\Programs\DiscImageCreator.exe dvd M ISO\Kao_2\Kao_2 8
settings here: https://imgur.com/a/MZ1h89K

clicking browse and selecting ISO dir manually works ok.
just the autofill seems to insert an additional \

Output a new text file with pertinent information pertaining to the specific console for easy redump.org submission.

fd
Dumping a floppy disk

Inspired by Cleanrip being able to check against known hashes, either allow checking against a folder of datfiles OR search on the Redump site. The former relies on the users more (an may not be preferred because of that). The latter may end up causing issues with Redump and potentially would have issues with logging into the site for access, though it would be the most up to date at any point.

An incorporation of the separate CLI progress info into a bottom area of the GUI (similar to DVD Decrypter).

As i told you time ago Reign, i would like to ask for an option to automatically package the whole dump and the logs on a (single/separated? Dont care too much) Rar or Zip file (dont care too about the format, what you see easy or better).

This option is basically interesting for casual dumpers that want to colaborate and share but dont have time for submitting or whatever reason, so they just upload the whole materia generated from the dumping process.

No rush on this, just wanted to leave the request formally done over here. Thanks so much for all your work buddy.

DICUI fails to launch if the Plextor drive doesn't have the final firmware. When running in DIC CLI it reports back to the user that the firmware isn't up to date.

Here's a message that could pop up:
"Please update your Plextor firmware to the final revision. You can download the final firmware for your Plextor model here."

Port of BurnOut code + enhancements should go in its own project that is linked to this one as a DLL.
Port of Unshield code + cleanup should go in its own project that is linked to this one as a DLL.

Add an automatic updater from GitHub releases. Related to #16

Personal goal to remove the usage of Tuple from the codebase. Either replace with a list of KeyValuePair or with a Dictionary<string, T>.

Update, look into OrderedDictionary<T>: https://msdn.microsoft.com/en-us/library/system.collections.specialized.ordereddictionary(v=vs.110).aspx and https://www.codeproject.com/Articles/18615/OrderedDictionary-T-A-generic-implementation-of-IO

Add a unit testing project so we can verify that everything that doesn't directly require the drive to exist works as planned. Recommended by Jack.

Hi,

only tested in 1.01b - but seems like trailing \ isn't appended to directory name on browse - which causes output directory to be appended onto filename and saved in Drive root.

see here for screenshots: https://imgur.com/a/vK5iCXr

For discs that support C2 error rereading, DiscImageCreator defaults to 4000 attempts. For most people, this is overkill. I suggest having a reasonable limit set by default, say 20-40, and have the value be configurable, for those disc types that support it.

There is the case where two discs will have the same exact name. There should be a safety mechanism in there that will alert users that there is an existing (complete) dump with the same name and path as the one they're attempting to do. It would most likely do best as a popup window that alerts the user and allows them to cancel. If they hit OK, it would then allow DIC to overwrite the existing dump.

It seems windows can't actually read these discs on a file/browser level, but DIC dumps them from the CLI process fine. DICUI doesn't do it :/

A popup message like this could come up:

This disc uses XGD3 copy protection, and will require an alternate dumping method. See this guide.

Tried two different CD-Roms with Joliet, both crashed at the final stage, dumping completed (including dat population etc).

If the new versions of DIC that support outputting the PIC.bin file for BluRay discs works as intended, we will be able to remove the usage and reliance on sg-raw from the UI.

Of note: the PIC.bin file that is output by sg-raw is two bytes longer than the one created by DIC, but it seems that both of those are null anyway. This is a note for DIC, but it should be good for dumping purposes.

Work around the fact that DIC does not like when there are . characters in the inputted path unless they're for the extension. Most likely all but the last instance of the . character will have to be replaced by the _ character, for safety.

Old Info

From antimatter:

"I tested a Xbox One game with DICUI 1.06 & it dumped when the path was set to the root D: not D:\ReDump\DCUI_1.06"
"Now i'm wondering if the path issue is because of the . in DICUI_1.06"
"yes & just retested & thats the problem
can't have a . in the path"

Short description: DICUI will crash on "Start Dumping" with IBM CD set, using an IDE drive externally attached.

Steps to Reproduce:

1. Connect a drive (I'm using a Plextor 716A over a UGREEN IDE/m-IDE/SATA adapter with the 12V AC adapter plugged in for more power) to a computer over USB (I'm using USB 2.0)
2. Launch DICUI.
3. Select IBM Compatible CD-Rom, and your settings
4. Press Start Dumping, and it crashes with the following error log

System Information: ThinkPad T61, Windows 7 Ultimate SP1, Intel Core 2 Duo T7100 1.8GHz, 4GB RAM. System is not yet activated, and at the time of the bug had 0 updates installed from Windows Update, but had .NET 4 and VCRedist installed using Microsoft's own installers.

Full list from: http://forum.redump.org/topic/10483/discimagecreator/

        cd <DriveLetter> <Filename> <DriveSpeed(0-72)> [/q] [/a (val)]
           [/be (str) or /d8] [/c2 (val1) (val2) (val3) (val4)] [/f (val)] [/m]
           [/p] [/raw] [/sf (val)] [/ss] [/np] [/nq] [/nr] [/ns] [/s (val)]
                Dumping a CD from A to Z
                For PLEXTOR or drive that can scramble Dumping
        data <DriveLetter> <Filename> <DriveSpeed(0-72)> <StartLBA> <EndLBA+1>
             [/q] [/be (str) or /d8] [/c2 (val1) (val2) (val3) (val4)]
             [/sf (val)] [/ss] [/r] [/np] [/nq] [/nr] [/ns] [/s (val)]
                Dumping a CD from start to end (using 'all' flag)
                For no PLEXTOR or drive that can't scramble dumping
        audio <DriveLetter> <Filename> <DriveSpeed(0-72)> <StartLBA> <EndLBA+1>
              [/q] [/a (val)] [/c2 (val1) (val2) (val3) (val4)]
              [/be (str) or /d8] [/sf (val)] [/np] [/nq] [/nr] [/ns] [/s (val)]
                Dumping a CD from start to end (using 'cdda' flag)
                For dumping a lead-in, lead-out mainly
        gd <DriveLetter> <Filename> <DriveSpeed(0-72)> [/q] [/be (str) or /d8]
           [/c2 (val1) (val2) (val3) (val4)] [/np] [/nq] [/nr] [/ns] [/s (val)]
                Dumping a HD area of GD from A to Z
        dvd <DriveLetter> <Filename> <DriveSpeed(0-16)> [/c] [/f (val)] [/q]
                Dumping a DVD from A to Z
        bd <DriveLetter> <Filename> [/f (val)] [/q]
                Dumping a BD from A to Z
        fd <DriveLetter> <Filename>
                Dumping a floppy disk
        stop <DriveLetter>
                Spin off the disc
        start <DriveLetter>
                Spin up the disc
        eject <DriveLetter>
                Eject the tray
        close <DriveLetter>
                Close the tray
        reset <DriveLetter>
                Reset the drive (Only PLEXTOR)
        sub <Subfile>
                Parse CloneCD sub file and output to readable format
        mds <Mdsfile>
                Parse Alchohol 120/52 mds file and output to readable format
Option (generic)
        /f      Use 'Force Unit Access' flag to delete the drive cache
                        val     delete per specified value (default: 1)
        /q      Disable beep
Option (for CD read mode)
        /a      Add CD offset manually (Only Audio CD)
                        val     samples value
        /be     Use 0xbe as the opcode for Reading CD forcibly
                        str      raw: sub channel mode is raw (default)
                                pack: sub channel mode is pack
        /d8     Use 0xd8 as the opcode for Reading CD forcibly
        /c2     Continue reading CD to recover C2 error existing sector
                        val1    value to reread (default: 4000)
                        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
        /m      Use if MCN exists in the first pregap sector of the track
                        For some PC-Engine
        /p      Dumping the AMSF from 00:00:00 to 00:01:74
                        For SagaFrontier Original Sound Track (Disc 3) etc.
                        Support drive: PLEXTOR PX-W5224, PREMIUM, PREMIUM2
                                       PX-704, 708, 712, 714, 716, 755, 760
        /r      Read CD from the reverse
                        For Alpha-Disc, Tages (very slow)
        /raw    Read the lead-out of 1st session and the lead-in of 2nd session
                        For Multi-session
        /sf     Scan file to detect protect. If reading error exists,
                continue reading and ignore c2 error on specific sector
                        For CodeLock, LaserLock, RingProtect, RingPROTECH
                             SafeDisc, SmartE, CD.IDX, ProtectCD-VOB, CDS300
                        val     timeout value (default: 60)
        /ss     Scan sector to detect protect. If reading error exists,
                continue reading and ignore c2 error on specific sector
                        For ProtectCD-VOB
        /am     Scan anti-mod string
                        For PlayStation
Option (for CD SubChannel)
        /np     Not fix SubP
        /nq     Not fix SubQ
        /nr     Not fix SubRtoW
        /nl     Not fix SubQ (RMSF, AMSF, CRC) (LBA 14100 - 16199)
                                               (LBA 42000 - 44399)
                        For PlayStation LibCrypt
        /ns     Not fix SubQ (RMSF, AMSF, CRC) (LBA 0 - 7, 5000 - 18799)
                                            or (LBA 30800 - 34799)
                                            or (LBA 40000 - 45799)
                        For SecuROM
        /s      Use if it reads subchannel precisely
                        val     0: no read next sub (fast, but lack precision)
                                1: read next sub (normal, this val is default)
                                2: read next & next next sub (slow, precision)
Option (for DVD)
        /c      Log Copyright Management Information

I am trying to dump the Crash Bandicoot Wrath of Cortex disc and it doesn't properly dump, it throws error instead. I can dump the PS2 DVD fine.

The optical drive I'm using is LG Slim Portable DVD Writer GP57EB40.

My setup

Here's what it printed when I hit Start Dumping:

AppVersion
        x86, AnsiBuild, 20180619 20619
/c2 val2 is omitted. set [0]
E:\Dumped games\PS2\DICUI_1.07\ISO\CRASH\ doesn't exist, so create.
CurrentDirectory
        E:\Dumped games\PS2\DICUI_1.07
WorkingPath
         Argument: ISO\CRASH\CRASH.bin
         FullPath: E:\Dumped games\PS2\DICUI_1.07\ISO\CRASH\CRASH
            Drive: E:
        Directory: \Dumped games\PS2\DICUI_1.07\ISO\CRASH\
         Filename: CRASH
        Extension: .bin
StartTime: 2018/07/16(Mon) 16:07:18
Set the drive speed: 1411KB/sec
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 1, SubCode: 0]
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 1, SubCode: 1]
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 1, SubCode: 2]
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 1, SubCode: 4]
LBA[-00001, 0xffffffff]: [F:ReadCDForCheckingReadInOut][L:475]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-2c-00 = ILLEGAL_REQUEST - COMMAND SEQUENCE ERROR
lpCmd: be, 04, ff, ff, ff, ff, 00, 00, 01, f8, 00, 00
dwBufSize: 2352
This drive can't read the lead-in
EndTime: 2018/07/16(Mon) 16:07:19

Not sure how to implement this, will take a bit of research, trial and error I suppose. Not high on the list IMO, but perhaps let's put it on the radar http://wiki.redump.org/index.php?title=GD-Rom_Dumping_Guide

System.AgumentOutOfRangeException is raised in MainWindow.xaml.cs, inside SetSupportedDriveSpeed() function, here:

string readspeed = Regex.Match(output.Substring(index), @"ReadSpeedMaximum: [0-9]+KB/sec \(([0-9]*)x\)").Groups[1].Value;

when output from DIC fails to produce expected output (for instance if another instance is already dumping).

This should be fairly simple, as DIC itself includes the ability to eject discs.

Simply running the command "discimagecreator.exe eject d" will eject drive d.

This would be a REALLY useful feature for those who dump a bunch of discs in a row.

For submitting discs, a lot of information needs to be consolidated from across multiple output files. It would be good if all of these could be automatically rounded up and made into a templated file that would be appropriate for the type of disc being dumped.

Of note, if any dump whatsovever has the _mainError.txt file with a size > 0, then the dump is not good. This is where hardware issues and errors get stored, so the output file should never be considered correct.

Auto-report maximum read speeds to "Disc Speed" selector, as discussed here: http://forum.redump.org/post/60394/#p60394

If a user does not submit the info for a particular disc immediately, it may not be apparent what type of disc they ripped. Adding two new fields to the submissionInfo.txt file would be useful for this. In the cases of custom inputs, this will have to be assumed that the default values are accurate, since we can't really tell an IBM CD from a Macintosh CD from an arcade CD based on inputs alone.

For after the single-/dual-layer change, this will also help clear up what sort of disc was actually just ripped.

A button to Detect the disc type based on format and root files / structure.

Certain formats follow certain rules / have root files or folders making them easy to detect with one-click, as opposed to finding the format manually.

A single downloadable EXE that makes it ever easier.

Subdump checking plz

http://forum.redump.org/post/54022/#p54022

note: i'm happy to beta test this.

I'm told the data can be gathered from a Hex Editor.

There's a PS4 pic.bin in here that can be used for testing: https://drive.google.com/open?id=1y6rGjEylg9yd92FNd4oEhx-IMwlK_ql5

Currently, if the program crashes, there is no way of determining what went wrong exactly. Implement a to-file logger that will write out in the event of an issue.

Possibly put one giant try-catch around the main app runtime?

Note: It appears all PS4 discs may carry the volume label "PS4VOLUME"

If you navigate inside the root folder bd, there is a file 'param.sfo'

Here is the param info for: http://redump.org/disc/32774/

As you can see when opening in notepad the version is 1.01

Currently, the system dropdown includes both the system and the type in one fell swoop. It may be in our best interest to make these completely separate things in order to make the disc cleaner. This was recommended and coded by Jack, whose PR will be coming.

Notes:

• This may work best by using the already-created "get disc types for known system" method
• Having it repopulate the Disc Type dropdown each time is also probably the best idea
• Placement on the screen may be tricky, but it is doable

I just grabbed DICUI to dump a disc using my PX716A, which was running firmware 1.07. When this drive is connected, DICUI just silently dies and plays the fail tones that DiscImageCreator.exe plays when you run it without arguments. I wasn't sure what was going on, so I ran the command to dump manually using the program in the Programs folder, and I saw exactly what was going on:

DiscImageCreator.exe returns this:
DiscImageCreator.exe cd h "image.bin" 24 /c2 /nl
AppVersion
x86, AnsiBuild, 20180619 20619
/c2 val1 is omitted. set [4000]
/c2 val2 is omitted. set [0]
CurrentDirectory
C:\Applications\DiscImageCreator\Programs
WorkingPath
Argument: image.bin
FullPath: C:\Applications\DiscImageCreator\Programs\image
Drive: C:
Directory: \Applications\DiscImageCreator\Programs
Filename: image
Extension: .bin
StartTime: 2018/07/14(Sat) 13:02:04
[ERROR] This drive isn't latest firmware. Please update.
EndTime: 2018/07/14(Sat) 13:02:04

This error is being silently dropped by DICUI, not even running it via command line shows it. After I updated the drive to 1.11 firmware, DICUI now starts up correctly.

Double-clicking the application doesn't do anything. There were three entries in Event Viewer, 2 errors and 1 info (attached).
error1.txt
error2.txt
info.txt

OS:
Windows 10 Pro

Drive:
VendorId: TSSTcorp
ProductId: DVD-ROM SH-D163B
ProductRevisionLevel: SB01
VendorSpecific: KREON V1.00

I was able to successfully rip an OG Xbox disc by running the following from the "Programs" dir:
DiscImageCreator.exe xbox e xboxgame.bin

If you want any more info, please just ask.

Here's a nice and simple issue. I tried to dump an Xbox One disc recently with DICUI at dizzzy77's request, even though I had already dumped a disc and got a matching checksum with ImgBurn. However, I was getting the error "Unknown option: [6]", which would later be "Unknown option: [4]" and then ""Unknown option: [8]" after messing with the disc speed. It turns out that DiscImageCreator doesn't have an option for dumping Blu-Rays at a specific speed, and that DICUI is adding it in anyway. As a result, selecting "Xbox One" or "PS4" in DICUI won't produce a proper dump.

Instead of constantly updating the README.MD with the newest changelist, put the info into a separate markdown file that can be updated with each release.

We need to figure out a way for DICUI to properly be able to dump discs that Windows can't recognize such as HFS and 3DO discs. DIC itself has no problem with it, it's just Windows recognizing them as valid drives that there's an issue. See if there's any flag that can be triggered.

This is a dumping ground for all known copy protections that are not detected by DICUI properly. For anyone commenting, please include the name of the disc, the name of the file, the protection that DICUI detected and the protection that ProtectionId detected. This will help keep track of things for better testing.

Known issues:

• No sector scanning
• Minor scanning of textfiles
• No scanning of archives - 7Z, RAR, PKZIP, ARC
• No internal key decryption for DVD, HD-DVD, BD, UHD-BD
  • DVD CSS keys taken care of by CSS.exe for DiscImageCreator (test build)
  • HD-DVD unhandled
  • BD/UHD-BD unhandled
• The following protection schemes need to be verified in the real world due to a decrement operation used in the code:
  • SolidShield 2, SolidShield 2 + TAGES
  • TAGES
  • VOB ProtectCD/DVD