Jump to content
The simFlight Network Forums
Sign in to follow this  
jhaley101

Installation destination?

Recommended Posts

Hello Peter,

Best of the season to you, all the best in 2011

Just installed Windows 7 OS for fs9.

I have three files in my flight simulator files folder under Documents and I don't think they belong there. The fsuipc.ini, fsuipc.log and the fsuipic key file are all in this folder in the same place where flightplans are stored. If I delete them and re-start the sim, they all reappear there.

My fsuipc installation showed that the program installed correctly, but something is clearly not right.

FS9 user

Windows7 64 bit

FSUIPC 3.98a

Heres a copy of the install log and the fsuipc.log

Installer for FSUIPC.DLL version 3.98a

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 (x86)\Microsoft Games\Flight Simulator 9\"

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

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

... No previous valid version found.

Okay -- installed FSUIPC into "C:\Program Files (x86)\Microsoft Games\Flight Simulator 9\Modules\FSUIPC.DLL"

"Modules\FSUIPC Documents" folder created okay!

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

Installed "FSUIPC User Guide.pdf" okay

Installed "FSUIPC for Advanced Users.pdf" okay

Installed "FSUIPC History.pdf" okay

Installed "List of FS2004 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 "Lua Plugins for VRInsight Devices.pdf" okay

Installed "Example LUA plugins.zip" okay

Installed "SIMSAMURAI+FSUIPC+TUTORIAL.pdf" okay

FSUIPC.DLL installed and signature checked out okay!

Deleted GlobalSign Root fix program ... no longer relevant

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

All installer tasks completed okay!

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

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

********* FSUIPC, Version 3.98a by Pete Dowson *********

Running on Windows Version 6.0 Build 6002 Service Pack 2

Verifying Certificate for "C:\Program Files (x86)\Microsoft Games\Flight Simulator 9\MODULES\FSUIPC.DLL" now ...

SUCCESS! Signature verifies okay!

Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)

User Name="John Haley"

User Addr"my email"

User WideFS Addr=""

FSUIPC Key is provided

WideFS Key is provided

Module base=61000000

ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E

WeatherOptions(Orig)=40003605[40003605]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=255

1966 System time = 26/12/2010 15:01:20

1966 \\FLIGHTSIMULATOR\Microsoft Games\Flight Simulator 9\

1981 System time = 26/12/2010 15:01:20, FS2004 time = 12:00:00 (00:00Z)

76347 FLIGHTS\OTHER\FLTSIM.flt

76409 AIRCRAFT\c172\Cessna172SP.air

76425 Aircraft="Cessna Skyhawk 172SP"

97002 Advanced Weather Interface Enabled

142086 Traffic File #15 = "scenery\world\scenery\traffic"

143771 Traffic File #441 = "scenery\world\scenery\traffic_aig_su10_alaskaairlines"

143911 Traffic File #486 = "scenery\world\scenery\traffic_aig_su10_deltaairlines"

144207 Traffic File #517 = "scenery\world\scenery\traffic_aig_su10_horizonair"

144270 Traffic File #824 = "scenery\world\scenery\traffic_htai_csep"

220398 WeatherOptions set, now E004378F (timer=0)

221537 Traffic File #596 = "scenery\world\scenery\traffic_aig_su10_usairways"

221584 Traffic File #158 = "scenery\world\scenery\traffic_000_woa_empire airlines_su09"

221631 Traffic File #627 = "scenery\world\scenery\traffic_aig_wi08-09_unitedexpress"

221724 Traffic File #680 = "scenery\world\scenery\traffic_aig_wi09-10_unitedairlines"

221740 Traffic File #322 = "scenery\world\scenery\traffic_01_ultimatec402"

221834 Traffic File #50 = "scenery\world\scenery\traffic sierra pacific su10"

221880 Traffic File #181 = "scenery\world\scenery\traffic_000_woa_gates learjet 25 ga package_wi08"

221912 Traffic File #840 = "scenery\world\scenery\traffic_kenmore air_su10"

221958 Traffic File #329 = "scenery\world\scenery\traffic_01_ultimatelear45"

222005 Traffic File #877 = "scenery\world\scenery\traffic_pai_dassault_falcon_900"

222036 Traffic File #57 = "scenery\world\scenery\traffic usa jet su10"

222083 Traffic File #62 = "scenery\world\scenery\traffic_000_uga_glex_fs9"

