Redump Forum

So far my drive still works and if your programm would brick my drive I sure would not held you responsible for it. Keep up the good work Sarami

It's recognized by windows and plextools, disc spins up, won't read.

When I ran DIC, it started using 100% CPU, I couldn't even move the console window. Effectively hardlocking my PC, so I tried to eject the disc and they tray opened normally, which gave me back control. The console window would NOT close so I rebooted... well that failed too, I was unable to close the process. So I hit the reset button to hard reboot (which I hate to do).

I've never had a piece of software act in such a manner, where you can't end the process, even windows couldn't end the process on rebooting. There is something really wrong with the code for such things to happen. Maybe you shouldn't use Visual Studio 2013 since it's not entirely proven stable yet.

Nexy wrote:When I ran DIC, it started using 100% CPU, I couldn't even move the console window. Effectively hardlocking my PC, so I tried to eject the disc and they tray opened normally, which gave me back control. The console window would NOT close so I rebooted... well that failed too, I was unable to close the process. So I hit the reset button to hard reboot (which I hate to do)

Happened with me with subdump and PX-716A once. Also 100% usage and was unable to kill the process, after reboot the drive locked and refused to eject the tray (the led was blinking for a few secs after pressing the eject button, nothing more). I've disconnected IDE and molex cables and reconnected after a hour or so - was working fine after that. So, I believe it's not a VS2013 issue (though, in your case, it lets you to eject the tray, but the drive is also different).

Nexy wrote:It's recognized by windows and plextools, disc spins up, won't read.

When I ran DIC, it started using 100% CPU, I couldn't even move the console window. Effectively hardlocking my PC, so I tried to eject the disc and they tray opened normally, which gave me back control. The console window would NOT close so I rebooted... well that failed too, I was unable to close the process. So I hit the reset button to hard reboot (which I hate to do).

Q1: Does it occur only with your PX-W5224A? Or all your drive?
Q2: Does it occur by a specific command and option? Or all command and option?
Q3: This app is built with VS2013 from ver.20131217. Which version does it occur from? (Old download link is written by ReadMe.txt.)

Please tell me if a test is possible.

I really don't know what caused it... and I don't feel like risking my last working plextor to test.

I think you need to have some kind of time out check, and some way to abort the process (crtl+q) or something...

Nexy wrote:I think you need to have some kind of time out check, and some way to abort the process (crtl+q) or something...

I belive it was the drive stucked (either driver or hardware issue), not the program itself, ctrl+q won't help in this case.

Possible bug discovered by Hustle, the first sector of certain PC game (CD, one single data track) is in scrambled form. Checking the logs and the sub the only unusual thing I see (besides of R-W filled with a non-standard data pattern) is the Q frame of the subcode at AMSF 00:02:00 replaced with a MCN frame.

Logs, sub and 0-16 sectors:

Thank you a report. Possible fixed.

I'm getting the following error message when using the latest version,

Internal error. Failed to analyze sub channel.

DIC won't create the actual processed and splitted dump. For any reason, the subcode data gets messed and therefore DIC will fail to process the scrambled dump.

Files (except the scrambled dump itself), the expected and fully clean subcode extracted by subdump to compare against and screenshots.