901

(3,488 replies, posted in General discussion)

reentrant wrote:

I'm having troubles with data command in latest git version. DIC seems to get stuck at the very beginning.

I fixed it yesterday.

reentrant wrote:

I want to compare resulting dumps (track to track basis)

Are these useful?
http://forum.redump.org/topic/12450/fin … ort-added/
http://forum.redump.org/topic/13085/parthash01/

EDIT (2/25)
- added: bd command

        bd <DriveLetter> <Filename> [/f (val)] [/q]
                Dumping a BD from A to Z

I tested some ps3 disc on ASUS BC-12D2HT and the hash matched.
- improved: PC-FX disc (Super PCEngine Fan Deluxe - Special CD-ROM Vol. 1)

EDIT (2/26)
- fixed: Doesn't check reading lead-in/out when uses audio command.

sarami wrote:
user7 wrote:

Is HL-DT-ST UH12NS30 still a drive that works

http://forum.redump.org/topic/15076/add … ification/
I don't have this drive, but he reported this drive worked about scrambled and lead-in.

I found the similar drive (ASUS BC-12D2HT).
This can read lead-in (-145 to -1) and read CD by scramble mode.

EDIT (2/27)
- fixed: /am

902

(3,488 replies, posted in General discussion)

Uploaded test version.
- added:

        mds <mdsfile>
                Parse Alchohol 120/52 mds file and output to readable format
        /am     Scan anti mod string
                        For PlayStation