222224 Traffic File #122 = "scenery\world\scenery\traffic_000_woa_british aerospace hawker xp800 ga package_su09"

222255 Traffic File #140 = "scenery\world\scenery\traffic_000_woa_continental air lines_su08"

222317 Traffic File #178 = "scenery\world\scenery\traffic_000_woa_frontier airlines_wi08"

222364 Traffic File #227 = "scenery\world\scenery\traffic_000_woa_martinair holland (cargo)_su09"

222364 Traffic File #318 = "scenery\world\scenery\traffic_00_uga_cl60"

222598 Traffic File #323 = "scenery\world\scenery\traffic_01_ultimatec550"

222645 Traffic File #324 = "scenery\world\scenery\traffic_01_ultimategulfstream3"

222692 Traffic File #757 = "scenery\world\scenery\traffic_dlh_wi0910"

222738 Traffic File #823 = "scenery\world\scenery\traffic_hs125_7"

222801 Traffic File #321 = "scenery\world\scenery\traffic_01_ultimatebbj"

223284 Traffic File #325 = "scenery\world\scenery\traffic_01_ultimategulfstream4"

223362 Traffic File #331 = "scenery\world\scenery\traffic_09_uga_bj400"

223534 Traffic File #425 = "scenery\world\scenery\traffic_aig_su10_aircanada_jazz"

223971 Traffic File #487 = "scenery\world\scenery\traffic_aig_su10_deltaconnection"

224220 Traffic File #531 = "scenery\world\scenery\traffic_aig_su10_jetblueairways"

224236 Traffic File #570 = "scenery\world\scenery\traffic_aig_su10_southwestairlines"

224314 Traffic File #600 = "scenery\world\scenery\traffic_aig_su10_virginamerica"

224330 Traffic File #661 = "scenery\world\scenery\traffic_aig_wi09-10_dhlexpress"

224423 Traffic File #701 = "scenery\world\scenery\traffic_airpac airlines_su10"

224564 Traffic File #705 = "scenery\world\scenery\traffic_american airlines_su10"

224579 Traffic File #804 = "scenery\world\scenery\traffic_fed ex_a300_su10"

224610 Traffic File #806 = "scenery\world\scenery\traffic_fed ex_md10-10f_su10"

224626 Traffic File #807 = "scenery\world\scenery\traffic_fed ex_md10-30f_su10"

224657 Traffic File #808 = "scenery\world\scenery\traffic_fed ex_md11_su10"

224860 Traffic File #854 = "scenery\world\scenery\traffic_martinaire_su10"

224907 Traffic File #947 = "scenery\world\scenery\traffic_su10_korean_air_cargo"

293313 NWI weather clear actioned

293313 External weather discarded

375229 Traffic File #870 = "scenery\world\scenery\traffic_mu2"

565816 System time = 26/12/2010 15:10:44, FS2004 time = 15:08:20 (22:08Z)

565816 *** FSUIPC log file being closed

Memory managed: 1627 Allocs, 30265 Freed

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

I took out my e-mail addresses from the above log, otherwise its as is.

Share this post


Link to post
Share on other sites

Tonight, I tried the registry repair tool and found that when I first started the tool, it was pointed to my documents folder. So I pointed it to the FS9 folder and then re-checked it again to make sure it was set properly.

But still no luck. After I uninstalled and then re-installed FSUIPC, it is still generating these 3 files in my flight simulator files in my documents folder.

I don't get it

John

Share this post


Link to post
Share on other sites

I have three files in my flight simulator files folder under Documents and I don't think they belong there. The fsuipc.ini, fsuipc.log and the fsuipic key file are all in this folder in the same place where flightplans are stored. If I delete them and re-start the sim, they all reappear there.

Really? Not FSUIPC.DLL as well?

Installer for FSUIPC.DLL version 3.98a

Looking in registry for FS9 install path:

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

Parameter"EXE Path"

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

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

Okay -- installed FSUIPC into "C:\Program Files (x86)\Microsoft Games\Flight Simulator 9\Modules\FSUIPC.DLL"

"Modules\FSUIPC Documents" folder created okay!

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

All that looks fine. It found your FS9 installation okay.

********* FSUIPC, Version 3.98a by Pete Dowson *********

Verifying Certificate for "C:\Program Files (x86)\Microsoft Games\Flight Simulator 9\MODULES\FSUIPC.DLL" now ...

