WRONG FSUIPC version

[Damar]

Hi,

I just recently went through he pain of re-installing FS. I have a 2 computer set up where i use wide client for active sky and FS real time and stuff like that, but after the reinstall, it is connecting just fine in the log, but when I try to use ASA or FS Real time it now says "maybe running on wide client, but FS not running on server, or wrong FSUIPC"

It has got me stumped. the config looks fine with the right computer name, I can see it connecting, but it is just not kicking over for some reason.

Flight PC is Win XP

Extras PC Vista Home

Regards,

Daniel.

[Pete Dowson]

... it is connecting just fine in the log, but when I try to use ASA or FS Real time it now says "maybe running on wide client, but FS not running on server, or wrong FSUIPC"

If WideClient says "Connected" in its title bar then it sounds like a registration problem in FSUIPC. First check the Windows system date on the FS PC. Maybe you haven't set that correctly yet? If it is set to a date before your FSUIPC or WideFS purchase then the data supplied by FSUIPC will be insufficient. It will look like a bad registration.

If not that, please close FS then paste here your FSUIPC, WideServer and WideClient logs.

Regards

Pete

[Damar]

Hi Pete,

First of all, thanks for this product, it is awesome and has brought me over 4000 hours of flight sim enjoyment.

OK this is the wide client log just after i start the application

********* WideClient Log [version 6.793] Class=FS98MAIN *********

Date (dmy): 20/02/10, Time 19:06:26.601: Client name is FLIGHT_DATA

265 Attempting to connect now

578 Trying TCP/IP host "Flight" port 8001 ...

578Okay, IP Address = 192.168.0.11

but ion the title bar (i un-hid it) it says not connected.

Should it not come up with a fail to connect int he log? It see "flight" and it is the correct IP on the network, really has me baffeled.

Will reply with the FSUIPC log in the next post.

Dan

[Damar]

OK FSUIPC log

********* FSUIPC, Version 3.971 by Pete Dowson *********

Running on Windows Version 5.1 Build 2600 Service Pack 3

Verifying Certificate for "C:\Program Files\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="Daniel Smith"

User Addr="daniel@***********ductions.com.au" // I edited the email address //

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

32375 System time = 20/02/2010 19:00:47

32407 \\FLIGHT\Flight Simulator 9\

32407 System time = 20/02/2010 19:00:47, FS2004 time = 12:00:00 (00:00Z)

52297 FLIGHTS\OTHER\FLTSIM.flt

52328 AIRCRAFT\c172\Cessna172SP.air

52360 Aircraft="Cessna Skyhawk 172SP"

61938 Advanced Weather Interface Enabled

95813 \\FLIGHT\Flight Simulator Files\UI generated flight.flt

95922 Clear All Weather requested: external weather discarded

138110 Traffic File #14 = "scenery\world\scenery\traffic030528"

138469 GoFlight GF166 detected: 1 device

138469 GoFlight GFRP48 detected: 1 device

1124000 \\FLIGHT\Flight Simulator Files\UI generated flight.flt

1124110 Clear All Weather requested: external weather discarded

1127594 System time = 20/02/2010 19:19:03, FS2004 time = 19:01:10 (03:01Z)

1127594 *** FSUIPC log file being closed

Memory managed: 3 Allocs, 7978 Freed

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

[Pete Dowson]

but ion the title bar (i un-hid it) it says not connected.

Is that as far as the log goes?

Where's the WideServer log file, please. The client is only half the story. There are two ends to every link! ;-)

Should it not come up with a fail to connect int he log? It see "flight" and it is the correct IP on the network, really has me baffeled.

No, it would only come up with a failure if there is one. not connecting might be perfectly legitimate -- as for when FS or WideServer isn't running on the Server, for instance.

Will reply with the FSUIPC log in the next post.

That's okay. Just the Server log missing now, then ...

Regards

Pete

[Damar]

Hello Pete

Sorry, Work got in the way of fun.

I can not see a server log. I have wideserver.ini on the remote comp. but on the FS PS there is no wideserver.log

Also I have checked the box to stop the resizing and moving of the flight deck and it still does it even with option selected.

is that a clue to the problems?

Regards,

Daniel.

[Damar]

Here is a little if the.ini in the modules folder confirming that the option is checked.

ShowMultilineWindow=Yes

SuppressSingleline=Yes

SuppressMultilineFS=No

ClearWeatherDynamics=No

OwnWeatherChanges=Yes

FixWindows=Yes

FixControlAccel=Yes

WeatherReadInterval=4

MoveBGLvariables=Yes

TimeForSelect=4

WeatherReadsFast=No

MainMenu=&Modules

SubMenu=&FSUIPC ...

Regards,

Daniel

[Pete Dowson]

I can not see a server log. I have wideserver.ini on the remote comp. but on the FS PS there is no wideserver.log

The "server log" is called WideServer.log, and is in the FS Modules folder. If it isn't there then you have never run WideFS.

There should certainly NOT be a WideServer INI file on the client PC. WideServer only runs in the FS PC. On the Client PC you should only have WideClient files and your remote applications.

Also I have checked the box to stop the resizing and moving of the flight deck and it still does it even with option selected.

is that a clue to the problems?

No, that is a completely unrelated matter and no doubt due to the option you have set in Windows to show windows whilst moving them. As the documentation clearly states, that option prevents that checkbox facility from working.

Pete

[Damar]

G'day Pete,

Thought that I might keep you updated! Problem fixed Sir!! The DLL file was missing from the modules folder on the FS comp. It is all working and just fine now. Thanks for your help.

Best regards,

Daniel.

[Pete Dowson]

Thought that I might keep you updated! Problem fixed Sir!! The DLL file was missing from the modules folder on the FS comp. It is all working and just fine now.

Good. Thanks for letting me know.

Pete