May 20, 20197 yr Author The nonvol folder is empty. Howard Jetline Systems: Intel 8th Gen Core i7 8700K (4.8GHz Overclock); GTX 1080 Ti; LG Curved UltraWide 3440x1440 Monitor .
May 20, 20197 yr Hi, I've finally managed to better understand the issue and here is a step-by-step guide. First things first: the problem is related to file security and your user login access rights. When the non volatile memory file is first created as a normal user, it will be fine. However when the non volatile memory file is first created when running as-admin, it won't have your user account access rights therefore it won't be accessible by the trainer when you run as a normal user. 1) locate the GTN 750 #1 non volatile memory file. It should be: C:\ProgramData\Garmin\Trainers\GTN\nonvol\sys_nandi 2) right click the sys_nandi file then select Properties > Security Your user account shouldn't be there if the file was first created when running as-admin: This is what is expected if the file was first created normally: this tells your [username] login has all the listed access rights (Allow column). The most important ones are: Read, Write and Read & Execute. 3) Click the "Edit" button to change the access rights 4) Click the "Add..." button to add your user account The "Select Users Or Group" window opens. Type your user account/login name in the "Enter the object names to select" area, then click the "Check Names" button to the right to validate, then click OK. The Permissions panel should show something like this: 5) Click the "Read & execute", "Read", and "Write" boxes in the "Allow" column then click "Apply" then "OK" The sys_nandi file should now have access rights both for your user account when running normally and when running as-admin.
May 20, 20197 yr Author Thanks Jean-Luc. Can you please tell me my username for the GTN750? Howard Jetline Systems: Intel 8th Gen Core i7 8700K (4.8GHz Overclock); GTX 1080 Ti; LG Curved UltraWide 3440x1440 Monitor .
May 21, 20197 yr Author Thank you! Howard Jetline Systems: Intel 8th Gen Core i7 8700K (4.8GHz Overclock); GTX 1080 Ti; LG Curved UltraWide 3440x1440 Monitor .
May 21, 20197 yr Let me know if this works for you and we'll see whether we can make this happening programatically in our future updates, so that 'black screen' is a thing of the past for all our customers running the solution once as-admin and being stuck from then on.
May 21, 20197 yr Author Hi Jean-Luc. I will be back home this afternoon and will definitely let you know if this works. Howard Jetline Systems: Intel 8th Gen Core i7 8700K (4.8GHz Overclock); GTX 1080 Ti; LG Curved UltraWide 3440x1440 Monitor .
May 21, 20197 yr Author I'm sorry Jean-Luc, but it did not work. It only started when I started as administrator. I did as you instructed above, but I can't attach a copy to show you. Howard (DESKTOP-Q847QE\Howard) Edited May 21, 20197 yr by Howiefly13 Howard Jetline Systems: Intel 8th Gen Core i7 8700K (4.8GHz Overclock); GTX 1080 Ti; LG Curved UltraWide 3440x1440 Monitor .
May 21, 20197 yr Author Yes, the first 3 lines. There is no 4th line. There are grey check marks in the allow column. Send me your email and I will forward a photo. Edited May 21, 20197 yr by RXP [privacy: removed email address] Howard Jetline Systems: Intel 8th Gen Core i7 8700K (4.8GHz Overclock); GTX 1080 Ti; LG Curved UltraWide 3440x1440 Monitor .
May 21, 20197 yr The 4th line, "Users ([computername]\Users)" is for all users. So do you mean initially you only had 2 lines instead of the 3 lines I've shown in the screenshots? It shouldn't be a problem not having the 'all users' entry as long as you've manually added your username, and similarly, you can add 'all users' exactly the same way you've added your username. NB: they are grey once you've APPLY + OK + reopen the panel (see the 'expected' screenshot above).
May 21, 20197 yr Author I did manually add my username and the checks are a light grey. Howard Jetline Systems: Intel 8th Gen Core i7 8700K (4.8GHz Overclock); GTX 1080 Ti; LG Curved UltraWide 3440x1440 Monitor .
May 24, 20197 yr Hi Howard, I'm glad we've managed to sort this one out, thanks to your enduring patience and assistance. I confirm a workaround to make this all automatic is on its way in a future update.
Archived
This topic is now archived and is closed to further replies.