Single Win 10 PC with two users. Although X-Plane and Garmin trainer works for both, the Reality XP GTN is dark in X-plane for one while works for the other one. Reinstalling for the non-working user does not help.

How to get it working for both?

Hi,

can you please detail what/who is running what? I'm lost.

Sorry, will try to be more clear.

1. Single PC with Win 10, two accounts. One adminstrator the other is standard (child family). However  do not thing the account types matter, I tried both set to administrator with the same outcome.

2. Administrator installs X-Plane 11 + Reality XP GTN 750 (which automatically installs Garmin Trainer)

3. For Administrator everything works

4. Now I log in with the standard account. X-Plane works, Garmin Trainer works, but the Reality XP GTN plugin just opens GTN turned off (dark/black)

Trouble shooting steps I tried:

- change account type to administrator rule out file permission problems

- reinstall (Reality XP plugin + Garmin Trainer)

Still same outcome. It looks to me like licensing issue?!

 

Thank you for the additional information.

The installation should be user account agnostic, as far as access-rights permit.

Please note changing account type to administrator doesn't rule out the file permission problem if any. Files ACL can be set for a specific user account restricting access from the others.

In addition, the Garmin Trainer uses both a global system and a per-user registry and this might be a factor as well.

Can you post the content of the RXP log files? (see RXP GTN User's Manual for file/path).

 

rxpGtnSim.dll.log shows multiple warnings:

20/02/08 11:25:22.056 19024 -    ] # rxpGtnSim64.dll version 2.5.22.1
20/02/08 11:25:22.056 19024 INFO ] 
20/02/08 11:25:40.082 19024 INFO ] GTN 750.1 - TRAINER 6620
20/02/08 11:27:48.158 19024 WARN ] FAIL: 01 ..\..\src\krnl\krnl_lib\sim\hwm_nand_drvr_sim.c(838) (null)
20/02/08 11:27:48.158 19024 WARN ] FAIL: 01 ..\..\src\krnl\krnl_lib\sim\hwm_nand_drvr_sim.c(838) (null)
20/02/08 11:27:48.159 19024 WARN ] FAIL: 01 ..\..\src\krnl\krnl_lib\sim\hwm_eeprom_win32.c(267) (null)
20/02/08 11:27:48.159 19024 WARN ] FAIL: 01 ..\..\src\krnl\krnl_lib\sim\hwm_eeprom_win32.c(319) (null)
20/02/08 11:27:48.160 19024 WARN ] FAIL: 01 ..\..\src\krnl\krnl_lib\sim\hwm_eeprom_win32.c(267) (null)
20/02/08 11:27:48.160 19024 WARN ] FAIL: 01 ..\..\src\krnl\krnl_lib\sim\hwm_eeprom_win32.c(319) (null)
20/02/08 11:27:48.161 19024 WARN ] FAIL: 01 ..\..\src\krnl\krnl_lib\sim\hwm_eeprom_win32.c(267) (null)
20/02/08 11:27:48.161 19024 WARN ] FAIL: 01 ..\..\src\krnl\krnl_lib\sim\hwm_eeprom_win32.c(319) (null)
20/02/08 11:27:48.161 19024 WARN ] FAIL: 01 ..\..\src\krnl\krnl_lib\sim\hwm_eeprom_win32.c(267) (null)
20/02/08 11:27:48.162 19024 WARN ] FAIL: 01 ..\..\src\krnl\krnl_lib\sim\hwm_eeprom_win32.c(319) (null)
 

for comparison, this is the same file for the working user:

20/02/08 11:13:28.326 01912 -    ] # rxpGtnSim64.dll version 2.5.22.1
20/02/08 11:13:28.325 01912 INFO ] 
20/02/08 11:15:44.235 01912 INFO ] GTN 750.1 - TRAINER 6620

 

The rxpGTN.xpl.log is identical for both users:

20/02/08 11:25:19.456 19024 -    ] # win.xpl version 2.5.22.1
20/02/08 11:25:19.456 19024 INFO ] 

and

20/02/08 11:13:25.891 01912 -    ] # win.xpl version 2.5.22.1
20/02/08 11:13:25.891 01912 INFO ] 

On 2/8/2020 at 6:32 AM, tjf21 said:

20/02/08 11:27:48.161 19024 WARN ] FAIL: 01 ..\..\src\krnl\krnl_lib\sim\hwm_eeprom_win32.c(267) (null)

I've just search the RXP forum with "hwm_eeprom_win32" and this gives the following discussion back in June:

I'd suggest you read this discussion for background information about what is happening on your system with the files.

TL;DR: you'll have to run the simulator at least once as-admin and it will adjust the Windows access rights automatically and permanently even if you run as a normal user afterward.

Edited May 11, 20206 yr by RXP

7 hours ago, RXP said:

TL;DR: you'll have to run the simulator at least once as-admin and it will adjust the Windows access rights automatically and permanently even if you run as a normal user afterward.

Yes, spot on. Running (once) as admin fixed the issue.

Thanks

T.