Print

[opjose]

   

Did you switch to the NeoGeo version of MameX (the BLUE screened one) before trying to run the NeoGeo games?

Also your NeoGeo roms MUST be fully merged. E.G. all of the ROM(s) and their clones in one zip file. This zip file should also include the NeoGeo bios roms (NeoGeo.zip).

Yes they work fine, with the exception of a few that are too large for the Xbox, and a few that still have some trouble.

Captain Tomoday, Nightmare in the Dark, Pulstar, Puzzle Bobble, etc. all work for me. If you get one to run, you can normally get most of the others to also work.

[kido23]

i have the same problem.I put the neogeo.zip in the roms folder and only appear the first window i press OK. but dont boot the game . and I need reset the x box for start again. and I what do you mean the neo geo roms must be fully merged. e.g.     ..........        merged e.g.? what is this?

[ajoflow]

i found out the problem....

load up the original MS dash and change the date.  for some reason the year got changed to 8097!   just change that and your neo geo roms should work fine.... enjoy!

[opjose]

QUOTE (kido23 @ Aug 29 2002, 09:03 AM)

i have the same problem.I put the neogeo.zip in the roms folder and only appear the first window i press OK. but dont boot the game . and I need reset the x box for start again. and I what do you mean the neo geo roms must be fully merged. e.g.     ..........        merged e.g.? what is this?

                       

You'll need "Introductory Mame 101".

Download CLRMame and Romcenter. Read the docs. These programs will do all the merging work for you.

Where? Google is your friend.  

[opjose]

QUOTE (geekstud @ Aug 29 2002, 02:04 PM)

What I did was to unzip the games into folders with the same name in the mame roms folder.  Then unzip neogeo.zip into each game folder.  Then burn as normal.

                   
Ouch!

I doubt you'll be able to fit more than 1/2 of all the Roms on a DVD this way. It's a waste of hard drive space, though it works.

You can rezip the folders (getting rid of the directory structure!) and things should work for you. But what a pain.

instead just use CLRMame or Romcenter to do the work for you.

 

[ZildjianKX]

Do Metal Slug 1,2,X,3, and 4 work in MAME-X?

[snakejoe]

QUOTE (ZildjianKX @ Aug 31 2002, 01:26 PM)

Do Metal Slug 1,2,X,3, and 4 work in MAME-X?

                                    Hi ZildjianKX. nice to meet you  

I just tried metal slug 1,2 they work great!!
but metal slug 4 can not since the rom is too large.

[ZildjianKX]

Howdy Snake Joe     What do you mean by the ROM is too large?    (THANKS for answering my question too!)

[snakejoe]

ROM size.

When running Mame X. it use all free XBOX ram to store roms (about 54mb). But the size of metal slug 4 after zip is 60mb. so it is impossible to play MS4.

[ZildjianKX]

Think there will be any way around it?     Too bad the Mame version of the ROM is so big, I know there is a 30 meg one that works with NeoRageX  

[opjose]

QUOTE (ZildjianKX @ Sep 3 2002, 04:16 PM)

Think there will be any way around it?     Too bad the Mame version of the ROM is so big, I know there is a 30 meg one that works with NeoRageX

                                    It's unlikely that you will see any fixes for this. As it is not only does the Xbox have to hold the entire ROM and workspace for the emulator and roms, but MameX also caches the rom list.

Notice that when you drop out of Mamex you immediately see the ROM list and MameX knows where it was?

Yeah it might be possible to recover another meg or two of RAM, but there is no getting around the 64 meg (realistically 54-58 meg) limit of the Xbox.

There have been a few (idiots) who have speculated on using one of those bogus RAM recovery programs, which in themselves are a joke.

The Xbox can cache things to the hard drive, but the roms for mamex must be ram resident to play since they must be loaded into the virtual "machine" in total.

Doing otherwise would require a complete Mamex rewrite and would possibly bring Mamex to it's knees on performance.

[Tom M.]

Well, why could not somebody rewrite the code? All you have to do is not to load all the roms at once, but load them level-by level.

[opjose]

QUOTE (Tom M. @ Sep 4 2002, 07:04 AM)

Well, why could not somebody rewrite the code? All you have to do is not to load all the roms at once, but load them level-by level.

                                    Doesn't work that way!

Most roms files are images of the roms stored on the actual circuit boards.

Some of the roms are used by other devices (which are also emulated by Mamex) such as sound devices.

All of the roms for a single game must be loaded into the emulator so it can decode the appropriate items. On the original boards the 8+ or so roms formed a matrix, with high order bytes on one rom, low on another, data on a third & fourth, graphics on a fith & six, etc.

Since the emulation routines are simulating the original circuit boards with MULTIPLE processors, the respective roms must all be loaded for each virtual processor to see what it needs.

Mame for the PC has the same restrictions because of this... of course memory is not an issue with the PC is it?

[opjose]

QUOTE (Tom M. @ Sep 4 2002, 07:04 AM)

Well, why could not somebody rewrite the code? All you have to do is not to load all the roms at once, but load them level-by level.

                                         

Young grasshopper, you most modify your thinking.

There are NO "LEVELS' on seperate ROMS to load. It doesn't work this way. The hardware boards were not designed in a PC fashion as you are thinking.

There are various emulators running (BTW: I answered this at length on another thread...) each which requires it's own set of roms to be RAM resident.

E.G. there might be 4 roms for one sound chip (and you need it's emulator running too) 8 for processor one, 8 for processor two, 10 for the video processor, etc.

Already make is highly optimized with a preponderance of hand written assembly code to achive any type of speed.

Mame is NOT a single emulator, rather it's a set of emulators which get loaded upon game startup. Each individual one handling the reproduction of an array of hardware.

Instead of a virtual PC, you have an array of virtual PC's which all must be running different code, as an analogy.