Jump to content
IGNORED

Namco : Assault Plus


Nebulon

Recommended Posts

  • 2 weeks later...

 

 

It is in current MAME, as:

assaultp Assault Plus (Japan)

Looks like the assaultp.zip file that's floating around out there on the net is incorrect. There are two versions: one is around 49K and the other 56K. MAME won't read either one. Why? Because more of the game data is missing (the original Assailt is a 1.2MB file -- for comparison). So if anyone knows where the real Assault Plus archive is...

Link to comment
Share on other sites

Looks like the assaultp.zip file that's floating around out there on the net is incorrect. There are two versions: one is around 49K and the other 56K. MAME won't read either one. Why? Because more of the game data is missing (the original Assailt is a 1.2MB file -- for comparison). So if anyone knows where the real Assault Plus archive is...

 

You'll need the parent romset "assault.zip" as well - since all but the two unique "assaultp" rom chip dumps will be sourced from there.

If you have them both in your rompath, the game should load what is needs from "assault.zip" then use "assaultp.zip" for its unique data.

  • Like 2
Link to comment
Share on other sites

 

You'll need the parent romset "assault.zip" as well - since all but the two unique "assaultp" rom chip dumps will be sourced from there.

If you have them both in your rompath, the game should load what is needs from "assault.zip" then use "assaultp.zip" for its unique data.

Yep. I have both assault.zip and assaultp.zip in the same directory. Only Assault works. Assault plus doesn't even show up in the audit.

 

This is on two different machines using two different versions of MAME with two different ROM sets.

 

Have you successfully run Assault Plus using the method you describe?

Link to comment
Share on other sites

Yup. They both work fine for me locally with current MAME available from mamedev.org

Both rom zip files (assault and assaultp) are in a folder which is identified in mame.ini in ROMPATH line

They both pass a -verifyroms test from command-line as well.

 

I can't figure why it doesn't work for you. There are no special bioses/devices that seems to be linked. Is the assaultp.zip file valid and not corrupted?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...