JoeViking245

Exactly (essentially). It doesn't a Force Close, so it's safe.

Grabbed from some old notes for doing something different, but the result is what you want... ; Master application Process, Wait, BigBox.exe Sleep, 5000 Process, Wait, BigBox.exe Process, WaitClose, BigBox.exe I'm not sure when exactly when the Startup App gets triggered, so for a safety measure we wait 2 times. The 1st Wait is for BB launched from LB's root folder. That exe starts BigBox.exe that's in the /Core/ folder then closes itself. We give the 1st exe a few seconds to do its thing then Wait for /Core/BigBox.exe to be running. Lastly, wait for it to exit before restoring things. You might be able to do away with the 1st two lines of code. But having them in there won't hurt anything and the cost (programmatically and financially) is free. 😎

Sounds like that'd be an excellent feature request. (Help & Support - Request a Feature [at the top of this page]) I'm not sure making the xml ReadOnly is a good idea but should do-the-trick. For a while. One problem, as mentioned is you wouldn't be able to save any changes to BB. But if you have it setup the way you want, there really is no need. Another [potential] problem would be when BB gets updated. I do this on my cab for (A) playing on the cabs monitor or (B) playing on the TV. I use different Themes for each and have a PowerShell script that will 'edit' BigBoxSettings.xml, changing the Theme accordingly. Then starts BigBox. (2 scripts actually. One for each screen.) Here's an example that will set the <LastPlatform> to "Arcade" and then start BigBox. Before using something like this, you will need to have had BB closed with the option Rember the Last Platform set to On. Otherwise, the script won't be able to find the element <LastPlatform>. $filePathToTask = "D:\LaunchBox\Data\BigBoxSettings.xml" $xml = New-Object XML $xml.Load($filePathToTask) $element = $xml.SelectSingleNode("//LastPlatform") $element.InnerText = "Arcade" $xml.Save($filePathToTask) & D:\LaunchBox\BigBox.exe Exit It's not the prettiest startup process (i.e. you see the PowerShell window pop up for a second), but is quite effective. You could probably do the same thing via an AutoHotkey script or maybe even a batch file, if those are more your flavor.

Option A Edit your RetroArch emulator and add a 2nd "Atari 800" Associated Platform, set it to use the other core and do not check the Default Emulator box. Save. Then to use the other core: Right-click a game and select Launch with - RetroArch and select the other core. Option B (the override option) Edit the games that you don't want to use the platforms' default core and set a custom command line parameter that'll load the 'other' core. Edit a game got down to Emulation check the box Use Custom Command-line Parameters type in the command to load the other core -L "cores/atari800_libretro.dll" (or whatever core you need to load) Save This would need to be done per-game (aka one-by-one). To do this in bulk (change if for several or many games all at once), you can use the Bulk Custom Command-Line Editor plugin.

Dang! I was sure that had worked before. But then again, I've been wrong before too. And after some testing, I find I am wrong again. Sorry about that. I don't actually use BB that often, and when I do, I'm usually playing in the same platform. One other option (not that the 1st one turned out to be an actual option) is to set the platforms Sort Title to something like "01". (LaunchBox, Edit platform, Details tab, Sort Title). Also, turn off Remember Last Platform (in BigBox). This should put it at the top of the list above 3DO. It might look funny being there, but it will still say "Arcade" and be the default starting platform.

Do the above steps not work to do that?

Pretty sure with most cores, you don't need to have LaunchBox extract the ROMs 1st. You might try unchecking that option on one or a couple of the Associated Platforms and test that way. I'm not saying they shouldn't work if LaunchBox extracts them 1st. It's just I've never tried it that way.

Yes. To start BigBox ON a specific platform: In BigBox, navigate to your Arcade platform. Exit BigBox (re)Start BigBox You should be on Arcade Goto System Menu - Options - General Turn Off Remember Last Platform I don't believe there's an option to start BigBox IN a specific platform (viewing the games).

