安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
If you are confused on how to switch your user account over to an administrator user (In Windows 8 and above, not sure how to below), you must go into PC settings on another user that is already an Administrator, click accounts, other accounts, select your user, click edit, and finally set your user to administrator.
Hope this helps.
Open regedit and go to this registry,
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
Right click and add new string value. Rename it with the file path name,(which ever drive and folder location fsx is installed in) Example, D:\Steam Games\steamapps\common\FSX\fsx.exe
Then right click and modify the registry with RUNASINVOKER in the value data section.
Start FSX like you usually would and when the UAC prompt pops up for steam, just hit the escape key or click no and FSX will run in standard user mode. That's it.
Found this when I was looking around in forums for a non-steam mmorpg game that requests admin. If only this was discovered ages ago.
The real solution here is for the developer to get their act together and make a handful of changes to the software: change the hardcoded string in the .exe file and change the default folder location.
Asking users to run in administrative mode is very irresponsible, even back when this software was released. Security folks have been asking developers to avoid this practice for a couple decades.
Let's take a look at those points.
First a couple of decades ago would put the year @ 1998 being the year of Windows 98, (Windows 95 in actuality as Win 98 didn't come out till near the end of June 1998) which basically had no security at all and you could login by just clicking the cancel button, it also didn't use NTFS so no real file system security and it's boot was MS-DOS based leaving none of the above in any way constructive to any sort of security.
Yes, these days running applications with admin rights are not in general a recommended policy, however there are many neccesary reasons for doing so and infact many Windows components and applications require admin rights to run.
In any case the issue is more that where differing accounts are used they cannot see each other's security context (a concept introduced by Microsoft), and the simplest and easist workaround is to add your personal user account to the Local Administrator's group, where (with UAC active) the account will run with standard user rights until an elevation request is made, at which point you can choose to elevate and run the app or not. There are also other options within this thread such as configuring the compatability layer Microsoft has available to workaround such issues, or alterantively there are simple free tools to edit the xml manifest that are as easy to use as cutting and pasting text in notepad.
Now when FSX was originaly released back in 2006 (that would be 12 years ago...) it did not require admin rights to run true enough, however when Dovetail managed to get a license from Microsoft to distribute on Steam they faced the issue of people who already had FSX installed and therefore needed to come up with a workaround.
The below statement comes from within this very thread, and as Martin says I hope it explains it for you.
Start FSX like you usually would and when the UAC prompt pops up for steam, just hit the escape key or click no and FSX will run in standard user mode. That's it.
THERE IS NO fsx.exe ANYWHERE IN THE STEAM FOLDER
fsx.exe lives in \Steam\steamapps\common\FSX\