James

Its way to early to make comments on an OS that is still in beta stages. Rather pointless bitchin about it at this point in time.

Very nice, Its good to see things are turning around

http://www.mamedev.org/ Derivative Builds: MAME32qa MAMEplus! DDEMAME plus! MAME32FX MAME32plus special MAME32Hp4 Dats: Mameinfo.dat v0.104u5 Notes:

I drop money in the tin at the same I press 5 I get that real arcade feel

http://www.mamedev.org/ Derivative Builds: MAMEplus! Dats: Mameinfo.dat v0.104u4 Notes:

Just go to here http://www3.emu-zone.org/host/mameplus/ And then find the correct rom.

60mb seems to be alot to me. Many tracker sites seem to allow BitComet 61 now..

Well your answer did not help

I forgot what CPU you have now ?

http://www.mamedev.org/ Derivative Builds: MAME32qa Mame32 plus special MAME32FX MAME32Hp4 MAMEplus! Dats: Mameinfo.dat v0.104u3 Notes:

http://aarongiles.com/

The offical Mame does not supprt AES mode. Mame Plus does though. if you compile your own you can add AES bios. Universe Bios is not supported by the offical Mame Unoffical builds like Mame Plus does though.

I am a 70/80's kid, More the 80's though.

It is blocked by a few tracker sites I use. That dam client gives bitcomet a bad name

http://www.mamedev.org/ Derivative Builds: MAME32qa MAMEplus! (replaced with v0.104u2a) Mame plus! with Kaillera MAME32 plus special Dats: Mameinfo History.dat 1.06a Notes:

Becuase they never bothered to check the date before that replied. Maybe this topic should be locked ?

If this burner has had alot of use and now is giveing errors at high speed burning it is more or less telling you its on way out. The laser does not last forever you know. If you are getting no errors at slower speeds then keep useing it but you will need a new burner sooner ot later.

K`dash is very excited about halo 2.

Its the same P rom that Mame uses now for svcpcb I have that rom by the way Also sometime ago there was no code to decrypt the V roms so when it loaded the roms it also loaded the decrypted and encrypted V roms. Mame did the same thing. The code to decrypt the V roms is rather new. It was not known when Kawaks DEV was created. There is hope that someone will work out how to decrypt the M rom properly then there will be no need for the decrypted M rom. As you can see with the code below the encrypted and decrypted M roms are loaded, It was the same for the V roms not all that long ago. ROM_START( svcpcb ) /* Encrypted Set, JAMMA PCB */ ROM_REGION( 0x2000000, REGION_CPU1, 0 ) ROM_LOAD16_WORD_SWAP( "269-p1.bin", 0x000000, 0x2000000, CRC(432cfdfc) SHA1(19b40d32188a8bace6d2d570c6cf3d2f1e31e379) ) ROM_REGION( 0x80000, REGION_GFX1, 0 ) /* larger char set */ ROM_FILL( 0x000000, 0x80000, 0 ) ROM_REGION( 0x20000, REGION_GFX2, 0 ) ROM_LOAD( "sfix.sfx", 0x000000, 0x20000, CRC(354029fc) SHA1(4ae4bf23b4c2acff875775d4cbff5583893ce2a1) ) ROM_REGION16_BE( 0x80000, REGION_USER1, 0 ) /* this contains both an ASIA and JAPAN bios, HARDDIP3 on the PCB selects which to use */ ROM_LOAD16_WORD_SWAP( "269-bios.bin", 0x00000, 0x80000, CRC(b4590283) SHA1(47047ed5b6062babc0a0bebcc30e4b3f021e115a) ) ROM_REGION( 0x90000, REGION_CPU2, 0 ) /* Encrypted */ ROM_LOAD( "269-m1.bin", 0x00000, 0x20000, CRC(7d337756) SHA1(205b8b5be7acc8d564fe17835795f25b13c27d7a) ) /* Decrypted */ ROM_LOAD( "269-m1_decrypted.bin", 0x00000, 0x20000, CRC(447b3123) SHA1(a09adc2c0ee2ee0f01287ceb97474a1a58093bd2) ) ROM_RELOAD( 0x10000, 0x20000 ) ROM_REGION( 0x10000, REGION_GFX4, 0 ) ROM_LOAD( "000-lo.lo", 0x00000, 0x10000, CRC(e09e253c) SHA1(2b1c719531dac9bb503f22644e6e4236b91e7cfc) ) ROM_REGION( 0x1000000, REGION_SOUND1, 0 ) /* Encrypted */ ROM_LOAD( "269-v1.bin", 0x000000, 0x800000, CRC(c659b34c) SHA1(1931e8111ef43946f68699f8707334c96f753a1e) ) ROM_LOAD( "269-v2.bin", 0x800000, 0x800000, CRC(dd903835) SHA1(e58d38950a7a8697bb22a1cc7a371ae6664ae8f9) ) ROM_REGION( 0x4000000, REGION_GFX3, 0 ) /* Encrypted */ ROM_LOAD( "269-c1.bin", 0x0000000, 0x2000000, CRC(1b608f9c) SHA1(4e70ad182da2ca18815bd3936efb04a06ebce01e) ) /* Plane 0,1 */ ROM_LOAD( "269-c2.bin", 0x2000000, 0x2000000, CRC(5a95f294) SHA1(6123cc7b20b494076185d27c2ffea910e124b195) ) /* Plane 0,1 */ ROM_END

From what I aware of it should still work with some older GFX cards and some current ones. We will find out for sure when the OS is close to being released. I am waiting until the latest beta ( RC1, RC2 ) to test then it should be known what GFX cards it will work with.

That emu is known to use bad roms. If you like kawaks so much then I suggest you wait until its offically supported in kawaks. Since it is already supported in Mame now.

I think the kf2k3pcb cx decrypt came from Razoola & Halrin.

I never followed this sort of game. I am not even sure if this game is being televised in Asutralia.

Offical Site: Official Site and Source Official Binaries and Source Derivative Builds: MAME32qa MAMEplus! MAME32FX WolfMamePlus Mame32 Plus Plus Neo-Arc-Mame32-plus! Nemo32plus Mame32plus-special Mame32Hp4 VCMame 0.104 for .NET 2003 Dats: Mameinfo NPlayers