Jump to content
The simFlight Network Forums

Help: WideFS checksum errors


Recommended Posts

Hi Pete,

I've been using your latest beta of FSUIPC v3.536/7 and recently noticed how slow my ASv6 sessions have been updating FS9 weather. ASv6 is on my Wideclient PC and I've retried the last two versions of the ASv6 updates. I do know for a fact that my network is solid and have no problems. All Windows shares work fine and no network event-log entries noted. I've been running this same 100MB LAN for several years with WideFS and nothing has recently changed as far as the network itself is concerned. I should also mention that a few times, Flightsim Flightkeeper, also in the WideClient PC, has also thrown an error saying that FS9 was not properly initialized when in fact, FS9 was up and running fine on the WideFS server. Anyway, I've tried reinstaling ASv6 several times and I've tried different FS9 startup situations. Can you point me in a good direction as to what to troubleshoot next? I'm starting to think that there's something going on here between the FSUIPC beta 3.536 and WideFS. I've put a lot of work into configuring my new AXIS facilites in the FSUIPC.ini file so dropping back to v3.53 or earlier really isn't an option if I can avoid it, even for troubleshooting. Thanks for your help.

Al

BTW, I removed many of the duplicate line errors to save space in this post.

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 27/02/06, Time 21:04:42.549: Server name is XPGAMER

98937 Initialising TCP/IP server

98953 Initialising IPX/SPX server

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

98953 Failed to start IPX/SPX Server

99031 Incoming connection Accepted ok (skt=7928)

99109 Connected to computer "XPSERVER" running WideClient version 6.510 (skt=7928)

99109 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=1246 (time=0)

99266 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=384 (time=533406)

99797 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=1491 (time=533906)

99906 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=162 (time=534015)

100031 Broadcasting service every 1 mSecs

100391 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=189 (time=534500)

101969 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=371 (time=536062)

103047 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=175 (time=537140)

103172 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=1306 (time=537250)

103734 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=298 (time=537828)

105094 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=973 (time=539219)

105172 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=259 (time=539281)

106219 **** ERROR! Sumcheck or length fails on received socket 7928 block, len=259 (time=540312)

268750 Closing down now ...

Memory managed: Offset records: 39 alloc, 39 free

Total number of received blocks having sumcheck errors = 248

Throughput maximum achieved: 26 frames/sec, 1802 bytes/sec

Throughput average achieved for complete session: 7 frames/sec, 315 bytes/sec

Average receive rate from "XPSERVER": 2 frames/sec, 3153 bytes/sec

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

FSUIPC v3.537 LOG:

********* FSUIPC, Version 3.537 by Pete Dowson *********

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

User Name="Removed For POST"

User Addr="Removed For POST"

FSUIPC Key is provided

WideFS Key is provided

Module base=61000000

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

WeatherOptions(Orig)=4000B7AF[4000B7AF]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=255

3859 System time = 21:04:42

3859 \\XPGAMER\E\Flight Simulator 9\

3875 C:\Program Files (x86)\ScreenGrab\ScreenGrab.exe

3922 System time = 21:04:42, FS2004 time = 12:00:00 (00:00Z)

13765 C:\Documents and Settings\jordana\My Documents\Flight Simulator Files\KIPT - Default.flt

13765 AIRCRAFT\beech_baron_58\FSD_B58TC.air

13968 Aircraft="Beech Baron 58"

19015 Module [M1] identified = "sb3gaugebridge.dll"

19015 Module [M1] "sb3gaugebridge.dll" access registration is okay

19015 Module [M2] identified = "ActiveRadar.dll"

19015 Module [M2] "ActiveRadar.dll" access registration is okay

67765 C:\Documents and Settings\jordana\My Documents\Flight Simulator Files\UI generated flight.flt

67968 Clear All Weather requested: external weather discarded

69625 Advanced Weather Interface Enabled

98172 Traffic File #18 = "projectai flightplans\scenery\traffic_mrai_wi04-05_federalexpress"

