sundogak

Doesn’t matter where it is located as long as after the apple2gs. RAM for most part won’t speed anything up for purpose of IIGS. Use the INSERT key to toggle fast forward to speed boot up. Link Insert Fast forward. While held, runs game with throttling disabled and with the maximum frameskip. (Windows non-SDL MAME only)

Bit more time this round..pesky work getting in the way. But here you go. Included the actual original PGM gen 1 logo style as well as the PGM style typically see in most themes. Plain Logos for a few hard to find clean images

Both of those check boxes must be off (Don't Use Quotes should be off.....Use File Name Only should be off) if using non-MAME software sets (or you unzipped/renamed a MAME set). Only if you are using the MAME software list disks/images provided by the MAME team in their format and their naming convention with full hash set do you leave those checked on. This applies to any software emulation for MAME, not just Apple. Basically, if you are NOT using the benefit/features of MAME XML HASH files then you have to use full command strings and paths for software sets (not speaking about arcade which is separate animal). This is why you are having to move files into MAME path. The benefit of doing it the "MAME way" for software sets is it uses the HASH file data to figure out what and how to load stuff AND you don't have to use full paths or extensions in that case. You are not doing that in your case. You will need the apple2gs -sl7 cffa2 command if you are using non-standard (to MAME) hard drive images. These statements are borking your setup since you don't seem to have a full/consistent MAME setup: No. MAME will do nothing with it called "ROM". MAME needs things in ZIP and specific checksums or won't use it. Also the Apple2GS.zip...what version is it...does it match your MAME version EXE? If you didn't have that in your MAME ROM setup prior then you didn't have a full/complete MAME set. MAME needs everything in specific file format, naming convention and checksums or you will tear your hair out trying to get things to work (particularly for software emulation). If you downloaded a full arcade rom set and you are using the same MAME exe version (i.e., 236 set of roms matching your MAME exe) then you have all the need. You cannot just plunk a random rom file in to setup. So make sure you have a complete arcade ROM setup first since MAME has parts and pieces in there it uses for non-arcade as well. Basically, the error your are getting is MAME isn't finding the driver and/or the actual PO file you are pointing to. Thus, that means you are missing ROMs in your "arcade set" somewhere or it cannot find path to disk file. This is why it is best to run via command line initially (outside LB). MAME gives more info on what is going on.

po, hdv, chd, and 2mg hard drive images will all launch now in MAME if running recent updates (somewhere +214 version). The newer command I use is below. The "cffa2" addition/update is what changed in recent versions of MAME which is more flexible than the scsi option on file types it will allow. Basically the command emulates a compact flash drive. Below has worked for all the HD images I have in po, 2mg, and HDV format (along with some had converted to CHD). For IIGS, a hard drive image is way to go. Less fiddling around with swapping disks. apple2gs -sl7 cffa2 -noautosave -gameio joy -ramsize 8M -keyboardprovider dinput -hard1

MAME is easy to get setup for IIGS particularly if sticking to one disk autoboot games. Skip to Step 5 if you are somewhat familiar with MAME and have been messing with Apple II already. That gives you the base commands in LB to get working in MAME. Someday I will go back and strip that down or hide the detail in my post since most won't/don't look at it. The other emulators like KEGS and GSPort work well enough and ActiveGS (standalone) is using a backend KEGS platform. I haven't messed with it much but looks a lot like AppleWin in how it works. It also seems to have relatively recent updates. If just using outside LB would say ActiveGS would be quickest to setup but have no experience as to if ActiveGS can be called via command line and/or how will work with LB. The issue you get into with the IIGS is start seeing games more frequently that need to either be launched from the desktop (like early Macs) or have to have system image to launch. That complexity will be same with any emulator however.

You have to use the -h1 parameter instead of -d1 if using HD images and launching via command line (which is in essence what LB is doing on backend). Using -h1 via command line will automatically enable the disk controller. If just have a few HD images then can set those using Edit Game, Launching, Emulation, and check the Use Custom Command-Line Parameters. If have quite a few HDV/PO files intermixed with floppy images then easier to setup two emulator instances in LB. One with parameter -d1 (say AppleWin_Disk as emulator name) and another with -h1 for HD images (say AppleWin_HD). You can call the emulator whatever you want and select all HDV images and change the emulator to that instance. Edit Note: you do need to add this to the HD command emulator or AppleWin will not unload Slot 7 HD and when you then try to launch a disk it will launch the hard drive image instead. AppleWin has a pretty good help manual with more detailed info on command lines. -s7-empty-on-exit -h1

For Apple IIGS found MAME works for most things so it is my primary in LB. I have KEGS and GSPort setup outside LB but don't really use them. The link above goes to a IIGS writeup, which there are some updates to but for most part will get you going if doing MAME. For Apple IIE there are several write ups in the forums. I primarily use MAME if autoboot type game making it more amenable to LB frontend type setup. If multi-disk and/or using hard drive images tend to stay with Applewin outside LB in that I find easier to navigate, switch disks, etc. The one thing that makes Applewin easy is being able to drag a disk image onto the emulator and it loads image and launches (again outside LB). So ultimately, use both and depends on what doing. If have a full MAME software list set can use the disk images inside the MAME zips (unzipped) in Applewin excluding the WOZ format which is not supported (so have to use MAME in that case). Both the MAME and Applewin emulators seem to have active development for the Apple emulation which is a plus. Like Headrush69 mentioned, it is a bit of preference on what want to do. MAME does have the better shaders than Applewin which are pretty basic. Here is setup for Applewin in LB (assuming disk 1 will have system to boot): -fs-height=1080 -noreg -no-printscreen-dlg -r 32 -d1 For both systems (like most computer emulation) you are ultimately dealing same aspects of the original systems so will run into games that don't auto boot (so need a system disk), non-consistent keyboard/joystick setups, and on multi-disk games having to swap disks at some point. Having some experience with the original systems helps in those cases. If start off with a few games and get them running, that is easiest.

Yes, I have 12.1 and works. No, if have Steam install then has to point to Steam folder.

You got Daphne working so that is better than most people on first crack at it.👍 Daphne isn't the simplest of emulators to get rolling. Also the Tools, Audit Platform feature is good when you are importing stuff to verify if LB "linked" the entry to it's database. Sometimes even with a title it can get confused. So if you are having issues with scraping verify that it is linked with a LB ID:

A bit more detail on what is not working will help folks guide you. LB doesn't mess with any of your emulator directories so it cannot destroy anything there. But if you want to revert to a prior working version this will get you started. Revert the LB Version LB keeps copies of older versions of the install files in the folder ..\\Launchbox\Updates\ You should be able to revert to version you had that worked for you prior by clicking on the EXE installer you want to go back to Revert the LB Settings to Earlier Working Version The other portion is that LB keeps a copy of your XML files (the actually settings, and database for LB) in the folder ..\\Launchbox\Backups You will find zip files with dates of the backups. Typically LB will do one on startup and one on shutdown automatically. To restore the XML files to older version you can do one of two ways. Within LB you can go Tools, Restore Data Backup. You can then select the backup file based on date to the last working version you wanted. The second way if for some reason you cannot open LB is open the zip manually with date you want to restore back to and copy the files in the zip to the folder ...\Launchbox\Data Reverting to an earlier XML date will lose any changes you made after the date. Lastly, you can turn off auto updates by going to Tools, Options, General, Updates and unchecking update on startup.

@HomerJ You need to update the titles to actual title and not the frame file name. LB DB can only match if title is correct. You can either edit them at the last import panel or go back and update each after added and rescrape media.

If you enter in a cabinet code into FX3 it will allow direct table launch without going to UI. Code is free but has to be requested from Zen. Thread below on direct table setup.

There are a couple pause themes which shows control images per platform and some templates for modification. You can customize those images and at least for the theme I have they they go in the ..\Launchbox\Images\Game Controls folder. The issue is this isn't automatic. If you wanted one per game you would have to modify each image manually in a graphics program. I had hacked together a pause theme version which shows the MAME controller panel like below but those were already done by others and you need one image per game named the same as the game title or ROM. For anything other than MAME, it would be a lot of work to do per game custom images (unless do selectively) versus just bringing up the Pause Menu and the manual.

@JoeViking245Great explanation! I don't typically do bezel setups on software lists and few I do are at the Machine level (i.e., Atari 2600 bezel, so a2600.zip works fine). But gave it a whirl to see. If I launch a CMD window within the MAME directory and launch these as you noted in your post they all work as expected with override (renamed a random artwork zip to "tank.zip"). mame pegasus tank -override_artwork 1942 mame pegasus tank -override_artwork tank First one launches the 1942 arcade bezel and second did whatever I renamed to "tank.zip". Unfortunately, MAME doesn't look beyond the Machine name for artwork without forcing with override. Side Note (related but off topic of bezels):

Just use the filter option, the funnel icon to the right of the Search box. Or if want it to be a permanent list then use the Playlist feature. Right click on left pane where platforms are listed and select Add, then New Playlist and you can make a playlist with various conditions. For example the playlist below sorts all games in entire collection that have Donkey Kong in title of game. A relatively new feature with the "funnel" sort option is that once you select what you want, you can save that sort query to a playlist and LB figures out what to put in the Auto-Populate settings.

You cannot daisy chain same name field conditions (basically an "AND" query). But you can accomplish what you want by doing as below with the "Has None of the Values" and separating the platforms you do not want by semicolon. Example below excludes Apple II, MAME, and MS-DOS games.

If for regular MAME, you would name the artwork/bezel zip the same as the machine/romset name. So in the case of Aamber Pegasus that would be pegasus.zip Aamber Pegasus - MAME machine (arcadeitalia.net)

There isn't any official logo of Swanstation since a RA core hack of Duckstation (which has a RA core as well). But here you go.

Here you go:

The download section has various packs here is one for example:

I typically err always on side of "leave it" unless it is wrongly placed (i.e., not a clear logo at all), junk quality, wrong regional logo (which is fixed by tagging correctly), or a dupe of existing (taking the better of the two). But just because it doesn't match the box art doesn't mean it isn't valid either for the reasons you gave. I have seen logos used for adverts/flyers that are not the same but it is still made by publisher. The DB for good and bad is somewhat up to general consensus rather than hard fast rules so somewhat up to the moderator view (s). But anytime I see something deleted it really needs to have a good reason. I have seen people delete stuff that should have stayed put or if a "tie" (or just their personal opinion) it is easier to keep in DB and allow user to determine if want it or not. My 2 cents FWIW.

If it is working for you now I would likely lean towards not messing with anything you have. Just be aware that if the MAME set at some point changes/renames the Sega Model 3 roms and Supermodel isn't updated yet the game may break (easy fix just restore the older version). But if you look in the Games.XML file you will see entry like which gives you zip name of clone (getbassdx.zip) and parent (bassdx.zip) it wants to see (assuming you have split or non-merged MAME set): <game name="getbassdx" parent="bassdx"> <identity> <title>Get Bass: Sega Bass Fishing</title> <version>Japan, Deluxe</version> <manufacturer>Sega</manufacturer> <year>1997</year> </identity> <hardware> <platform>Sega Model 3</platform> <stepping>1.0</stepping> <pci_bridge>MPC106</pci_bridge> <inputs> <input type="common" /> <input type="fishing" /> </inputs> </hardware> <roms> <region name="crom" stride="8" chunk_size="2" byte_swap="true"> <file offset="0" name="epr-20837.20" crc32="0x66FC2084" /> <file offset="2" name="epr-20836.19" crc32="0xF8E8EF57" /> <file offset="4" name="epr-20835.18" crc32="0xF8F19BB2" /> <file offset="6" name="epr-20834.17" crc32="0x17F466A6" /> </region> </roms> </game> Supermodel is hardcoded to look for these rom names and CRCs of files within the zip. The developer of Supermodel does update the emulator to manage newer ROM sets but if you are one that updates your MAME set on each monthly cycle then potential for Supermodel to lag until it is updated. I think when I set up originally, I didn't find a DAT so just did it the brute force approach. I looked at the XML, copied the MAME zip to separate folder, tested each game to see if it would launch in Supermodel and if didn't opened up Games.XML look at what CRCs it wanted. Most time is tended to be a version older MAME set wise where Supermodel hadn't yet been updated. I am sure there is more elegant approach but there isn't that many Sega Model 3 games to deal with in end. Basically, if your games all work now, you don't tend to mess with your MAME rom set often, then wouldn't worry too much about it as long as you may a mental note of "why is this not working when it did before!" to first look and see if a Sega Mode 3 rom was updated somewhere along line.

Your comment about "dir.txt": that is a simple readme file that says put XYZ in that folder. But it has no function in MAME nor Supermodel and neither look to that file for anything. So modifying the text file does nothing. I found it best to not try to use a common MAME and Sega Model 3 rom folder if using SuperModel. The Supermodel emulator needs specific rom sets identified in the Games.xml file (inside the CONFIG folder) which can lag the MAME rom sets depending on how frequently you update MAME rom set and what version of Supermodel you have. For Supermodel the main files need to be in this path/configuration (Roms can be wherever) ..\Sega Model 3\ << your Supermodel.exe and its install files here in root of this folder ..\CONFIG\ << has your Supermodel.ini and your Games.XML Your Supermodel.ini should have an entry called GAMEXMLFile=Config/Games.xml if you use the standard setup. ..\NVRAM << nvram files for Supermodel ..\Saves << save folder ..\ROMS << you can name this whatever, and it can be located somewhere else (like a common rom folder with MAME if choose to go that way). As JoeViking245 said, you are pointing to the full path to the ROM when doing via command or within LB so Supermodel doesn't care. Like JoeViking245 said, if you got the above and pointed LB emulator to the EXE and have the path to the roms there isn't much else setting wise (within LB). To be able to tell anything further, we would to see some screenshots of an example game and your emulator setup screen to see what is going on.

Here are my settings, there isn't anything particularly unique on Supermodel. The majority of settings should come from your Supermodel.ini in the Config folder. So as long as your Supermodel folder is setup to normal/default this should work below: Might double check your platform matches name in Associated Platform Then it just points to the ROM/Zip file (this is The Lost World).