FSUIPC 4.90 installer can't find version # of FSX

[RobertTalaj]

Hi, Peet!

After having noticed the need to install the new version 4.90 due to the licensing problem I got the following error message from the FSUIPC installer:

"Checking version of FSX.EXE:

Couldn't obtain version info! Asking user to find FSX.EXE..."

When I choose the fsx.exe within the explorer window nothing happens except that this window reopens again. It seem's that the installer couldn't get enough information about the fsx.exe.

What can I do? Do I have to reinstall FSX?

Kind regards

Robert

[Pete Dowson]

"Checking version of FSX.EXE:

Couldn't obtain version info! Asking user to find FSX.EXE..."

When I choose the fsx.exe within the explorer window nothing happens except that this window reopens again. It seem's that the installer couldn't get enough information about the fsx.exe.

The prompt to find FSX only appears if your registry is corrupt or you've moved FSX without reinstalling -- FSUIPC, like many programs, uses the Registry to locate the FSX installation. Have you perhaps restored your Windows system to a point before FSX was installed?

When you locate FSX.EXE in the Explorer style Wnidw, and actualy select it, the Installer should carry on. If it appears again you've not actually selected it.

Maybe you should show me the Installerr log file rather than quote bits from it?

You could also repair the registry first. This tool will do that for FS9 or FSX:

http://www.flight1software.com/files/FS_Registry_Repair.exe

Regards

Pete

[RobertTalaj]

Hi, Peet!

Thanks alot for your hint but it didn't work. Finally I had to repair FSX with the Original CD. Now it works - BUT!

I'm not able to get a registered version of FSUIPC even though I did the registration via the installer. Installer told me that everything is o.k. but when starting FSX and going to FSUIPC via the FSX menu I get an unregistered copy of FSUIPC. The key file is at it's location with the right entries.

I am a little confused about that.

Can you help once more?

Thank you in advance.

Kind regards

Robert

[Pete Dowson]

Thanks alot for your hint but it didn't work. Finally I had to repair FSX with the Original CD.

Even the Registry repair option? It sounds like your FSX.EXE was corrupted!

I'm not able to get a registered version of FSUIPC even though I did the registration via the installer. Installer told me that everything is o.k. but when starting FSX and going to FSUIPC via the FSX menu I get an unregistered copy of FSUIPC. The key file is at it's location with the right entries.

After you did the repair, did you also update FSX with the SP! and SP2 updates, or Acceleration?

Also, check your system date -- if it is incorrect it may make the registration look incorrect.

If it isn't either of these problems, I need more information! Please paste both the Install log and the FSUIPC4 log into a message here. Close FSX down first.

Pete

[RobertTalaj]

Peet, I think I have to tell you the whole story right now:

1. I wanted to assing particular controls, buttons, keys and so on to the FSX Acc. F/A-18

2. Every time I selected this a/c FSUIPC supposed the also installed VRS F/A-18

3. I tried several times to select the Acc-Hornet - every time the same

4. I read the section "Multiple INI files" in your document "FSUIPC4 for Advanced Users (for FSUIPC4 Version 4.88, April 2013)" and tried to work with different FSX.EXE files as described

5. I noticed that FSX created new fsx.cfg files even though there WAS a renamed file as you described in your document.

6. Because this procedure didn't work I changed back to the former installation status and from this time the problems began (see installation problem FSUIPC above)

7. After having tried to solve the problem with the registry tool fsx crashed when being started

