sundogak

Don't see this announced anywhere on their official forums, but here are two to add to the two already completed:

Here you go:

@legolas119 If the ROMs don't work after checking them then it is problem with your setup of Altirra because it checks the checksum of the file to look up in the DB. Plus if you are not able to run XEX and ATRs then indicates an issue with your setup, not the games. A straight reinstall with options recommended should work with all those formats with little to no modifications.

@legolas119You have to add the mapping and/or edit the existing ones. Then select the target in option box. Start and select will be there under target drop down.

@legolas119 It is a two step process. You choose whatever it says to use either in Altirra as recommended (less accurate) or in the second tool I linked (the Atari Rom Checker) which is more accurate. Once you have that step done then you can select whichever it says to. The second program will then add header to rom. I personally rename the file with "CAR extension" to keep straight which I have completed. They are not all the same so no "best". The ROM checker compares file to a set of checksums for known roms and gives you the information. Also be careful that anything with CAS extension is a cassette and that has nothing to do with any of this. The headers only apply to BIN/ROMs since the were taken from cartridges in most cases. XEX are executables and again have nothing to do with the headers for carts. If you try to have the rom checker analyze an XEX or CAS file it will not work and definitely do not want to use the ROM header tool on any CAS or XEX files or it will mess them up so they won't run.

