King Of Fighters 2003 (kof2003.zip) News III

[alphabetman]

Alphabeta, if you get that guy who needed to know what the byte number was in binary in contact with me, I can help him.  I have to read up on the bytes in hex and stuff, but I'll figure it out soon.

For the sake of uncluttering this thread, anyone who is working on this should consider just posting information concerning this there, not here. You can contact NeoGhost in this thread.

 

http://excoboard.com/exco/thread.php?forum...7&threadid=4549

Edited February 2, 2004 by alphabetman

[iamnotagod]

How does the rom work in MAME? Has anyone tried contacting the person who did that work in the first place? Perhaps they have some useful information.

[Agozer]

How does the rom work in MAME?  Has anyone tried contacting the person who did that work in the first place?  Perhaps they have some useful information.

I think we would have found the answer already if all it would take is to see how MAME does it.

[Xeon]

also the ROM is stolen, meaning unintentionally released (which isnt half-bad on our end ). can anybody even expect help from someone they've stolen from??

 

i dont think so. lets just get our asses working on the ROMs (though ive no clue now what to do next - i dont think working in 1MB chunks can do the trick).

[James]

also the ROM is stolen, meaning unintentionally released (which isnt half-bad on our end ). can anybody even expect help from someone they've stolen from??

 

i dont think so. lets just get our asses working on the ROMs (though ive no clue now what to do next - i dont think working in 1MB chunks can do the trick).

well i still think we should have a good look at the mame driver for kof2003 could be a good idea.

 

 

it loads the p roms. and going by the p roms region

 

ROM_START( kof2003 )

ROM_REGION( 0x800000, REGION_CPU1, 0 )

ROM_LOAD16_WORD_SWAP( "271-p1.bin", 0x100000, 0x400000, CRC(92ed6ee3) )

ROM_LOAD16_WORD_SWAP( "271-p2.bin", 0x500000, 0x200000, CRC(5d3d8bb3) )

ROM_CONTINUE( 0x000000, 0x100000 )

ROM_CONTINUE( 0x000000, 0x100000 )

 

the rom load is weird compaired to other rom loads for neogeo.

 

and i am sure there could be some info here as well

 

static unsigned short kof2003_tbl[0x1000];

 

static READ16_HANDLER( kof2003_16_r )

{

return kof2003_tbl[offset];

}

static WRITE16_HANDLER( kof2003_16_w )