- fixed: audio/data command (didn't work from 2017-12-10)

903

(15 replies, posted in General discussion)

Tested. (Alcohol 52% 2.0.3 Build 10203) (Plextor PX-755SA)
1: Inugami.mds http://redump.org/disc/25198/
This disc has Starforce and 52% says "Detected DPM".

DPM Ranges Count: 0

2: MS_FANDISK.mds http://redump.org/disc/18729/
This disc has Starforce and 52% says "Detected DPM".

DPM Range: 99500 - 100000 = 500 [+16 -25]
DPM Range: 178000 - 178500 = 500 [+11 -17]
DPM Ranges Count: 2

3. Audio CD.mds
This disc hasn't a protect and 52% say "Can't detect DPM".

DPM Range: 223500 - 224000 = 500 [+12 -15]
DPM Ranges Count: 1

904

(15 replies, posted in General discussion)

reentrant wrote:

it has some other functions like ripping sectors which require admin.

What function is it?

905

(3,488 replies, posted in General discussion)

dic gets the c2 (294 byte=2352bit). If error exists, a bit stands and coutinue checking this 2352 times.

how high is the chance that an unintentional error is exactly 312?

Unintentional error changes every times CD is read, but I don't know how high rate (depending on CD).
Anyways, I always recommend dumping at least twice, especially bad condition disc.

I don't know what those "header generated" messages mean.

Sync is 12byte (00 FF ... FF 00)

========== LBA[002832, 0x00b10]: Main Channel ==========
       +0 +1 +2 +3 +4 +5 +6 +7  +8 +9 +A +B +C +D +E +F
0000 : 00 FF FF FF 7F FF FF FF  FF FF FF 00 01 B9 A3 61   ...............a
========== LBA[002832, 0x00b10]: Main Channel ==========
       +0 +1 +2 +3 +4 +5 +6 +7  +8 +9 +A +B +C +D +E +F
0000 : 00 FF FF FF FF FF FF FF  FF FF FF 00 01 B9 57 61   ..............Wa

Fixed 0x7f to 0xff.

Assuming all unintentional C2 errors could be fixed, would this be a good or a bad dump?

Check _EdcEcc.txt. I don't know the error of this disc is truly 584 because I don't have this.

906

(3,488 replies, posted in General discussion)

Thanks. Uploaded the latest test.
added: Skip rereading for safedisc 312 errors
              => The problem is that dic skips rereading if unintentional error is also 312.

907

(3,488 replies, posted in General discussion)

The latest test version is only added the log message --- "Detected C2 error xxx bit". No need to dump full, I want to know "xxx" value of your all safedisc.

908

(3,488 replies, posted in General discussion)

Uploaded  test ver.
----
I confirmed the specific bit was error.

 :
LBA[002089, 0x00829] Detected C2 error 312 bit

LBA[002109, 0x0083d] Detected C2 error 312 bit

LBA[002114, 0x00842] Detected C2 error 312 bit

LBA[002134, 0x00856] Detected C2 error 312 bit

LBA[002159, 0x0086f] Detected C2 error 312 bit

LBA[002188, 0x0088c] Detected C2 error 312 bit
 :

If your disc also has a specific value of error bit count, app can exclude the sectors which this value has. As a result, app can only reread unintentional c2 error sector.
Please upload the log of your all safedisc. (Because I have only 1 safedisc..)

909

(3,488 replies, posted in General discussion)

user7 wrote:

Is HL-DT-ST UH12NS30 still a drive that works

http://forum.redump.org/topic/15076/add … ification/
I don't have this drive, but he reported this drive worked about scrambled and lead-in.

diego-rbb-93 wrote:

Plextor-W4012TU im using here keeps reporting me this error:

Try using the latest firmware.

sarami wrote:

Yes. Verbose rereading just occurs, surely real c2 errors may be fixed. Plz wait until I add the code.

Uploaded the test version. I haven't tested the protected disc except safedisc yet.

910

(3,488 replies, posted in General discussion)

Yes. Verbose rereading just occurs, surely real c2 errors may be fixed. Plz wait until I add the code.

911

(3,488 replies, posted in General discussion)

As you say, dic needs to reread the safedisc error range to fix the unintentional errors of the range. But dic can't judge whether the errors is intentional or not, therefore the intentional errors are also reread about 500-600 sector × multiple times.

912

(3,488 replies, posted in General discussion)

*2018-01-27
- added: Dumping of DVD which is the parallel track path and dual layer
- changed: Visual Studio 2015 to 2017
- fixed: Dumping of audio disc (didn't work from 2017-12-10)
- fixed: Rewrite .c2 file if c2 errors exist.

913

(3,488 replies, posted in General discussion)

rosewood wrote:

Here are some logs and the CloneCD sub file

CloneCD doesn't also recognize the track 1.

I 23:30:34 Reading Track 2 Pregap... (Blocks 0-250069)
I 23:37:30 Reading Track 2... (Blocks 250069-260319)
I 23:37:47 Reading Track 3... (Blocks 260319-697041)

And unfortunately, the track number of subchannel is also weird.

LBA[000000, 0000000]: P[ff], Q[41020055341900000200549e]{ Data,      Copy NG,                  Track[02], Idx[00], RMSF[55:34:19], AMSF[00:02:00]}, RtoW[0, 0, 0, 0]
LBA[000001, 0x00001]: P[ff], Q[41020055341800000201eeee]{ Data,      Copy NG,                  Track[02], Idx[00], RMSF[55:34:18], AMSF[00:02:01]}, RtoW[0, 0, 0, 0]
LBA[000002, 0x00002]: P[ff], Q[41020055341700000202bb74]{ Data,      Copy NG,                  Track[02], Idx[00], RMSF[55:34:17], AMSF[00:02:02]}, RtoW[0, 0, 0, 0]
 :
 :
LBA[250068, 0x3d0d4]: P[ff], Q[0102000000010055361875b8]{Audio, 2ch, Copy NG, Pre-emphasis No, Track[02], Idx[00], RMSF[00:00:01], AMSF[55:36:18]}, RtoW[0, 0, 0, 0]
LBA[250069, 0x3d0d5]: P[ff], Q[01020100000000553619881b]{Audio, 2ch, Copy NG, Pre-emphasis No, Track[02], Idx[01], RMSF[00:00:00], AMSF[55:36:19]}, RtoW[0, 0, 0, 0]
LBA[250070, 0x3d0d6]: P[00], Q[010201000001005536208530]{Audio, 2ch, Copy NG, Pre-emphasis No, Track[02], Idx[01], RMSF[00:00:01], AMSF[55:36:20]}, RtoW[0, 0, 0, 0]
 :
 :
LBA[260318, 0x3f8de]: P[00], Q[0102010216490057526801b1]{Audio, 2ch, Copy NG, Pre-emphasis No, Track[02], Idx[01], RMSF[02:16:49], AMSF[57:52:68]}, RtoW[0, 0, 0, 0]
LBA[260319, 0x3f8df]: P[ff], Q[01030100000000575269b421]{Audio, 2ch, Copy NG, Pre-emphasis No, Track[03], Idx[01], RMSF[00:00:00], AMSF[57:52:69]}, RtoW[0, 0, 0, 0]
LBA[260320, 0x3f8e0]: P[00], Q[010301000001005752709d68]{Audio, 2ch, Copy NG, Pre-emphasis No, Track[03], Idx[01], RMSF[00:00:01], AMSF[57:52:70]}, RtoW[0, 0, 0, 0]

It seems subdump also can't dump this disc.

http://redump.org/disc/36178/
http://redump.org/disc/35804/
To Jackal or gorelord4e or someone: Do these discs have really track1 on TOC and subchannel? If there is track 1, the disc of rosewood is irregular?

914

(3,488 replies, posted in General discussion)

rosewood wrote:

Sample 1: Probably works again, as it copies the data, but there seems to be a bug when it tries to calculate the hashes for the dat file.

Sorry, reuploaded.

rosewood wrote:

For Sample 3 the toc seems to be corrupt

_disc.txt

========== FULL TOC ==========
    FirstCompleteSession: 1
     LastCompleteSession: 1
    Session 1, FirstTrack  2, Format: CD-I
    Session 1,  LastTrack  3
    Session 1,      Leadout, MSF 63:01:29 (LBA[283604, 0x453d4])
    Session 1,     Track  2, MSF 55:36:19 (LBA[250219, 0x3d16b])
    Session 1,     Track  3, MSF 57:52:69 (LBA[260469, 0x3f975])

It seems "Track 1" is omitted. (same as isobuster)
And my cd-i disc (single track)

========== FULL TOC ==========
    FirstCompleteSession: 1
     LastCompleteSession: 1
    Session 1, FirstTrack  2, Format: CD-I
    Session 1,  LastTrack  2
    Session 1,      Leadout, MSF 56:05:00 (LBA[252375, 0x3d9d7])
    Session 1,     Track  1, MSF 00:02:00 (LBA[000150, 0x00096])

There is "Track 1", but "FirstTrack" and "LastTrack" is weird.

The multi-track of cd-i has data sector in pregap of track 1 (to hide the data?), and manipulates the toc (by the same reason? CD was developed by Philips, so this is permitted?)
It seems the single-track of cd-i can't hide the data in pregap. (If it is done, it's only leadout disc on toc.)

rosewood wrote:

I don't have CloneCD available

If it's possible, please use subdump http://forum.redump.org/topic/14725/subdump/
I need the sub file. Perhaps I think the track 2 of "Sample 3" is actually track 1, track 3 of that is actually track 2 and there isn't track 3.

915

(3,488 replies, posted in General discussion)

usurper wrote:

Same problem here (Sample 1)

Uploaded test version.

rosewood wrote:

Sample 2:

It can't get the directory record. It'll take some time to investigate.

rosewood wrote:

Sample 3:

========== TOC ==========
    Pregap Track   , LBA        0 -  250068, Length   250069
     Audio Track  1, LBA   250069 -  260318, Length    10250
     Audio Track  2, LBA   260319 -  283453, Length    23135
     Audio Track  3, LBA   283454 -4294967295, Length 4294683842

I don't know why it can't get the toc correctly.

916

(3,488 replies, posted in General discussion)

F1ReB4LL wrote:
sarami wrote:

1. Drives may sometimes not detect the c2 errors. If same sector isn't error every time it is dumped, I think this is true.

No error there if to dump again, so it's not constant. So I've thought maybe DIC has missed an error occasionally.

20180108 test
Fixed: Also rewrite .c2 file if c2 errors exist.
=> if unfixed errors exist with EdcEcc.exe or edccchk or cdmage though .c2 file rewritten is all zero byte, maybe the drive misses to report the c2 error.

917

(3,488 replies, posted in General discussion)

It seems your drive can't read lead-in/out. Such drive can't get the audio sector correctly.

ungodly.dumper wrote:

wait until I could obtain a real plextor drive?

I think so.

918

(28 replies, posted in General discussion)

F1ReB4LL wrote:

Those are multisessional

I think so too.
https://page.auctions.yahoo.co.jp/jp/auction/f122922824
There is the enhanced CD logo in the picture.

user7 wrote:

I haven't found any info on this and the wiki guide isn't for DIC.

ReadMe.txt

* Ripping Guide for GD-ROM (The high density area)
** Preparation
 create the audio trap disc in advance.
 (a disc with a hacked TOC of 99 mins audio, burn it with CloneCD or Alcohol 52/120%).
   http://www.mediafire.com/?2nygv2oyzzz

** Method 1 (Other tools)
 http://forum.redump.org/topic/2620/dreamcastnaomi-gdrom-dumping-instructions/

** Method 2 (Other tools)
 http://forum.redump.org/topic/9436/new-dreamcast-dumping-program-test-please/

** Method 3
1. insert the audio trap disc to a supported drive.
2. run below. (stop spinning disc)
   DiscImageCreator.exe stop [DriveLetter]
3. use a pin to press the escape eject button, so the tray will eject (or remove
   the drive cover).
4. insert the gdrom and gently push the tray back (or put the drive cover back on).
5. run below. (start rippping gdrom)
   DiscImageCreator.exe gd [DriveLetter] foo.bin [DriveSpeed(0-72)]

I confirmed this with TS-H353A, but jhmiller couldn't confirm by dic method though he used the same drive and firmware. I don't know the reason.

919

(28 replies, posted in General discussion)

https://www.suruga-ya.jp/product/detail/142002024001
https://www.suruga-ya.jp/product/detail/220005208001
These discs are not so expensive.

920

(3,488 replies, posted in General discussion)

tested kuon no kizuna (Drive: TS-H353A)

    0... 1428 AMSF[00:21:03] -> track1 and 2
 1429...24602 AMSF[05:30:00] -> lead-out
24603...24793 AMSF[05:32:43] -> unknown/corrupt subQ (Mirror # 1 ?)
                                main channel is all zero
24794...25104 AMSF[05:36:54] -> subQ all zero
                                main channel is all 0xff
25105...38692 AMSF[08:37:67] -> normal subQ (SEGA Logo ?)
                                RMSF of LBA 25105 is 00:02:14, so 'SEGA Logo?' perhaps starts from LBA 24941.
                                main channel is the mode 2
38693...38699 AMSF[08:37:74] -> unknown/corrupt subQ (Mirror # 2 ?)
38700...44849                -> unreadable (ILLEGAL_REQUEST - ILLEGAL MODE FOR THIS TRACK)

your drive 'lies' somehow?

Maybe so about mirror area, but I think the lead-out and SEGA logo sub is perhaps correct.

921

(3,488 replies, posted in General discussion)

24400...24602 AMSF[05:30:02] -> lead-out
24603...24793 AMSF[05:32:43] -> unknown subQ (Mirror # 1 ?)
24794...25104 AMSF[05:36:54] -> subQ all zero
25105...38692 AMSF[08:37:67] -> normal subQ (SEGA Logo ?)
38693...38699 AMSF[08:37:74] -> unknown subQ (Mirror # 2 ?)
38700                                        -> unreadable

Have you ever tried to test every sector from 0 to 44849 to find out, which sectors are readable?

0...24399 and 38701...44849 -> test it tonight.

but that's not correct, the secutity (ring) area has its own lead-in, it goes before the sector 24941, sectors 24825...24940, I think, but can't say for sure where does it exactly start, since it's hard to read the sectors before 24853 on my drives (but 24853 to 24940 are clearly the security area TOC sectors).

As far as seeing the log, these area haven't the normal lead-in/TOC subQ. I don't know whether these area is trully TOC or not.

The HD zone starts not at 45000, btw, but at 44850, sectors 44850...44999 contain the 3rd track's pregap.

I agree.

Btw, what drive and tools you use to read HD area?

922

(3,488 replies, posted in General discussion)

What areas does DIC read for DC? 0...leadout and 45000...leadout?

dic reads from 45000 to 549150 using gd command.

Maybe worth to read the 24941...38689 ringcode area as well?

Tried. It seems these area has the mode 2 sector.

923

(3,488 replies, posted in General discussion)

I agree. Low speed may not be good.
http://forum.redump.org/post/56911/#p56911

ref.
http://www.ippinkan.com/magazine/magazine_2013-3.htm

取り込みに使うCD-Rドライブは、本来24-48倍速という高速でCD-Rを回転させます。この速度になるとディスクは、「自らのジャイロ効果」で安定します。ジャイロ効果で安定して回転するディスクを支えるための「主軸(ベアリング)」は、高回転時に安定するように「がたつきを大きく(大きめのクリアランス)で設計されます。クリアランスの大きいベアリングを低速で回すと、ディスクの振れが大きくなります。ディスクは高回転で回す方が安定し、読み取りエラーが少なくなる。

I don't know the detail about the hardware, but this article may be reliable.

924

(3,488 replies, posted in General discussion)

reentrant wrote:

Is it possible to continue execution even if there are C2 errors (I know the image will be bad but I'm aware of it)?

It's possible.
https://github.com/saramibreak/DiscImag … dforCD.cpp
Change the Line 1640:

throw FALSE;

to

break;

or comment out 'throw FALSE;'

But is it really uncorrectable errors? Please try the default times (4000).

reentrant wrote:

Is your C2 algorithm using C2 bits to select bytes which are good / bad and rereads until there are no C2 bits set (making use of C2 bits from previous rereads)?

Yes. It's checked by the func 'ContainsC2Error' of the Line 1630.

925

(3,488 replies, posted in General discussion)

Supported PTP and DL disc.