FSUIPC Not Being Detected By Any Software...?

[CaptainNegatory]

Hello Everyone,

As of recently, my FSUIPC (Unregistered) hasn't been working properly. None of my other add-ons for FS9 can detect FSUIPC they say that my FS isn't running i.e. (VAFS, SB4, FSINN) so I'm assuming something happened along the line that the files became corrupt. Thinking that replacing the files would help, I moved them all onto my desktop, ran FS, quit out and replaced the files still with no luck. Then, I replaced all of my FSUIPC assosciated files with a friends, and still no luck. Finally, I deleted all the FSUIPC files, and re-ran the installer.exe, and the below is what I got.

Installer for FSUIPC.DLL version 3.93

Looking in registry for FS9.1 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.1

Parameter"EXE Path"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.1

Parameter"EXE Path"

... NOT found! ...

Looking in registry for FS9 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.0

Parameter"EXE Path"

... >>> OK! FOUND FS9! <<< ...

Looking in registry for FS8 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\8.0

Parameter"EXE Path"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\8.0

Parameter"EXE Path"

... NOT found! ...

Looking in registry for FS7 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\7.0

Parameter"path"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\7.0

Parameter"path"

... NOT found! ...

Looking in registry for FS6.1 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\6.1

Parameter"InstallDir"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\6.1

Parameter"InstallDir"

... NOT found! ...

Looking in registry for CFS2 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Combat Flight Simulator\2.0

Parameter"EXE Path"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Combat Flight Simulator\2.0

Parameter"EXE Path"

... NOT found! ...

Looking in registry for CFS1 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Combat Flight Simulator\1.0

Parameter"EXE Path"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Combat Flight Simulator\1.0

Parameter"EXE Path"

... NOT found! ...

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

INSTALLATION FOR FS9:

EXE Path="C:\Program Files\Microsoft Games\Flight Simulator 9"

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

C:\Program Files\Microsoft Games\Flight Simulator 9\Modules\FSUIPC.DLL

... Version 3.930 found.

Failed to place FSUIPC.DLL into folder as "C:\Program Files\Microsoft Games\Flight Simulator 9\Modules\FSUIPC.DLL"

Error 32 reported ("The process cannot access the file because it is being used by another process. ")

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

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

If anybody can help me out so I can log my hours and fly on VATSIM again I would really appreciate it!

Thanks Much,

CaptainNegatory

[JSkorna]

Hi,

XP or Vista?

Is FS closed down when you tried to re-install FSUIPC?

Try a re-boot of your computer and then a re-install attempt.

Thanks,

[Pete Dowson]

As of recently, my FSUIPC (Unregistered) hasn't been working properly. None of my other add-ons for FS9 can detect FSUIPC they say that my FS isn't running i.e. (VAFS, SB4, FSINN) so I'm assuming something happened along the line that the files became corrupt. Thinking that replacing the files would help, I moved them all onto my desktop, ran FS, quit out and replaced the files still with no luck. Then, I replaced all of my FSUIPC assosciated files with a friends, and still no luck. Finally, I deleted all the FSUIPC files, and re-ran the installer.exe, and the below is what I got.

Well, an FSUIPC.LOG file would have been far more useful. It would probably actually show what you have wrong.

The install log shows nothing wrong, except this:

Failed to place FSUIPC.DLL into folder as "C:\Program Files\Microsoft Games\Flight Simulator 9\Modules\FSUIPC.DLL"

Error 32 reported ("The process cannot access the file because it is being used by another process. ")

which shows that when you tried to Install FSUIPC, it was not only already installed, but running! In other words, FS2004 was also still running!

The installer cannot replace a file currently in use -- Windows won't allow it.

Close FS properly first. If it has no Window then it has probably hung on termination -- use the task manager to terminate it. Show me the complete FSUIPC log file. Also state whether there's an FSUIPC menu entry in the "modules" menu in FS.

Regards

Pete

[CaptainNegatory]

Hi,

XP or Vista?

Is FS closed down when you tried to re-install FSUIPC?

Try a re-boot of your computer and then a re-install attempt.

Thanks,

Windows Vista Home 32bit

which shows that when you tried to Install FSUIPC, it was not only already installed, but running! In other words, FS2004 was also still running!

The installer cannot replace a file currently in use -- Windows won't allow it.

Close FS properly first. If it has no Window then it has probably hung on termination -- use the task manager to terminate it. Show me the complete FSUIPC log file. Also state whether there's an FSUIPC menu entry in the "modules" menu in FS.

Regards

Pete

Well, I tried but the FSUIPC installer keeps going "Not Responding" I've attached the FSUIPC.log File if it helps.

FSUIPC Install.rar

[Pete Dowson]

Well, I tried but the FSUIPC installer keeps going "Not Responding" I've attached the FSUIPC.log File if it helps.

