I'm using the latest edition of PortableApps Launcher and found this bug when developing Dolphin Emulator Portable. When I set "RunAs" as try (needed in Dolphin), the main executable Dolphin.exe gets the argument "UAC" ed to the program executable, in case of Dolphin, making the emulator won't open, only showing "unknow command line argument" message...
The current workaround I'm using is calling the main executable through a BAT file, however this is weird and break ing of real CLI arguments through the launcher...
Visit the Community page
our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
Why does it need try? Actually, why does it need at all?
Sometimes, the impossible can become possible, if you're awesome!
In computers running Windows XP and Vista, the XAudio2_7.dll isn't present, and this DLL in particular only works if I it through regsvr32 before app run (of course, I un the DLL when the app close). Calling regsvr32 as a normal make the registration fail with an 0x80070005 error (accordingly to Microsoft because the DLL need elevated privilegies), so, I ask to run as to make the DLL work. If doesn't have rights (or refuse the UAC prompt), the launcher warn the that some features won't work, in this case, the Xaudio2 backend (needed in some games for proper audio emulation)...
But if it is already installed, does it work without ? If so, I'd suggest removing try and keeping a note about that. By policy, apps like games are not allowed to require or prompt for rights. Only system apps that would normally require . If certain functions of an app require in portable mode that the app itself does not require, it is unlikely that app will ever be released officially.
Sometimes, the impossible can become possible, if you're awesome!
In this case I'll remove the RunAs requirement from Dolphin Emulator Portable and then warn the , however, the bug itself still here...
There is a fix or some workaround to this bug? Probably this is affecting all apps that use PAL, but I'm pretty sure that almost all of them doesn't care about unknown command line arguments, so, this bug wasn't discovered before.
Yes, this would still be a bug in PAL it seems when Try is set.
Sometimes, the impossible can become possible, if you're awesome!
When PAL 3.0 was still called 2.2.
Previously known as kAlug.
I'm using PAL 2.2 (the latest version available here) and this bug isn't fixed, still present. If a fix was made it isn't present in the current version
It's fixed, just not released.
Previously known as kAlug.
Is there an beta release? If yes, where we can get it?
There is no beta available, however you are able to compile from source. The source is available from SourceForge here: http://sourceforge.net/p/portableapps/launcher/ci/default/tree/
[edit] change to compile