Jump to content
LaunchBox Community Forums

sundogak

Members
  • Posts

    827
  • Joined

  • Last visited

  • Days Won

    6

sundogak last won the day on June 2

sundogak had the most liked content!

2 Followers

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

sundogak's Achievements

64-Bit Supercomputer

64-Bit Supercomputer (6/7)

418

Reputation

  1. yeah, if using non-mame name like no-intro then skip to the "kludge" way which is select a non-MAME emulator at first. Then it will import. It's because for MAME LB is trying to compare to a proper MAME arcade name and doesn't see it so it ignores it. Normally it makes sense if using arcade import since want to use the XML MAME provides to convert the zip file name to a real name but for "loose" software it doesn't work.
  2. If importing them in MAME zip naming format then make sure you check the "force using MAME metadata...." box at end of import process. It will bring up the MAME import window at that point. That may not work depending on name/type of file trying to import. Software list imports are not really supported in LB directly. There is a plug-in that does allow you to import software list MAME sets and located here: If you are using MAME to run software that isn't in MAME standard naming format like say Apple II, Apple IIGS software that sourced somewhere besides a MAME set, then I found you had to select an emulator on import that isn't using the MAME.EXE or it won't show up on end import (no matter if dupes checked or not). It doesn't matter what you select, just something other than MAME initially. Then once imported you can toggle it back to the MAME emulator instance you want to use.
  3. 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)
  4. 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
  5. 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.
  6. 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
  7. 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.
  8. 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
  9. sundogak

    eXoDOS v5

    Not easily since v4 was in separate directories by genre vs v5 all in one directory. Plus any zips that were updated for V5 wouldn't join if different size/date and looking through most of the date stamps, you will wind up replacing most. You could merge and then use TorrentZip Torrentcheck to verify but found it easier to just download V5 without messing with the V4 files. However, there is an upgrade path for 5.0 to 5.1 which is talked about in the first page of this thread.
  10. sundogak

    Apple Emulation

    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.
  11. Yes, I have 12.1 and works. No, if have Steam install then has to point to Steam folder.
  12. 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:
  13. 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.
  14. @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.
  15. 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.
×
×
  • Create New...