cosmic_lord

Yea, about 10 minutes after I posted that Edit to my original post, I tried doing that and it works every time when I do it right, but I didn't say anything cuz I figured somebody might know something better to try . Anyway, thanks. I had problems with that move on SvC for a while now, and it bugged the crap out of me. I finally got off my ass and figured out how to do it so it's cool now.

There was a link to a supposed NRX version in one of the threads, and I couldn't get to it last night but I kept refreshing and finally got to it... it's the same dman one we've been using, so it was false advertising. Bah.

Here's a quick question about SvC Plus. After doing the Kin 1211 Shiki: Yaotome (qcf,hcb+P), can anyone get the followup Ura 306 Shiki: Saika (qcfx4+AC) to work? I've tried the blasted thing a blue million times. I never had any trouble getting it to work on any of the KOF games. The CPU controlled Iori has never done the followup on me, so I figured they might have taken it out... I don't know. Either way this irritates me [Edit] OK... I used a cheat to make the CPU player 2 character Iori, and turned the difficulty up to Expert and just sat there letting him smack me, and he finally did the damn thing... so I know it's there. I still think the timing must have been altered greatly from the KOF games, because I only managed to perform this move like once after trying it a dozen times in Practice just now. Any help for this new timing?

I know this part of my post is kind of off topic, I just wanted to let everyone know why I haven't posted in a couple of days. I've been playing Garou:MOTW for the first time... (yes I know that is sad.) Anyway, so there's a KOF2003 for NRX now? *crosses fingers praying it's not fake*

So... are you saying that if the p2 rom was changed to be 0x200000 in size, tand still have that same crc, the ROM_CONTINUE portion would be unnecessary?

You'd have to compile your own version of MAME 32k. You would do this in the same manner that you would compile MAME 32 plus to run this game, except when adding the driver, there's an extra section you have to add: Add the following code in neogeo.c just before ROM_START( nam1975 ) static UINT32 cpu1_second_bankaddress; void neogeo_set_cpu1_second_bank(UINT32 bankaddress) { data8_t *RAM = memory_region(REGION_CPU1); cpu1_second_bankaddress = bankaddress; cpu_setbank(4,&RAM[bankaddress]); } void neogeo_init_cpu2_setbank(void) { UINT8 *mem08 = memory_region(REGION_CPU2); cpu_setbank(5,&mem08[bank[0]]); cpu_setbank(6,&mem08[bank[1]]); cpu_setbank(7,&mem08[bank[2]]); cpu_setbank(8,&mem08[bank[3]]); } static void neogeo_init_cpu_banks(void) { neogeo_set_cpu1_second_bank(cpu1_second_bankaddress); neogeo_init_cpu2_setbank(); } For a compile tutorial, check the General Neo Geo emulation board, I have a very in depth tut on compiling the newest version of mame32 plus. So if mame32k has been updated to version.79, then it would work exactly the same way exccept to add in the code above would be an extra step, and you'd be using the mame32k source instead of the mame32 plus source.

I'll give two answers. The more serious one, Iori, because he's definitely the most outdated char. on't get me wrong, I love Iori to death, he's one of my favorites, but he's had the exact same outfit ever since KOF95, lol. The second answer, hm... I guess I'd have to say Ash, because he looks like a flaming transvestite.

Allright, I looked into the question I asked earlier. Apparently, in the driver for kof2003, in the line ROM_LOADp2 etc etc, 0x500000,0x200000 the 500000 is the address it loads the p2 rom to in the memory region. I'm not used to writing drivers so I don't know what that means, but somebody should. But still what bugs me is that the mame driver lists the p2 rom as 0x200000 for its size. The p2 rom I have (that works on mame with this driver) is 0x400000 and has the same CRC as the p2 rom the driver reports as 0x200000. How? Mame must somehow dice up the p2 rom... I've tried all the combinations of 2 roms I can think of to try and get the right CRC and none of them worked, so I don't know. Anyway, I was thinking, in kawaks or nebula dat files. For example, kof2003 271-p1.bin,0,400000,92ed6ee3,0 Well, from running these tests, I know that if you leave the CRC slot with a 0, nebula determines it dynamically. So, I'm assuming that the 0 following the CRC slot is the SHA1 slot, and every rom I've seen leaves it with a 0 to let it be determined dynamically because CRC is accurate enough to identify a rom. But I'm going to put in the right SHA1 values and see if it helps any, give me some feedback here people.

