James

strange thing this i have never been to that site before but i got this message when i tried to veiw it vBulletin Message Sorry. The administrator has banned your IP address. To contact the administrator click here If you have a dynamic ip, maybe they banned someone who had it before. Or, more probably they banned a whole provider or geographic region. Also possible is that they use the list from peerguardian and that you accidently got into it... Anyway I had no problem entering the site. oh well the best i can do is email them and see what happens

just so you know this is not kof2003 it is cthd2003 they must really think thats the kof2003 rom

strange thing this i have never been to that site before but i got this message when i tried to veiw it vBulletin Message Sorry. The administrator has banned your IP address. To contact the administrator click here

i am over this i do not care anymore

EGCG NeoRAGEx... Get it from http://www.neogamez.net i have this emulator and when i try to start it up, it just brings me back to windows. i have it in the same folder as my metal slug 5 hacked neorage. is there a problem here? i myself will not answer this agian bad rom sets are known to cause this problem. check ur rom set.

my nortons blocks that site says there is a virus

dam getting the bios is the easy part it is all over the net do a search just type neogeo places like filemirrors google and so on stop being lazy and expecting others to do it for you thank you

maybe we can be nice to Pyro the proof i need is the rom in my roms folder

the pic of the Kawaks emulator are fake which are here http://members.westnet.com.au/the-kula/mame.html the other screenshots i am not sure about

it is running slow looks like i may have rename the pics so it will stop all the linking to the site

hhmm you can get roms from other sites that work fine in kawaks so please post facts not fiction thank you

u CLICK the link

i use mame and so far you have not told me the crc for these roms you have.

do not hate it, they are not stupid, they are creative and different, that is all!! (respect your opinion, no offence) for all of you who would like to try the blue version, cause you alredy are sick and tired of the original or just want to change colors as if is in one menu, here is the blues version hack made by jeff. for best result follow the next procedures. make a copy of the svcplus roms and rename it svcplus"blue" or any name then in that put the hacked blued p1, then in your dat file, copy and paste the dat for the original svcplus so you will have two. now change the name of one for svc plus blue or any name and then the target romset to svcplus"blue" or the name of your choice. in this way you will be able to paly both whitout repalce the original. it is the same as the original but the colors lokk great, also kyo has a new nice color ok boys here is the p1 jeffs page the creator ENJOY!!! oh it is a pretty blue . how nice it looks hahahahahahahahahahahahahahahaha seems more like a messed up rom to me . no offence

make sure your roms have the same crc i made this dat so i can use my rom set in mame as well this dat works on Nebula and Kawaks please note to use a dat in kawaks you will need a Loader and a file called asr.dat System: NEO RomName: samsho5 Game: Samurai Shodown 5 [Program] 270-p1.bin,0,800000,fe6f92e0,0 [Text] 270-s1.bin,0,20000,33227D62,0 [Z80] 270-m1.bin,0,20000,18114FB1,0 [samples] 270-v1.bin,0,400000,6849136C,0 270-v2.bin,400000,400000,222E1774,0 270-v3.bin,800000,400000,CD9E7ADC,0 270-v4.bin,C00000,400000,8B305CAC,0 [Graphics] 270-c1.bin,0,800000,4E7BDEA1,0 270-c2.bin,1,800000,7B444985,0 270-c3.bin,1000000,800000,8C709A9B,0 270-c4.bin,1000001,800000,CFD53F5C,0 270-c5.bin,2000000,800000,C026D318,0 270-c6.bin,2000001,800000,B3D9D204,0 270-c7.bin,3000000,800000,FE03A025,0 270-c8.bin,3000001,800000,89DB2D34,0 [system] CartridgeID: 270 GfxCrypt: 0 GfxKey: 0 ButLayout: 9 Fix: 0