Why are you continuing to try installing when I've told you it is already installed, and in fact was running when you tried to install last?

What does " the FSUIPC installer keeps going "Not Responding"" mean? I don't understand that part. If you mean this error:

Error 32 reported ("The process cannot access the file because it is being used by another process. ")

then that is a report from Windows -- the error message is a Windows one, and I've no reason to believe that Windows is lying. Use the Task Manager's Process list to find and delete the FS9.EXE process.

If there's an FSUIPC.LOG file to show me, then FSUIPC is either running or has been running, therefore it is installed. And what is the file you attached, yet another Install log, which is of no interest in any case -- you already showed me one which i commented on?

Find the FSUIPC.LOG file, not the Install file, as I asked before. There's no need to attach the file. If FSUIPC isn't doing anything, and there's a log, it must be pretty short in any case, so paste it into a message. If you want to attach files, use ZIP please, not "RAR".

Kindly move on. Let's try to deal with any problems you have with running FSUIPC, not with installing it, which isn't (or wasn't) a problem according to your previous report. If there's no FSUIPC.LOG file then you've probably got two or more installations of FS, and you are running one which is not the one pointed to by the Registry, and so doesn't have FSUIPC installed. Try going to

C:\Program Files\Microsoft Games\Flight Simulator 9

and double-clicking on FS9.EXE in that folder, so that you are sure you are running the copy known to Windows.

Regards

Pete

[CaptainNegatory]

I'm trying to reinstall only after reinstalling and that's when, on occasion its freezing up. I'm not sure how to make a .zip file and I know "Most" people prefer to use .rar so thats why I packaged it like so. Thats not an installation log it's the FSUIPC.log that you requested previously. When I say "Not Responding" I'm referring to when the box becomes greyed out, and Windows tells me "The Program Has Stopped Responding". That log is from the first install I attempted, when yes it was already installed and FS was running. The main problem is, when I have FSUIPC installed properly, it's not being detected by any 3rd Party Softwares.

Thanks,

C. negatory

[Pete Dowson]

I'm trying to reinstall only after reinstalling and that's when, on occasion its freezing up.

Sorry, what is "freezing up"?

There's no need to reinstall FSUIPC as the install log shows it is already installed.

I'm not sure how to make a .zip file and I know "Most" people prefer to use .rar so thats why I packaged it like so.

No, ZIP is much more common. I've managed to download a RAR decoder, but ZIP is understood by Windows by default and is generally used universally. You can ZIP using Windows or Winzip or any one of many other zip programs.

Thats not an installation log it's the FSUIPC.log that you requested previously.

No, it is most definitely an install log. I've now managed to look at it. It looks like the same one you already pasted into your message.

When I say "Not Responding" I'm referring to when the box becomes greyed out, and Windows tells me "The Program Has Stopped Responding".

You've never reported that before. What program does it say has stopped responding? What "box" becomes "greyed out"?

That log is from the first install I attempted, when yes it was already installed and FS was running.

Well, what was the point of trying that? You cannot re-install a running program! :-(

At least it proves that FSUIPC was installed and running (as I keep saying), and thererfore must have produced a Log file!

The main problem is, when I have FSUIPC installed properly, it's not being detected by any 3rd Party Softwares.

I understand that, as I did right from the beginning, and, as I keep saying, the answer may lie in the FSUIPC log file -- the log file which is produced by FSUIPC when it is running. It is absolutely nothing to do with the Installer, and so far the only information you've supplied is for the installer despite my requests.

It is late here (after 01:20 am) and i am going to bed soon. I'm out in the morning, but I will be looking here again later tomorrow.

Regards

Pete

[CaptainNegatory]

Well, tell me exactly what you would like me to do then, and I'd be more than happy to do it for you, I'd like to get this problem solved.

[Pete Dowson]

Well, tell me exactly what you would like me to do then, and I'd be more than happy to do it for you, I'd like to get this problem solved.

Can you please re-read the thread and answer the questions already asked which you have not yet done so. Most importantly show me the FSUIPC Log file which you've not bothered to do yet.

I'm afraid it is useless to continue until there is some measure of understanding about what the problem actually is. I'm afraid you've only been confusing the issue so far, and supplying the wrong information. In order to progress we need to be clear AND have the correct information to hand.

Regards

Pete

[CaptainNegatory]

Most importantly show me the FSUIPC Log file which you've not bothered to do yet.

-Right, I got WinZip went into Modules and made of copy of FSUIPC.log and and zipped it up, it's attached.

I'm afraid it is useless to continue until there is some measure of understanding about what the problem actually is. I'm afraid you've only been confusing the issue so far, and supplying the wrong information. In order to progress we need to be clear AND have the correct information to hand.

-My apologies. The installer is what was freezing up, but since it said the module is already running, we can assume its installed and in somewhat of a working order, disregard that.

Thanks Much,

C. Negatory

FSUIPC.zip

[Pete Dowson]

I got WinZip went into Modules and made of copy of FSUIPC.log and and zipped it up, it's attached.

The log shows nothing wrong. what programs are you running which says it isn't there?

The installer is what was freezing up

The installer freezes, not FS? But the installer logs you've already shown show it running to completion, even to the

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

message at the end -- the last thing it does just before terminating normally! I've never heard of anyone getting a freezing installer -- it's so simple, it seems so unlikely! Earlier on you seemed to be running the Installer when FS was already running, in which case of course it couldn't do its job in any case. Perhaps when you thought it was "frozen" it was just in its Window waiting for you to say whether you wanted to register or not -- which I see you never have. So you don't actually want to use FSUIPC for anything yourself?

Maybe you think it is frozen because you placed the logging window or FS in front of the window asking for Registration?

This thread has taken a rather weird turn! How long have you been talking about only the Installer and not about FS and FSUIPC?

Pete

[CaptainNegatory]

It was when I was trying to figure out what was wrong and I attempted a reinstall that it froze. FSUIPC has since been succesfully installed and that's not the problem. The problem is that when I'm in FS9 and I try to connect with VAFS, SB4, or FSINN, none of the programs are detecting FSUIPC, so I can only Imagine the problem is with FSUIPC?

[Pete Dowson]

It was when I was trying to figure out what was wrong and I attempted a reinstall that it froze. FSUIPC has since been succesfully installed and that's not the problem. The problem is that when I'm in FS9 and I try to connect with VAFS, SB4, or FSINN, none of the programs are detecting FSUIPC, so I can only Imagine the problem is with FSUIPC?

Do those programs use FSUIPC? I know that SB3 did, but SB4 doesn't use it in FSX, so I'm not sure about that. I don't know either VAFS or FSInn.

What indications do they give that they are trying to connect to FSUIPC and failing? FSUIPC is certainly running fine.

Are you by any chance running FS and any of those programs at different privilege levels? Under Vista or Win7, if you run FS "as administrator" or any programs "as administrator", they run at a higher privilege level called "elevated administrator", the same as afforded to installers. If you do this, then everything needs running at the same level -- Vista and Win7 actively prevent programs of different levels talking to each other.

Regards

Pete

[CaptainNegatory]

All of the programs say that they use FSUIPC to communicate with FS9 I'm quite sure. Yes, even in administrator mode nothing can communicate with FS9, I thought that FSUIPC is how all these programs talked with each other? Is that not what FSUIPC does?

[Pete Dowson]

All of the programs say that they use FSUIPC to communicate with FS9 I'm quite sure. Yes, even in administrator mode nothing can communicate with FS9, I thought that FSUIPC is how all these programs talked with each other? Is that not what FSUIPC does?

Do those programs actually want to talk to each other? I thought SB4 and FSInn were competitors.

FSUIPC provides an interface into FS for programs which choose to use it. But I'm not sure whether those do, that's all. FSInn and SB4 most certainly have other needs in their interface with FS, which FSUIPC doesn't meet -- multiplayer or AI traffic injection, for starters. I don't know VAFS, as I said.

Do the programs actually state that they are trying to interface FSUIPC and failing? Maybe their error message will tell you something? The log you provided most certainly showed FSUIPC was running fine.

Have you tried using the support services for the programs you are having trouble with?

Pete

[CaptainNegatory]

Yes, I have tried to get support but I don't think any is offered for FSUIPC. I'm unsure about VAFS or FSINN as I haven't used them in awhile. When opening SB4 it says, "Trying To Detect FSUIPC" and fails.

[Pete Dowson]

Yes, I have tried to get support but I don't think any is offered for FSUIPC.

It isn't FSUIPC you need support for. I opffer support for FSUIPC. The problems you have are with sapplications -- FSUIPC is running fine.

I'm unsure about VAFS or FSINN as I haven't used them in awhile. When opening SB4 it says, "Trying To Detect FSUIPC" and fails.

Well, I don't know what checkls they carry out to detect that, but if they do things properly then if that's the message then I'm pretty sure it must be because you have FS and SB4 operating at different privilege levels, or different compatibility modes. Check the properties of both programs, make sure the various ways of running them are the same for both.

Pete

[CaptainNegatory]

Problems solved. All I had to do was right click the .exe>properties>Always Run As Admin (Ticked)>Apply. Thanks Pete!

[Pete Dowson]

Problems solved. All I had to do was right click the .exe>properties>Always Run As Admin (Ticked)>Apply. Thanks Pete!

That's the same as right-clicking each time and selecting "run as administrator", as I suggested. Changing it in the properties just saves having to remember that each time.

All the programs involved need to run at the same privilege level. There should be no need to run any of them at the elevated level, but if you do, you have to run them all that way.

Regards

Pete