It goes back a bit. There's things altered between versions but the setup requires alteration too. 

Flight1 used the old trainer version to create the new complete package?

Quote

 

 

Edited April 8, 20188 yr by newtie
sp

Even though on a weekend I just heard back from Flight 1, the GTN devs have my notes and are in care of the situation.

You're the best in the west
Been put to the test
If in doubt
Check Steve out!

Edited April 8, 20188 yr by newtie
chng

My trainer is 6.21.0

 

Vic

2 hours ago, vgbaron said:

My trainer is 6.21.0

 

Vic

Mine too, so it seems it is related to the trainer version.

S.

There's a couple of things in it to do.

Actually, they just got back to me, fully understood, and an update will be issued shortly.

 

11 hours ago, newtie said:

You're the best in the west
Been put to the test
If in doubt
Check Steve out!

Ain't no cowboys around here pardner, only lawmen. 

Thanks for the background info guys - it helped a lot.

On April 8, 2018 at 5:57 AM, SteveW said:

You might notice the RXP has a similar issue - no import button, but has work arounds. This properly uses the C:\ProgramData folder for access by all users,

Hi, actually there used to be some issues with some users even though it was in C:\ProgramData\ folder, however, it is solved since the last 2 versions (and the last version has been released today) per our users reports.

The Reality XP GTN 750/650 Touch also allows you creating a shortcut (.lnk) named "FPLN', instead of a folder, which you can then redirect to any folder on any drive, be it with the latest GTN Trainer 6.41.1 or the quite old 6.21.

The Reality XP GNS 530/430 V2 also has flight plan import, with a folder or a file shortcut, and also exports the saved catalog routes to disk via an in-GNS convenient 'export' menu entry!

How is this different from the Flight1 unit? 

Will it be picked up by aircraft (ex. Flysimware Lear) like the Flight1 750?

Thanks,

Mark

9 hours ago, RXP said:

Hi, actually there used to be some issues with some users even though it was in C:\ProgramData\ folder, however, it is solved since the last 2 versions (and the last version has been released today) per our users reports.

Yes that's correct. Although in the C:\ProgramData\ folder it is still the responsibility of the installer to create the app settings folder in there and provide Modify access to the users Group. Otherwise there would be problems.

By 'users group' that means the authenticated users of the system or perhaps a special group created for allowing use of the app by certain authenticated users. Of course we generally only need the system ready 'Users' group (or 'Authenticated Users' - the equivalent network aware group) as perhaps only we are using the PC. We are a member of Users when we log into Windows. Apps that put User settings in the Program Files folder can be helped in the same way with providing those folders Users group with the Modify Allow permission too. Often we see this as a result of the regular user having automatic access on Windows XP. The technique was incorrect then as well, but not an issue so long as the permission to write there is given to the user. The old trick of making a folder to install into and finding it all works perfectly is simply because we own that private folder. However, devs should be made aware that installing apps into a Private Folder can actually become a problem later if certain issues arise in Windows user profiles. We simply give the modify permission to the Users group concerned whenever we have a folder where we want to write out to - logged on as a mere user.

 

Edited April 10, 20188 yr by SteveW

...By the way. That's not something I thought up last week might be a good idea. That's from the Windows application development manual from Win XP days.

While we are on that subject let's look at the C:\ProgramData\ folder - That is the physical location of C:\Users\All Users - Parts of All Users might actually exist on a server farm - not on the PC. Folders pertaining to network apps and users settings for example, may also have a group defined for authenticated access.

C:\Users\[YOU] very similar - some of these folders might be on the server so beware installing your apps in those circumstances. We find apps for FSX/P3D might not be aware.

 

Edited April 10, 20188 yr by SteveW