FSUIPC Problem Type-1 -- Redux

[HighGround]

Hullo, Pete:

It's with *great* reluctance that I write this puling little tome in hopes that I can perhaps overcome this persistent "Type-1" problem. I've tried every related method I can find on this Forum, including deletion of the SimConnect folders and running the "Repair" facility on the FSX disks. All to no avail.

Everything was peachy and hotsy-totsy until the HDD which handles Flight-Sim exclusively became uninterested in further toil. Upon replacing the (miserable) offending HDD, I re-installed FSX, and soon thereafter I attempted installation of my beloved and enormously necessary FSUIPC V4.50 with its attendant WideFS.

Simply, there seems to be no way in which I can get an "Add-Ons" menu entry! Nothing works, hence this bothersome (to you) Forum entry. :(

FSX SP1

FSUIPC V4.50

I'm hoping that perhaps something will be disclosed to your practiced eye in the following file readouts:

+++++++++++++++++++++

Installer for FSUIPC4.DLL version 4.50

Looking in registry for FSX install path:

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

Parameter"SetupPath"

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\SOFTWARE\Microsoft\Microsoft ESP\1.0

Parameter"AppPath"

... NOT found! ...

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

INSTALLATION FOR FSX:

AppPath="F:\Program Files\Microsoft Games\Microsoft Flight Simulator X\"

Checking version of FSX.EXE:

... Version 10.0.60905.0 (Need at least 10.0.60905.0)

Checking compatibility with installed SimConnect:

Found SimConnect build 60905 (Original)

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

F:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL

... Version 4.500 found.

FSX Modules folder already exists.

Okay -- installed FSUIPC4 into "F:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL"

Looking for the current user's Application Data path:

... found as "C:\Documents and Settings\Jon Houston\Application Data"

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

Looking in "C:\Documents and Settings\Administrator\Application Data"

No FSX.CFG there

Looking in "C:\Documents and Settings\All Users\Application Data"

No FSX.CFG there

Looking in "C:\Documents and Settings\Default User\Application Data"

No FSX.CFG there

Looking in "C:\Documents and Settings\Jon Houston\Application Data"

Found FSX.CFG in "C:\Documents and Settings\Jon Houston\Application Data\Microsoft\FSX\FSX.CFG"

Now checking DLL.XML ...

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

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

... FSUIPC4 section of DLL.XML written okay

Now checking for a SimConnect.XML file ...

... No SimConnect.XML file found. This is okay.

Looking in "C:\Documents and Settings\LocalService\Application Data"

No FSX.CFG there

Looking in "C:\Documents and Settings\NetworkService\Application Data"

No FSX.CFG there

Now installing additional files into the Modules 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 "GlobalSign Root.exe" okay

Installed "FSUIPC Lua Library.pdf" okay

Installed "FSUIPC Lua Plug-Ins.pdf" okay

Installed "Lua License.pdf" okay

Installed "Example LUA plugins.zip" okay

FSUIPC4.DLL installed and signature checked out okay!

Deleted GlobalSign Root fix programno longer relevant

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

All installer tasks completed okay!

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

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

++++++++++++++++++++++++++++++++++++++

********* FSUIPC4, Version 4.50 by Pete Dowson *********

NOTE: SimConnect Acc/SP2 Oct07 is supported, but it isn't installed.

User Name="Jon Houston"

User Addr="highground@eastlink.ca"

FSUIPC4 Key is provided

WideFS7 Key is provided

Running inside FSX (using SimConnect SP1 May07)

Module base=61000000

Wind smoothing fix is fully installed

DebugStatus=255

171 System time = 19:33:48

171 FLT UNC path = "C:\Documents and Settings\Jon Houston\My Documents\Flight Simulator X Files\"

171 FS UNC path = "F:\Program Files\Microsoft Games\Microsoft Flight Simulator X\"

906 LogOptions=00000000 00000001

906 SimConnect_Open succeeded: waiting to check version okay

28578 Exception 5 "VERSION_MISMATCH", Ref 448, Version 0.60905: Open: SimConnect Version incorrect!

28578 Trying another version of SimConnect ...

28687 Now running with SimConnect Original

28687 SimConnect_Open succeeded: waiting to check version okay

28687 Exception 5 "VERSION_MISMATCH", Ref 448, Version 0.60905: Open: SimConnect Version incorrect!

28687 Trying another version of SimConnect ...

28812 Could not link to all needed SimConnect facilities

28812 Failed on SimConnect_CallDispatch for Message, return = 0xFF100020

43843 **** Retrying SimConnect connection****

43843 Could not link to all needed SimConnect facilities [code 0]

58906 **** Retrying SimConnect connection****

58906 Could not link to all needed SimConnect facilities [code 0]

74000 **** Retrying SimConnect connection****

74000 Could not link to all needed SimConnect facilities [code 0]

89031 **** Retrying SimConnect connection****

89031 Could not link to all needed SimConnect facilities [code 0]

104062 **** Retrying SimConnect connection****

104062 Could not link to all needed SimConnect facilities [code 0]

116359 System time = 19:35:44

116359 *** FSUIPC log file being closed

Memory managed: 2 Allocs, 2 Freed

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

I do hope I've included everything you need, Pete!

Cheers, Sir.

[i]-Jon

-------[/i]

[Pete Dowson]

FSX SP1

...

Checking compatibility with installed SimConnect:

Found SimConnect build 60905 (Original)

...

NOTE: SimConnect Acc/SP2 Oct07 is supported, but it isn't installed.

...

Running inside FSX (using SimConnect SP1 May07)

...

28578 Exception 5 "VERSION_MISMATCH", Ref 448, Version 0.60905: Open: SimConnect Version incorrect!

Well, the installation is a mess. The Installer finds only the base version of SimConnect, no SP1 addition at all. When FSX is running and has loaded FSUIPC, it appears to be masquerading as the SP1 SimConnect, but in fact identifies itself also as the base (60905) version and refuses to allow the connection.

I'm afraid there's nothing i can do about this. You have a screwed up FSX installation. I don't know how it has arisen, but the only solution which has worked in the past has been the manual deletion of the SimConnect folders in the WinSxS folder, and the reinstallation of them, usually by reinstalling FSX.

If, as you say, you've tried that and have had no success I really cannot help further. You need Microsoft expertise.

As one last gasp, as it were, could you show me the actual WinSxS folders -- the full names and contents? Also, do a complete search on your hard disk for all "simConnect.dll" copies, list where they are and their version numbers.

You say

Upon replacing the (miserable) offending HDD, I re-installed FSX, and soon thereafter I attempted installation of my beloved and enormously necessary FSUIPC V4.50 with its attendant WideFS.

You don't mention installing Windows. Did you format your new hard disk and install Windows from scratch, or did you copy a back-up partition from somewhere? I really cannot imagine how a straight format, Windows install, FSX install, FSUIPC4 installcan go wrong. Everything should be pristine.

You DID run FSX first, after installing it, didn't you? Before installing the SP1 update, and before installing FSUIPC4? This should be the sequence:

1. Format HDD

2. Install Windows

3. Install FSX

4. Run FSX, make sure all is well.

5. Close FSX, install FSUIPC4.

6. Run FSX + FSUIPC4, ensure all is well.

7. Install FSX SP1

8. Run FSX + FSUIPC4, ensure all is well still.

9. Install FSX SP2

10. Run FSX+ FSUIPC4, ensure all is still well.

Regards

Pete

[HighGround]

Hullo again, Pete:

Well, it's working now. But what a boondoggle.

First: Yes, my sequencing seems to have been correct -- for whatever that's worth. The referenced drive is my fourth of four drives, so Windows wasn't really a factor, being way back there on the C: drive. F: is reserved for things FS.

But here's the rub: I definitely *had* installed SP1 and it was deemed successful. So after posting the original post, above, I thought for the heck of it I'd install SP2. It wouldn't install, saying I needed SP1 first.

So I went to Add/Remove Programs and UN-installed SP1. Then I re-installed it. Said it was fine. Tried SP2, but same deal: "Can't do it -- need SP1 first". What a cyber-catch-22!!

So, acting on a hunch, I went for the Full Monty: I installed Acceleration. [ I'd installed it long ago on the original FSX installation, but ran into problems with my beloved FS9 aircraft, so I reverted to SP1 and all was well ]

After starting FSX, there it was, in all its glory -- "Add-ons" in the Menu bar. And, of course, under Add-ons was FSUIPC with my WideFS enabled, ready to go (hooking-up to a second computer with FS Commander).

So. Installing Acceleration seemed to "jump the queue", bypassing SP1 and SP2, and getting the pea-pickin' SimConnect to . . . connect.

So I'll leave it at that, for the nonce. I don't know what removing Acceleration will do, but perhaps I'll look into that one day in future when I feel brave again. Meanwhile, I think I'll leave the sleeping dog lie and enjoy some flying again.

Many thanks for your time and efforts, Pete! I truly appreciate your fine program, and the sterling backup you provide for us mugglers.

Cheers, Sir.

-Jon

-------

[Pete Dowson]

Well, it's working now.

Oh, good.

Windows wasn't really a factor, being way back there on the C: drive. F: is reserved for things FS.

Unfortunately that isn't true. Many things FS are entangled in the Windows system -- several places in documents & Settings (ProgramData and AppData in Visa), for "All Users" and specific users installing FSX too. And then of course there's the run-time library and other support systems installed into Windows by the FSX installer. And thenSimConnect, which is a Windows side-by-side library installation, affecting not only the Windows WinSxS folders, but almost uncountable places in the Windows Registry too!

I did try to work out al the places in the windows system which are affected by and affect FSXbut i gave up after several pages full.

So I went to Add/Remove Programs and UN-installed SP1. Then I re-installed it. Said it was fine. Tried SP2, but same deal: "Can't do it -- need SP1 first". What a cyber-catch-22!!

So, acting on a hunch, I went for the Full Monty: I installed Acceleration. [ I'd installed it long ago on the original FSX installation, but ran into problems with my beloved FS9 aircraft, so I reverted to SP1 and all was well ]

Ah, you had Acceleration installed toosome mess to do with it and SP2 no doubt. They are alternatives.

So. Installing Acceleration seemed to "jump the queue", bypassing SP1 and SP2, and getting the pea-pickin' SimConnect to . . . connect.

The Acceleration install is cleaner, and it does include SP1 and SP2.

Regards

Pete

[HighGround]

Hullo once again, Peter:

Well, much has happened, and to my infinite relief and pleasure, it's all for the good.

Something or things that you wrote (above) must've planted the seed, because I awoke in the wee hours, this morning, having one of those early-morning satoris, if you're into Zen, but otherwise known as a rush of crap to the brain. I remembered that when I had done the reinstall to the new drive, I'd been distracted at the beginning, and accidentally installed to the default C: drive, versus my Flight-Sim F: drive.

Not to worry, said I to myself, brimming with ill-conceived confidence, I'll just *move* it over, and change the paths in the Registry. So rather than abort the install, yank it out, and start over, I took the "easy" way out. And then I forgot all about my unorthodox installation.

My current suspicions are that there is perhaps an install.log or something of that sort which gets referred-to by any subsequent fiddling. So that would account for my SP1 installation apparently going just fine, but not registering in FSX, which was "over there" on another drive. Probably pooched the SimConnect hook-up, too. All of which caused FUIPC to come a cropper when it tried to do what it was designed to do in "Normal People's" machines.

After I had installed Acceleration, last evening, I quickly re-discovered why I'd dumped it previously: aircraft graphics were helter-skelter, with some missing and others warped. Once removed, thingss reverted to the "Bad State" I was originally in, so I did what I shoulda aughta done in the first place -- I yanked everything and started over, taking care to do it right, this time.

Probably needless to say, everything's perfect, and as it should be. Sigh! :( Silly duffer!

So again, my thanks, Peter. Sorry to have involved you in a mess of my own making. Next time, I promise I'll be more circumspect about it all.

Cheers,

-Jon

-------

[Pete Dowson]

I'll just *move* it over, and change the paths in the Registry.

That sort of thing was easy with FS9 and before, but as you've found out, not a good idea with FSX and ESP. I suspect most modern programs, designed to be Vista-entangled, would suffer from such things. The installations are not nice and clean like they once were. (I hate them too!)

Pete