And FSUIPC knows where it lives ... there's nothing else shown in the log of interest. FSUIPC uses a shortened version of that path above to save its INI files etc.

In your later message:

Tonight, I tried the registry repair tool and found that when I first started the tool, it was pointed to my documents folder. So I pointed it to the FS9 folder and then re-checked it again to make sure it was set properly.

Odd, then, that the FSUIPC install log shown above proves that the registry was okay!?

But still no luck. After I uninstalled and then re-installed FSUIPC, it is still generating these 3 files in my flight simulator files in my documents folder.

And not in the FS9 Modules folder at all?

To make sure we are using the same software, should I need to ask for some logging options, please update to the current interim version, 3.989t, in the Download Links subforum.

Regards

Pete

Share this post


Link to post
Share on other sites

Hi Pete,

Thanks for the assistance.

It is a strange thing for sure. I've never seen this before, but then I've never run FS9 on a Windows 7 OS. This morning, I did a clean install of FSUIPC and same problem. I did update the .dll to the latest version as per your request. Will the .ini file settings still hold in FS9, even if the .ini file is located outside the modules folder?

Hope you can help.

I also have WideFS installed and registered too, although I did the registration for that after the FSUIPC, would that have something to do with it? I doubt it, but I'm out of my league on this one. Again, in the documents folder under Flight Simulator Files are the FSUIPC.ini, FSUIPC.key and FSUIPC.log files and that's it. The .dll is in the modules folder of FS9. Also in the modules folder are fsuipc install.log, fsuipc.dll and fsuipc.key.

Here's a copy of the log file from the documents folder, I just removed my e-mail address under user Addr=, otherwise its unchanged.

********* FSUIPC, Version 3.989t by Pete Dowson *********

Running on Windows Version 6.0 Build 6002 Service Pack 2

Verifying Certificate for "C:\Program Files (x86)\Microsoft Games\Flight Simulator 9\MODULES\FSUIPC.dll" now ...

SUCCESS! Signature verifies okay!

Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)

User Name="John Haley"

User Addr=

FSUIPC Key is provided

WIDEFS not user registered, or expired

Module base=61000000

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=15

3354 System time = 28/12/2010 10:58:57

3354 C:\Program Files (x86)\Microsoft Games\Flight Simulator 9\

3354 System time = 28/12/2010 10:58:57, FS2004 time = 12:00:00 (00:00Z)

77034 FLIGHTS\OTHER\FLTSIM.flt

77065 AIRCRAFT\c172\Cessna172SP.air

77065 Aircraft="Cessna Skyhawk 172SP"

83024 Advanced Weather Interface Enabled

112446 Traffic File #15 = "scenery\world\scenery\traffic"

113538 Traffic File #517 = "scenery\world\scenery\traffic_aig_su10_horizonair"

113787 Traffic File #322 = "scenery\world\scenery\traffic_01_ultimatec402"

113912 Traffic File #331 = "scenery\world\scenery\traffic_09_uga_bj400"

113928 Traffic File #425 = "scenery\world\scenery\traffic_aig_su10_aircanada_jazz"

113975 Traffic File #178 = "scenery\world\scenery\traffic_000_woa_frontier airlines_wi08"

114021 Traffic File #824 = "scenery\world\scenery\traffic_htai_csep"

114037 Traffic File #122 = "scenery\world\scenery\traffic_000_woa_british aerospace hawker xp800 ga package_su09"

114068 Traffic File #680 = "scenery\world\scenery\traffic_aig_wi09-10_unitedairlines"

114224 Traffic File #486 = "scenery\world\scenery\traffic_aig_su10_deltaairlines"

114224 Traffic File #318 = "scenery\world\scenery\traffic_00_uga_cl60"

114271 Traffic File #158 = "scenery\world\scenery\traffic_000_woa_empire airlines_su09"

114287 Traffic File #840 = "scenery\world\scenery\traffic_kenmore air_su10"

114333 Traffic File #324 = "scenery\world\scenery\traffic_01_ultimategulfstream3"

114474 Traffic File #705 = "scenery\world\scenery\traffic_american airlines_su10"

114567 Traffic File #513 = "scenery\world\scenery\traffic_aig_su10_hawaiianairlines"

114583 Traffic File #441 = "scenery\world\scenery\traffic_aig_su10_alaskaairlines"

114755 Traffic File #854 = "scenery\world\scenery\traffic_martinaire_su10"

114770 Traffic File #50 = "scenery\world\scenery\traffic sierra pacific su10"

