1 Reply by zcal

(5 replies, posted in General discussion)

I was thinking about next trying to just discard the -c446261 parameter and see if I can zero in on the part(s) of the discs that are causing matching problems.

Worthwhile?  I understand Section 40 is dumped as a 10x larger chunk of data because those last sections tend to be trouble on their own.

Go to forum: General discussion

2 Reply by zcal

(5 replies, posted in General discussion)

I'll give that a try.  Thanks for the tip.  I've certainly let the H352C run for many passes over long periods of time.  It's way slower and more finnicky about dumping than the H192C.

Dealing with this, it's amazing to me that there are as many Dreamcast dumps in the database as there are!

Go to forum: General discussion

3 Topic by zcal

(5 replies, posted in General discussion)

I've been trying to get a verified dump of a Dreamcast disc with DCdumper for the past month or so with no luck.  I've tried with five different discs.  I have two compatible drives for GD-ROM HD area dumping: a TS-H192C and a TS-H352C.  Both reliably get matches on sections 1-39.  They will both match section 40 occasionally (sometimes takes a LOT of passes), but not yet so that I have been able to verify any dump against the database.  Also, I haven't been able to get the same hash on a section 40 match for the same disc twice.

From testing with my copy of Virtual On - Oratorio Tangram, I am certain that the drives are pulling good data from sections 1-39.  This disc has 58 tracks on the HD area and I have been able to match checksums on the first 57 from multiple dumps.  I've never been able to match the 58th.

I find it hard to believe that this is a problem with all five of my discs.  None of them have any significant scuffs or scratches, and Virtual On is pristine.  I've tried dumping with two separate PCs, with PowerShell and with the command prompt (not that I think either of these variables would matter).

Is this a common issue with Dreamcast dumping?  Is there anything else I can try?  Or should I really assume that both my drives are lemons?  How many drives should I expect to go through before I find one that'll do the job with section 40?

Go to forum: General discussion

4 Reply by zcal

(3,497 replies, posted in General discussion)

I'm trying to dump the HD area of my Dreamcast discs.  I have a TS-H192C drive, which is either recommended or untested but should work.  sarami confirmed its ability to dump the HD area a few years ago.

I get the following errors when I try to dump from any of my Dreamcast discs.  I'm using DIC version 20201101.

StartTime: 2020-12-11T11:17:20-0600
Set the drive speed: 1411KB/sec
[WARNING] /c2 isn't set. The result of dumping may be incorrect if c2 error exists.
This drive can read data sectors at scrambled state [OpCode: 0xbe, C2flag: 0, SubCode: 0]
This drive can read data sectors at scrambled state [OpCode: 0xbe, C2flag: 0, SubCode: 1]
This drive can read data sectors at scrambled state [OpCode: 0xbe, C2flag: 0, SubCode: 2]
LBA[045000, 0x0afc8]: [F:ExecSearchingOffset][L:185]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
lpCmd: be, 04, 00, 00, af, c8, 00, 00, 01, f8, 04, 00
dwBufSize: 2448
Couldn't read data sectors at scrambled state [OpCode: 0xbe, C2flag: 0, SubCode: 4]
LBA[045000, 0x0afc8]: [F:ReadCDForCheckingSubQAdr][L:949]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
lpCmd: be, 04, 00, 00, af, c8, 00, 00, 02, f8, 04, 00
dwBufSize: 2448
Checking SubQ adr (Track)  3/ 3
LBA[045100, 0x0b02c]: [F:ReadCDForCheckingSubRtoW][L:1091]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
lpCmd: be, 04, 00, 00, b0, 2c, 00, 00, 01, f8, 04, 00
dwBufSize: 2448

Reading DirectoryRecord   14/  14
Set OpCode: 0xbe, SubCode: 4(Pack)
LBA[044999, 0x0afc7]: [F:ProcessReadCD][L:288]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
EndTime: 2020-12-11T11:17:39-0600

Go to forum: General discussion

5 Reply by zcal

(9 replies, posted in General discussion)

So I managed to get the CloneCD trial working on a fresh Windows 10 install.  Audio trap disc burned correctly and I'm test dumping a Dreamcast disc now.

I'd still be interested to know if anyone can get the trap disc to burn with another program.

Go to forum: General discussion

6 Reply by zcal

(9 replies, posted in General discussion)

So far I haven't had any luck.  CD Manipulator has been the most promising, but it hasn't burned the trap disc correctly.  Tried it on my Windows 10 laptop, in Wine on my Linux box, with two different drives...

I think my next step is going to be a fresh install of Windows 10 - maybe in a VM or something - and cross my fingers that an install of CloneCD there won't think that its trial period has elapsed.

Go to forum: General discussion

7 Reply by zcal

(9 replies, posted in General discussion)

olofolleola4 wrote:

I've used CD Manipulator 2.7.0 with Wine to burn the Audio Trap Disc smile

I tried CD Manipulator and it finished with errors, but it did actually burn data to the disc.  Other programs have refused to write anything to the disc at all, so this is encouraging at least!

I'll try dumping a Dreamcast disc sometime this week and see if the trap disc works.

Go to forum: General discussion

8 Reply by zcal

(9 replies, posted in General discussion)

user7 wrote:

Well I think dcdumper is windows only anyway so... not sure how you'd dump the HD area on linux.

I wouldn't. I have both operating systems. Only saying that I am able to try both Windows and Linux programs/methods to burn the trap disc if there are any suggestions.

Go to forum: General discussion

9 Topic by zcal

(9 replies, posted in General discussion)

