Kawaks Crash?

[darkmage479]

Agozer  Posted Today, 08:04 PM

  Thank you for the correct Progear DAT, although that's not the issue here.

 

Yes, thank you Necromancer. Nebula indeed seems to be a bit more "picky" than Kawaks, what with the random shutdowns and all of the rest of it. I'm finding it pretty tedious to go through and reevaluate my romsets, some of which were "mashes" of different C and V data that required self-written 1.46 DATs.

 

I'm still looking for a fix to the Kawaks issue - crash after rom loading. If i deselect 'autostart' the game stays at pause but the application closes upon unpausing with NO error message.

 

In the meantime, the KOF2002 set is the 'original' one, as it works in Kawaks 1.48 dev (not listed as 'bootleg'). I'm still working on Metal Slug 5 (may need a new romset). Thanks to everyone for their help.

[Agozer]

If I've understood correctly, Kawaks/dev uses it's own sets, which are so unique that no other emulator supports them.

[darkmage479]

Agozer  Posted Today, 06:54 AM

  If I've understood correctly, Kawaks/dev uses it's own sets, which are so unique that no other emulator supports them.

 

Almost. Kawaks 1.48dev supports the so-called 'official' sets and contains no ASR.dat - all of the ROM information is preloaded. It also runs KOF2003 with the older P1 and 271-bios.bin. It marks these sets as 'original', 'alternate', 'bootleg' etc. in the ROM loader window. 1.54 is the newest legit release with official support for Rage of the Dragons, Matrimelee, and Progear, and it is correlated with the MAME set for older games.

 

Kawaks 1.46 allows users to edit its DAT file to load newer games. Unfortunately, there are about 3 known dumps of Metal Slug 5, 2 of Metal Slug 4, and around 4-5 each of Rage of the Dragons and Matrimlee (Matrimlee especially due to the release of patches for a touchy C5 rom). Also, the C and V roms for these newer games were often released at diferent times. Therefore, the DAT files I have for 1.46 run cobbled-together romsets for Metal Slug, ROTD, and Matrimelee that may not be any recognized 'original' or 'bootleg ' sets - for example, some have encrypted V but decrypted C roms and vice versa. However, they do run.

 

However, these certain DAT files are rejected by Nebula and i still can't figure out why. Perhaps the DAT manager is simply different, but i'm fast running out of patience for trial and error.

 

I'm continuing my search for a kawaks fix...

[Necromancer]

Wait... You cant run any games with kawaks 1.46 (sorry if i have missunderstood u because English is not my native language)? What about Kawaks 1.54? Can u play any games with it?

 

As for your DATs - I suggest u to test them all in Nebula first! It is much easier to import games in Nebula than in Kawaks. And if they are working under Nebula then they will probably work under Kawaks (i said probably, i mean most of them ). So try them in Nebula. And when importing DATs, i mean games, in Nebula forget about your ASR.DAT! Use romdatamaker to make a particular Dat file for every single (newer) game you have. After you make a dat file test that game, if it works fine, make a dat for another and test it If they are working under Nebula then it wont be hard to "convert" them for Kawaks with loader

 

Regarding KOF2002 problem :

If I've understood correctly, Kawaks/dev uses it's own sets, which are so unique that no other emulator supports them.

 

Mslug4 for Kawaks dev is the same one that is supported by Kawaks 1.54, MAME and FBA - original set, encrypted. You just need to rename m1_decrypted.bin to m1d.bin KOF2002 is almost the same. The only difference is that Kawaks dev set has ADDITIONAL Vxd roms. That means that Kawaks/dev set will work with FBA,MAME, Kawaks 1.54 and Nebula(maybe). So, Darkmage, scan kof2002.zip with RomDataMaker and make sure that everyting is right - for example do not put m1d.bin under [program] files etc Make a new dat... At the end you have to edit it :

 

Replace this:

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

 

With this:

[System]
CartridgeID: 265
GfxCrypt: 2
GfxKey: EC
ButLayout: 9
Fix: 1E

That set is encrypted, that's why you need to do this

 

KOF 2003:

It also runs KOF2003 with the older P1 and 271-bios.bin

Those files are part of Kof2003 PCB set. AFAIK they are not old - i haven't seen newer versions of those roms. And there is NO WAY you make it run under Kawaks 1.46+loader (kof2003 PCB). You will need a P1 file with broken protection for kof2003 if you wanna play it under Kawaks with loader.

Edited August 17, 2005 by Necromancer

[Spiffy]

just use the 1.46 w/ loader n update ur asr dats.

[darkmage479]

Spiffy  Posted Today, 11:13 AM

  just use the 1.46 w/ loader n update ur asr dats.

 

ouch.. i feel like nobody really understands the problem.

 

NO versions of kawaks work on my new computer, which runs XP pro SP2. The asr.DAT file is from kawaks 1.46 on my OLD computer (XP home SP1) which works fine. I originally posted asking for help on getting Kawaks running and this suddenly turned into a Nebula thread.

 

Any new ideas?

[Agozer]

Spiffy  Posted Today, 11:13 AM

  just use the 1.46 w/ loader n update ur asr dats.

 

ouch.. i feel like nobody really understands the problem.

 

NO versions of kawaks work on my new computer, which runs XP pro SP2. The asr.DAT file is from kawaks 1.46 on my OLD computer (XP home SP1) which works fine. I originally posted asking for help on getting Kawaks running and this suddenly turned into a Nebula thread.

 

Any new ideas?

Try this: Change the compatibility mode for the Kawaks execute to Win 98 or 2000.

[Spiffy]

sorry 4 dat i got slepy here, btw try to change its xp compatibility as stated above or u may try change the video memory allocation..

[darkmage479]

i had already tried adjusting the compatibility, no luck...

 

i fiddled with the Kawaks video memory (the Radeon 9000 on the new machine is an IGP) and the Kawaks blitter but still have no luck. I'm gonna read the Radeon manual and see if there are any Direct3D or OpenGl settings i can fiddle with...

[Alucard1475]

If you have multiple dats of a ROM, you may just loooose. My kawaks crashed cause I had 14 dats of samsho5sp. I've reduced it to a single one.