Re: DiscImageCreator

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

302 (edited by Nexy 2014-03-06 21:24:38)

Re: DiscImageCreator

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.

Plextor PX-760A 1.07 (+30) : Plextor PX-W5224A 1.04 (+30) : Plextor PX-W1210TA 1.10 (+99) : Plextor PX-W1610TA (+99) : Lite-On LTR-48246S (+6) : Lite-On LH-20A1H LL0DN (+6) : BenQ DW1655 BCIB (+618) :  ASUS DRW-2014L1 1.02 (+6) : Yamaha CRW-F1 (+733)

Re: DiscImageCreator

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).

304 (edited by sarami 2014-03-07 18:29:19)

Re: DiscImageCreator

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.

305 (edited by Nexy 2014-03-07 22:13:09)

Re: DiscImageCreator

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...

Plextor PX-760A 1.07 (+30) : Plextor PX-W5224A 1.04 (+30) : Plextor PX-W1210TA 1.10 (+99) : Plextor PX-W1610TA (+99) : Lite-On LTR-48246S (+6) : Lite-On LH-20A1H LL0DN (+6) : BenQ DW1655 BCIB (+618) :  ASUS DRW-2014L1 1.02 (+6) : Yamaha CRW-F1 (+733)

Re: DiscImageCreator

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.

307 (edited by pablogm123 2014-03-24 18:28:56)

Re: DiscImageCreator

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:

http://www.mediafire.com/?4qm5id2m57f5hhl
On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

Re: DiscImageCreator

Thank you a report. Possible fixed.

Re: DiscImageCreator

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

Internal error. Failed to analyze sub channel.

Re: DiscImageCreator

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.

http://www.mediafire.com/?7lcpwnoadeg5g5k
On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

Re: DiscImageCreator

Sorry. Reuploaded.

312

Re: DiscImageCreator

Well good news, I did what Fireball suggested, and disconnected the drives, and power cycled twice to let the chipset and windows reset everything about the IDE bus. Now my 5224A works again, ALSO my 760A can read DVD's again... so it's some stupid bug with either windows, or this j-micron controller on my motherboard.

I apologize for flying off the handle at you sarami, it wasn't your fault at all.

btw, someone reported that DIC is no longer working with PX-W2410A and old version worked.

Plextor PX-760A 1.07 (+30) : Plextor PX-W5224A 1.04 (+30) : Plextor PX-W1210TA 1.10 (+99) : Plextor PX-W1610TA (+99) : Lite-On LTR-48246S (+6) : Lite-On LH-20A1H LL0DN (+6) : BenQ DW1655 BCIB (+618) :  ASUS DRW-2014L1 1.02 (+6) : Yamaha CRW-F1 (+733)

313 (edited by olofolleola4 2014-03-30 01:46:34)

Re: DiscImageCreator

Nexy wrote:

btw, someone reported that DIC is no longer working with PX-W2410A and old version worked.

That was me.

PX-W2410TA (PX-W2410A 1.04) has never worked properly with DIC, but the support got completely broken somewhere between version 20140110 and 20140306
Before that, I could use the device to dump either the audio tracks and getting a data track with the wrong hashes, or I could dump the data track and got audio tracks with the wrong hashes.
I always get the same error message like the one that is described in the first post about the PX-W4824TU/TA.
I could only dump at 16x speed.

sarami, could I be of any assistance to get the device supported in DIC?

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.

Re: DiscImageCreator

In the past, I confirmed that there was some probrem about PX-W2410TA (fw 1.04), PX-320A(fw 1.06), PX-W8432T(fw 1.09), PX-W1210A(fw 1.10)

[PX-W2410TA, PX-320A]
. If it doesn't read a subchannel using 0xd8 command, an offset of drive is +99, but if it read a subchannel using 0xd8 command, an offset of drive is +686.

[PX-W2410TA, PX-320A, PX-W8432T, PX-W1210A]
. If a data track exists in track 1 and read it using 0xd8 command, it becomes the read error (ILLEGAL_REQUEST. ILLEGAL MODE FOR THIS TRACK)

So, I can't support these drive at this time.

Re: DiscImageCreator

olofolleola4 reported that the PX-W2410TA drive can rip a mixed-mode disc using the classic cdtoimg-d8 program, so at least the basic D8 command with neither subcode nor C2 pointers works for this drive.

Does D8+C2, without raw subcode reading, work properly in these drives and the offset is the expected one (+98 and not +686)?

If so, I guess that a possible workaround would be to implement another additional reading mode, this way:

-Detect the CATALOG, ISRCs, DCPs, PRE flags... according to the TOC and analyzing the subcode (not issuing certain commands to read CATALOG, ISRCs... because there are drives which can give fictitious CATALOG and/or ISRCs), D8+raw subcode command. Additionaly, it would be cool that the program could detect TOC vs. subcode desyncs and print this as a warning. Examples of discs which suffer from this annoying issue:

http://redump.org/disc/29165/
http://redump.org/disc/27420/
http://redump.org/disc/29606/

-Once analyzed the TOC and the subcode to build the proper cue and ccd, rip the disc as usual, D8 + (optional) C2 command. Logically, no actual subcode from the disc is ripped and the dump is splitted and unscrambled according to the info previously detected.

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

316

Re: DiscImageCreator

With my 1210 and 1610, D8 worked most of the time with data tracks, and only some discs it failed with illegal mode for this track errors.

Interesting to know about the offset differences when reading subcode, something I did not know. AFAIK the older drives do not support C2 at all.

The only thing to note with these drives is that they are better at reading discs with weak sectors towards the end of the disc with some revisions of SafeDisc. Newer drives will dump erroneous sectors, where these drives can dump them fine.

Plextor PX-760A 1.07 (+30) : Plextor PX-W5224A 1.04 (+30) : Plextor PX-W1210TA 1.10 (+99) : Plextor PX-W1610TA (+99) : Lite-On LTR-48246S (+6) : Lite-On LH-20A1H LL0DN (+6) : BenQ DW1655 BCIB (+618) :  ASUS DRW-2014L1 1.02 (+6) : Yamaha CRW-F1 (+733)

317

Re: DiscImageCreator

Has there been a fix for the Error 121: semafoor issue?

I'm also having these with the latest version. However i tried an older version (Dated 2013-06-19) that i found on my laptop that works just fine with the exact same hardware.

The hardware used: Plextor PX-716A, Some old cheap USB cd drive enclosure, Apple rMBP running win8.1 update 1 through Boot Camp.

I'm pretty sure it's not the USB enclosure that creates the error, as i tried this exact same drive in my backup pc connected directly to the motherboard and it also works with the earlier mentioned older version, but not with the latest one.

318 (edited by sarami 2014-04-13 13:15:32)

Re: DiscImageCreator

1. reenabled PX-W2410TA, PX-320A, PX-W8432T, PX-W1210A for the present.
2. added: execute EccEdc.exe in this program. it places in same dir.
    (EccEdc.exe is tool that checks a user data(2048byte) using ecc/edc.)
     http://www.mediafire.com/?glwmoytaqo00e55/
    [EDIT] fixed help msg.
