I have searched for information on this subject, to no avail, so perhaps someone can point me in the right direction or even have the answer in their own pocket.

Situation:
GPL is installed on my external HDD and has been thus for years.
It has always performed faultlessly. I open it up with GEM and the use the various features of that program to pick and choose which mod I wish to play (from 1955 through 1969 plus GTs and Can-Am).
Never had a problem with GEM in all the time that I have been using it.
The PC into which my HDD is plugged has been with me for several years now and again, it has been ultra-reliable.

Two days ago I bought a Windows 10 PC - nothing flash, mostly intended just for office work, emailing and browsing.
I wondered how GPL would perform on it so plugged in the HDD.
Clicked on the GEM icon - the exact same icon which I have clicked on for the past several years without failures - and I get a "Fatal Error" message.
Clicked on one of the GPL .exe files for one of the mods and GPL started up without any dramas.
Played the game for a few minutes, backed out and clicked on GEM again.
"Fatal Error".

Clicked on another GPL mods's .exe file and.....no dramas. Everything ran as per normal without any faults whatsoever.
Ditto and ditto and ditto for every other GPL mod, from the original all the way through to 1955.
They all work fine but I cannot pick and choose which ones to use or which circuit to run because I cannot get GEM to fire up!!

So GPL certainly runs under Windows 10 but for some obscure reason it doesn't like my GEM.

I have windows 10 and GEM+ runs ok without any major problems. Maybe by dumb luck. What I did seems to contradict what Ginetto and Cookie say.

When I last moved PCs I just copied all my GPL folders onto a new hard drive. This included the GPLSecrets folder. I don't think I installed GEM+ just ran it asis and configured the exe target folder (maybe my memory is wrong). In Windows 10 it always gave me the User Access Control warning when running it, even if I Runs as Administrator (have you tried that?).

Getting bored of the UAC warning I moved the whole GPLSecrets folder into "Program Files (x86)", still not running the install routine. That works fine for me, with no warnings. GEM+ does then store it's ini settings etc. in C:\Users\Public\Public Documents\GEM+.

Bloody Windows 10 had EVERYTHING to do with it.
I also plugged my external HDD into an old Windows XP laptop I have floating around the place and guess what, matey?
GEM+ fired up without any dramatics or hissy-fits.
So there!

Sim interest:I am here to spam and wish to be deleted after registering

Posted Apr 06 2018 - 03:39 PM

Bruce, on Apr 05 2018 - 11:06 PM, said:

Bob Simpson, on Apr 04 2018 - 07:13 PM, said:

So "bloody" Windows 10 had nothing to do with it?

Bloody Windows 10 had EVERYTHING to do with it.
I also plugged my external HDD into an old Windows XP laptop I have floating around the place and guess what, matey?
GEM+ fired up without any dramatics or hissy-fits.
So there!

No no no no no no no, that's not how this works. GEM needs to know where it's settings files are stored, the way GEM+ knows where it's settings are stored is by writing the location in the registry, which happens once when you install it on the system. Every Windows I had since XP I had to reinstall GEM+ when I reinstalled the OS. In all that time I havn't touched the main GPL install.Let me guess you installed GEM on the XP machine ages ago, right?