|
More info.......
I noticed when mounting the image of a self boot game (or looking at the files on a already burned selfboot CD) that works in my DC that the files I see are all the data files on the disk (not audio.raw) whereas when I use the Echelon method (or BIN2Boot) all I see is Audio.raw after burning the CD. Oh, and the Echelon or BIN2Boot method leave the image file corrupted, whereas all my other selfboot images mount just fine.
Can a DC expert please help me out? I'm a Software Enginneer so I'd really like to understand exactly what the difference is between a selfboot and non-selfboot game so I can stop using these "magic" apps and create a more robust program to convert non-sboot to sboot. Any info anyone has on developing DC games might help (such as the DC OS's APIs and file formats..... is there a dev kit for DC?)
So what method is being used by these games to make them selfboot? Does anyone know? Is the data supposed to be in the first session and audio.raw in the second?
|