@MuddyWaters79 Glad you got it working. Sometimes just going from scratch works best. Not sure why that video (which haven't looked at) is saying to unzip a bios/rom unless it was referring to a Retroarch MAME setup which is different animal. For MAME standalone, it looks for things inside the zip files if it is a ROM/BIOS. CHDs it assumes are standalone. Software list CHDs, like CDI are are bit different but as you found as long as MAME can find the CHD path and the ROM path then will launch.

I am talking about the ROMs not the CHDs. You said in your post you unzipped the MONO rom. Those do not get unzipped.

@MuddyWaters79 You never extract the ROMs. They stayed zipped in your main MAME folder that you have pointed MAME to in your setup.

I have never gotten around to setting up SINGE so might be a bit different, but looking at my Daphne command line I would try a couple things: move the -fullscreen flag before the x and y flags. if that doesn't work, try moving the fullscreen and x,y flags to after your framefile reference.

@WiredKydd Your log indicates LB is telling ePSX to launch Fighting Force (USA) (Track 02).bin. You cannot point to a second track for multi BIN games. LB should be pointing to CUE for multiple binary files. So likely an issue with what you have in the launch path for the ROM and ePSX is just launching the start ROM but no game was passed to it. Otherwise, there is nothing in the LB log to indicate a problem on LB side.

For standalone MAME see these threads: But quick setup is to add the default command cdmono1 -cdrom in your MAME setup.

That is because the BIN/ROM files are missing the header needed by Altirra. You cannot force Altirra via a setting to auto load the one it assumes. Cartridge files with proper header will typically have the *.CAR extension to differentiate from those that do not (ROM/BIN). So you can either get the prompt each time, use a different emulator that has built in DB to determine header on the fly, or use the following two tools to put the correct headers on BIN/ROM files: http://www.wudsn.com/index.php/productions-atari800/tools/atarirommaker http://www.wudsn.com/index.php/productions-atari800/tools/atariromchecker

F2 is Start just like on an actual Atari you had to hit that to begin in many case. So should map that to your controller if using controller: Yes, you can install in LB. Map to profiles if using for different platforms. If just using one such as 800 then I believe it starts up with the last profile used. I generally turn off start up screens on the computer emulators so can see what is going on. If want to map reset, save, load and swap discs then need to put appropriate AHK commands in since LB will not have anything by default. You don't have to do this just makes the pause screen usable for those options. I also mapped a running AHK script for the ESC key to exit but depends on what you are doing. Sometimes with Computer emulators you may need to use that key. For most part I am sticking with carts and a few cassettes that I used in the day.

@legolas119 For Altirra, I would double check your Video settings in Configure System window and turn off any "Video Effects" since in the one screen shot has scan lines. You may be getting driver conflict. Although it wouldn't cause the crash, you don't need to turn on "Accurate sector timing" for most part. It will take a long time to load an ATR file if you have that on. Otherwise looking at the instructions they appear fine so you should be up and running with no changes (other than sector timing). I would make a backup of your Altirra.ini and make a blank one. Then return to running the installer (there is a 4.0 version released now as well so would download that). Do the defaults as noted in your screenshots and then see if can run before making any other changes. XEX (mostly) and binary/cart files should run instantly whereas ATR and CAS will have to load. So I would stick with testing XEX and BINs first. Otherwise if you do you fresh install and those don't run out of the gate then may be some issue with the ROMs you have, particularly if you have one or two ROMs that work. I tried XEX for Encounter and booted fine with default Altirra install as well as Star Raiders both ATR and Cart versions (Cassettes are a different animal).

The LB pause menu feature will not work with FX3 or Future Pinball if using BAM. Visual Pinball X is only one the pause menu in LB will work on. However, the controller exit combos in LB will exit FX3.

I saw that thread plus another where a Norton user missed the pop up. So agreed on this part, that it is easy enough for user to miss it or not read it, particularly if not expecting it (I did in the 11.5 betas initially). Assuming user has not turned on silent mode, it will do a task bar pop up that stays up for ~20 seconds or so. The bigbox.dll one is actually a red popup since flags as high risk. If no user interaction (or click on details) the pop up will hide itself. The quarantine history will show it as unresolved but as you noted, user is unlikely to open history window in AV software. But like said above, LB never had issues 11.4 or prior and AV junk or not, these are brands that many may have on their PCs (XFinity in US gives Norton away "free", for example). So will continue to be an annoyance for many if not resolved on LB side since most won't dump/change their AV program.

It isn’t just Norton since saw reference to folks with Avast having issues as well (just one I recall off top of head). Norton does advise it found issue with the DLL and pops up notification accordingly, so the comment on its behavior is incorrect. It also notes in log or quarantine if it moved. It started with code changes to LB, not something new to Norton. Also 11.5 was coded to avoid triggering AVs with some fiddling by Jason. So it is something that is workable on LB side even if it sounds like it is annoying from a coding perspective. Defender is great, but I wouldn’t use it as sole AV. To each their own. I also have no grand allegiance to Norton, but it (and others) has served me well over the decades. LB is also great software, but ultimately it is the code changes in LB that started falsely triggering and from my perspective should be addressed by LB, at least from a support headache view as well as user experience. These are large market share AVs having issues, so the LB user base in aggregate is going to keep running in to it, regardless of views positive or negative on their worth.

I have Norton as well and it has issues with the Bigbox.dll since they moved to the Net-core platform. It was resolved for 11.5 but popped back up on 11.6 and the 11.7 beta. It is a false positive , but it is annoying in that prefer not excluding things if can help it.

Just a wild stab since works fine on my end. Have you toggled/checked your video player settings in LB? Does it happen on other themes or just default? The video is scaling to TV size and not the theme window. Have you tried changing resolution on TV (not a fix, but just to see if glitch there).

Means you have an incomplete MAME set if some work and others don't. That's a MAME thing, not LB. However, if some run and you want that one to work when launching as default within LB, then go into the game via edit and select Additional Apps. You can then select one you know works and make it the default. Then LB will launch that version. However, won't fix the other versions until you get MAME squared away.

Go to Tools, Options and adjust your video priorities for video type you want to play when game selected. There is no way "on the fly" to get option to choose however.

Check your antivirus software. Likely it quarantined the big box.dll as a false positive which has been issue since the switch to the new Net.core I know it does it on Norton. So reinstall the program and whitelist that dll when it flags it.

TPAFreeCamMod is checking the executable to verify proper version since it works by altering code in real time once TPA is launched. So if you have a hacked executable (Regardless of version) it isn’t going to work with the Mod since it won’t see the code it is looking for. So will not be able to use it as launcher. There is another launcher beyond the CamMod out there, but haven’t used it to know if would be similar issue.

Try a reinstall. Copies of the installers are in the ..\Launchbox\Updates folder. Check you antivirus log. Particularly if using a beta version, make sure checking your antivirus is not nuking parts of LB install. For some antivirus programs (like Norton which I use) it will flag and remove parts of the LB install and it won't work unless whitelisted/restored.

1) Backup XMLS are not stored in the original directory but are zipped up and stored in ...\Launchbox\Backups LB makes backups and launch and exit and stores them there as well as if you do a manual database backup via menu in LB. 2) You should check after fully closing LB/BB before searching, they can get cached so may not see if have LB open. It basically "has" to be there if it is showing in LB upon relaunch since that is what LB uses to show data. 3) shouldn't. Not sure why they would be deleted on a reboot since shouldn't be anything to remove an XML. I would check to see if your backups folder has copy upon shutdown of the current version you added or see if those date stamps/versions are also seeing issues. Then upon exiting LB, if the XMLs appear updated (date/time stamp). If reboot is nuking them then something outside LB that is causing that. You might try installing a dummy LB into another folder and see if seeing the same issues there or some corrupted install/directory in Windows.