114817 Traffic File #877 = "scenery\world\scenery\traffic_pai_dassault_falcon_900"

114833 Traffic File #818 = "scenery\world\scenery\traffic_h25b"

114911 Traffic File #60 = "scenery\world\scenery\traffic_000_jhm_suncountry_fall10"

115004 Traffic File #140 = "scenery\world\scenery\traffic_000_woa_continental air lines_su08"

115113 Traffic File #264 = "scenery\world\scenery\traffic_000_woa_seaport airlines_su09"

115316 Traffic File #321 = "scenery\world\scenery\traffic_01_ultimatebbj"

115316 Traffic File #323 = "scenery\world\scenery\traffic_01_ultimatec550"

115550 Traffic File #604 = "scenery\world\scenery\traffic_aig_su10_westjet"

115613 Traffic File #823 = "scenery\world\scenery\traffic_hs125_7"

115675 Traffic File #325 = "scenery\world\scenery\traffic_01_ultimategulfstream4"

115956 Traffic File #326 = "scenery\world\scenery\traffic_01_ultimateka_f90"

115971 Traffic File #328 = "scenery\world\scenery\traffic_01_ultimatelear40"

116018 Traffic File #329 = "scenery\world\scenery\traffic_01_ultimatelear45"

217590 WeatherOptions set, now 40003605 (timer=0)

217700 Traffic File #424 = "scenery\world\scenery\traffic_aig_su10_aircanada"

218448 Traffic File #487 = "scenery\world\scenery\traffic_aig_su10_deltaconnection"

218589 Traffic File #531 = "scenery\world\scenery\traffic_aig_su10_jetblueairways"

218604 Traffic File #548 = "scenery\world\scenery\traffic_aig_su10_northamerican"

218636 Traffic File #551 = "scenery\world\scenery\traffic_aig_su10_omniairinternational"

218651 Traffic File #570 = "scenery\world\scenery\traffic_aig_su10_southwestairlines"

218776 Traffic File #596 = "scenery\world\scenery\traffic_aig_su10_usairways"

219260 Traffic File #600 = "scenery\world\scenery\traffic_aig_su10_virginamerica"

220352 Traffic File #627 = "scenery\world\scenery\traffic_aig_wi08-09_unitedexpress"

220461 Traffic File #657 = "scenery\world\scenery\traffic_aig_wi09-10_continentalairlines"

221303 Traffic File #701 = "scenery\world\scenery\traffic_airpac airlines_su10"

223300 Traffic File #804 = "scenery\world\scenery\traffic_fed ex_a300_su10"

226623 Traffic File #936 = "scenery\world\scenery\traffic_sf_abx_air_spring2008"

And here's a copy of the install.log from the fs9 modules folder

Installer for FSUIPC.DLL version 3.98a

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 (x86)\Microsoft Games\Flight Simulator 9"

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

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

... Version 3.989tåw0œ­ found.

Installed version is later: it is not overwritten.

"Modules\FSUIPC Documents" folder already exists.

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

Installed "FSUIPC User Guide.pdf" okay

Installed "FSUIPC for Advanced Users.pdf" okay

Installed "FSUIPC History.pdf" okay

Installed "List of FS2004 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 "Lua Plugins for VRInsight Devices.pdf" okay

Installed "Example LUA plugins.zip" okay

Installed "SIMSAMURAI+FSUIPC+TUTORIAL.pdf" okay

FSUIPC.DLL installed and signature checked out okay!

Deleted GlobalSign Root fix program ... no longer relevant

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

All installer tasks completed okay!

Registration for WideFS was successful! (result code 00)

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

Share this post


Link to post
Share on other sites

It is a strange thing for sure. I've never seen this before, but then I've never run FS9 on a Windows 7 OS.

Windows 7 makes no difference. I run FS on three win7 systems and have never seen any difference which would account for this.

Will the .ini file settings still hold in FS9, even if the .ini file is located outside the modules folder?

If it writes it there it should read it there. I assume the Macro files and Lua plug-ins would also have to go there. But I don't understand, yet, how it gets there. It makes no sense to me. I'd need to work out a way of finding out.

I also have WideFS installed and registered too, although I did the registration for that after the FSUIPC, would that have something to do with it?

No.

Where does the WideServer log file go to? Same place?

