Ripping GDR's

Let us know how it goes Tachi, Im anxious to hear!

 

Will give it a bash tomorrow morning (hangover willing) just need to find my rip tools CD and coders cable.

It won't even kick off the ripping of GDR's this time, originals fine, but it just won't start the dumping process, will need to have a fiddle.

 

You sick little monkey!! :lol: :lol:

...and then he goes on to say he needs to have a fiddle. Hmm. I feel like I'm on the set of a Carry On movie!

 

Well, when you have kids, the Mrs isn't as willing as she used to be, so...

 

in greece they say : "get an ugly wife and have a hot mistress"

 

Any luck so far, Tachikoma?

 

Yes please, an update!

 

Sorry, not had a chance to try it since, I had a brief flashback though, I think last time I had this trouble and did a W0mbat-esque swap-trick, where I booted up the software with a retail then swapped for a GDR before clicking ok to start the dump.

 

Here are the same steps I sent Dot50Cal via PM (BBA method):

 

You need to change the IP in hex edit on that iso, just so you know.

 

Thats what I have been doing (albeit via the serial port...) but it just sits there and doesn't do anything when you hit start. With a retail it chugs away nicely, dumping the game, but a GDR just sits there.

 

That probally explains why I never got it to run, can you maybe explain how I exactly do that?

 

Ok, in DC GUI set your IP to
192.168.0.100

and then use this DJ iso Im uploading in your DC. It'll give you the MAC Add in your DC.

Check the option just below the IP and enter your mac address in there for the DC.

This ISO is set to use 192.168.0.100 so it shouldnt interfere with your other network card that connects to the internet (192.168.1.xxx)

Thats how I got it to work properly, should be faily easy after that. The only thing I can think of for GDROM's is changing the address or filesize in dc-tool to get GDROM's working. Anyone have any offset data for retails vs GDROM? If we can find the starting address that should work, but im no expert in this by any means.

http://rapidshare.com/files/18758387/dcload-ip-103-0.0.0.0-DiscJuggler3.cdi.html

You should get track.txt (very small, and unopenable?) and track3.iso which is the main file. Use the extract.exe program on it (which is included in earlier versions of dreamrip) and you have all the data on your HDD.

What you should see is this if you rip retails:



All you get with a GDR is "Dreamrip 2.01 By Bero" and then the DOS prompt dies, and your network card resets. I know this is possible to rip these, as Propeller Arena has been released. So can someone here please lay some knowlege down?

Update: System Disc 2 works, and since it acts as a loader for GDR's maybe someone can fiddle with the data and see what addresses it loads code into? Anyone? D:

 

Yeah, that's something we need to find out: what're the layout/offset differences between a ordinary GD and a GDR.

 

My Wombat swap-trick I did last time didn't work, it stopped streaming after 10k:



Going to try with my other DC now to see if that fairs any better.

 

A friend who knows some people in the warez scene suggested that in order to rip a GDR it might be a good idea to try using a DC File browser app (like an FTP). Ill give that a whack soon, as I dont really care about getting a working ISO, one can be created to self boot as long as access to the files is done.

Ill see if I can try swapping them out, Did the laser stop spinning it like you thought it would after a bit tachi?

 

Yeah it did exactly as I thought it did, it spun the disc back up once you clicked "ok" and it read a small part of the disc then gave up. The other DC did the same thing. I did have 4 Dreamcasts at one point, so it's possible I have since sold the one that managed to read it (Belokk said only some can rip GDR's)

 

He didnt specify the model number or anything, did he?

Edit: trying to swap method now.

! Might have this working! Will report results when its done ripping!!

 

Good man, keep me informed!

 

Works!!! Will have a guide up when I confirm this isnt limited by TOC size!

Ok, the game you choose does have something to do with it. While my one prototype ripped fine, the other is having issues as it seems the company placed two audio tracks inside the session seperating the data. I can get through them fine using the actual retail copy of the game as a boot method, but once it gets to the final data track it ends at about 44MB.

Trying various discs now to see if I can get around it.

Slight update:

Seems the session info is whats taken from normal DC retails when using the swap method for GDR. This is a big problem as this one proto I have doesnt have a standard track layout, and doesnt match the retail releases either. So its doubtful Ill ever get this one working :|

Im checking this now by ripping the retail of this prototype I have, which has a non standard track layout. Its either as I described above or if this retail too fails its a flaw in the ripping app.

However, if you have a proto with a normal 1 data section it should rip fine using a retail which has 1 data session as well.

Edit: Confirmed, my prototype is using a whacky track layout :| Damnit. Likely these will never get ripped as you need a retail disc which has the same exact track data if it has more than 1 track in Session 2.

Method:

Tape down your lid sensor

DC Load IP in your DC, to boot the ripping app

Take tape off so it opens the lid and insert a retail DC game (only works if track layouts are same on proto and retail)

Let that spin with the lid sensor down

When it stops (3-5 min), put the GDR in its place and execute the upload

If this fails and you see that your connection was dropped momentarily it means the track layouts on the retail and the proto dont match.

If anyone can lend a hand in possibly finding the real track layouts on GDR's that would eliminate all this trouble.

Note: System Disc 2 in place of the retail also fails if you use a non standard track layout on the prototype :\

Edit:

More news, Resident Evil 2 retail uses split up tracks like I mentioned earlier. Even when properly extracted all you get is 0 byte files from one and a proper ip.bin, and ip.bin from the other (they dont match CRC).