1 Reply by Cut Into Fourteen Pieces

(14 replies, posted in General discussion)

Just to be clear:

The discs that prompted me to post this thread are not bad burns. They intentionally have a file with a random number in it. That is, each disc was technically a custom one-off burn created by a DVD-burning station, probably with a robot disc changer so the publisher could make a stack of a few hundred quickly.

They are also not otherwise identical to the release version of the game. Some of them are from months before the release build, and others have debug functionality enabled.

In other words, even without making other assumptions, these are very unique versions of the games. There were likely never versions of these discs made that didn't each have a unique ID file.

user7, I have a few like that as well, however, I err on the side of submitting them because of the somewhat-recent discovery that some PS2 master discs had prototype data used as disc padding. That is, even if the game data looks virtually identical, there may be something unusual that's not visible in the filesystem.

Go to forum: General discussion

2 Topic by Cut Into Fourteen Pieces

(14 replies, posted in General discussion)

What are people's thoughts on how to handle game prototypes or other CD/DVD/BD-R releases where each disc has a different hash because of unique identifiers in one or more files on the disc?

I know that this affects Capcom prototypes in the Xbox 360 era, probably other publishers too.

Most prototypes were probably destroyed or lost, but in a worst case scenario, it's possible that there might be a few hundred entries for the same edition, all with different hashes. Same for any indie releases that have watermarked files or similar.

Go to forum: General discussion

3 Reply by Cut Into Fourteen Pieces

(3 replies, posted in Guests & account requests)

Hello.

You can email me.

[ removed my email address after contact was made ]

Go to forum: Guests & account requests

4 Reply by Cut Into Fourteen Pieces

(6 replies, posted in General discussion)

It turns out that I was at least partially mistaken. There might be a missing link in the tool chain, but it's not where I thought it was.

If I burn the images back to DVD-R, they work in my XDK, and Xbox Backup Creator can read the filesystem, at least if they're in the Kreon drive. So, as far as I can tell, DiscImageCreator is working as expected, and is creating a very accurate representation of the disc. However, VirtualCloneDrive, XBox Backup Creator, and ISOBuster are unable to handle the image correctly, so the *only* way I see right now to extract the contents from the resulting image is to burn it back to disc first.

I'm out of time for today, but I'll do some comparison of the files that XBC extracted from the originals and the reburned versions to make sure nothing is getting corrupted. I have several DVD drives now that can read these discs without errors, so I will compare hashes and make sure the images are identical as well.

Go to forum: General discussion

5 Reply by Cut Into Fourteen Pieces

(5 replies, posted in General discussion)

Correct. I successfully dumped a "not for sale" pressed GD-ROM demo version of Demolition Racer. The prototype I'm having trouble with is a recordable GD-R.

Go to forum: General discussion

6 Topic by Cut Into Fourteen Pieces

(5 replies, posted in General discussion)

Apologies for the series of dumping trouble threads, but I think this will be the last one for awhile.

I've successfully dumped a pressed GD-ROM using the instructions in http://wiki.redump.org/index.php?title= … ing_Guide, so I know that my hardware is working correctly. I'll be posting that one later today.

I also have a GD-R prototype, and while I can dump the LD area of that one, attempting to dump the HD area fails *badly*, and I'm wondering if there is something about GD-R discs that makes the GD-ROM process not work (i.e. maybe I need a different audio trap disc, etc.).

I do this:

- Insert audio trap disc.
- Stop drive.
- Pin-eject tray*.
- Insert GD-R and press tray back into drive.
- dcdumper [drive letter] -c446261 -df -ft -t0 -p20