98172 Traffic File #17 = "scenery\world\scenery\traffic-ga"

98781 Traffic File #224 = "projectai flightplans\scenery\traffic_pai_vir"

98875 Traffic File #22 = "projectai flightplans\scenery\traffic_pai_aal"

98875 Traffic File #74 = "projectai flightplans\scenery\traffic_pai_dal"

99000 Traffic File #159 = "projectai flightplans\scenery\traffic_pai_nwa"

99047 Traffic File #210 = "projectai flightplans\scenery\traffic_pai_usa"

99640 Traffic File #25 = "projectai flightplans\scenery\traffic_pai_aca"

99750 Traffic File #48 = "projectai flightplans\scenery\traffic_pai_aza"

99875 Traffic File #67 = "projectai flightplans\scenery\traffic_pai_coa"

100000 Traffic File #192 = "projectai flightplans\scenery\traffic_pai_swa"

100234 Traffic File #209 = "projectai flightplans\scenery\traffic_pai_ups"

100484 Traffic File #75 = "projectai flightplans\scenery\traffic_pai_dals"

100609 Traffic File #79 = "projectai flightplans\scenery\traffic_pai_dlh"

100718 Traffic File #86 = "projectai flightplans\scenery\traffic_pai_egf"

101000 Traffic File #193 = "projectai flightplans\scenery\traffic_pai_swr"

101047 Traffic File #208 = "projectai flightplans\scenery\traffic_pai_ual"

107843 NWI weather clear actioned

107843 External weather discarded

271609 System time = 21:09:06, FS2004 time = 14:29:21 (19:29Z)

271609 *** FSUIPC log file being closed

Memory managed: 1257 Allocs, 1834 Freed

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

WideClient LOG:

********* FSUIPC, Version 3.537 by Pete Dowson *********

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

User Name="Removed For POST"

User Addr="Removed For POST"

FSUIPC Key is provided

WideFS Key is provided

Module base=61000000

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

WeatherOptions(Orig)=4000B7AF[4000B7AF]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=255

3859 System time = 21:04:42

3859 \\XPGAMER\E\Flight Simulator 9\

3875 C:\Program Files (x86)\ScreenGrab\ScreenGrab.exe

3922 System time = 21:04:42, FS2004 time = 12:00:00 (00:00Z)

13765 C:\Documents and Settings\jordana\My Documents\Flight Simulator Files\KIPT - Default.flt

13765 AIRCRAFT\beech_baron_58\FSD_B58TC.air

13968 Aircraft="Beech Baron 58"

19015 Module [M1] identified = "sb3gaugebridge.dll"

19015 Module [M1] "sb3gaugebridge.dll" access registration is okay

19015 Module [M2] identified = "ActiveRadar.dll"

19015 Module [M2] "ActiveRadar.dll" access registration is okay

67765 C:\Documents and Settings\jordana\My Documents\Flight Simulator Files\UI generated flight.flt

67968 Clear All Weather requested: external weather discarded

69625 Advanced Weather Interface Enabled

98172 Traffic File #18 = "projectai flightplans\scenery\traffic_mrai_wi04-05_federalexpress"

98172 Traffic File #17 = "scenery\world\scenery\traffic-ga"

98781 Traffic File #224 = "projectai flightplans\scenery\traffic_pai_vir"

98875 Traffic File #22 = "projectai flightplans\scenery\traffic_pai_aal"

98875 Traffic File #74 = "projectai flightplans\scenery\traffic_pai_dal"

99000 Traffic File #159 = "projectai flightplans\scenery\traffic_pai_nwa"

99047 Traffic File #210 = "projectai flightplans\scenery\traffic_pai_usa"

99640 Traffic File #25 = "projectai flightplans\scenery\traffic_pai_aca"

99750 Traffic File #48 = "projectai flightplans\scenery\traffic_pai_aza"

99875 Traffic File #67 = "projectai flightplans\scenery\traffic_pai_coa"

