Prepared a starter kit with a ready-to-burn image, precompiled DreamInducer disc and some nice homebrew games:
http://www.dcevolution.net/dsdevelop...ter-Kit-v1.zip
Hope it helps.
Printable View
Prepared a starter kit with a ready-to-burn image, precompiled DreamInducer disc and some nice homebrew games:
http://www.dcevolution.net/dsdevelop...ter-Kit-v1.zip
Hope it helps.
I did follow your guide without "skipping steps or looking at other guides in between". I also had several friends look at it, who agreed with me whole-heartedly and thought it was a complete waste of time. They were right.
Unless someone has foreknowledge of many of the applications you mention (and don't explain) the guide is completely useless. (IF IT EVEN WORKS).
YOU LEAVE STEPS OUT AND ARE VERY VAGUE IN MANY AREAS.
Your antagonistic response was very predictable.
In hindsight it really isn't worth the effort to play 20 year old games on system that hasn't really been supported in half a decade. Especially considering they are emulatable on any 233 MHz PC with Neo Rage.
Thanks for your comments & support.
is there any way to get Rage Of The Dragons on Neo4ALL/AES? i never been able to convert it
The guide worked for me.
Hurray for old threads.
I'm having a problem getting The King of Fighters '95 Neo CD to boot as a standalone disc. I've done both Metal Slugs and they've worked fine. If I open the disc with one of the programs like DCHakker I think it's called, I can scan the 1st_read.bin and run it, but, otherwise it doesn't work. Has anyone else had problems with KOF95?
1st_read.bin is in scramble format?
I've used the same one for Metal Slug 2 and the first Metal Slug and they both boot without a hitch, I forgot whether it's supposed to be scrambled or unscrambled as I haven't really messed with anything like this for like 3 years until recently, but, if I'm using the same 1st_read.bin and it boots other games, then, I don't know why it would be a problem with the 1st_read.bin. Could this be an issue of the Dreamcast simply giving up on finding the 1st_read.bin? KOF95 has a ton of files that are like for examle: 0018.extension that are all placed before the 1st_read.bin. Opening up the disc in DC Hakker, you have to scroll for a long time until you can actually get to the 1st_read.bin.
Actually, weird idea:
Using BINHACK.EXE could I redirect the IP.BIN to point to something like 000000000.bin for the DC to boot from so it would be the first file it would read? This would then bring up another problem though as BootDreams wants your IP.BIN to point to the 1st_read.bin...
1st_read.bin must be scrambled
you can rename 1st_read.bin to 00000000.bin and create a new IP.bin file (use IP.BIN creator) with new first-read filename