8. I ran firstly the FSX repair tool from the RTM DVD and noticed later by research that I should have maybe repair the ACC instead (I'm actually not sure right now)

9. After that I ran the ACC DVD repair tool.

10. Thereafter FSX started again

11. FSUIPC installer ran perfectly - but with the above mentioned registration problems.

Puh! Lot of text. Do you have an idea what I destroyed...?

Even the Registry repair option? It sounds like your FSX.EXE was corrupted!

Didn't work. Tool's message was that it worked succesful.

After you did the repair, did you also update FSX with the SP! and SP2 updates, or Acceleration?

No, I didn't

Also, check your system date -- if it is incorrect it may make the registration look incorrect.

system date is correct.

Please paste both the Install log and the FSUIPC4 log into a message her

Here you are :oops:

********* FSUIPC4, Version 4.90 by Pete Dowson *********

Running inside FSX on Windows 7

... FSX has been renamed as "fsx "

Module base=5EEB0000

User Name=""

User Addr=""

FSUIPC4 not user registered

WIDEFS7 not user registered, or expired

16 System time = 08/05/2013 16:02:56

16 FLT path = "C:\Users\Robert\Documents\Flight Simulator X Files\"

63 Trying to connect to SimConnect Acc/SP2 Oct07 ...

63 FS path = "D:\Programme\Microsoft Games\Microsoft Flight Simulator X\"

671 LogOptions=00000000 00000001

671 SIM1 Frictions access gained

671 Wind smoothing fix is fully installed

671 G3D.DLL fix attempt installed ok

671 SimConnect_Open succeeded: waiting to check version okay

671 Trying to use SimConnect Acc/SP2 Oct07

671 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

671 Initialising SimConnect data requests now

671 FSUIPC Menu entry added

733 D:\Programme\Microsoft Games\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT

733 D:\Programme\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

48626 System time = 08/05/2013 16:03:44, Simulator time = 16:02:52 (23:02Z)

53633 Starting everything now ...

54803 Advanced Weather Interface Enabled

61012 System time = 08/05/2013 16:03:57, Simulator time = 16:02:57 (23:02Z)

61012 *** FSUIPC log file being closed

Average frame rate for running time of 5 secs = 150.1 fps

G3D fix: Passes 326, Null pointers 0, Bad pointers 0, Separate instances 0

Memory managed: 5 Allocs, 5 Freed

********* FSUIPC Log file closed ***********

Installer for FSUIPC4.DLL version 4.90

Looking in registry for FSX install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0

Parameter"SetupPath"

... >>> OK! FOUND FSX! <<< ...

Looking in registry for ESP install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0

Parameter"SetupPath"

Not there, so looking in:

HKEY_CURRENT_USER\ESP

Parameter"AppPath"

... NOT found! ...

Looking in registry for Prepar3D install path:

HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D

Parameter"SetupPath"

Not there, so looking in:

HKEY_CURRENT_USER\Prepar3D

Parameter"AppPath"

... NOT found! ...

===========================================================

INSTALLATION FOR FSX:

SetupPath="D:\Programme\Microsoft Games\Microsoft Flight Simulator X\"

Checking version of FSX.EXE:

... Version 10.0.61637.0 (Need at least 10.0.60905.0)

Checking compatibility with installed SimConnect:

Found SimConnect build 60905 (Original)

Found SimConnect build 61242 (SP1 May07)

Found SimConnect build 61259 (Acc/SP2 Oct07)

Checking if there's already a version of FSUIPC4 installed in:

D:\Programme\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL

... Version 4.900 found.

FSX Modules folder already exists.

Okay -- installed FSUIPC4 into "D:\Programme\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL"

Looking for the current user's Application Data path:

... found as "C:\Users\Robert\AppData\Roaming"

Now finding \Microsoft\FSX\FSX.CFG for all users, including this one

Looking in "C:\Users\All Users\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Default\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Default User\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Public\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Robert\AppData\Roaming"

Found FSX.CFG in "C:\Users\Robert\AppData\Roaming\Microsoft\FSX\FSX.CFG"

Now checking DLL.XML ...

... There is a previous DLL.XML, checking for FSUIPC4 section.

... FSUIPC4_Loader section already exists but will be replaced.

(with FSUIPC4_Loader entry)

... FSUIPC4 section of DLL.XML written okay

Now checking for a SimConnect.XML file ...

... There is a SimConnect.XML, checking for "local" section.

... "local" section already exists, file not modified.

Looking in "C:\Users\UpdatusUser\AppData\Roaming"

... No FSX.CFG there

"Modules\FSUIPC Documents" folder already exists.

Now installing additional files into the "Modules\FSUIPC Documents" folder:

Installed "FSUIPC4 User Guide.pdf" okay

Installed "FSUIPC4 for Advanced Users.pdf" okay

Installed "FSUIPC4 History.pdf" okay

Installed "List of FSX controls.pdf" okay

Installed "FSUIPC Lua Library.pdf" okay

Installed "FSUIPC Lua Plug-Ins.pdf" okay

Installed "Lua License.pdf" okay

Installed "Lua Plugins for VRInsight Devices.pdf" okay

Installed "LuaFileSystem.pdf" okay

Installed "Example LUA plugins.zip" okay

Installed "Offset Mapping for PMDG 737NGX.pdf" okay

Installed "FSUIPC4 Offsets Status.pdf" okay

===========================================================

All installer tasks completed.

Registration check for FSUIPC4 and WideFS was successful! (result code 00)

*************** End of Install Log ***************

Thank you!

[Pete Dowson]

1. I wanted to assing particular controls, buttons, keys and so on to the FSX Acc. F/A-18

2. Every time I selected this a/c FSUIPC supposed the also installed VRS F/A-18

Using FSUIPC's "aircraft specific" or using Profiles? If the former case it would only do that if you actually assigned to the aircraft by its name -- they must have dfferent names. If you used Profiles, then the names are added to the profile when you ask for them to be. It is NOT automatic. It sounds like you must have actually edited the INI file and shorted the name to F/A-18 so including both aircraft!

3. I tried several times to select the Acc-Hornet - every time the same

The same as what? Sorry, you need to be more specific.

You do not SELECT aircraft in FSUIPC. It offers no such facilities. You select aircraft using FSX's menus!

4. I read the section "Multiple INI files" in your document "FSUIPC4 for Advanced Users (for FSUIPC4 Version 4.88, April 2013)" and tried to work with different FSX.EXE files as described

What for? You never EVER need to use that facility unless you want different FSX.CFG files. FSUIPC has easy to use Profiles to separate all your assignments and calibrations. This is probably the biggest and most well-used facility of FSUIPC!

5. I noticed that FSX created new fsx.cfg files even though there WAS a renamed file as you described in your document.

FSX creates a new FSX CFG if there's not one there already. You obviously masde an error, but you really shouldn't be messing about like that in the first place unless you wanted different FSX configurations completely -- e.g. a DX9 and a DX10 load.

Puh! Lot of text. Do you have an idea what I destroyed...?

It seems you've gone off half-cocked doing all sorts of odd things. I'm not surprised you got problems!

********* FSUIPC4, Version 4.90 by Pete Dowson *********

Running inside FSX on Windows 7

... FSX has been renamed as "fsx "

Your FSX.EXE is not named caorrectly. You have a space after FSX!!! I'm not surprised nothing has worked properly. Why are you renaming it from the correct name?

User Name=""

User Addr=""

FSUIPC4 not user registered

WIDEFS7 not user registered, or expired

This shows that there most certainly NOT an FSUIPC4.KEY file in your FSX Modules folder. The Name and Addr fields will ALWAYS be shownhere if there was one.

Is this where you looked?

D:\Programme\Microsoft Games\Microsoft Flight Simulator X\Modules

Why are you re-registering in any case? did you delete your previous FSUIPC4.KEY file? If so, why? Did you make a backup?

Because of the renamed FSX, other files will be wrongly named too.

In your Install log I also notice:

... FSUIPC4_Loader section already exists but will be replaced.

(with FSUIPC4_Loader entry)

Why are you using the Loader? What was the problem which suggested you should install that?

I think you have been making very simple things very very complicated, and then made things worse. I would suggest you start again with a clean everything.

Regards

Pete