100000 Traffic File #192 = "projectai flightplans\scenery\traffic_pai_swa"

100234 Traffic File #209 = "projectai flightplans\scenery\traffic_pai_ups"

100484 Traffic File #75 = "projectai flightplans\scenery\traffic_pai_dals"

100609 Traffic File #79 = "projectai flightplans\scenery\traffic_pai_dlh"

100718 Traffic File #86 = "projectai flightplans\scenery\traffic_pai_egf"

101000 Traffic File #193 = "projectai flightplans\scenery\traffic_pai_swr"

101047 Traffic File #208 = "projectai flightplans\scenery\traffic_pai_ual"

107843 NWI weather clear actioned

107843 External weather discarded

271609 System time = 21:09:06, FS2004 time = 14:29:21 (19:29Z)

271609 *** FSUIPC log file being closed

Memory managed: 1257 Allocs, 1834 Freed

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

Link to comment
Share on other sites

I'm starting to think that there's something going on here between the FSUIPC beta 3.536 and WideFS.

The interface WideFS uses into FSUIPC hasn't changed at all, not for many years. It looks like you have some performance or, more likely, reliability problems.

I've put a lot of work into configuring my new AXIS facilites

Do you think it is possible that there are so many axes being scanned that the FS PC is overwhelmed? Ir possibly you've set the "Delta" so low that every little jitter in each axis creates many FS messages?

Perhaps you ought to show me the [Axes ...] sections of your FSUIPC.INI file, just in case? You could also temporarily remove them (just make a copy of FSUIPC.INI and delete those sections frmo the one in FS Modules folder), and run FS and wideFS again, for comparison?

There is a parameter which can change the polling frequency FSUIPC uses, so we can try adjusting that, but let's see if it is anything to do with the axis assignments at all first.

Some other information is relevant to, please:

* FS PC's operating system and version

* FS PC's Processor type & speed

* FS PC's main memory size

* FS's frame rate limiter setting

* Whether FS joysticks are enabled or disabled

However, whilst it would be a good idea to check them all, now looking at the WideServer log I really don't think it can be any of the above. Sumcheck errors mean that the data arriving from the Client is certainly corrupt. I have never seen such errors without there being something wrong with the network somewhere, and in fact I've never seen such a bad example -- even on a faulty Network card I've only seen the odd sumcheck error from time to time.

I really think this is more likely to be due to one of:

* faulty network card or driver

* faulty hub or switch if you are using one

* bad cable

* main memory faulty

* IRQ or DMA conflicts in the FS PC, possibly with the video card

The network may look to be working fine for other things, but in my experience this is an illusion, as Windows doesn't appear to check things -- it takes it on faith that the Network subsystem guarantees data integrity. Last time I had a faulty network card things like file transfers from Explorer appeared to go well, but when doing file comparisons afterwards (using the binary file comparer "FC /B" or Directory Toolkit) nearly all the files (and certainly all of the large ones) contained differences -- a crucial problem when such files are supposed to be programs!

Incidentally you did not show me the WideClient Log, though you appearently intended to. If you look it seems to be another copy of the FSUIPC Log, which in fact isn't relevant in any case.

Regards

Pete

Link to comment
Share on other sites

Thanks Pete; I'm at work right now so I can't provide answers. To everything right now. Sorry about not posting the WideClient Log. You were correct that was my intention, but a couple of beers and sleepy-eyes messed-up my copy-&-past abilities. When you mentioned network issues, it did jar my memory a bit. A couple of weeks ago, I physically relocated my WideFS PC which ment undoing all the cables. One thing I do explicitly remember was changing the LAN cable from the switch to the WideFS PC. I hoping that cable I used might be slightly faulty. Now I have to wait all-day before I can get home and test my theory.

I remoted home and gathered all the log files and ini files for you and ziped them up for you as an attachment below.

WideFS PC:

WinXP x64-bit Pro | AMD-64 3500+ | Corsair XMS 1GB RAM (2x512) | Asus A8N-SLI Deluxe MB | Nvidia NF4 SATA Raid-0 x3 80GB) | EVGA Nvidia 6800GT PCI-x | NF4 Chipset LAN 100MB | FS9.1 FR 25 FPS | FS9.1 Joysitcks disabled | FSUIPC v3.537 AXIS & Buttons Enable w/Aircraft specfic settings.

WideClient PC:

WinXP Pro (32bit) | AMD 3200+ | Corsair XMS 1GB RAM (2x512) | Gigabyte A7NNXP MB | 2 x 80GB IDE | EVGA Nvidia 5900 | NF2 100MB LAN

jordanal - WideFS Checksum Error logs.zip

Link to comment
Share on other sites

WideFS PC:

WinXP x64-bit Pro

You are using a 64-bit operating system? This will have all new drivers for all the bits and pieces in your system, presumably mostly in Beta? Are you a Beta tester for Microsoft, or do you just like living dangerously?

Really, that would be my main concern here. Nothing of mine has been tested on WinXP 64 in any case, so if its 32-bit support is iffy then that could generate problems. and, those drivers, they must all be version 1's or earlier, or Betas, surely?

Corsair XMS 1GB RAM (2x512)

Isn't 1Gb RAM rather low for WinXP 64 Pro, with FS and so on? I don't really know, but I'd recommend 1Gb to anyone using FS on a WinXP 32 bit system, and MS always grow their systems bigger and hungrier, never smaller and leaner.

The WideClient log shows nothing wrong, by the way.

Regards,

Pete

Link to comment
Share on other sites

Nope, WinXP x64 went final in March of '05 and has been running great for almost a year now on my rig. Checkout the Hardware forums on Avism under the FS general discussion. This is not new, or beta, but quickly becomeing routine for the AMD64 product line. You are correct that WinXP 64 does require specific driviers but that's it. This OS includes a Windows-on-Windows32 subsystem (WoW32) which allows most 32 bit applications to run fine on the 64bit OS. Anyway, all my drivers inlcuding the Nvidia NForce and Geforce drivers have been final for a while now and have already gone through several itteraions. FS actually runs a bit smoother on the Win64 OS as noted by several others on the AVSIM hadware forum. 1GB RAM is fine even for AMD64. No difference noted. Just as with the 32bit version more RAM is always better. Anyway, my AMD64 system, which is quite standard now, is not the issue here. I'll try changing the LAN cable tonight. I appreciate you taking the time to look through my logs.

Al

Link to comment
Share on other sites

Well, I think I've solved my checksum errors. The problem was a newly installed McAfee Personal Firewall Plus application on the 32bit WideClient PC only. Comcast, a major U.S. broadband cable provider here on the East coast of the US recently started offering free subscriptions to McAfee antivirus, personal security, and personal firewall.

After swapping LAN cables, reseting My Netgear Router/switch, uninstalling and reinstalling my NForce2 MB chipset/Ethernet drivers, I discovered that when I reinstalled all three of the McAfee products mentioned above, my ASv6 station writing slows down and I start getting the checksum errors as noted in the WideFS server log again. I then uninstalled only the Personal Firewall Plus product and my problems and log events disappeared.

Comcast is a major provider and it won't surprise me if others start seeing similar problems using this firewall product. I hope my findings here benefit anyone else who start having these checksum errors.

v/r,

AL

Link to comment
Share on other sites

Well, I think I've solved my checksum errors. The problem was a newly installed McAfee Personal Firewall Plus application on the 32bit WideClient PC only.

Wow! I wonder what that is doing? blocking messages is one thing, but changing them? That's very naughty!

The sumchecking I'm doing is only of the data parts of whatever protocol you are using. Possibly if you switched to IPX/SPX it would get through unmolested? Certainly I am not using "RAW" mode on the connections and have no access to any of the TCP/IP red tape which, possibly, they may legitimately tamper with!

Thanks for letting me know.

Regards

Pete

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

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.