FSUIPC4 Installer for FSX Problem

[CNicholson]

Hi Pete,

I have FSX Deluxe activated and installed on my E Drive and am using Windows XP Pro with SP2.

I also have FSUIPC 4.02 installed, registered and working.

When I tried to install v4.03 I got the following Installer errors:

Warning: This installation attempt will proceed, but note that your FSX installation is not correctly registered in Windows. This may well cause you problems.

Clicked OK and then got: Problem! Cannot place FSUIPC4.dll into FSX\Modules folder. Please check for Read Only/Attributes.

I have looked for applicable files marked Read Only without success.

I have also checked the Registry and every location where FSX is recorded with a path it shows E:\Flight Simulator X

Can you help?

Regards, Chuck (CYOW)

[Thomas Richter]

Hi Chuck

delete the Modules folder in FSX and install 4.03 again.

[Pete Dowson]

I also have FSUIPC 4.02 installed, registered and working.

When I tried to install v4.03 I got the following Installer errors:

Warning: This installation attempt will proceed, but note that your FSX installation is not correctly registered in Windows. This may well cause you problems.

Erthat only happens if BEFORE that it comes up with ann Explorer type window saying:

"FSX not found! Please locate and 'open' FSX.EXE:"

Did you do that? Did you find the correct FSX.EXE? (Of course there should only be one).

If you had to do that then the registry entry for the path is wrong.

What may have changed on your PC between the two installs? Have you by any chance rolled back Windows registry? The correct Registry entry is:

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

with "SetupPath" containing the path to the FSX folder.

Clicked OK and then got: Problem! Cannot place FSUIPC4.dll into FSX\Modules folder. Please check for Read Only/Attributes.

It sounds like it was looking in the wrong place altogether then.

Please check that Registry entry, and tell me exactly what you did, step by step. Something is missing here, including a very important step of FSX.EXE location.

Regards

Pete

[Pete Dowson]

Hi Chuck

delete the Modules folder in FSX and install 4.03 again.

Hi Thomas,

Why? None of these symptoms indicate that. Have you found out something else?

Regards

Pete

[CNicholson]

Hi Pete,

Your observation is correct. I did receive the Windows popup requesting I direct it to fsx.exe. As soon as I did and then clicked on Open the Installer warning message appeared.

I checked the registry location and the setup path correctly addresses E:\Flight Simulator X.

I have not added any new hardware. I have added some FSX software including Capt Sim's B757 for FSX and FS Genesis Mesh. I have also applied some of the lesser complicated tweaks to see if my fps would improve around the larger airports annd cities.

I also read somewhere that removing the modules folder was a requirement and I tried that but it made no difference.

There is one other software change that I believe may have been made after I initially installed FSUIPC 4.02 but before I registered it. That was to change Internet Explorer from v6 to v7.

If we cannot get the Installer to correctly recognize the proper path, is it possible to download v4.03 without the Installer?

Regards, Chuck

[Pete Dowson]

I checked the registry location and the setup path correctly addresses E:\Flight Simulator X.

Well, that's really weird then, because that's al it needs for the installer to find FSX automatically. I use exactly the same standard Windows calls as all other installers will, so I think you will have problems with any other add-ons you try to install in future.

There is one other software change that I believe may have been made after I initially installed FSUIPC 4.02 but before I registered it. That was to change Internet Explorer from v6 to v7.

If that didn't change the registry entry it shouldn't matter.

You ARE installing FSUIPC as an administrator, aren't you, or a user with Admin privileges? I wonder if IE7 might change some of those types of settings?

If we cannot get the Installer to correctly recognize the proper path, is it possible to download v4.03 without the Installer?

Who's we? It's only you at present I think. I can email you 4.031 not 4.03, but I still think you need to try to solve the problem.

Regards

Pete

[CNicholson]

Hi Pete,

Thanks for your time and the DLL file.

I'll keep working on the problem and if I find the answer, I'll get back to you.

Regards, Chuck