{

UINT32 bankaddress;

kof2003_tbl[offset]=(kof2003_tbl[offset]&mem_mask)|((~mem_mask)&data);

if(offset>0xff9) return;

bankaddress=((kof2003_tbl[0xff8]>>|(kof2003_tbl[0xff9]<<)+0x100000;

*(((UINT8 *)kof2003_tbl)+0x1ff0)=0xa0;

*(((UINT8 *)kof2003_tbl)+0x1ff1)&=0xfe;

*(((UINT8 *)kof2003_tbl)+0x1ff3)&=0x7f;

neogeo_set_cpu1_second_bank(bankaddress);

*(((unsigned char *)memory_region(REGION_CPU1))+0x58196)=kof2003_tbl

[0xff9]&0xff;

}

 

DRIVER_INIT( kof2003 )

{

install_mem_read16_handler (0, 0x2fe000, 0x2fffff, kof2003_16_r);

install_mem_write16_handler (0, 0x2fe000, 0x2fffff, kof2003_16_w);

init_neogeo();

}

Edited February 2, 2004 by james

[Agozer]

So the program read and writes the mem handler and then proceeds to initialize the banking methods + the offsets and hex values... (or is it the other way around?) What am I missing here?

Edited February 2, 2004 by Agozer

[Lucian]

I have a control issue with Mame32. I play Kof, the VS series and all sorts of games with my friends at college. For some strange reason I cant get both my controllers to play in mame32 with KOF2k3. I have a Belkin Nostromo (the one that looks like a ps2 pad, you can find it on Liksang.com) and a Saitek P880 with the six button set up and dual analog sticks. I dont know what to do since I have never had this problem with any of my emulators cept for godforsaken MAME. Why!? Oh Why does MAME hate me so!?

 

I just tried my PS2(the sony controllers) with my adapters that I had also gotten from Liksang.com and they work with all my emulators and games cept for flippin Mame. Whoever built Mame to be unresponsive with multiple controllers is flippin lame I tell you. LAME!!

 

I just started trying to play multiplayer in MAME and it's also my first time using mame so I figure Im just MAME illiterate. Everything else is so goddamn easy to figure out any way. As James said "It's so easy to use my 5yr old niece could use it." or something of that nature. Damn babies and thier super intelligence.

Edited February 2, 2004 by Lucian

[Urquan2x]

I have a control issue with Mame32.  I play Kof, the VS series and all sorts of games with my friends at college. For some strange reason I cant get both my controllers to play in mame32 with KOF2k3. I have a Belkin Nostromo (the one that looks like a ps2 pad, you can find it on Liksang.com) and a Saitek P880 with the six button set up and dual analog sticks.  I dont know what to do since I have never had this problem with any of my emulators cept for godforsaken MAME.  Why!? Oh Why does MAME hate me so!?

 

I just started trying to play multiplayer in MAME and it's also my first time using mame so I figure Im just MAME illiterate. Everything else is so goddamn easy to figure out any way. As James said "It's so easy to use my 5yr old niece could use it." or something of that nature. Damn babies and thier super intelligence.

odd... i use two saitek p880s and mame works just fine

what u can do is copy and paste the old folders of mame into the mame one u use for kof2k3

 

if that doesn't help well.... perhaps its an hardware issue

[cosmic_lord]

0x29e is a hex byte.

 

the 0x is merely to indicate it's a hex byte. then, the 29 e must be converted to binary.

 

we break it into two groups.

 

29 e

 

29 in hex is 00101001, or more simply 101001 in binary

e in hex is 1110 in binary. So...

 

29e in hex is 001010011110, or more simply 1010011110 in binary.

Edited February 2, 2004 by cosmic_lord

[Songoko]

Please, can someone tell me where to get King of Fighters 2003 rom on Mame32?

 

Thanks

[Juniel]

There are links somewhere in this post.....I suggest you read the whole thing...

[cosmic_lord]

A new forum sounds good. But I think that it should only be accessible to those who are actually working on this. I know that may not be possible, but there's always a chance that one can get cluttered too. Oh well, we can move from forum to forum like lochusts ^.^

 

Anyway, that guy is very correct. I checked that string, it does indeed appear in every p1 rom I looked for it in. However, I looked in the p2 of mslug4nd and it's not there, so that also confirms you can delete one of the two, be it p2_3 or p2_4. Either way, when you do delete one, the other one WILL have to be moved to the p1 rom. But there's still a problem, I mean, for all we know, the right sequence could be P2_4 + p1_4 + p2_2 + p2_1 for the p1 file, and the p1_1 p1_2 and p1_3 are supposed to go in the p2 file. I'm not very proficient in ascii... I can sort of understand the basics of ascii though. I do understand hex... I just havne't worked with it in over a year...lol.

 

One thing I do think, I don't have much of a reason to think it, but, I can't recall seeing a 7MB p file. I've seen 6 and 8... maybe I've seen 7 and just don't remember, but back to what I was saying before, about the rom banking, I read somewhere that mslug5 and kof2003 use the same rom banking. If that's true, then it's possible that the rom banking has been correct all along and the p roms really are skewed! It's just a hunch, but since the p file for mslug5 is 6 mb (for mine anyway, it works, I beat it and all so I guess it's right) I have a hunch that one of the remaining 6 files from the group p1_1 p1_2 p1_3 p1_4 p2_1 p2_2 is also unnecessary. That would structure the prom (or p roms if you split it into two pieces) like mslug5. I think that could give us a better guideline to go on as to how big it needs to be or at least something helpful. Maybe I'm just spouting off here, but hey it's an idea isn't it?

 

Here's the dat file for my mslug5 just to make sure you know which one I have:

 

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

 

System: Neo

RomName: mslug5nd

Game: Metal Slug 5 (Fully Decrypted)

Parent: mslug5

 

[Program]

268-p1d.bin,0,600000,975EB06A,0

 

[Text]

268-s1d.bin,0,20000,64952683,0

 

[Z80]

268-m1d.bin,0,20000,6FA01C9A,0

 

[samples]

268-v1.bin,0,400000,C3540E0D,0

268-v2.bin,400000,400000,77BD2F4,0

268-v3.bin,800000,400000,39B14567,0

268-v4.bin,C00000,400000,969FF3B2,0

 

[Graphics]

268-c1d.bin,0,800000,969C0D62,0

268-c2d.bin,1,800000,C69AE867,0

268-c3d.bin,1000000,800000,D7BEAEAF,0

268-c4d.bin,1000001,800000,E1B1131B,0

268-c5d.bin,2000000,800000,2FA1A5AD,0

268-c6d.bin,2000001,800000,6DE89589,0

268-c7d.bin,3000000,800000,97BD0C0A,0

268-c8d.bin,3000001,800000,C0D5BC20,0

 

[system]

CartridgeID: 268

GfxCrypt: 0

GfxKey: 0

ButLayout: 9

Fix: 0

 

Maybe somebody has a mame driver for mslug5 they could post? We could compare the rom bankings that way.

[Songoko]

I tried some links that I found, for example www.suprnova but it isn`t now there!

[Juniel]

I used devil666's link...it came with MAME32+.....

 

EDIT:speaking of such, I have a question.

 

If I wanna get it working on Kawaks or Nebula( once KOF starts running on it)

 

Do I need to download the files again or can I edit the MAME version I have, to

 

make it run on Nebula or kawaks?

Edited February 2, 2004 by Juniel

[cosmic_lord]

I used devil666's link...it came with MAME32+.....

 

EDIT:speaking of such, I have a question.

 

If I wanna get it working on Kawaks or Nebula( once KOF starts running on it)

 

Do I need to download the files again or can I edit the MAME version I have, to

 

make it run on Nebula or kawaks?

Generally there is no "MAME version" or whatever... but assuming thetheory we're going on is correct, for some reason mame must have an automated process of reassembling the p roms.

 

Anyway, in short, no. If you have to download anything new, it will be the new p rom(s), which would be like 8 megs max. Probably around 6 or 7 megs. It would be a bit smaller than that zipped though