Ripping problems

Oh netto golf has been successfully ripped ? i have to find it, i tried to dump it my self but in vain...

 

hehe hian I would have included and dummied the first 2 tracks anyway as they contain spoilers

I was thinking of using HxD but not looking forwards to it - I'd need to work out the LBA references in relation to the hexa references in the editor though - or just fuck it, get the first and last line of code from the files I'm starting and stopping from, then search and zerofill in between but alas no VNC access atm.

I'm not too sure if ASSEMbler dumped it with subchannel data though (it is not a default option) and his BBA was on loan so he may have returned it. I did put a second clean dump for checksum and maybe a 3rd with subchannel on the shopping list though.

Sadly I haven't been as active at debugging this as I'd like, I'm out of coasters, I'm out of money and I've been spread thin on other projects. I will sink my teeth into this some more, but I thnk my energy will be spent for the time being redoing the whole pack another way, though I will include the preloaded files too. Hopefully the VNC will come back soon though so I can and then you can crack on with it.

 

What!? Do you got a pre-reselase DC? Pics!

 

It shouldn't be hard. Each LBA sector is 2048 bytes (2048 iso format) or 0x800
For example, MIFF/FONT/KANJI.BIN is at LBA 462904
462904 -45000 = 12904
12904 x 2048 = 26427392 = 0x193 4000
so KANJI.BIN should start at offset 0x193 4000 of track3.iso

 

No point mate as it looks just like a normal dreamcast.

Yakumo

 

SC.MIFF WTF!

Ola again chaps.

I'm currently manually blanking the track03.bin to release to our comradEs and noticed another oddity I though it best to share.

I was navigating to the end of SC.MIFF to find the raw data tacked on the end before the next sector/file and guess what? The end of SC.MIFF is fine extracted, but it is in WTF mode in the TRACK03.BIN



EDIT: I redid the pics. You can see in SC.MIFF the two lines hilighted. In TRACK03.BIN in between these lines some weirdness has been injected in there.

 

Even the internals? Oh

 

VOLUMES.MIFF WTF!

Same deal as SC.MIFF, VOLUMES.MIFF has code injected inside it in TRACK03.BIN near the end of the file / before the raw data. Still zeroing atm not got time to ponder why they do it yet, I'm sure by the time I zerod someone will have informed me But they could be like tacs etc.

 

You seem to be comparing a data-only dump (2048) to a raw dump (2352). Those extra bytes in the 2nd pics are the ecc and sector sync header.

 

That's strange I'm sure they were extracted in 2352 mode without converting to user data. I'll have another extract but quite tired now TBH but the 2352 zeroing is still correct as I found the other parts NP. I'll redo the whole thing from scratch tomorrow after I've been shopping to be sure though.

EDIT: I redid it all from scratch and it turns out I did it right enough after all just the long way round Even the faster manual way still took some hours so. It was an interesting day anyway. Here is what I did so far, but bear in mind it is late, I need to be up early to fix a PC tomorrow then do a 60 odd mile round trip. I still need to zero the padding yet (havent bothered looking for it yet) to reduce spoilers but it is something trivial which I can look into when I get home tomorrow. As you will see though I have included the 5 extra preloaded files for lols.

I'm knackered though, my eyes are blurred and my ears are ringing so I probably broke something stupid like saved over the IP.BIN or directories or some bullcrap like that but it shall have to wait until tomorrow now.

Anyhow:

FILE START END

ZEROFILL 290E9260 - 3A90B53F

\MIFF\SMAINFO.MIFF 3A90B540 - 3A90BE6F

ZEROFILL 3A90BE70 - 3A9604FF

\MIFF\FONT\KANJI.BIN 3A960500 - 3A96D84F

ZEROFILL 3A96D850 - 3A9758EF

\MIFF\FONT\RES.MIFF 3A9758F0 - 3A976B4F

ZEROFILL 3A976B50 - 3A99F79F

\MIFF\FONT\SLICKER16.MIFF 3A99F7A0 - 3A9C83EF

ZEROFILL 3A9C83F0 - 3AA6594F

\MIFF\FONT\TERMINAL_6X8.MIFF 3AA65950 - 3AA67E0F
\MIFF\GENERAL\SC.MIFF 3AA67E10 - 3AA6906F
\MIFF\GENERAL\VOLUMES.MIFF 3AA69070 - 3AA6D0BF

ZEROFILL 3AA6D0C0 - 441C149F

\SOUND\ARMCOM.DRV 441C14A0 - 441D15DF
\SOUND\GEISTNEW.MPB 441D15E0 - 4421DBCF

ZEROFILL 4421DBD0 - 466C631F

1ST_READ.BIN 466C6320 - 46A7E3FF

 

@LeGIt

Good job! But don't work too hard. You may end up spending more time to correct errors than to take good rests ;p

NO, I don't mean you have made any mistake.

To be safe, it is good practice to extract the non-dummied files and compare them against the original files and I am sure you have already done so.
FYI, there are programs out there that can compare a folder (incl sub-folders) against another folder. "Treediff" is one of them. It will save you time finding out if the files are identical (CRC wise).

 

.GDI dump incoming!

Right I figured out why the .GDI failed to load - track01.bin was completely dummied, so I redid it in HxD to only remove the offending items. The files extract fine but bear in mind the majority of them (1756 of 1766) are dummied and only 10 of them contain data - they are the bare necessities and for lulz, the preloaded files.

Even with my problems I'm positve I dummied only the uneccessary files - as with the original Bare Necessities this grants access to the debug menu ONLY. The only difference here is the preloaded files and .GDI format.

The only real catch is the file names will inevitably give rise to some spoilers, but as previously stated 1756 of the files are empty so there is nothing anyone can do with them

GFBN.rar 20.94 MB (WARNING: will extract to 1.12 GB!)

The archive has been password protected though but the password is attached in the .txt document below as the forum will parse it.

Enjoy!

 

Just sent it to "patriot", let's hope he cracks it soon enough!

\crossfinger

FG

 

I just wanted to say thanks to everyone who has been working on this project. It doesn't seem like gratitude is given often enough to the peeps that work on these projects and generally only after it is finished. You guys are very much appreciated.

 

This GD-R disc work on retail Dreamcast?
What is different your Pre releas Dreamcast and retail Dreamcast?

 

As in the video, it works on retail with SYSTEM-DISC 2, yes - as is the case for most other GD-R.

 

Or you could do the disc swap as well :nod: that would mean either installing a drive switch or taking the top off the Dreamcast though.

Yakumo

 

Hello,

I cannot help at all with these problems, but I wanted as others members to thanks everyone who's working on it ! Thank you !

Lyo.

 

Geist Force Debug Menu MIL-CD test

Geist Force Debug Menu MIL-CD test
http://www.youtube.com/watch?v=CvrFq2rXJ_A