3. fixed: parsing subchannel (LBA -1 and adr flag isn't 1.  e.g. [PCE]1552 Tenka Tairan)
4. changed: ScsiPassThroughDirect.TimeOutValue (2 => 60)

Has there been a fix for the Error 121: semafoor issue?

I want to fix it. But I don't know in detail. And this error doesn't show in my PC. So I can't confirm this.

[EDIT]
5. added: msg that if it isn't index 0 at LBA 0 /p is ignored.

319 (edited by pablogm123 2014-04-13 05:32:06)

Re: DiscImageCreator

/p option doesn't work properly, Plextor drives can rip only the -75, -1 range of the first pregap directly. It's somewhat hard to explain the correct method to dump properly the first pregap when this one contains actual audio data (the miniCD Audio disc bundled with Tenbu MegaCD Special, for example), but would something like this.

-Read the -5000,-76 range, D8 command of couse. When reach more or less the -1000 LBA will report many read errors, it's normal and expected.

-A part of the lead-in, the entire first pregap and a piece of the first track, index 1, is dumped.

-Then use the first sectors of the normal dump to search them in the dumped file, find the portion which matches those first sectors and extract the previous 352800 bytes into a separated file.

-The subcode is easy, just extract into a separarated file the frames with 00:00:00 - 00:01:74 AMSF.

http://www.mediafire.com/?470d0r269wg6bce

I have uploaded a sample, the entire minidisc and the pregap extracted as I have proposed via the audio option.

Then, I have hashed the first 75 sectors of the first track and these ones are the results. Program used is parthash, much easier than cutting the dump and whatnot:
http://forum.redump.org/topic/13085/


D:\MiniCD\Main dump>parthash "MiniCD (Track 1).bin" 176400
#        Size   CRC-32                        MD5/SHA-1
1      176400 fa5fa23f 4e9bff8a8ab29fafb6252977de6b11ea
                714a04d835419264528b0327c143de4267e3d961
2    39588864 e0c9e590 4083df206ba8ab18864aa27590ac346c
                dc47b01492f14f26b60bccd4de635d016a2b239d

Then I run the findcrcs.exe program by V. in the lead-in+first pregap+a piece of first track dump and these are the results:

D:\MiniCD\Pregap>findcrcs Pregap.bin 176400 FA5FA23F
4290048  fa5fa23f  4e9bff8a8ab29fafb6252977de6b11ea

Thus 4290048 is the starting point of the main dump, so I have to extract 3937248-4290047 range into a separated file to have the actual pregap ripped once and for all. The subcode is easy, just delete everything except the range with AMSF 00:00:00 - 00:01:74.

findcrcs.exe program is here, including source code.

http://forum.redump.org/topic/12450/

With these suggestions, perhaps you can implement a proper routine to extract properly the first pregap of these discs.

And it would be cool to implement another routine to extract the lead-out of certain discs which contains audio data in the lead-out. My Alanis Morissette - Jagged Little Pill [UK(9362-459012)], as far you remember you purchased this one to perform certain tests related to the slowness when ripping discs with R-W filled with 0xff, contains data in the actual lead-out, so could be useful to implement an option to rip into a separated file the first 100 sectors of the lead-out, applying either the offset correction autodetected by D8 (if disc contains a data track, Heavy nova for MCD for example), the standard one of AccurateRip or the overriden by the /a parameter.

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

320 (edited by sarami 2014-04-13 13:35:46)

Re: DiscImageCreator

Plextor drives can rip only the -75, -1 range of the first pregap directly.

Somebody knows a drive that it can rip under -75 (=from -150 to -76) LBA?

-A part of the lead-in, the entire first pregap and a piece of the first track, index 1, is dumped.

This is unexpected for me. I don't know why these data get by a plextor drive.

Re: DiscImageCreator

sarami wrote:
Plextor drives can rip only the -75, -1 range of the first pregap directly.

Somebody knows a drive that it can rip under -75 (=from -150 to -76) LBA?

Plextors rip from -75 for Audio CDs and from -142 for Data CDs.

sarami wrote:
-A part of the lead-in, the entire first pregap and a piece of the first track, index 1, is dumped.

This is unexpected for me. I don't know why these data get by a plextor drive.

It's a known trick. You can also try to dump not "-5000 to -76" range, but "$FF000000 to -1". Exactly "$FF000000" as a starting sector.

Re: DiscImageCreator

Testing the new complement...

D:\Redump\PX-755SA\Forsaken\DIC>discimagecreator.exe cd g: Forsaken-USA 8 /c2 1000 8192 8
OS
        MajorVersion: 5, MinorVersion: 2, BuildNumber: 3790
        PlatformId: 2, CSDVersion: Service Pack 2
AppVersion
        x86, AnsiBuild, Apr 12 2014 20:02:22
CurrentDir
        D:\Redump\PX-755SA\Forsaken\DIC
InputPath
         path: Forsaken-USA
        drive:
          dir:
        fname: Forsaken-USA
          ext:
Start: 2014-04-15(Tue) 20:08:31
Checking reading lead-out
Creating bin from 275759 to 275760 (LBA) 275760
Reading lead-out: OK
Allocating memory for C2 error: 8192/8192
Creating img(LBA) 275759/275758
C2 error didn't exist
Copying .scm to .img
Descrambling data sector of img(LBA)  39264/ 39264
Check LBA 275758/275758
User data vs. ecc/edc doesn't match num: 39265
Creating bin, cue, ccd(Track) 13/13
Free memory for C2 error: 8192/8192
Calculating hash. D:\\Redump\PX-755SA\Forsaken\DIC\\Forsaken-USA (Track 13).bin
End: 2014-04-15(Tue) 20:16:45

"User data vs. ecc/edc doesn't match num: 39265" is the expected error for this no EDC in form 2 sectors and with audio tracks PS1 disc, right? That sector is the 39264 actually, though.

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

Re: DiscImageCreator

>pablogm123
Thank you testing.
EccEdc_20140416.7z
http://www.mediafire.com/?74xxfl46ozbt1tz
fixed: detect  mode 2

>F1ReB4LL

"$FF000000 to -1"

sorry, I don't understand "$FF000000".

Re: DiscImageCreator

To try to read the very beggining of the lead-in.

http://www.cdtool.pwp.blueyonder.co.uk/instructions.htm
http://club.myce.com/showthread.php?p=1067119

Anyway, I have tried this a few of times and I got only strange mechanical noises, the drive remains busy for a few of minutes and whatnot, so assume that this is a no go (or at least works with only very few discs/drives combinations) and unhealthy for the drive.

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

Re: DiscImageCreator

I tried the CDTool.exe (with PX-755SA, PX-4824TA) and inputted $FF000000 or $F0000000 in sector input box of "View sectors".
But I didn't get the sector data, and continued to start and stop reading disc.
Eventually, I got the error below.

Sector could not be read.

Error while processing ReadCD command.

Unknown sense key code combination:

Sense key:3

Additional sense code:2

Additional sense code qualifier:129.

Does my way make a mistake of any?