Actually double posting isn't much to him. In the other thread that we moved here from, he posted the exact same thing like 8 times in a row.

Basara, I compiled my own version of Mame32 Plus version.79 to run it... and I wrote a very in-depth tutorial on how to do that. I started it in the NextGen Emulation section, but I think it got moved to General NeoGeo Emulation.

Well, it was just a theory, and it gave me something to try during boredom, which is better than doing nothing . Anyway, I think we can all agree that the problem is in the p roms... From what you just said, if you re structured the p rom in a hex editor to make it satisfy the forumla for the typical bank switch, would that not work? I do believe there is something to the "cooked" part, though. The kof2003 p2 rom has the typical p1 header in it, twice. Bah... why can't Nebula and Kawaks be open source?

I'm on windows XP, and what I meant by Nebula having an errror, when I load a bad p rom or something it comes up with one of those error report dialogs, and nebula closes when I click on don't report. Normally when it does that, Nebula goes to "Not Responding" status in the task manager, maybe it would be possible to use that in some way, I don't know. If worse comes to worse, I guess you make the program omit the part about checking it in nebula, and have it rename test.rom to liek 1.rom and then when it repeats itself, to 2.rom and so on, so you owuld have output p files to test. I know there would be like 720 of them, but you could sit there for a few hours and test them one by one with nebula yourself, that way you could see if each one worked or not. If you don't want to do that, if you can configure the script to do what i said you can send it to me and I will when I have time.

Here's a quick question: In this line of a dat file for example, I'll use kof2003 271-p1.bin,0,400000,crc,0 What do those two single 0's represent? I know the 400000 is the size of the p file, and the crc is the crc, but what are the other two? I think these are important questions, because I was looking over the beginning of the 2003 driver for mame. According to that, a dat file for kof2003 would be like 271-p1.bin,100000,400000,92ed6ee3 271-p2.bin,500000,200000,5d3d8bb3 I left off the typical,0 at the end there, because I think the ROM_CONTINUE( 0x000000, 0x100000 ) part might have something to do with it. Maybe it would be like this 271-p1.bin,100000,400000,92ed6ee3,0,100000 271-p2.bin,500000,200000,5d3d8bb3,0,100000 I'm not sure, but I've never seen that ROM_CONTINUE thing before, so it must do something different when writing a dat file liek that. Anyway, one thing that strikes me about the mame driver, is the p2 file. It lists the p2 file's size as 200000, but still gives it the same CRC as the p2 file I have is, and that file has a size of 400000. If that's right, I think two of the p2 files are unnecessary, but I already tried adding p2_1 + P2_2 and then p2_2 + p2_1, and the file didn't have the same CRC as the original p2 file, so I'm going to try all teh combinations I can of 2 files.

All I can tell from looking at those drivers is that there are at least some similarities... like the cpu1 in the rom start for both kof2003 and mslug5. I don't use mame unelss I have to, so I really don't know how to read these too well. That's more your dept I think james. Bah. It aggrovates the hell out of me that I can't figure this damn thing out.

Ok, everyone that's helping with the p rom project, switch over to the thread here. Everyone else is welcome to look at this topic, but it can't get off topic like this thread did, we don't want this new one all cluttered and redundant. I'm not a moderator or admin but I think james has the same opinion I do and he is hehe.