mine run ok no sound issues and it does not crash what i need to know is your roms what are th crc's for the m1 ? and the v roms ? and p rom ? do these match your roms check the dat %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% System: NEO RomName: svc Game: Snk vs Capcom chaos [Program] 269-p1.bin,0,600000,0e2b56e0,0 [Text] 269-s1.bin,0,20000,3334ac31,0 [Z80] 269-m1d.bin,0,20000,7f01dac5,0 [samples] 269-v1.bin,0,400000,E7203930,0 269-v2.bin,400000,400000,675159C3,0 269-v3.bin,800000,400000,F8810665,0 269-v4.bin,C00000,400000,B57B4EA3,0 [Graphics] 269-c1.bin,0,800000,465D473B,0 269-c2.bin,1,800000,3EB28F78,0 269-c3.bin,1000000,800000,F4D4AB2B,0 269-c4.bin,1000001,800000,A69D523A,0 269-c5.bin,2000000,800000,BA2A7892,0 269-c6.bin,2000001,800000,37371CA1,0 269-c7.bin,3000000,800000,56AC5FB9,0 269-c8.bin,3000001,800000,DE99E613,0 [system] CartridgeID: 269 GfxCrypt: 0 GfxKey: 0 ButLayout: 9 Fix: 0 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% System: NEO RomName: svcplus Parent: svc Game: Snk vs Capcom chaos Plus (Hack) [Program] 269p-p1.bin,0,600000,2a2516de,0 [Text] 269p-s1.bin,0,20000,aaef740c,0 [Z80] 269-m1d.bin,0,20000,7f01dac5,0 [samples] 269-v1.bin,0,400000,E7203930,0 269-v2.bin,400000,400000,675159C3,0 269-v3.bin,800000,400000,F8810665,0 269-v4.bin,C00000,400000,B57B4EA3,0 [Graphics] 269-c1.bin,0,800000,465D473B,0 269-c2.bin,1,800000,3EB28F78,0 269-c3.bin,1000000,800000,F4D4AB2B,0 269-c4.bin,1000001,800000,A69D523A,0 269-c5.bin,2000000,800000,BA2A7892,0 269-c6.bin,2000001,800000,37371CA1,0 269-c7.bin,3000000,800000,56AC5FB9,0 269-c8.bin,3000001,800000,DE99E613,0 [system] CartridgeID: 269 GfxCrypt: 0 GfxKey: 0 ButLayout: 9 Fix: 0 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

sounds like yiu have bad V roms

do you have the mslugnd.zip (rom) if so you then download the p1 rom which is in the zip (there is no password ) then you replace the old p1 rom with the fix

unzip the p rom and put it the mslug5nd.zip which came from here http://www.neogamez.net/Downloads/Utilidad...g5_p1%201.1.zip this is the dat i used make sure your rom names are the same or rename the names on the dat to match your roms making sure the crc are the same System: Neo RomName: mslug5nd Game: Metal Slug 5 [Program] 268-p1.bin,0,600000,02247965,0 [Text] 268-s1.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

this is from the neogames homepage (i hope this is not true ) http://www.neogamez.net/ is in spanish After a brief time without an update because I was attending a forum 0_o the only other news I have is the fact that there will be no rom of kof 2003, for the simple fact that metal slug 5 was released so fast SNK lost money, the point is I believe in order to repay for what was lost with metal slug 5 there will be no kof 2003 rom according to team EFMP which are the ones that were in charge of dumping it, so too bad we all have to share in the blame with those that STOLE the rom that's all

if you allready have mslugnd then just use this p rom it work in neorageX mame Nebula Kawaks http://www.neogamez.net/Downloads/Utilidad...g5_p1%201.1.zip

i know i sound a bit nasty but if i find this rom i will not post it here . as there is too much crap here.no newz i doubt i will be first to find the rom anyway.

