kof2003 on winkawaks

[garyoak99]

All I know is that KOF2003 works in both Nebula Loader and NeoRAGEx for me. I also have all the newer sets for MAME, which proves that those sets work in MAME. You were either missing the Neo-Geo BIOS or the romset you had wasn't a MAME set.

<{POST_SNAPBACK}>

 

I do have the Neo-Geo BIOS since I can run all of the other Neo Geo ROMs just fine! The romset I have isn't a MAME set; it is a romset meant to be used with either NeoRAGEx or Nebula.

 

Which versions of NeoRAGEx and Nebula Loader do you use?

Edited March 20, 2006 by garyoak99

[Agozer]

Nebula 2.25 Loader

I don't know about NeoRAGEx, it's some EGCG version, but not the latest. Oh yeah, MAME doesn't recognize non-MAME sets (NeoRAGEx, Nebula, Kawaks).

[garyoak99]

Nebula 2.25 Loader

I don't know about NeoRAGEx, it's some EGCG version, but not the latest. Oh yeah, MAME doesn't recognize non-MAME sets (NeoRAGEx, Nebula, Kawaks).

<{POST_SNAPBACK}>

 

Oh, wait! I finally got it loaded into the Nebula Loader It looks like there may be some files missing with the romset after all.

 

000-lo.lo, File not found

271-p1.bin, File not found

271-p2.bin, File not found

271-s1.rom, Bad CRC Expected 7C7829AA, Found C47F8AC3

271-m1d.bin, File not found

 

When I try to continue I get the Microsoft XP pop-up message:

 

nebula.exe has encountered a problem and needs to close.  We are sorry for the inconvenience.

 

What does this mean?

[Agozer]

Well, 000-lo.lo is part of the MAME Neo-Geo BIOS set. What DAT are you using and what are the contents of your set?

[garyoak99]

Well, 000-lo.lo is part of the MAME Neo-Geo BIOS set. What DAT are you using and what are the contents of your set?

<{POST_SNAPBACK}>

 

I have two romsets; one meant for NeoRAGEx and another for MAME.

 

The 1st one for NeoRAGEx contains:

 

271-c1.rom

271-c2.rom

271-c3.rom

271-c4.rom

271-c5.rom

271-c6.rom

271-c7.rom

271-c8.rom

271-m1.rom

271-p1.rom

271-s1.rom

271-v1.rom

271-v2.rom

271-v3.rom

271-v4.rom

 

The MAME one contains:

 

271-c1c.bin

271-c2c.bin

271-c3c.bin

271-c4c.bin

271-c5c.bin

271-c6c.bin

271-c7c.bin

271-c8c.bin

271-m1_decrypted.bin

271-m1c.bin

271-p1c.bin

271-p2c.bin

271-p3_decrypted.bin

271-p3c.bin

271-v1c.bin

271-v2c.bin

 

I put the following into the NEOGEO.DAT in the romdata folder of Nebula.

 

System: Neo
RomName: kof2003
Game: King of Fighters 2003 (Bootleg)

[Program]
271-p1.bin,0,400000,92ED6EE3,0
271-p2.bin,400000,400000,5D3D8BB3,0

[Text]
271-s1.rom,0,20000,7C7829AA,0

[Z80]
271-m1d.bin,0,40000,396e17cd,0

[Samples]
271-v1d.rom,0,400000,D2B8AA5E,0
271-v2d.rom,400000,400000,71956EE2,0
271-v3d.rom,800000,400000,DDBBB199,0
271-v4d.rom,C00000,400000,1B90C4F,0

[Graphics]
271-c1d.rom,0,800000,E42FC226,0
271-c2d.rom,1,800000,1B5E3B58,0
271-c3d.rom,1000000,800000,D334FDD9,0
271-c4d.rom,1000001,800000,D457699,0
271-c5d.rom,2000000,800000,8A91AAE4,0
271-c6d.rom,2000001,800000,9F8674B8,0
271-c7d.rom,3000000,800000,374EA523,0
271-c8d.rom,3000001,800000,75211F4D,0

Edited March 20, 2006 by garyoak99

[Agozer]

Change System: Neo to System: NEO. This is crucial sometimes.

 

Oh, and you are totally missing this at the end:

 

[system]

CartridgeID: 271

GfxCrypt: 0

GfxKey: 0

ButLayout: 9

Fix: 0

 

Here's my DAT for reference, although it won't help much methinks:

 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

 

System: NEO

RomName: King of Fighters 2003

Game: King of Fighters 2003

 

[Program]

2k3_p1.rom,0,800000,B87049F2,0

 

[Text]

2k3_s1.rom,0,20000,DF422440,0

 

[Z80]

2k3_m1.rom,0,20000,396E17CD,0

 

[samples]

2k3_v1.rom,0,400000,D2B8AA5E,0

2k3_v2.rom,400000,400000,71956EE2,0

2k3_v3.rom,800000,400000,DDBBB199,0

2k3_v4.rom,C00000,400000,1B90C4F,0

 

[Graphics]

2k3_c1.rom,0,800000,E42FC226,0

