cpujunkie

apparently you can just turn off the prompts but uac is still active? So yeah.. I thought disabling the prompts turned uac off but apparently it just auto excepts and grants elevated rights. Just go to the Change User Account Control settings in control panel. Not the best solution but definitely easy

apparently you can just turn off the prompts but uac is still active? So yeah.. I thought disabling the prompts turned uac off but apparently it just auto excepts and grants elevated rights

disabling uac on Windows 10 doesn't allow windows store apps (uwp) to run or I would (gears of war, super luckys tail, etc). Plus the lil bit of a safety net when using the computer

learn something new everyday. There goes my way of getting rid of uac prompts when launching games. Been using Windows since '93 and launchbox since it's price went from 10 to 20 dollars but didn't know that about programs with different elevation of rights.

I was wondering exactly what issues are caused by running LB/BB as admin. Which emulators have issues, what are the issues. Which utilities and what's their behavior. Any other weird behavior. The reason I run as admin is to stop those UAC prompts when launching pc games (especially the old ones). Could Jason make a startup utility / service that could launch just the games and emulators we wanted with admin rights so we don't get uac prompts and LB/BB won't have to run with admin rights? Like a check box somewhere "Launch this with Admin Rights"

which programs? Are they processes spawned by launchbox? After searching for an answer on the web one of the best solutions was to run a program launcher as admin and launch the apps from that to not have the uac prompt.

one tip is go into the file properties for launchbox and big box and check run as administrator. then anything launchbox launches will just start up. As for launching the games outside of launchbox, directly from Windows there are ways but I don't know them off the top of my head.

Cool, if it works it work. I'm trying to figure it all out so in the future I can do a better guide

one problem I run into all the time with emulators and pc games is if the controller isn't turned on \ plugged in before I start said application then it doesn't see it at all after I do turn on the controller. This was the main reason I went to retroarch for emulation and also why I also started using retroarch for mame. There are still other emulators and plenty of pc games I play. But having to quit then restart or if a second player wants to join just to get the controllers recognized. Sometimes the controller settings get wiped and I have to set it up all over again. Is there a program like x360ce but for dinput so I can setup a "virtual" controller then emulator/game thinks is always plugged in? Like x360ce setup multiple controllers player1, player2, etc. So I can just start these applications then pick up my wireless Xbox 360 controller turn it on and start playing?

Is there any spaces in the path\file name for the rom? That was the thing causing people the errors in loading was needing quotes around the whole arguments and the quotes around the file name. That's where the backslashes around the quoted romfile and path come in. They tell the command line that the argument doesn't end at that second quote. If the path\file doesn't have spaces we could just add it to the normal retroarch emulator entry. This whole thing started because I wanted to run neogeo cd in retroarch and the cd image file names and path have spaces in them.

does the ps3 read the Linux file system? I'm not sure on Windows how to format and copy files to a Linux formatted drive. Could boot up a live Linux distro. Format and copy over

The only thing I can think of is format the drive in exfat or some kind of fat32 made for large drives. I think the 32GB drive is small enough for a normal fat32 format. just a guess

don't forget that second double quote at the end "a5200 -cart \"%romfile%\""

the why on example 1 not having a -rp (rompath) is because the core has generated the ini file with that info in it so I tested it without and it worked. The rompath is there for the bios the mame core is looking for. In my neocdz.ini the rom path has a directory listed. You could run once, edit the corresponding ini file to fill in the rompath and not have the whole -rp c:\directory in the command line. I believe to be able to generate an ini file the option of mame_write_config has to be enabled and probably also mame_boot_from_cli has to be enabled in the retroarch cfg file of retroarch-core-options.cfg

go ahead and make it it's own guide ?

I believe in the retroarch-core-options.cfg file that the option mame_write_config = "enabled" This method works without hash files or softlists

