Retro808

I think we are going to need more information than that.

Here is a link so you can click on the contact us. Also a pic of the email as it looks like translation may have changed it from support to destek. https://www.unbrokensoftware.com

If you are on Win 7, 8, 0r 8.1 then LB version 13.8 is the last version you can use. Older Winows OS will no longer be able to use 13.10 and future LB updates. You can email our team for the 13.8 installer if you do not have it in your \Updates folder. support@unbrokensoftware.com

You pasted the script in the wrong section. You were advised to paste it in the “Running Script” tab.

Nothing storefronts related was removed. It was just updated to fix an issue. The "Enable Automatic Imports On Startup" is still there in the >Manage >Storefronts setting.

Been following this thread as it is a good learning experience. End goal is to have even 20% the knowledge of @JoeViking245 and @skizzosjt. So setting up AHK as an emulator and testing using the scripts provided I am seeing the same thing as @5thWolf. With the last one skizzosjt posted I get the same thing 5thWolf is showing in the video. Without fail and it does it on a couple machines. I modified a bit and so far no issues. It launches numerous times flawlessly. What is odd is if I change the Send line to read Send, f it reverts back to what happens in the video. Even if I add the sleep timer in it. For some reason it does not like sending f. Any ides why that would matter? Or is this just case of some stupid fluke with this particular game? SetWorkingDir %A_ScriptDir% #SingleInstance, Force Run, Z2TAOL_P03.exe WinWaitActive, ahk_exe Z2TAOL_P03.exe Send {Alt Down}{Enter}{Alt Up} $Esc:: Send, !{F4} ExitApp Return

The reinstall likely installed LB into a double folder \Launchbox\Launchbox Open up your original \Launchbox folder and see if you have another Launchbox folder inside it. If you do you can remove that one and rerun the 13.8 installer. Make sure the path is just \Launchbox. At the end of the installer UI it will show you the install path. Change it there is you see it is \Launchbox\Launchbox

Video playback is a premium feature.

We do not really troubleshoot rom seller builds of LB as we have no way of knowing what they did. Your best bet is reaching out to the seller. Not to mention most here look down on those scum. I will say look in your \updates folder and if there is the installer for the prior version you can reinstall it over top of the build.

Yes. It has it's own exe and you can load from within LB. You can also be in BB and select the option to close BB and open into LB. Yes.

All prior versions you installed are in your \Updates folder. It will not change any settings. Just run the installer. Verify it installs to \Launchbox and not \Launhbox\Launchbox.

Yes. You can either just select the game roms in Windows and drag and drop them into LB to begin the rom import process or in LB -Tools -Import -Rom Files then select the Files button and manually select the roms. A few things to consider: If you do not have the roms stored in the default Mame rom folder you will need to make sure you open Mame and update the rom folder location. You can do this either by manually editing the Mame.ini or just opening Mame exe without a game and navigate to the directories setting and manually select the folder path. If you donwload individual roms as opposed to a Full Mame rom set I would first make sure your roms work in Mame directly to ensure you have the needed support files. During import I would not have LB move the roms. Leave them in your original folder. Depending on the Mame set you have moving individual rom files out of a Mame set could break things. Leaving them in the Full Mame set folder negates the need to fuss over having a non-merged, merged, or split rom set. Just makes things easier. Also doing this way if you ever update the full mame set you do not really need to update anything in LB (Except in some rare instances of rom name change/removal).

Are you on Win 7, 8, or 8.1?

In LB right click the Genesis Platform name and edit it. Go to the "Parents" tab and see if you have a check mark for the platform to show up in 2 places. Remove the one you do not want it to show up in.

Did you do what the error is telling you to do? Restore the file from one of the backup copies in your \Launchbox\Backup folder?

Email support@unbrokensoftware.com and let them know you are on win 7 and need a copy of 13.8 LB.

You are experiencing something different than what the original post is about. If you are not actually getting a specific error then it could be a few different things. If LB is just not opening at all check to see if your antivirus has quarantined anything related to LB (we have seen overly aggressive AV do this on updates). If that is not the issue try to reinstall a version prior to 13.10 and see if it opens.

If you are on Win 7, 8, or 8.1 then LB 13.10 and future versions will not work any longer. Updates required now make 13.9 the last LB/BB versions that will work on any of those older OS.

Ah crap my bad. Android bit me again. I have not messed with Android much so I cannot help much. Well, it is not really like I helped at all.

Additionally you can just launch the mame.exe without a game. Then while Mame is open just go to >Configure Options >Configure Directories >Roms then just manually locate your folders. Save that and the ini file and your Rom/CHD paths will be set.

Thanks @JoeViking245 and @skizzosjt for chiming in. Joe did mention the AHK install part and I forgot to edit my post. I forget sometimes some software used over the years is not normally installed by others.

@100dedo I deleted your other post. Please do not post the same thing in multiple threads.

When you say "not showing a file" or that it is hidden can you clarify exactly where you mean. As there is a difference in 1: Not showing in the list of games to import when inside the Import Wizard. and 2: Not showing in your C64 LB platform after being imported. In this case hidden usually means you have one of the “Hide Games Missing” options checked under the View menu in LB. If you have any of those checked just change the drop-down box under the search box in the left side of LB to "Games Missing Media". You then get a list of filters and can see hidden games. LB is file agnostic and does not know nor care if it is a game file or not. It imports what you tell it. With exception to the Mame Full Rom set importer and/or ticking the box the "Use Mame Metadata" when importing. If a game is not in our LB Games DB it will still get imported just not have any metadata or images. LB does not compare if a game is in our DB to determine if it should import/show the game. I do not have C64 games imported so I did a test with a few roms and AlleyKat (I hope is the same game you are referring to). It imported using the name the rom file was named and pulled no metadata or images from our DB since it is not there.

The steps are in my post. I numbered the steps so it is cleaner to read.

You could make a launcher exe for it to run the game and send the AHK script. 1. In the game's exe folder right click an empty space and choose New AutoHotKey Script. 2. A new file will appear so give it a name. I called this one "Adventure of Link Enhanced Launcher". Once you rename it open the file with Notepad or Notepad++ 3. Write your own/better script or past in the one I used below. Now save the file. 4. Right click on that ahk file and choose Compile Script. A new exe will be created. 5. Point LB to that as the game's file. I tested this using something JoeViking helped me with a few years ago and it worked without issue. I am sure there is better code/format for this. I have only tinkering knowledge of coding/AHK scripting. So maybe skizzosjt can make better sense of my patchwork. For some reason it would only work if I used the name Windows was showing when the app was running. Maybe using the exe name I had a typo, but I was rushing so you can try with the exe name in the WInWait line. Run, Z2TAOL_P03.exe WinWaitActive, GameMaker: Studio Send {Alt Down}{Enter}{Alt Up} $Esc:: Send, !{F4} ExitApp Return