WideFS: wideclient quits after a while

[Retard]

Hi,

I am running FSX on "client1" and wideclient on "client2" for a long time. After having replaced "client2" (XP) by a Windows 7 /64 machine (like running on "client1") this configuration doesn't work properly anymore.

Both PCs are in the same workgroup and can see each other (though the "homenetgroup" by yet unknown reason doesn't work on "client2"). I use latest versions of WideFS and FSUIPC (both are registered of course).

WideClient.exe (with admini rights) starts and connects to FSX on "client1" and initially all works fine. Unfortunately after a while client.exe usually quits, sometimes with an error message (sorry german only:)

"Die Anweisung in 0x738a3f1d verweist auf Speicher 0x0000004. Der Vorgang konnte nicht im Speicher durchgeführt werden. Klicken Sie auf "OK", um das Programm zu beenden."

Could it be a problem with memory although all other applications work fine?

Here is the WideClient.log:

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

Date (dmy): 26/09/11, Time 18:32:04.571: Client name is CLIENT2

2558 D:\SIMULATOR TOOLS\Active Sky\Modules\ASv6

2558 D:\SIMULATOR TOOLS\Active Sky\Modules\ASv6\ASv6.exe

2636 New Client Application: "ASv6" (Id=5908)

4274 D:\SIMULATOR TOOLS\FS2006\Tools\FS Realtime

4274 D:\SIMULATOR TOOLS\FS2006\Tools\FS Realtime\FSRealTime.exe

5429 D:\SIMULATOR TOOLS\FlightsimCommander

5429 D:\SIMULATOR TOOLS\FlightsimCommander\FSC.exe

5429 LUA: "D:\SIMULATOR TOOLS\Dowson Software (FSUIPC_WideFS)\Wideclient\Initial.LUA": not found

5429 Attempting to connect now

5429 Trying TCP/IP host "client1" port 8002 ...

5429 ... Okay, IP Address = 192.168.1.11

5444 Connection made okay!

12121 Lost contact with ASE WX requester

13915 New Client Application: "FSRealTime" (Id=4624)

18486 New Client Application: "FSC" (Id=2380)

And here comes WideServer.log from client1:

********* WideServer.DLL Log [version 7.709b] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 26/09/11, Time 18:24:20.010: Server name is CLIENT1

15070 Initialising TCP/IP server

15070 Initialising IPX/SPX server

15070 IPX/SPX socket() failed [Error=10044] Socket type not supported

15070 Failed to start IPX/SPX Server

15070 Initialising UDP/IP server

16162 Broadcasting service every 1000 mSecs

43899 Incoming connection Accepted ok (skt=9540) TCP

44024 Connected to computer "CLIENT2" running WideClient version 6.860 (skt=9540) TCP

383061 Error 10054: client socket disconnected at Client: removing (skt=9540) TCP

465835 Incoming connection Accepted ok (skt=8576) TCP

466131 Connected to computer "CLIENT2" running WideClient version 6.860 (skt=8576) TCP

814591 Error 10054: client socket disconnected at Client: removing (skt=8576) TCP

I would appreciate some help.

Best regards

Ulrich

[Pete Dowson]

I use latest versions of WideFS and FSUIPC (both are registered of course).

Unfortunately "latest" does not define the version. Do you really mean FSUIPC 3.998c or 4.733, and WideClient 6.899, as available in the Download Links subforum? I've no idea from "latest" if you are using FSUIPC3 or FSUIPC4 -- though I see you provided logs which do give me version numbers. Thank you.

WideClient.exe (with admini rights) starts and connects to FSX on "client1" and initially all works fine. Unfortunately after a while client.exe usually quits, sometimes with an error message (sorry german only:)

Why "admin rights"? You shouldn't need that.

Google translates that to

The instruction at 0x0000004 referenced memory 0x738a3f1d. The operation could not be performed in memory. Click on OK to terminate the program

which is certainly very odd because no programs have instructions at memory address 4, even virtually.

Could it be a problem with memory although all other applications work fine?

I don't know. It could be.

WideClient is quite good, but not perfect, at protecting itself from bad data from applications. Look at the FSUIPC interfacing programs are you using. The log shows just these three:

2636 New Client Application: "ASv6" (Id=5908)

13915 New Client Application: "FSRealTime" (Id=4624)

18486 New Client Application: "FSC" (Id=2380)

We need a process of elimination. Try not running one of them, and use three runs to see whether it only happens when a specific add-on is running. Then we can switch on more logging to find out more.. But first go get the latest Wideclient from Download Links so we are looking at the same code.

Regards

Pete

[Retard]

Hi Pete,

Unfortunately "latest" does not define the version. Do you really mean FSUIPC 3.998c or 4.733, and WideClient 6.899, as available in the Download Links subforum? I've no idea from "latest" if you are using FSUIPC3 or FSUIPC4 -- though I see you provided logs which do give me version numbers. Thank you.

my apologies, the "latest versions" I referred to were the ones available at schiratti.com. I am afraid I did not check the forum for updates which will never happen again. Anyway now FSUIPC 4.734 and WideClient.exe 6.899g are running here.

Why "admin rights"? You shouldn't need that.

Good to know, I set "administrator rights" as a matter of precaution :-) .

We need a process of elimination. Try not running one of them, and use three runs to see whether it only happens when a specific add-on is running. Then we can switch on more logging to find out more.

Thanks, I have checked that out for some hours now and have even reinstalled all relevant add-ons. But I am afraid 'it' happens even when no add-on is running. Please see my logs (both PCs were freshly rebooted and only FSX and Wideclient.exe were started manually. The client quit after 1 or 2 minutes):

********* FSUIPC4, Version 4.734 by Pete Dowson *********

User Name=(removed)