2k3_c2.rom,1,800000,1B5E3B58,0

2k3_c3.rom,1000000,800000,D334FDD9,0

2k3_c4.rom,1000001,800000,D457699,0

2k3_c5.rom,2000000,800000,8A91AAE4,0

2k3_c6.rom,2000001,800000,9F8674B8,0

2k3_c7.rom,3000000,800000,374EA523,0

2k3_c8.rom,3000001,800000,75211F4D,0

 

[system]

CartridgeID: 271

GfxCrypt: 0

GfxKey: 0

ButLayout: 9

Fix: 0

 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

[garyoak99]

Change System: Neo to System: NEO. This is crucial sometimes.

 

Oh, and you are totally missing this at the end:

 

[system]

CartridgeID: 271

GfxCrypt: 0

GfxKey: 0

ButLayout: 9

Fix: 0

 

Here's my DAT for reference, although it won't help much methinks:

 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

 

System: NEO

RomName: King of Fighters 2003

Game: King of Fighters 2003

 

[Program]

2k3_p1.rom,0,800000,B87049F2,0

 

[Text]

2k3_s1.rom,0,20000,DF422440,0

 

[Z80]

2k3_m1.rom,0,20000,396E17CD,0

 

[samples]

2k3_v1.rom,0,400000,D2B8AA5E,0

2k3_v2.rom,400000,400000,71956EE2,0

2k3_v3.rom,800000,400000,DDBBB199,0

2k3_v4.rom,C00000,400000,1B90C4F,0

 

[Graphics]

2k3_c1.rom,0,800000,E42FC226,0

2k3_c2.rom,1,800000,1B5E3B58,0

2k3_c3.rom,1000000,800000,D334FDD9,0

2k3_c4.rom,1000001,800000,D457699,0

2k3_c5.rom,2000000,800000,8A91AAE4,0

2k3_c6.rom,2000001,800000,9F8674B8,0

2k3_c7.rom,3000000,800000,374EA523,0

2k3_c8.rom,3000001,800000,75211F4D,0

 

[system]

CartridgeID: 271

GfxCrypt: 0

GfxKey: 0

ButLayout: 9

Fix: 0

 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

<{POST_SNAPBACK}>

 

That extra bit at the end helped a bit but Nebula still says I'm missing several files:

 

271-p1.bin

271-p2.bin

271-s1.rom, Bad CRC. Expected 7C7829AA, Found C47F8AC3

271-m1d.bin, File not found

 

That other DAT provided doesn't help me because my romset is named differently.

[Agozer]

Then just rename the stuff that needs renaming. The DAT values aren't set in stone, geez.

 

Make sure that the set name matches yours to the letter. If it doesn't, change them to match yours.

 

Make sure that the filenames match yours to the letter. If they don't, change them to match yours.

 

Make sure that the CRC values match yours to the letter. If they don't, change them to match yours.

 

Make sure that the filesizes in hex match yours. If they don't, change them to match yours.

 

 

 

Are you beginning to see a pattern here?

[garyoak99]

Then just rename the stuff that needs renaming. The DAT values aren't set in stone, geez.

 

Make sure that the set name matches yours to the letter. If it doesn't, change them to match yours.

 

Make sure that the filenames match yours to the letter. If they don't, change them to match yours.

 

Make sure that the CRC values match yours to the letter. If they don't, change them to match yours.

 

Make sure that the filesizes in hex match yours. If they don't, change them to match yours.

 

 

 

Are you beginning to see a pattern here?

<{POST_SNAPBACK}>

 

Yep, I spent twenty minutes changing the filenames, setnames and CRC values so that they match the ones in the DAT file.

 

Now there seems to be only 1 problem left:

 

271-m1.rom, Wrong size. Expected 262144, Found 524288

 

I don't see any values in the DAT file that look like size requirements.

How do I change the filesizes in hex then?

Edited March 20, 2006 by garyoak99

[Agozer]

...

 

I hope that you are changing the DAT contents to match your set, and not the other way around, like that first sentence of yours indicated.

 

The filesize in hex is after the filename and the after the first indexing number. When there are multiple C or V roms, the indexing number uses pretty much a predefined format, but I'm sure you have little trouble with those if you look at my DAT example.

 