I'm trying to burn an audio trap disc for dumping the HD area of GD-ROMs.  The wiki advises the use of CloneCD.  When I try to use CloneCD, it complains that my trial period has expired.  Never mind that I just installed the program today.  :\

I'm really not looking to use CloneCD for anything other than this, so I have no intent to purchase it.  Is there a recommended alternative program/method (Windows or Linux) for burning this audio trap disc?

Note:
I've tried converting the CCD image to ISO using ccd2iso in Linux in order to try burning it with cdrecord, but it throws the error:

Unrecognized sector mode (0) at sector 0!

I've also tried mounting the IMG as a virtual drive that I could use mkisofs against, but it fails to mount.  I suspect this has to do with the nature of the image.

Go to forum: General discussion

10 Reply by zcal

(4 replies, posted in General discussion)

Thanks, nitro322!

I've seen that format in others' submissions, so I figured that was coming from !submissioninfo.txt.  I'll see what I can do about piecing the bits together.

In the other thread that you linked you noted how (it appears) you get the PVD.  Any idea how you w/should do this for multi-track discs?  I've got some Sega Saturn discs that generate ~20 .bin files each when dumped.

Also, I noticed in the other thread that you asked if your dump was going to be added to the database.  That was in December.  Did you have luck with other dumps that you've done with Linux getting entered?

Go to forum: General discussion

11 Reply by zcal

(4 replies, posted in General discussion)

Sorry for bumping an older post, but I'm also interested in the answer to question #2.  And furthermore, would manually assembled information that would otherwise be included in !submissioninfo.txt be trusted enough for a database submission?  This is assuming that all other relevant output files from the dump were included and an approved drive was used.

Go to forum: General discussion

12 Reply by zcal

(3,497 replies, posted in General discussion)

sarami wrote:

Try to use su or sudo.

That fixed it.  Thanks.
But why does DIC require root privileges?

Go to forum: General discussion

13 Reply by zcal

(3,497 replies, posted in General discussion)

I'm testing dumping with a Plextor PX-708A using the 20191223 release of DiscImageCreator.  I'm able to dump a Sega Saturn disc correctly in Windows, but I get the below errors in Linux using the same parameters.  I have the same issue with the 20191116 release.

[zcal@computer disc]$ ./DiscImageCreator_linux.out cd /dev/sr0 foo.bin 24
AppVersion
        x64, AnsiBuild, 20191223 223711
CurrentDirectory
        /home/zcal/download/disc
WorkingPath
         Argument: foo.bin
         FullPath: /home/zcal/download/disc/foo.bin
            Drive: /
        Directory: home/zcal/download/disc/
         Filename: foo
        Extension: .bin
StartTime: 2020/01/12(Sun) 08:34:34
[F:ReadEeprom][L:912] GetLastError: 1, Operation not permitted
Please wait for 25000 milliseconds until the device is returned
[F:SetDiscSpeed][L:775] GetLastError: 1, Operation not permitted
Please wait for 25000 milliseconds until the device is returned
[WARNING] /c2 isn't set. The result of dumping may be incorrect if c2 error exists.
[F:ExecSearchingOffset][L:114] GetLastError: 1, Operation not permitted
Please wait for 25000 milliseconds until the device is returned
lpCmd: d8, 00, 00, 00, 00, 00, 00, 00, 00, 01, 00, 00
dwBufSize: 2352
This drive doesn't support [OpCode: 0xd8, SubCode: 0]
[F:ExecSearchingOffset][L:114] GetLastError: 1, Operation not permitted
Please wait for 25000 milliseconds until the device is returned
lpCmd: d8, 00, 00, 00, 00, 00, 00, 00, 00, 01, 01, 00
dwBufSize: 2368
This drive doesn't support [OpCode: 0xd8, SubCode: 1]
[F:ExecSearchingOffset][L:114] GetLastError: 1, Operation not permitted
Please wait for 25000 milliseconds until the device is returned
lpCmd: d8, 00, 00, 00, 00, 00, 00, 00, 00, 01, 02, 00
dwBufSize: 2448
This drive doesn't support [OpCode: 0xd8, SubCode: 2]
Retry 1/10 after 10000 milliseconds
[F:ExecSearchingOffset][L:114] GetLastError: 1, Operation not permitted
Please wait for 25000 milliseconds until the device is returned

Go to forum: General discussion

14 Reply by zcal

(3,497 replies, posted in General discussion)

sarami wrote:

Tell me please.

This is the main one I noticed, though OP doesn't say what drive s/he's using.
http://forum.redump.org/topic/22712/pc- … sion-help/

Looking back, I found that the other threads I saw are ~5 years old or not using DIC, so aren't really relevant.

Go to forum: General discussion

15 Reply by zcal

(3,497 replies, posted in General discussion)

Nexy wrote:

The readme in the OP has a list of supported drives. https://github.com/saramibreak/DiscImag … /README.md

I know I've seen some other threads where unlisted drives were used to dump.  I was just wondering if there's any other troubleshooting I can do for my error.  Sounds like not.

Go to forum: General discussion

16 Reply by zcal

(3,497 replies, posted in General discussion)

I'm unable to get DIC to dump using my drive.  I'm using a Pioneer DVR-XD09 with DIC 20191001 on Linux and am testing with PlayStation discs.

Using the basic arguments for dumping a CD:

./DiscImageCreator_linux.out cd /dev/sr0 foo.bin 24

I get the below output:

This drive can read data sectors at scrambled state [OpCode: 0xbe, C2flag: 0, SubCode: 1]
Failed to get write-offset
Retry 1/10 after 10000 milliseconds

What can I do?  Am I out of luck with this drive?

Go to forum: General discussion