Is it possible to write a program that does the following: 1. Create a list, with p2_2.bin, p2_1.bin, p1_4.bin, p1_3.bin, p1_2.bin, p1_1.bin as elements of this list. I'll call this list A to avoid confusion. 2. Randomly select a file from this list, and remove it from list A and add it to a new list, list B. 3. Randomly select a file from the remaining files in list A and add it as the second term in list B. Repeat this process until list A is empty and list B has all of list A's terms, but arranged randomly. 4. Open the command prompt and execute 'copy /bin "p2_4.bin" + "list B term 1" + "list B term 2" + "list B term 3" + "list B term 4" + "list B term 5" + "list B term 6" "test.rom" but with the filenames instead of list B term x. 5. (My nebula folder is located in Emulators\Nebula\ from the desktop where I keep the p files) Add test.rom to Emulators\Nebula\roms\kof2003t.zip; copy test.rom's CRC and store it as the variable C. Create text from kof2003t.dat in your romdata folder, but for the test.rom CRC, input A and save this output file to Emulators\Nebula\romdata\kof2003t.dat 6. Open Nebula and run kof2003t. 7. If Nebula has an error (which it usually does when u put the test.rom file's CRC in instead of 0), then the program will repeat itself over again, but since the list B was generated randomly, it will do a different chain of files, but this chain always starts with p2_4.bin. If no error occurs, the program will stop. I have done a lot of programming in BASIC, and a little with javascript and ActionScript (in Flash). I know most of this is possible, I'm not sure about steps 5 and 6, particularly 6. I think this would be a pretty simple program. But where these values would be generated randomly it would probably have to run for a long time before it got the right combination... but if somebody else knows how to do it and make it remember and avoid what combinations it took, it would go a lot faster. Maybe I'm just crazy, but I think this could be done mostly in BASIC, so I'm sure that anyone who knows an advanced language could do this without trouble, I'm just not sure that steps 5 and 6 can be done with programming.

ROM_START( mslug5 ) ROM_REGION( 0x800000, REGION_CPU1, 0 ) ROM_LOAD16_WORD_SWAP( "268-p1.bin", 0x000000, 0x800000, CRC(3F1CF3D2) SHA1(2C85EB5ACDEDE4816675B91F8989C9E13C1573F8) ) ROM_REGION( 0x20000, REGION_GFX1, 0 ) ROM_FILL( 0x000000, 0x20000, 0 ) ROM_REGION( 0x20000, REGION_GFX2, 0 ) ROM_LOAD( "sfix.sfx", 0x000000, 0x20000, CRC(354029fc) SHA1(4ae4bf23b4c2acff875775d4cbff5583893ce2a1) ) NEO_BIOS_SOUND_128K( "268-m1d.bin", CRC(6FA01C9A) SHA1(3DAB7593BFCCE318D22EC3DF672EE3B4AB73DCF5) ) ROM_REGION( 0x1000000, REGION_SOUND1, ROMREGION_SOUNDONLY ) ROM_LOAD( "268-v1.bin", 0x000000, 0x400000, CRC(C3540E0D) SHA1(BF7CA3ABE291B28A4CFAEF791F0C556CC98AD8D8) ) ROM_LOAD( "268-v2.bin", 0x400000, 0x400000, CRC(077BD2F4) SHA1(1699959D17F8C7113CEBDB9DA2E1CD18CE48486C) ) ROM_LOAD( "268-v3.bin", 0x800000, 0x400000, CRC(39B14567) SHA1(1658612A93BA30130F9260BC41D3F18F6B90C1E7) ) ROM_LOAD( "268-v4.bin", 0xc00000, 0x400000, CRC(969FF3B2) SHA1(50FECEB741A1C08B000B077A33151AB1352EB798) ) NO_DELTAT_REGION ROM_REGION( 0x4000000, REGION_GFX3, 0 ) ROM_LOAD16_BYTE( "268-c1.bin", 0x0000000, 0x800000, CRC(27d59de8) SHA1(DE3C5CFA980CCA2FAB0416AC0D292948B5D4C9C3) ) /* Plane 0,1 */ ROM_LOAD16_BYTE( "268-c2.bin", 0x0000001, 0x800000, CRC(e600dee1) SHA1(3198EE5C7C2C7563B49EBD9F7BA95D9B0B303F6C) ) /* Plane 2,3 */ ROM_LOAD16_BYTE( "268-c3.bin", 0x1000000, 0x800000, CRC(b650f098) SHA1(99443EA4C1BAB45F1977A390EB7E1A0163915110) ) /* Plane 0,1 */ ROM_LOAD16_BYTE( "268-c4.bin", 0x1000001, 0x800000, CRC(10499589) SHA1(68A36D336582069E79AD481638D92F57C4CD6523) ) /* Plane 2,3 */ ROM_LOAD16_BYTE( "268-c5.bin", 0x2000000, 0x800000, CRC(19352405) SHA1(4AE15D29BA979601598EDDF8905072FE1D9E0A98) ) /* Plane 0,1 */ ROM_LOAD16_BYTE( "268-c6.bin", 0x2000001, 0x800000, CRC(bbec8745) SHA1(86A6C036BF51AF516FEA83A30874026EC1586A83) ) /* Plane 2,3 */ ROM_LOAD16_BYTE( "268-c7.bin", 0x3000000, 0x800000, CRC(fe2c1338) SHA1(30F3280FE527098ECF46541CC645A59B366105EA) ) /* Plane 0,1 */ ROM_LOAD16_BYTE( "268-c8.bin", 0x3000001, 0x800000, CRC(ecce3141) SHA1(B5D0D81D5CC624538B0651C568295E578A1330D1) ) /* Plane 2,3 */ ROM_END ROM_START( mslug5nd ) ROM_REGION( 0x800000, REGION_CPU1, 0 ) ROM_LOAD16_WORD_SWAP( "268-p1.bin", 0x000000, 0x800000, CRC(3F1CF3D2) SHA1(2C85EB5ACDEDE4816675B91F8989C9E13C1573F8) ) ROM_REGION( 0x20000, REGION_GFX1, 0 ) ROM_FILL( 0x000000, 0x20000, 0 ) ROM_REGION( 0x20000, REGION_GFX2, 0 ) ROM_LOAD( "sfix.sfx", 0x000000, 0x20000, CRC(354029fc) SHA1(4ae4bf23b4c2acff875775d4cbff5583893ce2a1) ) NEO_BIOS_SOUND_128K( "268-m1d.bin", CRC(6FA01C9A) SHA1(3DAB7593BFCCE318D22EC3DF672EE3B4AB73DCF5) ) ROM_REGION( 0x1000000, REGION_SOUND1, ROMREGION_SOUNDONLY ) ROM_LOAD( "268-v1.bin", 0x000000, 0x400000, CRC(C3540E0D) SHA1(BF7CA3ABE291B28A4CFAEF791F0C556CC98AD8D8) ) ROM_LOAD( "268-v2.bin", 0x400000, 0x400000, CRC(077BD2F4) SHA1(1699959D17F8C7113CEBDB9DA2E1CD18CE48486C) ) ROM_LOAD( "268-v3.bin", 0x800000, 0x400000, CRC(39B14567) SHA1(1658612A93BA30130F9260BC41D3F18F6B90C1E7) ) ROM_LOAD( "268-v4.bin", 0xc00000, 0x400000, CRC(969FF3B2) SHA1(50FECEB741A1C08B000B077A33151AB1352EB798) ) NO_DELTAT_REGION ROM_REGION( 0x4000000, REGION_GFX3, 0 ) ROM_LOAD16_BYTE( "268-c1d.bin", 0x0000000, 0x800000, CRC(969C0D62) SHA1(DE3C5CFA980CCA2FAB0416AC0D292948B5D4C9C3) ) /* Plane 0,1 */ ROM_LOAD16_BYTE( "268-c2d.bin", 0x0000001, 0x800000, CRC(C69AE867) SHA1(3198EE5C7C2C7563B49EBD9F7BA95D9B0B303F6C) ) /* Plane 2,3 */ ROM_LOAD16_BYTE( "268-c3d.bin", 0x1000000, 0x800000, CRC(D7BEAEAF) SHA1(99443EA4C1BAB45F1977A390EB7E1A0163915110) ) /* Plane 0,1 */ ROM_LOAD16_BYTE( "268-c4d.bin", 0x1000001, 0x800000, CRC(E1B1131B) SHA1(68A36D336582069E79AD481638D92F57C4CD6523) ) /* Plane 2,3 */ ROM_LOAD16_BYTE( "268-c5d.bin", 0x2000000, 0x800000, CRC(2FA1A5AD) SHA1(4AE15D29BA979601598EDDF8905072FE1D9E0A98) ) /* Plane 0,1 */ ROM_LOAD16_BYTE( "268-c6d.bin", 0x2000001, 0x800000, CRC(6DE89589) SHA1(86A6C036BF51AF516FEA83A30874026EC1586A83) ) /* Plane 2,3 */ ROM_LOAD16_BYTE( "268-c7d.bin", 0x3000000, 0x800000, CRC(97BD0C0A) SHA1(30F3280FE527098ECF46541CC645A59B366105EA) ) /* Plane 0,1 */ ROM_LOAD16_BYTE( "268-c8d.bin", 0x3000001, 0x800000, CRC(C0D5BC20) SHA1(B5D0D81D5CC624538B0651C568295E578A1330D1) ) /* Plane 2,3 */ ROM_END add this to the driver DRIVER_INIT section int ms5_bank_offset = 0; static WRITE16_HANDLER( mslug5_calc_bankoffset_w ) { ms5_bank_offset = (data>>12)%0x03; } static WRITE16_HANDLER( mslug5_bankswitch_w ) { neogeo_set_cpu1_second_bank( (neogeo_ram16[0x10/2] + ms5_bank_offset) << 20 ); } DRIVER_INIT( mslug5 ) { neogeo_fix_bank_type = 1; kof2000_neogeo_gfx_decrypt(0x19); install_mem_write16_handler(0, 0x2ffff0, 0x2ffff1, mslug5_bankswitch_w); install_mem_write16_handler(0, 0x2ffff2, 0x2ffff3, mslug5_calc_bankoffset_w); init_neogeo(); } DRIVER_INIT( mslug5nd ) { /* the S data comes from the end fo the C data */ { int i; int tx_size = memory_region_length(REGION_GFX1); int rom_size = memory_region_length(REGION_GFX3); UINT8 *src = memory_region(REGION_GFX3)+rom_size-tx_size; UINT8 *dst = memory_region(REGION_GFX1); for (i = 0;i < tx_size;i++) dst = src[(i & ~0x1f) + ((i & 7) << 2) + ((~i & >> 2) + ((i & 0x10) >> 4)]; } install_mem_write16_handler(0, 0x2ffff0, 0x2ffff1, mslug5_bankswitch_w); install_mem_write16_handler(0, 0x2ffff2, 0x2ffff3, mslug5_calc_bankoffset_w); init_neogeo(); } GAMEB( 2003, mslug5, neogeo, neogeo, neogeo, neogeo, mslug5, ROT0, "SNK Playmore Helmet2003", "Metal Slug 5" ) GAMEB( 2003, mslug5nd, mslug5, neogeo, neogeo, neogeo, mslug5nd, ROT0, "SNK Playmore Helmet2003", "Metal Slug 5 (decrypted C)" ) Here's the driver for mslug5, can anyone verify that it's correct?

The C roms are graphics as far as I know. What does your audit tell you? I don't use the uni bios, just the original... and when i'm playing this game i use the modded bios that fgives you the bosses. No problem Lotus

No problem . I read through a topic on compiling mame32 plus, and i saw that the people kept having problems trying to do what the guy said. What he said was right, but that was for compiling mame.78, and the people must not have understood what he was saying. That's why I tried to do mine as in-depth and explanatory as possible, and I chose version.79 since it's out now. Anyway, sorry for the bit off topic James. O have spent hours trying to fix the p roms... with no luck. I mean, I must not be doing it right. When I try with any individual piece, only the p2_4 or p2_3 works (makes it come up with black where you can access dips by pressing F2 in nebula.) That along with the info from hex editor viewing tells you that part has to be first. So when I try two parts, p2_4 + any other part, all the combinations work. When I try p2_4 + x + x all the combinations work. I mean, it's a rarity that any of the combinations I try does not work, so I must not be doing it right. I have put together several different 6 and 7 MB roms that worked, but when I changed hte test.rom,0,,0,0 to test.rom,,[CRC],0 it wouldn't load the rom, and had an error. I think maybe you have to have advanced knowledge of ascii and the structure of rom p files to do this. You'd have to be good with a hex editor too. i mean I can use the hex editor easily, I just don't understand it like that one guy because I don't know ascii. Maybe I'm just doing it wrong.

I don't use mame because I hate it... although I compiled my own version of mame32 plus to beat kof2003 on a few times. Anyway, you use it james. Do you have a mslug5 driver for us to look at? I read somewhere that the rom bankings are similar, and I want to see if that's right or not.

I would, but they don't run a cable line back in the boonies. Kyo's hcb+k move works... all the moves he had in kof2002 work to the best of my memory, although that one super where he charges up fire then charges forward with it comes out really, really slow now.

lol, yea that's a biatch. Didn't have that happen to me many times though, unless I was downloading like an mp3 or something.

Metallica Nirvana Staind Manson

go to neogamez.net and on the main page, there should be a link near the top that says "neo geo rom fixes". click it, and KOF2003 is the top one. There's a link to the rom that should work, and also you can download the fix for the s1 rom and the bios that allows u to use the bosses.

Most of the new characters in KOF2003 either look gay or are men that look like women... (Ash). Anyway, well, duh. Mai, boobs down, errr... hands down.