2000000 = 32MB (33,553,432

800000 = 8MB (8,388,608

600000 = 6MB

400000 = 4MB (4,194,304

200000 = 2MB (2,097,152

100000 = 1MB

80000 = 512kB (524,288

40000 = 256kB (262,144

20000 = 128kB (131,072

10000 = 64kB

 

Are you beginning to see a pattern again?

Edited March 20, 2006 by Agozer

[garyoak99]

...

 

I hope that you are changing the DAT contents to match your set, and not the other way around, like that first sentence of yours indicated.

 

The filesize in hex is after the filename and the after the first indexing number. When there are multiple C or V roms, the indexing number uses  pretty much a predefined format, but I'm sure you have little trouble with those if you look at my DAT example.

 

2000000 = 32MB (33,553,432 B )

800000 = 8MB (8,388,608 B )

600000 = 6MB

400000 = 4MB (4,194,304 B )

200000 = 2MB (2,097,152 B )

100000 = 1MB

80000 = 512kB (524,288 B )

40000 = 256kB (262,144 B )

20000 = 128kB (131,072 B )

10000 = 64kB

 

Are you beginning to see a pattern again?

<{POST_SNAPBACK}>

 

Yep, I modified the DAT file so it matched the contents of my romset.

I changed the file size successfully too.

Then when I loaded it in the Nebula Loader; all I got was a green screen!

 

This is what I now have in my DAT after all those changes:

 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

System: NEO
RomName: kof2003
Game: King of Fighters 2003 (Bootleg)

[Program]
271-c1d.rom,0,800000,E42FC226,0
271-c2d.rom,1,800000,1B5E3B58,0

[Text]
271-s1.rom,0,20000,C47F8AC3,0

[Z80]
271-m1.rom,0,80000,E86AF8F,0

[Samples]
271-v1d.rom,0,400000,D2B8AA5E,0
271-v2d.rom,400000,400000,71956EE2,0
271-v3d.rom,800000,400000,DDBBB199,0
271-v4d.rom,C00000,400000,1B90C4F,0

[Graphics]
271-c1d.rom,0,800000,E42FC226,0
271-c2d.rom,1,800000,1B5E3B58,0
271-c3d.rom,1000000,800000,D334FDD9,0
271-c4d.rom,1000001,800000,D457699,0
271-c5d.rom,2000000,800000,8A91AAE4,0
271-c6d.rom,2000001,800000,9F8674B8,0
271-c7d.rom,3000000,800000,374EA523,0
271-c8d.rom,3000001,800000,75211F4D,0

[System]
CartridgeID: 271
GfxCrypt: 0
GfxKey: 0
ButLayout: 9
Fix: 0

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

 

What changes would you suggest?

Edited March 21, 2006 by Agozer

[Agozer]

Why did you place two C roms that you've already commented in the Graphics section into the Program section where the P rom(s) should be?

 

...

 

And then you failed to comment in the P roms. :/

 

You need to be thorough or you'll never get any games working.

[garyoak99]

Why did you place two C roms that you've already commented in the Graphics section into the Program section where the P rom(s) should be?

 

...

 

And then you failed to comment in the P roms. :/

 

You need to be thorough or you'll never get any games working.

<{POST_SNAPBACK}>

 

I just made the correction and now my DAT looks like:

 

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

System: NEO
RomName: kof2003
Game: King of Fighters 2003 (Bootleg)

[Program]
271-p1.rom,0,400000,92ED6EE3,0

[Text]
271-s1.rom,0,20000,C47F8AC3,0

[Z80]
271-m1.rom,0,80000,E86AF8F,0

[Samples]
271-v1d.rom,0,400000,D2B8AA5E,0
271-v2d.rom,400000,400000,71956EE2,0
271-v3d.rom,800000,400000,DDBBB199,0
271-v4d.rom,C00000,400000,1B90C4F,0

[Graphics]
271-c1d.rom,0,800000,E42FC226,0
271-c2d.rom,1,800000,1B5E3B58,0
271-c3d.rom,1000000,800000,D334FDD9,0
271-c4d.rom,1000001,800000,D457699,0
271-c5d.rom,2000000,800000,8A91AAE4,0
271-c6d.rom,2000001,800000,9F8674B8,0
271-c7d.rom,3000000,800000,374EA523,0
271-c8d.rom,3000001,800000,75211F4D,0

[System]
CartridgeID: 271
GfxCrypt: 0
GfxKey: 0
ButLayout: 9
Fix: 0

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

 

I run the Nebula Loader and it crashes without any errors. I get the usual Windows XP pop-up:

 

nebula.exe has encountered a problem and needs to close. We are sorry for the inconvenience.

 

If you were in the middle of something, the information you were working on might be lost.

 

Please tell Microsoft about this problem.

We have created an error report that you can send to us. We will treat this report as confidential and anonymous.

 

What might be the problem now?

[Agozer]

Hard to say. Are you starting Nebula with nl.exe (The Nebula unlocker/loader executable)?

 

You must have mentioned this before, but the set works perfectly in NeoRAGEx, yes?

 

EDIT: It seems that you had some serious graphics corruption in NRX, which means that there's something wrong with the set you have, and that can lead to Nebula crashing unexpectedly.

[garyoak99]

Hard to say. Are you starting Nebula with nl.exe (The Nebula unlocker/loader executable)?

 

You must have mentioned this before, but the set works perfectly in NeoRAGEx, yes?

 

EDIT: It seems that you had some serious graphics corruption in NRX, which  means that there's something wrong with the set you have, and that can lead to Nebula crashing unexpectedly.

<{POST_SNAPBACK}>

 

Yes, I was starting Nebula using the Loader executable.

 

Yes, it was starting with some serious graphics corruption in NeoRAGEx. I tried using your DAT file but even after I changed their filenames to match the ones in the romset; it still came up with the message that ALL the files were missing!

 

I'll definitely try a different romset and emulator then since there is probably something wrong with this one.