figured out how to copy the post I'm going to post this answer in a few different areas on the forum. I have been trying to figure out how to launch retroarch mame for the systems that don't have a stand alone core. I have finally found a mostly elegant solution 1) Add a New Emulator - I have named mine RetroArch MAME console cores Add your retroarch.exe Make sure to check "Don't use quotes..." 2) Tab over to the Associated Platforms Here's the magic sauce example 1 "neocdz -cdrm \"%romfile%\"" example 2 "a5200 -rp \"F:\Roms\Atari 5200\" -cart \"%romfile%\"" example 3 "coleco -rp F:\Roms\ColecoVision\ -cart \"%romfile%\"" The reason for the "Don't use quotes" and adding this as a new emulator is because of the special thing we have to do to the command line using mostly the same arguments has standalone mame/mess you have to have all the arguments in double quotes " but because of how Windows handles long file names with spaces the locations have to be in quotes to. This throws retroarch/the windows commandline off. This is where the \ before the double quote at the beginning and the \ before the closing double quote per directory/location. Also we can use the launchbox variable %romfile% to help make this work. 3) On top of all that you also have to specify the rompath if the mame core hasn't generated an ini with the rompath. This is needed for the bios of the core you are loading. If all your mame console bios files are in the same dir you could just use that for each entry The core will generate ini files for each system after first run. 4) I also edited my retroarch core options file. I probably enable boot to bios but I don't at the moment. There is my setup for launching roms through retroarch mame. I hope this helps

figured out how to copy the post I'm going to post this answer in a few different areas on the forum. I have been trying to figure out how to launch retroarch mame for the systems that don't have a stand alone core. I have finally found a mostly elegant solution 1) Add a New Emulator - I have named mine RetroArch MAME console cores Add your retroarch.exe Make sure to check "Don't use quotes..." 2) Tab over to the Associated Platforms Here's the magic sauce example 1 "neocdz -cdrm \"%romfile%\"" example 2 "a5200 -rp \"F:\Roms\Atari 5200\" -cart \"%romfile%\"" example 3 "coleco -rp F:\Roms\ColecoVision\ -cart \"%romfile%\"" The reason for the "Don't use quotes" and adding this as a new emulator is because of the special thing we have to do to the command line using mostly the same arguments has standalone mame/mess you have to have all the arguments in double quotes " but because of how Windows handles long file names with spaces the locations have to be in quotes to. This throws retroarch/the windows commandline off. This is where the \ before the double quote at the beginning and the \ before the closing double quote per directory/location. Also we can use the launchbox variable %romfile% to help make this work. 3) On top of all that you also have to specify the rompath if the mame core hasn't generated an ini with the rompath. This is needed for the bios of the core you are loading. If all your mame console bios files are in the same dir you could just use that for each entry The core will generate ini files for each system after first run. 4) I also edited my retroarch core options file. I probably enable boot to bios but I don't at the moment. There is my setup for launching roms through retroarch mame. I hope this helps

https://forums.launchbox-app.com/topic/39086-passing-parametersarguments-to-retroarch-cores/?do=findComment&comment=286675 Heres a link to my solution. I didn't know how to embed the post

I'm going to post this answer in a few different areas on the forum. I have been trying to figure out how to launch retroarch mame for the systems that don't have a stand alone core. I have finally found a mostly elegant solution 1) Add a New Emulator - I have named mine RetroArch MAME console cores Add your retroarch.exe Make sure to check "Don't use quotes..." 2) Tab over to the Associated Platforms Here's the magic sauce example 1 "neocdz -cdrm \"%romfile%\"" example 2 "a5200 -rp \"F:\Roms\Atari 5200\" -cart \"%romfile%\"" example 3 "coleco -rp F:\Roms\ColecoVision\ -cart \"%romfile%\"" The reason for the "Don't use quotes" and adding this as a new emulator is because of the special thing we have to do to the command line using mostly the same arguments has standalone mame/mess you have to have all the arguments in double quotes " but because of how Windows handles long file names with spaces the locations have to be in quotes to. This throws retroarch/the windows commandline off. This is where the \ before the double quote at the beginning and the \ before the closing double quote per directory/location. Also we can use the launchbox variable %romfile% to help make this work. 3) On top of all that you also have to specify the rompath if the mame core hasn't generated an ini with the rompath. This is needed for the bios of the core you are loading. If all your mame console bios files are in the same dir you could just use that for each entry The core will generate ini files for each system after first run. 4) I also edited my retroarch core options file. I probably enable boot to bios but I don't at the moment. There is my setup for launching roms through retroarch mame. I hope this helps

I have been working on this issue for awhile and have figured it all out. I am using retroarch mame to load systems that retroarch doesn't have stand alone cores for. When I get back at my computer I'll post the three different ways I have solved this problem.