I doubt it, but I'm out of my league on this one. Again, in the documents folder under Flight Simulator Files are the FSUIPC.ini, FSUIPC.key and FSUIPC.log files and that's it. The .dll is in the modules folder of FS9. Also in the modules folder are fsuipc install.log, fsuipc.dll and fsuipc.key.

No WideServer log in either? And the Key file in both places?

I'm going to have to delay on this one for a few days -- guests here all this week and I'm not doing any development work. It's going to need additional logging to work out. Please remind me next Monday. Okay?

Regards

Pete

Share this post


Link to post
Share on other sites

No problem, I appreciate your support.

The Wideserver.dll and Wideserver.ini are both in the modules folder. But I don't see any type of Wideserver log file.......

Its' just the FSUIPC files that are in the documents folder of fs9. I do believe its working okay. I just finished a 4 hour 5 minute flight from Montreal to Denver and some of the settings within were perfect, so it does appear to be working.

I'm at a loss to explain the love affair the documents folder has with these files, but I do appreciate you having a look

John

Share this post


Link to post
Share on other sites

The Wideserver.dll and Wideserver.ini are both in the modules folder. But I don't see any type of Wideserver log file.......

But presumably it was you who placed those two files there? If WideServer runs at all it must create a log file. So, has it been used yet?

Regards

Pete

Share this post


Link to post
Share on other sites

I have three files in my flight simulator files folder under Documents and I don't think they belong there. The fsuipc.ini, fsuipc.log and the fsuipic key file are all in this folder in the same place where flightplans are stored. If I delete them and re-start the sim, they all reappear there.

Just coming back to this question. It's quite a story.

When Windows Vista came out and folks installed FS9 in the Program Files folder (the default), Windows actually made aliassed folders for FS which could be written to, because FS9 is not "Vista-aware" and needs to write to its own folders. Normally all Program Files folders are read-only, except for Installers and others running in "elevated administrator" mode.

Programs installed in and aware of Vista's rules installed their data in "ProgramData" or "AppData" folders instead. These are the modern Microsoft rules (which, incidentally, I detest, because it means the system disk gets full and fuller as more data is generated).

At this time I had no installer for FSUIPC. There was no need -- WinXP and previous versions of Windows had no file access problems affecting FSUIPC, so simply placing the DLL into the Modules folder was a doddle for any user. With Vista, however, problems started arising straightaway, because, although FSUIPC was duly writing its files, the LOG, INI and KEY, into the Modules folder, users, in general, could not access them. Vista was showing them the aliassed non-writable folders and not the real ones. The only way to access the real ones was to run Explorer "as administrator", to give it elevated privileges.

To get around this I changed FSUIPC to detect Vista and then save its files into the Flight Simulator Files folder. (Not the ProgramData or AppData folders which, in my opinion, are too difficult for users to find easily, so defeating the object).

Later, when I had to make an Installer for FSUIPC4 for even more critical reasons, I did one for FSUIPC3 too. Both installers make the FS Modules folder fully User read/write accessible, so solving the original problem. Hence, a newly installed FSUIPC3 or 4 on Windows 7, for instance, uses the modules folder for all of its files. However, i did not dare change it for Vista users, because anyone updating their copy of FSUIPC would find their previous setting and registrations apparently lost -- and anyway they would have been used to looking in the Flight Simulator Files folder for these.

Most folks, in any case, using FS9 on Vista, set the Compatibility option for XP emulation in any case, and in this case thjere was no problem and FSUIPC used the Modules folder even on Vista.

Now, to come to your case: from your Log, this line:

Running on Windows Version 6.0 Build 6002 Service Pack 2

indicates that, though you installed Windows 7, you have set FS9 to run in Windows Vista (Service Pack 2) compatibility mode. I think this is a mistake for FS9. Windows 7 is actually quite clever, more so than Vista was, and automatically runs FS9 in Windows XP compatibility mode even if you don't specify this, UNLESS you override that by the compatibility setting.

So, I think you'll find that things will revert to normal if you remove that setting. Right-click on the short cut for FS9 (or the FS9.EXE), select Compatibility, and uncheck the "Run this program in ..." (or select WinXP SP2, its best setting, instead of Vista, its worst). You'll also want to move those three files back to the Modules folder before running FS9 again.

Regards

Pete

Share this post


Link to post
Share on other sites

You're a smart guy Peter, thanks a ton. That did the trick. Files are where they are supposed to be. Hopefully someone else with the same problem will read this post and apply the same.

Thanks,

John

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.