PaavoP Posted June 10, 2012 Report Share Posted June 10, 2012 Dear Pete, about a month ago I released "FSX to Prepar3D Migration Tool", which creates a virtual FSX installation that among many small hacks redirects registry keys and folders to Prepar3D. The purpose of my tool is to enable the trouble-free installation of FSX addons into Prepar3D. Some addons, most notably PMDG 747, try to aquire handles to FSX.exe and fail because Prepar3D runs as Prepar3D.exe. This causes many compatibility issues. To overcome this limitation, I've added so-called Legacy Mode, which starts Prepar3D as FSX.exe. The FSX.exe is copied-over Prepar3D that has been patched a bit. However, users are reporting that when Prepar3D is run in Legacy Mode, registered versions of FSUIPC report that they are not registered. I assume that this is caused by FSUIPC's DRM. Would it be possible to accommodate a change in FSUIPC in upcoming versions that would allow it to be used with Prepar3D running as FSX.exe? Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 11, 2012 Report Share Posted June 11, 2012 Would it be possible to accommodate a change in FSUIPC in upcoming versions that would allow it to be used with Prepar3D running as FSX.exe? The INI, LOG and KEY files FSUIPC uses are all named in accordance with the EXE name. Have you tried simply renaming those files accordingly? Pete Link to comment Share on other sites More sharing options...
PaavoP Posted June 12, 2012 Author Report Share Posted June 12, 2012 Thanks for the tip, didn't know key file name could be linked with running exe name. Problem solved. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now