"Version" is not in the options to be displayed in the Game Details (your 2nd screenshot, "Information"). But you are able to display it along with the text in the Main View. (You'll also need to have Text on All Games checked.) View - Show / Hide, Versions

If done per the method shown in the video, the image only gets saved to the appropriate /LaunchBox/Images/... subfolder.

You can't have both open at the same time. You can either start BigBox by itself (BigBox.exe) or when in LaunchBox, you can press Ctrl+B. This will close LaunchBox and open BigBox. There will be a slight delay between closing and opening while LaunchBox saves all the data.

The MAME full-set import wizard doesn't look at your physical ROMs (except to initially verify that you have a full-set) during import. The ROMs that get imported are based on your selection(s) (i.e. include non-working) and crossed with the 'known list' of all ROMs for that version of MAME. The "known list" is generated during the import process directly from [your version of] mame.exe.

I think you got lucky 'simply adding another one'. But as I illuded towards, a pretty cool happenstance. Why there are two "ToggleEverything": We set the variable ToggleEverything to equal the return value of the method HideDesktop(). So looking at what HideDesktop() does, the last thing it does is it returns 2 values. So now ToggleEverything is holding (equal to) 2 separate values. Making it an 'Array'. The 1st value in the array is stored in ToggleEverything[1] and the 2nd value is in ToggleEverything[2]. Now when you look at the method RestoreDesktop, it requires that 2 parameters be sent to it. "originalWallpaper" and "origBackground)". So when you execute it under "To Restore Everything", you have to send with it, the 2 parameters. Note, we place these 2 parameters inside of the methods parenthesis. RestoreDesktop ( ToggleEverything[1] , ToggleEverything[2] ) (added spaces and colors for clarity) Now adding a comma after the last (closing) parenthesis of this method we're executing, allows us to string together multiple commands. (so I had learned, today) I'm not sure how far you can go with it command_1, command_2, command_3, command_4 ... But from a coding readability aspect, probably don't want to go too far.

That's quite elegant. I'd never thought to put 2 methods onto one line. TBH, I didn't know you could [and just separate them with a comma]. Today is a good day as I learned something new. Thanks for this! ; To hide blah, blah, blah and set custom cursor ToggleEverything := HideDesktop(), SetSystemCursor(file) ;*** VS *** ; To hide blah, blah, blah ToggleEverything := HideDesktop() ; Set custom cursor SetSystemCursor(file) Out of curiosity, what did you do differenly to make it work?

The file = [pathToCursorFile] variable would go near the top of the script with any other variable declarations (and before any hotkey assignments). The 2 functions ( SetSystemCursor(file) and RestoreCursors() ) would go at the bottom of the script (below any hotkeys and subroutines). Then inside the method (or function or subroutine) that 'starts the file', add in the single line SetSystemCursor(file) (removing the F3 hotkey assignment). Likewise, wherever the file gets 'closed', add in RestoreCursors() (removing the F4 hotkey assignment). Sorry. I don't. I ran the 2 RegWrite lines back-and-forth several times. In between, checking the registry (HKCU\Control Panel\Desktop\ScreenSaveActive) to verify that it changed. And it had. (note: when looking at the registry, you'll need to click a different folder, then click back to the 'Desktop' folder to see the change)

Thanks! Not personally tested, but this looks like it should work. You'll need to have the custom cursor file and edit the 1st line to point to it. https://www.autohotkey.com/boards/viewtopic.php?p=356126&sid=6cea5e7a2d7eb46ec819002b2927457f#p356126 I haven't used a screen saver since the early 90's. lol The easiest way is probably to change the registry value directly. ;Disable screen saver RegWrite, REG_SZ, HKEY_CURRENT_USER, Control Panel\desktop, ScreenSaveActive, 0 ;Enable screen saver RegWrite, REG_SZ, HKEY_CURRENT_USER, Control Panel\desktop, ScreenSaveActive, 1

OK. Well, I assume when you edit that game (Crisis Zone) in LaunchBox, in the Launching section, ROM file it pointing to "E:\Games\PCSX2\CZ.ahk". Go to the Emulation section and un-check Use an emulator to play this game (primarily for console games). Save and close. Click Play and it should now launch the AHK script directly, just as it had done from Windows Explorer.

Looks like it's saying that pcsx2 can't run an AHK script. What I suspect you're essentially doing right now is: pcsx2-qt.exe "E:\Games\PCSX2\CZ.ahk" Which of course doesn't work. You need to have that game NOT use an emulator, and just run the script. If you have AutoHotkey installed on your computer, it should work this way. If you don't have AutoHotkey installed, you'll need to go another route. If you simply double-click CZ.ahk in Windows Explorer, does it all run correctly?