User Addr= (removed)

FSUIPC4 Key is provided

WideFS7 Key is provided

Running inside FSX on Windows 7

Module base=61000000

Wind smoothing fix is not installed

DebugStatus=255

172 System time = 27/09/2011 19:30:28

172 FLT UNC path = "\\CLIENT1\Users\Ulli\Documents\Flight Simulator X-Dateien\"

219 Trying to connect to SimConnect Acc/SP2 Oct07 ...

234 FS UNC path = "\\CLIENT1\D FLIEGEN\FSX\"

811 LogOptions=00000000 00000001

811 SimConnect_Open succeeded: waiting to check version okay

811 Trying to use SimConnect Acc/SP2 Oct07

6022 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

6022 Initialising SimConnect data requests now

6022 FSUIPC Menu entry added

6037 \\CLIENT1\D FLIEGEN\FSX\FLIGHTS\OTHER\FLTSIM.FLT

6053 \\CLIENT1\D FLIEGEN\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

33728 \\CLIENT1\D FLIEGEN\FSX\SimObjects\Airplanes\FA-18\FA-18.AIR

33728 Weather Mode now = Custom

33728 \\CLIENT1\Users\ulli\documents\flight simulator x-dateien\99.FLT

34804 System time = 27/09/2011 19:31:02, Simulator time = 09:16:10 (16:16Z)

34882 Aircraft="FA-18 Hornet 13"

203207 Starting everything now ...

203301 LUA: beginning "D:\FSX\Modules\ipcReady.lua"

203301 LUA: ended "D:\FSX\Modules\ipcReady.lua"

206780 Advanced Weather Interface Enabled

********* WideServer.DLL Log [version 7.734] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 27/09/11, Time 19:33:51.262: Server name is CLIENT1

15897 Initialising TCP/IP server

15897 Initialising IPX/SPX server

15897 IPX/SPX socket() failed [Error=10044] Socket type not supported

15897 Failed to start IPX/SPX Server

15897 Initialising UDP/IP server

16146 Broadcasting service every 1000 mSecs

39687 Incoming connection Accepted ok (skt=9308) TCP

39843 Restarting service due to zero reception!

39843 Failed to start IPX/SPX Server

39890 Incoming connection Accepted ok (skt=5216) TCP

39968 Connected to computer "CLIENT2" running WideClient version 6.899 (skt=5216) TCP

70107 Failed to start IPX/SPX Server

********* WideClient Log [version 6.899g] Class=FS98MAIN *********

Date (dmy): 27/09/11, Time 19:34:36.481: Client name is CLIENT2

125 Attempting to connect now

125 LUA: "D:\SIMULATOR TOOLS\Dowson Software (FSUIPC_WideFS)\Wideclient\Initial.LUA": not found

140 Trying TCP/IP host "client1" port 8002 ...

140 ... Okay, IP Address = 192.168.1.11

140 Connection made okay!

312 Connection closed by server!

312 Attempting to connect now

312 Connection made okay!

12106 Lost contact with ASE WX requester

Anything else I could try?

Best regards

Ulrich

[Pete Dowson]

Thanks, I have checked that out for some hours now and have even reinstalled all relevant add-ons. But I am afraid 'it' happens even when no add-on is running.

Sorry,then. It has got to be either hardware -- memory or network/ethernet controller in your PC -- or a driver, possibly the network driver.

There's no way an idling WideClient can get into trouble. All it is doing is sending and receiving identical "I am here, are you there" type messages at regular intervals. Memory seems the most likely as each new message will claim a little buffer in memory, probably different from the previous, till it wraps around.

Regards

Pete

[Retard]

Ooops that is really bad news, Pete. Actually WideClient is the only program which causes troubles so far.

Ok, in this case I will continue to test and meanwhile reactivate my former client2 as client3 for all WideFS-based applications (unfortunately this machine is located in another room :-) .

One more word: I may be mistaken but I am getting the impression that my problem can be simulated by pausing FSX. It seems that almost instantly WideClient quits, but I think this needs more observation.

By the way, would it help to send you the files which are generated by Windows 7 as error report for Microsoft next time this option is offered?

Best regards

Ulrich

[Pete Dowson]

One more word: I may be mistaken but I am getting the impression that my problem can be simulated by pausing FSX. It seems that almost instantly WideClient quits, but I think this needs more observation.

I couldn't imagine anything in the client being affected by FS pausing.

By the way, would it help to send you the files which are generated by Windows 7 as error report for Microsoft next time this option is offered?

I don't know. Possibly, if it shows the state of the stack at the time and identified the modules concerned. my betting is that it's crashing deep in the TCP/IP stacks.

You could try uninstalling the Ethernet device or board on that PC and reinstalling, using the Device Manager. hopefully that will reinstall the drivers for Ethernet and may resolve things if it was down to some file corruption.

Regards

Pete

[Retard]

Quick update:

Problem still unsolved, uninstalling network device did not help.

Strange enough Wideclient runs on the same PC in a virtual XP-machine (VMWare) without any problem! So for the time being I use this as a workaround while continueing to figure out the reason for the malfunction. I agree it must be something deep inside the Windows7 installation and a reinstallation would probably help. But this is currently not an option.

[Pete Dowson]

Strange enough Wideclient runs on the same PC in a virtual XP-machine (VMWare) without any problem!

In that case, wouldn't it also run with XP compatibility mode selected in the right-clickpProperies-Compatibility options?

Regards

Pete

[alaxus]

Use this program here to do a thorough check on your memory.

http://www.memtest.org/#downiso

go to the free download links and download the 4.20 version. Its is a iso which you burn to a cd (bootable) or use the usb version. If you have a large amount of ram you may need to run this for at least 12 hrs.

At least this will rule out memory issues.