0.78u2 ------ The only change in u2 is the overhaul of the memory system mentioned below, no new drivers have been added General Source Changes ---------------------- Significant overhaul of the memory system. This is the first of several phases, but it lays the groundwork for future improvements. This first change will also be the most disruptive, touching every CPU core and every driver file [Aaron Giles] Memory system changes --------------------- The biggest change is the introduction of the concept of address spaces. Each CPU can have up to 3 separate address spaces now, with the possibility of easily adding more in the future. Each address space has its own addressing semantics, including databus width, address bus width, address shift, and unmapped memory value. The three existing address spaces are defined to be program, data, and I/O. The program address space is where code is assumed to live; it is also where all memory lives in standard von Neumann architecture CPUs. The data address space is for Harvard architecture CPUs, and will be used in the future to do proper program/data separation for the CCPU, PIC16C5x, ADSP210x, TMS32010, and TMS32025. The I/O address space is used for port accesses, such as those performed by the Z80 and x86 CPUs. The read/write handlers used by CPUs to access memory have all been renamed in the shuffle, both in order to match the address space naming conventions (program/data/io) and in order to make it clearer what they do. In addition, they have been unified to a large degree. Instead of separate memory accessors based on both the address bus width and the data bus width, there is now just one shared set of memory accessors for each data bus width. Here are some examples of how older functions map to newer ones: cpu_readmem16, cpu_readmem17, cpu_readmem20, -> program_read_byte_8 cpu_readmem21, cpu_readmem24 cpu_writemem_16bew_word, cpu_writemem18bew_word, -> program_write_word_16be cpu_writemem_24bew_word, cpu_writemem32bew_word cpu_readport -> io_read_byte_8 A common annoyance used to be that drivers would need to know which of these functions to call in order to read memory. A table of accessors is now included as part of the memory context switch, which allows the addition of generic functions that can be used by the drivers to access memory. For example, a driver trying to read a word from a 68000's address space used to have to call cpu_readmem24bew_word(). Now the driver can just call program_read_word(), and the memory system will do the right thing. In addition, there is now a single change_pc() macro used by all CPU cores, regardless of the databus or address bus width. Along with these changes, the macros for defining memory maps has changed for consistency as well, as follows: MEMORY_READ_START -> PROGRAM_READ8_MAP_START MEMORY_READ16_START -> PROGRAM_READ16_MAP_START MEMORY_READ32_START -> PROGRAM_READ32_MAP_START MEMORY_WRITE_START -> PROGRAM_WRITE8_MAP_START MEMORY_WRITE16_START -> PROGRAM_WRITE16_MAP_START MEMORY_WRITE32_START -> PROGRAM_WRITE32_MAP_START MEMORY_END -> PROGRAM_MAP_END PORT_READ_START -> IO_READ8_MAP_START PORT_READ16_START -> IO_READ16_MAP_START PORT_READ32_START -> IO_READ32_MAP_START PORT_WRITE_START -> IO_WRITE8_MAP_START PORT_WRITE16_START -> IO_WRITE16_MAP_START PORT_WRITE32_START -> IO_WRITE32_MAP_START PORT_END -> IO_MAP_END Along the way, support has been also added for CPUs with a 64-bit data bus, so there are also macros for PROGRAM_READ64_MAP_START, etc. One of the future goals of the memory system is to support not just ranges of memory, but also better support for mirrors and more complicated situations where addressing is repeated at regular intervals. In order to facilitate this, macros have been created that must be used when defining a memory map: MEMORY_READ_START PROGRAM_READ8_MAP_START { 0x0000, 0xffff, MRA_RAM }, -> READ_RANGE( 0x0000, 0xffff, MRA8_RAM ) MEMORY_END PROGRAM_MAP_END MEMORY_WRITE_START PROGRAM_WRITE8_MAP_START { 0x0000, 0x0fff, MRA_RAM }, WRITE_RANGE ( 0x0000, 0x0fff, MRA_RAM ) { 0x1000, 0x7fff, MRA_RAM, &foo }, -> WRITE_RANGE_P ( 0x1000, 0x7fff, MRA_RAM, &foo ) { 0x8000, 0xffff, MRA_RAM, &bar, &bar_size }, WRITE_RANGE_PS( 0x8000, 0xffff, MRA_RAM, &bar, &bar_size ) MEMORY_END PROGRAM_MAP_END Since all the memory maps were changing anyway, static 8-bit handlers have been renamed for consistency. This means that MRA_NOP becomes MRA8_NOP, etc. Prior versions of MAME allowed special entries in the read/write maps to control the number of effective address bits. This mechanism has changed so that you can supply an arbitrary combination of flags: MEMORY_ADDRESS_BITS(20) -> PROGRAM_MAP_FLAGS( MEMORY_ABITS(20) ) and it has been enhanced to also allow you to specify the unmapped memory value: PROGRAM_MAP_FLAGS( MEMORY_UNMAPPED_0 ) /* unmapped reads return all 0's */ PROGRAM_MAP_FLAGS( MEMORY_UNMAPPED_1 ) /* unmapped reads return all 1's */ Because of this mechanism, the old function memory_set_unmap_value() has been deprecated. All drivers using this have been updated to use the new mechanism instead. Also note that the MRA_NOP handlers have been changed to return the unmapped value as well, instead of always returning 0. Another "feature" that has changed is that unmapped reads and writes to address spaces of less than 20 bits no longer act like RAM. This may break some drivers, but it ends the special treatment of 8-bit address spaces. In the machine driver macros, the address space is now explicitly specified: MDRV_CPU_MEMORY(read,write) -> MDRV_CPU_PROGRAM_MAP(read,write) /* not applicable */ -> MDRV_CPU_DATA_MAP(read,write) MDRV_CPU_PORTS(read,write) -> MDRV_CPU_IO_MAP(read,write) CPU Interface Changes --------------------- The other significant change in this release is the way CPUs are defined and referenced. Previously, the file cpuintrf.c contained a huge table with many pointers into each CPU, and a bunch of data about each CPU type. This was problematic to maintain, and left a bunch of data out of the CPU core to be defined by MAME instead. The new release defines a new function that every CPU core must implement, of the form: <cputype>_get_info(UINT32 state, union cpuinfo *info) This is the only public function defined for each CPU core. The table in cpuintrf.c now simply consists of an enumerated index for the CPU type, followed by the pointer to the actual CPU's get_info function. The flexible get_info function is then responsible for providing pointers to all the remaining functions. In addition, the number of other functions has been greatly reduced: void set_info(UINT32 state, union cpuinfo *info); void get_context(void *context); void set_context(void *context); void init(void); void reset(void *param); void exit(void); int execute(int cycles); void burn(int cycles); offs_t disassemble(char *buffer, offs_t pc); The old functions get_reg, set_reg, set_irq_line, set_irq_callback, info, get_cycle_table, set_cycle_table have all been incorporated into get_info and set_info. All the existing MAME CPU cores have been updated to work with this new system. Also, for most cores, all functions and the icount global variable have been made static apart from the get_info function. A number of selectors for get_info/set_info have been defined to return information about the CPU, including the address and data bus sizes for all address spaces, clock dividers, IRQ line size, context size, etc. NOTE TO PORTERS: the cpuintrf[] array is now populated dynamically by the cpuintrf_init() function. This means that if you have informational code or other code that relies on the CPU information being present (i.e., if you call any of the cputype_* functions) before calling run_game(), you must manually call cpuintrf_init() first. Don't worry, it is safe to call cpuintrf_init() multiple times.