It is very obvious almost immediately that the drive is unhappy with what it is being asked to do. It spins up, spins down, spins up, etc. a few times. dcdumper generally reports a couple of read errors, and then the drive stops responding entirely. The only way to get it to respond again is to physically cut power to the drive (e.g. by powering off the attached PC, or disconnecting power to the drive if it's powered externally). The disc is still spinning, which I learned because if I pin-eject the tray, I can hear it spinning down. If I do that *without* cutting power, the eject button on the drive starts working again, but the drive is completely unrecognized by Windows until power to the drive is cut and restored.

I'm going to dig my Dreamcast out of storage next week and give the old-school dumping method a try using the ethernet adapter, but I'm wondering if anyone here has successfully dumped a GD-R using the GD-ROM instructions? I only have the one, so it's technically possible there's a problem with the disc, but it looks fine.

* I'm using the pin-eject method because the "take the top off" method scares the crap out of me. In my drive, at least, the disc is held against the spindle by a second spindle that's attached to the top of the case. If the top of the case is not screwed on, the disc could come loose at full speed and send GD-ROM shrapnel everywhere.

Go to forum: General discussion

7 Reply by Cut Into Fourteen Pieces

(6 replies, posted in General discussion)

OK, so returning to this topic, some of you have been doing this way longer than I have, but I think maybe this type of disc is not handled 100% correctly by current tools.

I've successfully dumped quite a few Xbox and 360 discs that were signed for retail consoles, including two prototype/preview builds which are on pressed (not burned) DVDs. One of those prototypes is for the OG Xbox, and the other is for the 360, so I have at least basic coverage of a couple of use cases. With all of those, I can dump an image using DIC and the image is readable by the Image Browser in Xbox Backup Creator.

However, I have five DVD-R prototypes (four 360, one OG Xbox) and one pressed DVD 360 prototype (all six signed for use on XDK instead of retail) which are all behaving like this:

- They play correctly on XDKs.
- I can extract the contents of the filesystem if I use the Image Browser in XBox Backup Creator, having it read the physical disc while it's in an SH-D163B drive with the Kreon firmware.
- They show up as an empty disc in Windows Explorer.
- Dumping using Xbox Backup Creator fails.
- Dumping using DIC in xbox mode fails.
- Dumping using DIC in dvd mode succeeds on most drives with no errors, but the image is unusable - Xbox Backup Creator's Image Browser doesn't recognize it (either loaded directly or when mounted using VirtualCloneDrive), and neither does ISOBuster. ISOBuster specifically gives me the error "Iso9660 Error 4: Do you want to risk it and proceed?"

I'm burning two of the unusable (in XBC/ISOBuster) ISOs back to disc right now to see if they can be read by XBC while physically in the Kreon drive - the image of the one OG Xbox DVD-R prototype I currently have, and one of the 360 prototypes which is small enough to fit on a single-layer DVD-R - but I figure if this were going to work, then XBC would read the ISOs.

The prototypes in question were produced by 4 different publishers (Sega, Microsoft, Tecmo, and EA), and I obtained them from at least three different people in completely different countries from each other, so I don't think this is especially uncommon.

Have any of you successfully dumped and then made use of a prototype like these? The "made use of" part is key, IMO, because it proves that the dump is uncorrupted.

Go to forum: General discussion

8 Reply by Cut Into Fourteen Pieces

(6 replies, posted in General discussion)

I have another one of these discs and was able to dump it successfully with DIC in xbox mode, using an SH-D163B drive with Kreon firmware. I know someone else successfully dumped one of these, because we both submitted dumps within days of each other. If it was User7, did you figure out what the problem was?

Go to forum: General discussion

9 Reply by Cut Into Fourteen Pieces

(3,521 replies, posted in General discussion)

Good news: both of those cards (the StarTech 2 Port PCI IDE Controller Adapter Card, and the IOCrest PCIe SI-PEX40059) both work for me with DIC under Windows 10. The StarTech card is a little hard for me to recommend, however, because it blocks the use of the next slot down on the motherboard. If one doesn't need that slot, or the PCI slot is the last slot, that wouldn't be a problem. The IDE connector will press against the next card down when a cable is connected to the IOCrest card, but at least it doesn't actually block the slot. I guess if one is handy with a soldering iron, they could also swap out the downward-facing IDE connectors on either card for ones that face outward.

Go to forum: General discussion

10 Reply by Cut Into Fourteen Pieces

(3,521 replies, posted in General discussion)

sarami wrote:
Cut Into Fourteen Pieces wrote:

Here is the output when I try to dump the same disc with the drives connected to the Ultra133 PCI card instead:

FormatCode: 43, 69, 6d etc... are not defined. It seems the Ultra133 PCI card doesn't support ReadDiscStructure command. Please try to update the driver of PCI card if not latest.

I'm using the latest driver, and the latest BIOS sad.

I'm reasonably sure this card isn't going to work, based on what you've said.

It sounds like I'm the first person in this specific situation (needing to add more IDE/ATA ports to an existing system for use with DIC), so I'm going to order these and see if either of them work any better:

https://www.amazon.com/IO-Crest-SI-PEX4 … 00BI4Z4H6/

https://www.amazon.com/Port-PCI-Control … 000P9VHOO/

I'll report back in a week or two, once I've had time to test.

Go to forum: General discussion

11 Reply by Cut Into Fourteen Pieces

(3,521 replies, posted in General discussion)

sarami wrote:
Cut Into Fourteen Pieces wrote:

Are there any PCI/PCIe IDE/ATA cards that are supported/work with DIC?

If drives are recognized with your PC, DIC will work.

OK, thank you. I have a bunch of drives that work when attached directly to an IDE port on a motherboard, or via a USB adapter, but fail to read discs via DIC when attached to one of the two ports on the PCI card. They can be used in Windows, just not to dump images via DIC.

I am confident that the PCI card works, because I just used it to dump a disc image of an original Xbox dev kit's hard drive.

I've tried with the following drives just now so that I'd have raw output for you:

- PX-712A
- GDR-8163B
- TS-H352C
- Samsung SM308 (random DVD drive I had laying around which I've gotten good dumps from using other pre-DIC tools)

Here is the output when dumping a standard retail PS2 disc when the first two are connected directly to the motherboard:

C:\DiscImageCreator\Release_ANSI>DiscImageCreator.exe dvd x test-px712a-motherboard.iso 8
AppVersion
        x86, AnsiBuild, 20181022 162920
CurrentDirectory
        C:\DiscImageCreator\Release_ANSI
WorkingPath
         Argument: test-px712a-motherboard.iso
         FullPath: C:\DiscImageCreator\Release_ANSI\test-px712a-motherboard.iso
            Drive: C:
        Directory: \DiscImageCreator\Release_ANSI\
         Filename: test-px712a-motherboard
        Extension: .iso
StartTime: 2018/11/22(Thu) 13:47:34
LBA[000000, 0000000]: [F:ReadEeprom][L:889]
        Opcode: 0xf1
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 06-28-00 = UNIT_ATTENTION - NOT READY TO READY CHANGE, MEDIUM MAY HAVE CHANGED
Please wait for 40000 milliseconds until the device is returned
Set the drive speed: 11080KB/sec
Reading DirectoryRecord    3/   3
Creating iso(LBA)  2136560/ 2136560
Calculating hash: test-px712a-motherboard.iso [4375674880/4375674880]
Calculating hash: PFI.bin [2048/2048]
Calculating hash: DMI.bin [2048/2048]
EndTime: 2018/11/22(Thu) 13:55:26
C:\DiscImageCreator\Release_ANSI>DiscImageCreator.exe dvd d test-gdr-8163b-motherboard.iso 8
AppVersion
        x86, AnsiBuild, 20181022 162920
CurrentDirectory
        C:\DiscImageCreator\Release_ANSI
WorkingPath
         Argument: test-gdr-8163b-motherboard.iso
         FullPath: C:\DiscImageCreator\Release_ANSI\test-gdr-8163b-motherboard.iso
            Drive: C:
        Directory: \DiscImageCreator\Release_ANSI\
         Filename: test-gdr-8163b-motherboard
        Extension: .iso
StartTime: 2018/11/22(Thu) 13:56:40
Set the drive speed: 11080KB/sec
Reading DirectoryRecord    3/   3
Creating iso(LBA)  2136560/ 2136560
Calculating hash: test-gdr-8163b-motherboard.iso [4375674880/4375674880]
Calculating hash: PFI.bin [2048/2048]
Calculating hash: DMI.bin [2048/2048]
EndTime: 2018/11/22(Thu) 14:03:08

Here is the output when I try to dump the same disc with the drives connected to the Ultra133 PCI card instead:

C:\DiscImageCreator\Release_ANSI>DiscImageCreator.exe dvd s test-sm308.iso 8
AppVersion
        x86, AnsiBuild, 20181022 162920
CurrentDirectory
        C:\DiscImageCreator\Release_ANSI
WorkingPath
         Argument: test-sm308.iso
         FullPath: C:\DiscImageCreator\Release_ANSI\test-sm308.iso
            Drive: C:
        Directory: \DiscImageCreator\Release_ANSI\
         Filename: test-sm308
        Extension: .iso
StartTime: 2018/11/22(Thu) 13:23:44
LBA[000000, 0000000]: [F:SetDiscSpeed][L:752]
        Opcode: 0xbb
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-20-00 = ILLEGAL_REQUEST - INVALID COMMAND OPERATION CODE
LBA[000000, 0000000]: [F:ReadDiscStructure][L:816]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
EndTime: 2018/11/22(Thu) 13:23:44
C:\DiscImageCreator\Release_ANSI>DiscImageCreator.exe dvd d test-px712a.iso 8
AppVersion
        x86, AnsiBuild, 20181022 162920
CurrentDirectory
        C:\DiscImageCreator\Release_ANSI
WorkingPath
         Argument: test-px712a.iso
         FullPath: C:\DiscImageCreator\Release_ANSI\test-px712a.iso
            Drive: C:
        Directory: \DiscImageCreator\Release_ANSI\
         Filename: test-px712a
        Extension: .iso
StartTime: 2018/11/22(Thu) 13:22:11
Set the drive speed: 11080KB/sec
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 43 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 69 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 6d failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 43 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 74 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 52 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 61 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 41 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 74 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 37 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 2e failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 5c failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 5c failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 5c failed

[ DiscImageCreator.exe crashes - popup in Windows with error reporting option ]
C:\DiscImageCreator\Release_ANSI>DiscImageCreator.exe dvd e test-GDR-8163B.txt 8

AppVersion
        x86, AnsiBuild, 20181022 162920
CurrentDirectory
        C:\DiscImageCreator\Release_ANSI
WorkingPath
         Argument: test-GDR-8163B.txt
         FullPath: C:\DiscImageCreator\Release_ANSI\test-GDR-8163B.txt
            Drive: C:
        Directory: \DiscImageCreator\Release_ANSI\
         Filename: test-GDR-8163B
        Extension: .txt
StartTime: 2018/11/22(Thu) 13:31:52
Set the drive speed: 11080KB/sec
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 43 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 69 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 6d failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 43 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 74 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 52 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 61 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 41 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 74 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 52 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 36 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 74 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 5c failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 5c failed

[ DiscImageCreator.exe crashes - popup in Windows with error reporting option ]
C:\DiscImageCreator\Release_ANSI>DiscImageCreator.exe dvd d test-TS-H352C.txt 8
AppVersion
        x86, AnsiBuild, 20181022 162920
CurrentDirectory
        C:\DiscImageCreator\Release_ANSI
WorkingPath
         Argument: test-TS-H352C.txt
         FullPath: C:\DiscImageCreator\Release_ANSI\test-TS-H352C.txt
            Drive: C:
        Directory: \DiscImageCreator\Release_ANSI\
         Filename: test-TS-H352C
        Extension: .txt
StartTime: 2018/11/22(Thu) 13:29:33
Set the drive speed: 11080KB/sec
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 43 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 69 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 6d failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 43 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 74 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 52 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 61 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 41 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 74 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 2d failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 32 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 5c failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 5c failed

[ DiscImageCreator.exe crashes - popup in Windows with error reporting option ]

If this is something you're interested in troubleshooting, I'm happy to buy you one of these cards if it will help, or send you money to buy one yourself. They're old, but there are tons of them out there on eBay, etc.

If there's an equivalent, more modern card that you know works and is < US$100, I'm also happy to just buy it. My goal here is to be able to quickly dump discs without having to power down and swap cables. I try to avoid IDE cable swapping if at all possible, because it's so easy to bend or break the pins.

My fallback plan is to buy a USB => IDE adapter for each of the drives and connect them to a hub inside the tower.

Go to forum: General discussion

12 Reply by Cut Into Fourteen Pieces

(3,521 replies, posted in General discussion)

Are there any PCI/PCIe IDE/ATA cards that are supported/work with DIC?

I figured out today that the ancient Promise Ultra133 XT2 that I had in my spare parts box is incompatible,[1] but I'm hoping there's a more recent option that will give me at least two extra IDE/ATA ports that I can attach drives to for DIC. All of the i7-compatible motherboards I have only have one IDE/ATA port, and I've got 4-5 format-specific drives with that interface which I'd like to put in my legacy-media-dumping system.

If there's an interest in debugging the Ultra133 problem, I'm happy to help out with that too, but I assume that supporting 15+-year-old cards is not a priority smile.

[1] I assume because its driver makes attached drives look like SCSI devices instead of ATAPI.

Go to forum: General discussion

13 Topic by Cut Into Fourteen Pieces

(1 replies, posted in General discussion)

I'm pretty new here, so I apologize if this has already been discussed at length.

I'm part of a group that's dumping prototypes for preservation purposes. We decided to standardize on Redump's methods, since they seem to be by far the best/most accurate. In discussing various things with other Redump members, I also discovered that I have a few non-prototype discs that are rare enough that they've not been added to the DB yet, so I've been working on adding those as well.

I personally don't have a vested interest in ring codes - I care about the data that's on the discs. However, I know that information is very important to Redump, and so when I submit dumps from our collection, I want to make sure I can do as good a job as possible. There's only one photo of a ring in the wiki, and it's specifically a PS2 disc. Is there any interest in adding additional photos so that it's very clear which text goes in which field in the submission form? I have the following photos already, taken with a DSLR and macro lens:

- Dreamcast retail NTSC
- GameCube retail NTSC
- GameCube Action Replay disc (non-standard ring)
- PlayStation pressed silver bootleg disc
- PlayStation 2 retail NTSC-J
- PlayStation 2 promo PAL
- PlayStation 2 public beta PAL
- PlayStation 2 publisher-issued DVD-R
- PlayStation 3 pressed review code PAL
- PlayStation 4 pressed review code PAL
- Xbox retail NTSC
- Xbox pressed silver preview disc (signed for retail consoles)
- Xbox publisher-issued DVD-R for dev/debug consoles
- Xbox 360 retail NTSC
- Xbox 360 pressed silver preview disc (signed for retail consoles)
- Xbox 360 pressed silver preview disc (signed for dev/debug consoles)
- Xbox 360 publisher-issued DVD-R for dev/debug consoles

I can easily get examples of these types of discs using the same equipment:

- Dreamcast retail PAL
- Dreamcast publisher-issued GD-R
- Dreamcast GameShark
- Nuon retail NTSC
- PlayStation retail PAL
- PlayStation publisher-issued CD-R
- PlayStation 2 retail NTSC
- PlayStation 2 retail PAL
- PlayStation 2 Code Breaker
- PlayStation 2 GameShark
- PlayStation 3 retail NTSC
- PlayStation 4 retail NTSC
- Saturn retail NTSC
- Wii retail NTSC
- Xbox retail PAL

I have various other PlayStation discs as well, but don't have an IR camera to capture their ring codes.

Is any of that of interest?

Go to forum: General discussion

14 Reply by Cut Into Fourteen Pieces

(6 replies, posted in General discussion)

OK, thank you.

At least some of these seem to not be using a standard DVD-ROM format. I will do a more comprehensive examination over the weekend, but the one I'm dumping right now behaves this way:

- GDR-8163B
  - Shows it as an empty disc in Windows Explorer
  - Can dump an image of it in DVD mode using DiscImageCreator
  - Can extract files from it using the image browser in Xbox Backup Creator
- PX-716SA
  - Shows it as an empty disc in Windows Explorer
  - Fails immediately with an error about being unable to recover the table of contents when attempting to dump via DiscImageCreator
  - Haven't tried via image browser
- SH-D163B w/Kreon firmware
  - Haven't tried via Windows Explorer
  - Can dump an image of it in DVD mode using DiscImageCreator
  - Can extract files from it using the image browser in Xbox Backup Creator

I know at least one of the others behaved the same way. I have a couple of other drives I can try too. I'll dump them in DVD mode using several drives and see if the hashes match between any of them. I'll also try burning the dumps back to disc and make sure they're playable on the dev/debug kits.

Go to forum: General discussion

15 Topic by Cut Into Fourteen Pieces

(6 replies, posted in General discussion)

Apologies for the noob question, but I can't find an answer in the wiki or the DiscImageCreator docs.

I have a number of prototypes for the Xbox and Xbox 360. I have dumped prototypes for other platforms, but not this one.

For the prototypes which are signed for use on a retail system, the standard method (DiscImageCreator xbox [drive] [filename] [speed]) works without issues using a drive with the Kreon firmware.

For the prototypes which require use of a dev/debug kit, DiscImageCreator immediately fails with the following type of error:

LBA[-16581121, 0xff02fdff]: [F:ExtractSecuritySector][L:1131]
     Opcode: 0xad
     ScsiStatus: 0x02 CHECK_CONDITION
     SenseData Key-Asc-Ascq: 05-30-02 = ILLEGAL_REQUEST - CANNOT READ MEDIUM - INCOMPATIBLE FORMAT

This occurs on every dev/debug disc I have, regardless of source or if it is a pressed disc or DVD-R. Attempting to dump via Xbox Backup Creator also fails, although its image browser is able to extract the contents of the discs' filesystems. I assume this is because the dev/debug prototypes are not secured in the same way as discs for retail systems.

For Redump-grade dumps of these prototypes, what process should I use? DiscImageCreator in DVD mode instead of Xbox? This seems to work if I also use the Kreon drive, but fails if I use a Plextor DVD drive. I have not had time to burn the DVD-mode dumps back to disc to see if they work.

When submitting dumps of prototypes on publisher-issued DVD-Rs (i.e. sent to game reviewers) is the ring code information still important?

Go to forum: General discussion