Build Your Own Arcade Controls Forum

Main => Software Forum => Topic started by: crashdmj on July 31, 2003, 02:58:27 am

Title: Mamewah
Post by: crashdmj on July 31, 2003, 02:58:27 am

Ya know when you DL the new version and unzip and do setup....do I unzip the additional zip file called mamewah as well (they seem to be the same). Just call me a newb
Derek

Title: Re:Mamewah
Post by: gndprx on July 31, 2003, 10:25:14 am

Unzip the download into a temporary directory.  Run the setup.exe file and this will install MAMEWAH into the directory of your choosing.

Then go to the new MAMEWAH directory and unzip the LAYOUTS.ZIP file and you're all set.

Hey Minwah, why doesn't the layouts.zip get extracted during install?  It's a required portion for even the default layouts?  Just curious.

Title: Re:Mamewah
Post by: Minwah on July 31, 2003, 11:19:27 am

Quote from: gndprx on July 31, 2003, 10:25:14 am

Hey Minwah, why doesn't the layouts.zip get extracted during install?  It's a required portion for even the default layouts?  Just curious.

I couldn't figure how to get the installer to make a layouts folder with subfolders, and extract each .LAY file into the correct folder.  The Package & Deployment tool allows you to add files, but not recurse folder (AFAIK), so this would cause problems since there are 4 files called 'layout.lay' as standard.

If anyone knows how to do this, please let me know...

Title: Re:Mamewah
Post by: IIOIOOIOO on August 01, 2003, 10:00:18 am

IIRC, I ran into the same problem using (I assume you are) the built-in deployment wizard. The solution I ended up using ran something along the line of choosing to "save this package for later use," which creates a bunch of files used in BUILDING the installer file. Then, just poke around... it's a fairly rudimentary scripting language, but much can be accomplished.

Title: Re:Mamewah
Post by: Minwah on August 01, 2003, 11:44:55 am

Quote from: IIOIOOIOO on August 01, 2003, 10:00:18 am

IIRC, I ran into the same problem using (I assume you are) the built-in deployment wizard. The solution I ended up using ran something along the line of choosing to "save this package for later use," which creates a bunch of files used in BUILDING the installer file. Then, just poke around... it's a fairly rudimentary scripting language, but much can be accomplished.

Thanks, I'll have a poke around before my next installer release...