to be honest i hate all these hacks and i think they are stupid .

System: NEO RomName: svc Game: Snk vs Capcom chaos (original) [Program] 269-p1.bin,0,600000,0e2b56e0,0 [Text] 269-s1.bin,0,20000,3334ac31,0 [Z80] 269-m1d.bin,0,20000,7f01dac5,0 [samples] 269-v1.bin,0,400000,E7203930,0 269-v2.bin,400000,400000,675159C3,0 269-v3.bin,800000,400000,F8810665,0 269-v4.bin,C00000,400000,B57B4EA3,0 [Graphics] 269-c1.bin,0,800000,465D473B,0 269-c2.bin,1,800000,3EB28F78,0 269-c3.bin,1000000,800000,F4D4AB2B,0 269-c4.bin,1000001,800000,A69D523A,0 269-c5.bin,2000000,800000,BA2A7892,0 269-c6.bin,2000001,800000,37371CA1,0 269-c7.bin,3000000,800000,56AC5FB9,0 269-c8.bin,3000001,800000,DE99E613,0 [system] CartridgeID: 269 GfxCrypt: 0 GfxKey: 0 ButLayout: 9 Fix: 0 System: NEO RomName: svcplus Game: Snk vs Capcom chaos Plus (Hack) Parent: svc [Program] 269p-p1.bin,0,600000,2a2516de,0 [Text] 269p-s1.bin,0,20000,aaef740c,0 [Z80] 269-m1d.bin,0,20000,7f01dac5,0 [samples] 269-v1.bin,0,400000,E7203930,0 269-v2.bin,400000,400000,675159C3,0 269-v3.bin,800000,400000,F8810665,0 269-v4.bin,C00000,400000,B57B4EA3,0 [Graphics] 269-c1.bin,0,800000,465D473B,0 269-c2.bin,1,800000,3EB28F78,0 269-c3.bin,1000000,800000,F4D4AB2B,0 269-c4.bin,1000001,800000,A69D523A,0 269-c5.bin,2000000,800000,BA2A7892,0 269-c6.bin,2000001,800000,37371CA1,0 269-c7.bin,3000000,800000,56AC5FB9,0 269-c8.bin,3000001,800000,DE99E613,0 [system] CartridgeID: 269 GfxCrypt: 0 GfxKey: 0 ButLayout: 9 Fix: 0