Solved Error With Alt Luncher 4.37.3 Full Installer U3
-
@CloudWallace1981 @Razor161 @Vespa Can you guys verify the permissions on the BMS registry key?
The installer should be granting full-control to all users… (if it’s not, for some reason … this would explain why launching as admin helps.)
But so far I’m unable to repro, even on a clean-box test virtual machine. My systems all look like this =>
-
@airtex2019 how can I check exactly?
BTW, there was no prompt during BMS installation to restrict privileges of the launcher to a specific user, or to install it only for the current user
My usual clean installation procedure is
-
Install F4 from the standalone GOG installer to a “dummy” folder on a different HDD (like F:…\Falcon4)
-
Launch F4 once anche check that the usual registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\MicroProse\Falcon\4.0 and HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\MicroProse\Falcon\4.0\MPR are there
-
Install BMS in C:\FALCON BMS 4.xx
-
OPTIONAL: remove everything from the dummy F:…\Falcon4 except for the game exe, to save space
-
-
@CloudWallace1981 see my screenshot with orange arrows.
(right-click on the
Falcon BMS 4.37
registry key, and select “Permissions…” on the popup menu … then click ‘Advanced’ button) -
Ok, I’ve googled how to check permissions on keys. What kind of access level should my local user have?
I’m on mobile atm, I’ll verify this evening CET time
-
@CloudWallace1981 ty… no worries – I just repro’d this, on my test virt.
ordinarily, normal (non-admin) users would have readonly access to everything under HKLM
the BMS installer does (did? should?) grant full-control to all local users, for stuff under the “Benchmark Sims” key
it sounds like this isn’t happening, for quite a few of you…
-
@airtex2019 I might have an idea…
Did those people use the new installer?If yes, there might be some issues linked to the new 64bit format that doesn’t trigger specific plugins…
If this is the case, I’ll have to redo a new installer…
-
@MaxWaldorf
I used the full installer for 4.37.3. -
@airtex2019 said in Error With Alt Luncher 4.37.3 Full Installer U3:
@CloudWallace1981 @Razor161 @Vespa Can you guys verify the permissions on the BMS registry key?
The installer should be granting full-control to all users… (if it’s not, for some reason … this would explain why launching as admin helps.)
But so far I’m unable to repro, even on a clean-box test virtual machine. My systems all look like this =>
@airtex2019
The permissions are set to “Read”. So that might be the issue here.Edit:
I disabled permission inheritance for “Falcon BMS 4.37” and assigned “Full Controll” to “Users”.
Problem solved. -
@MaxWaldorf I used the new full installer, yes
-
@Razor161 said in Error With Alt Luncher 4.37.3 Full Installer U3:
set to “Read”. So that might be the issue here.
yep … the AL code tries to open the key as read/write, because it updates the PilotName/PilotCallsign values
this was never an expected mode of failure, so it ends up with an empty-string for the install directory, then chaos ensues… I’ll fix AL to behave better, but that will take a while. Max will probably bake a new installer before that happens.
I’ll see if I can make a little script to patch this, to unblock folks, in the meantime…
-
@MaxWaldorf i use U3 Full installer too.
-
@CloudWallace1981 @Razor161 @Vespa @Roger-Burgess thanks everyone for helping investigate and debug this very unusual and unexpected problem.
we’ll fix the installer and improve AL to deal with this… in the meantime:
short-term workarounds => run AL and BMS as admin.
or, open Regedit and grant full-control of
HKLM\SOFTWARE\WOW6432Node\Benchmark Sims
registry key to the all-users group. -
@airtex2019 Thank you too
-
@airtex2019 I’ll go for the regedit way, thanks
-
@CloudWallace1981 said in Error With Alt Luncher 4.37.3 Full Installer U3:
@Razor161 try launching Launcher.exe as an admin
I had this exact problem. This fixed it.
-
-
@Roger-Burgess A new installer will be posted in the coming days to solve that issue…
-
@MaxWaldorf
No worries, I fixed the permissions issue using the registry. Just reporting that it worked so people can see commonality of resolution of the issue. -