James

you are missing a file from the neogeo bios. try and find a newer version of the neogeo.zip

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(); }

Sengoku 2 has been updated are the roms updated to mame 79

Ok guys I have started this thread just for the rom status for Kawaks, Nebula, NeorageX and for the work on the p rom. So please post news or some tips and keep it with the topic of this thread. All other Topics to be posted here: http://www.1emulation.com/forums/index.php...?showtopic=4580 Please note anyone who post off topic will be deleted without notice!

To all members please keep with the topic. if anyone else posts off topic i will have to lock the thread. please stay with the topic.or do not post as all thank you

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(); }

M1 (128 Kb) & M1 (64 Kb) is in fact the same thing, because when U split the first one (128 Kb) in 2 parts, U can notice the 2nd part (64 Kb) is a dummy file. So, M1 (64 Kb) is useless. how is the m1 64k useless if it works with no problem.

Good luck i have spent many hours on this and so far no good

yes maybe. I like the other emulators as well. but mame is the one i use the most.

This is a reminder to anyone who posts things withouit checking what has been posted allready. will be deleted thanks

dam here is another one who does not read. P' ROMS: There's someting very interesting with the P' roms. When I donwloaded the game (the same day it was released), I wanted to play it with anything else, I hate MAME (30 fps/buggy). So, I opened it with a HEX editor and searched this: 45 4e 2d 4f 45 47 (EN-OEG, typically in the header). It was found at the offset 00200100, and the offset 00200108 contains 71, the cartrigde ID. Eureka! So, if you chop them into 8 pieces (1 MB), the last two pieces of the P2 are the same thing (using the BAT attached, P2_3.bin and P2_4.bin). And they have a typical P1 header. If you run the game with Nebula only with this piece, it will partially work (the BIOS only, and some "parts"). miko from Romshare created an interesting theory that the rom is "cooked": the roms were chopped and joined in a different order. It may be 1 MB pieces, or smaller. This was supposely to protect the game and make it run only with that MAME. Anyway, we can try to join the roms all again. Unfortunately, may computer takes 17 minutes to load the game, so this would be a big loss of time. Using the BAT bellow, you can try. The P2_4 and P2_3 are the same thing, so discard one of them, and use the other to be the head. There are 6 pieces left. Try one by one, eg.: P2_4 + P1_1, if doesn't works, try P2_4 + P1_2, and so on. Join them using this DOS, command: eg.: copy /b "p2_4.bin" + "p1_1.bin" "test.rom" Zip this test.rom into a ZIP name "kof2003t.zip" and place it in Kof2003's directory. Use this DAT to load the game: %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% System: Neo RomName: kof2003t Game: The King of Fighters 2003 (Test) Parent: kof2003 [Program] test.rom,0,[insert size],0,0 [Text] 271-s1.rom,0,20000,7C7829AA,0 [Z80] 271-m1d.bin,0,80000,0E86AF8F,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,01B90C4F,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 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Size is in Hexa, so 1 MB is 100000, 2 MB 200000, and so on. If you succeed with 2 parts, join another, until you rebuild the complete ROM. Good luck! Download the Do-It-Yourself Kit (3,7 KB) http://kof2003.web1000.com/test.zip with gamecop consent i would like to delete the repeated posts

well ok you try to do something as well.

so far there is no need for a patch. all is needed is to work out what combination of the spilt files . once that is done a patch could be made.

i think you missed the point. this has allready been posted. the fact is no one seems to check what was posted before and end up posting the same thing over and over.

how many dam more times are we going to get this link. it was just posted on the last page (page 48). no wonders there is to many pages. this very thread alone has so much crap in it. it is beyond the joke so before you post. please read the thread.

some of the info on how the mame driver should be written is wrong hmm.... should someone notify him? i dont know squat about mame drivers the error was on my part it is all correct just for forgot the driver for mame32k needs an extra part

some of the info on how the mame driver should be written is wrong

Keep trying the servers maybe busy.

Uni-BIO Does IT Effect The Spites,cause I Seen Shingo using No Fire Or Am I Worng Shingo Does Not Hav A SP.Ebility To Make Fire(Not A Gr8 Fans Of Shingo) you are not able to use the uni-bios unless you can see how to set it up. there seems to be a small problem with the driver and loading the uni-bios.however the other MVS bios's works fine,

please keep to the topic of this thread anymore offtopic posts will be deleted .

no sorry i would have to use an outdated emulator to do that . i am in the hope that someone who knows about it will help me compile this into mame 79

i am not sure about this. once the correct driver is worked out.those who compile MACmame should be able to ge it to run. maybe with some changes. youre right, MAME code is portable. however, im trying to show him what he can expect later. judging by his post, you can clearly say he cant compile for his own (rom renaming?) and since majority here uses any Win32 MAME (Windows in itself actually), thats how i got the conclusion that only Windows users may get to enjoy the game in MAME. Yes i get it. then he has to find someone who can compile MACmame for him

Update i have now updated my mame compile thanks to Andrew at Arcade@home now supports King of fighters 2003 http://members.westnet.com.au/the%2Dkula/mame.html please note for some reason it wont work with the uni-bios so that means no console mode the uni-bios works the problem is you cannot see it

Indeed, and a "recommending a P4" is just nasty. Sure, everyone has lots and lots of cash handy just to upgrade their computer... well buy an old P4 then.The P4 is old now. here is a tip build your own Computer Save lots of money.

would you like a loan of my walking stick ? oh yeah sorry if you see my edit in your post. I clicked the wrong one. see old age is getting to me.