FS2002 crashes constantly

[avioniko]

Hello,

I am using latest versions, FSUIPC3.44 and the WideFS 6.44 plus 6.447

The main flightsim server is an Intel P-IV 3,0 Ghz, 512Mb etc.

Windows 98 SE is the OS together with FS2002!

As long as I run it all, with FSUIPC 3.44 it works great, so smooth no hick-ups or whatsoever. When I put back the installed wideserver.dll and wideserver.ini files into the modules folder of FS, then I get a constantly lockup/crash. The whole system hangs and I can only use the reset button on the machine. The time differs greatly when the system crashes, but most of the time within a minute. Also I get an IPX socket connection error, but I can click that away by pressing 'ok'.

For testing purposes I didn't turn on all the client machines (happened with them turned on as well).

So far my thoughts and elimination of the problem(s) occuring is back to and down to wideserver unfortunally.

Is there any possibility to email my wideserver -and client.ini files, as well te wideserver logs and so on? Btw, some of those are 30-80mb large??????????

I am waiting for any reply, thanks so much in advance.

Best regards,

NG

avioniko@chello.nl

[Pete Dowson]

So far my thoughts and elimination of the problem(s) occuring is back to and down to wideserver unfortunally.

It sounds very much like a problem with the driver of your Network on that PC. The network driving part of WideServer is virtually unchanged now for 6 years and is based on examples from Microsoft themselves.

Try TCP/IP instead -- that's default in any case.

Also try the test release available in the Announcement at the top of this forum.

Is there any possibility to email my wideserver -and client.ini files, as well te wideserver logs and so on? Btw, some of those are 30-80mb large??????????

80Mb large? Have you been messing with the options or is that all with default logging? Do NOT send me those. Change to defaults, keep the session short, show me an extract if there errors showing.

Regards,

Pete

[avioniko]

Hello Peter,

First of all, thanks for your reply!

Have some more info for you, to determine the error perhaps.

I do use FSUIPC 3.44 as well WideFS 6.44 AND the WideFS6.447Test over the previous one:-)

The networkcard we use, is an onboard one of the motherboard, with correct drivers installed for motherboard (original cd), as well network card, video -and soundcard and so on. I don't expect any erors there, but who can be sure in these circumstances:-)

The networkcard is regonised as: Marvell Yukon Gigabit Ethernet 10/100/1000 Base-T Adapter. So for so good...

When FS2002 is "completely" started (on the ramp, dark cockpit, weather injected) then immediately afterthis within a split second (probably while searching for the wideserver.dll file?) I get an error stating:

--------------------------------------------

WIDESERVER ERROR

ipx/spx socket{} failed [Error=10044]

Socket type not supported

--------------------------------------------

When I click on the OK button in this particular field, the windowframe of FS2002 states:

FS2002 with WideServer: waiting for clients....

Here downunder the WideServer.ini file:

; PLEASE SEE the documentation for parameter details

;==================================================

[Config]

Port=8002

AutoRestart=0

AutoUpdateTime=13

MaximumBlock=4096

NoStoppedRestarts=Yes

RestartTime=10

SendTimeout=15

TCPcoalesce=No

; -----------------------------------------------

[user]

AllowShutdown=App

Run1=D:\MCP\mcp.exe

Run2=D:\PMSounds\pmsounds.exe

Close2=Yes

Close1=Yes

Log=Errors+

;===============================================

[ClientNames]

1=CLIENT5

2=CLIENT4

3=CLIENT3

4=CLIENT2

5=CLIENT1

Here downunder also a filecheck (after system crash):

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 19/01/05, Time 16:32:35.540: Server name is FS-MAIN

45497 Initialising TCP/IP server

45550 Initialising IPX/SPX server

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

49307 Failed to start IPX/SPX Server

87307 Restarting service due to total lack of use

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

87307 Failed to start IPX/SPX Server

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

104745 Failed to start IPX/SPX Server

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

115126 Failed to start IPX/SPX Server

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

126506 Failed to start IPX/SPX Server

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

137769 Failed to start IPX/SPX Server

174209 GetRealAddr(2200CAF8)=6108F558 (orig 0C29)

174209 READ1 [P-911099] 0C29, 4 bytes: 30 30 2E 30

174209 GetRealAddr(2200CB02)=6108F562 (orig 0C33)

174209 READ1 [P-911099] 0C33, 4 bytes: 30 30 2E 30

174209 GetRealAddr(220002FC)=61082D5C (orig 32FC)

174209 READ1 [P-911099] 32FC, 2 bytes: 01 00

174209 READ1 [P-911099] 0C48, 2 bytes: 00 00

174209 READ1 [P-911099] 0C4A, 2 bytes: 00 00

174209 READ1 [P-911099] 0C4C, 2 bytes: 00 00

174209 READ1 [P-911099] 0C4E, 2 bytes: 00 00

174209 READ1 [P-911099] 0C50, 2 bytes: 00 00

174209 READ1 [P-911099] 0C5A, 2 bytes: 00 00

174209 READ1 [P-911099] 0C5E, 2 bytes: 00 00

174209 READ1 [P-911099] 0C60, 2 bytes: 00 00

174209 READ1 [P-911099] 0C6A, 2 bytes: 00 40

174209 READ1 [P-911099] 0EC6, 2 bytes: 53 3F

174209 READ1 [P-911099] 0E8A, 2 bytes: D0 07

174209 READ1 [P-911099] 0E90, 2 bytes: 01 00

174209 READ1 [P-911099] 0E92, 2 bytes: D9 01

174209 READ1 [P-911099] 0ECA, 34 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

174209 00 00 00 00 00 00 00 00 FF FF 10 77 01 00 DB FF

174209 00 00

174209 READ1 [P-911099] 0EEE, 2 bytes: 13 77

174209 READ1 [P-911099] 11BE, 2 bytes: FF 7F

174209 READ1 [P-911099] 11C6, 2 bytes: 10 00

174209 READ1 [P-911099] 11D0, 2 bytes: 2C 0F

174209 READ1 [P-911099] 1278, 2 bytes: 00 06

174209 GetRealAddr(220000C4)=61082B24 (orig 2EE0)

174209 READ1 [P-911099] 2EE0, 4 bytes: 01 00 00 00

174209 GetRealAddr(24002147)=0151C163 (orig 2F80)

174209 READ1 [P-911099] 2F80, 2 bytes: 01 00

174209 GetRealAddr(2200C980)=6108F3E0 (orig 3000)

174209 READ1 [P-911099] 3000, 8 bytes: 00 00 00 00 00 00 00 00

174209 GetRealAddr(2200C99F)=6108F3FF (orig 301F)

174209 READ1 [P-911099] 301F, 8 bytes: 4F 54 52 20 00 00 4F 54

174209 GetRealAddr(2200C9BE)=6108F41E (orig 303E)

174209 READ1 [P-911099] 303E, 8 bytes: 00 00 00 00 00 00 00 00

174209 GetRealAddr(22000308)=61082D68 (orig 3308)

174209 READ1 [P-911099] 3308, 2 bytes: 06 00

174209 GetRealAddr(2400058D)=0151A5A9 (orig 3060)

174209 READ1 [P-911099] 3060, 24 bytes: 00 00 00 00 00 00 00 00 60 50 12 1E 3D B8 F2 3F

174209 C0 88 56 1E C8 16 75 BF

174209 GetRealAddr(240005D5)=0151A5F1 (orig 3078)

174209 READ1 [P-911099] 3078, 8 bytes: 57 C7 92 7E 58 74 75 BF

174209 GetRealAddr(22000324)=61082D84 (orig 3324)

174209 READ1 [P-911099] 3324, 4 bytes: F4 FF FF FF

174209 GetRealAddr(220023A0)=61084E00 (orig 5BA0)

174209 READ1 [P-911099] 5BA0, 48 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

174209 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

174209 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

174209 GetRealAddr(22001D50)=610847B0 (orig 5550)

174209 READ1 [P-911099] 5550, 8 bytes: 00 00 00 00 00 00 00 00

174209 GetRealAddr(22000380)=61082DE0 (orig 3380)

174209 READ1 [P-911099] 3380, 4 bytes: 00 00 00 00

174209 GetRealAddr(22001C00)=61084660 (orig 5400)

174209 READ1 [P-911099] 5400, 48 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

174209 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

174209 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

174209 GetRealAddr(22001D20)=61084780 (orig 5520)

174209 READ1 [P-911099] 5520, 16 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

174209 READ1 [P-911099] 0C1A, 2 bytes: 00 01

174209 GetRealAddr(22001D08)=61084768 (orig 5508)

174209 READ1 [P-911099] 5508, 24 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

174209 00 00 00 00 00 00 00 00

175280 WRITE1 [P-911099] 3380, 4 bytes: 50 72 6F 6A

175280 WRITE1 [P-911099] 3384, 4 bytes: 65 63 74 20

175280 WRITE1 [P-911099] 3388, 4 bytes: 4D 61 67 65

175280 WRITE1 [P-911099] 338C, 4 bytes: 6E 74 61 20

175280 WRITE1 [P-911099] 3390, 4 bytes: 4D 43 50 3A

175280 WRITE1 [P-911099] 3394, 4 bytes: 20 53 74 61

175280 WRITE1 [P-911099] 3398, 4 bytes: 72 74 69 6E

175280 WRITE1 [P-911099] 339C, 4 bytes: 67 20 55 70

175280 WRITE1 [P-911099] 33A0, 4 bytes: 00 20 20 20

175280 WRITE1 [P-911099] 32FA, 2 bytes: 07 00

175281 READ1 [P-911099] 02C8, 2 bytes: 00 00

175874 WRITE1 [P-911099] 07BC, 4 bytes: 00 00 00 00

175874 WRITE1 [P-911099] 07C8, 4 bytes: 00 00 00 00

175874 WRITE1 [P-911099] 07D8, 4 bytes: 00 00 00 00

175874 WRITE1 [P-911099] 07D0, 4 bytes: 00 00 00 00

175874 WRITE1 [P-911099] 07D8, 4 bytes: 00 00 00 00

175874 WRITE1 [P-911099] 0810, 2 bytes: 00 00

175874 WRITE1 [P-911099] 07E4, 4 bytes: 00 00 00 00

175874 WRITE1 [P-911099] 07DC, 4 bytes: 00 00 00 00

175953 WRITE1 [P-911099] 04F0, 2 bytes: 00 08

176159 WRITE1 [P-911099] 0810, 4 bytes: 01 00 00 00

176159 WRITE1 [P-911099] 07E4, 4 bytes: 00 00 00 00

176160 WRITE1 [P-911099] 0810, 4 bytes: 00 00 00 00

176235 AP READOUTS: Flags1=00000005, Flags2=00000000

176238 WRITE1 [P-911099] 0810, 4 bytes: 01 00 00 00

176238 WRITE1 [P-911099] 07DC, 4 bytes: 00 00 00 00

176241 Client Application: "PMSOUNDS" (Id=-795711)

176241 D:\PMSOUNDS\PMSOUNDS.EXE

176241 Product="pmSounds"

176241 Company="Enrico Schiratti"

176241 READ repeated 5 times

176241 READ1 [P-795711] 0020, 4 bytes: 00 FD FF FF

176241 READ1 [P-795711] 023B, 1 bytes: 0F

176241 READ1 [P-795711] 023C, 1 bytes: 11

176241 READ1 [P-795711] 0240, 2 bytes: D5 07

176241 READ1 [P-795711] 0274, 2 bytes: 5C 0F

176241 GetRealAddr(24000018)=0151A034 (orig 029C)

176241 READ1 [P-795711] 029C, 1 bytes: 00

176241 READ1 [P-795711] 029D, 1 bytes: 00

176241 READ1 [P-795711] 02A0, 2 bytes: 02 FE

176241 READ1 [P-795711] 02B4, 8 bytes: 00 00 00 00 00 00 00 00

176241 GetRealAddr(2200CB7C)=6108F5DC (orig 02BC)

176241 READ1 [P-795711] 02BC, 4 bytes: 00 00 00 00

176241 READ1 [P-795711] 02C8, 2 bytes: 00 00

176241 GetRealAddr(2200037E)=61082DDE (orig 337E)

176241 READ1 [P-795711] 337E, 2 bytes: 6E 20

176241 READ1 [P-795711] 0330, 2 bytes: 4D 3F

176241 READ1 [P-795711] 034C, 12 bytes: 14 04 30 27 50 10 90 13 00 12 00 00

176241 GetRealAddr(220010F0)=61083B50 (orig 48F0)

176241 READ1 [P-795711] 48F0, 4 bytes: 00 00 00 00

176241 READ1 [P-795711] 0366, 2 bytes: 01 00

176241 READ1 [P-795711] 036E, 1 bytes: 00

176241 READ1 [P-795711] 04E0, 80 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

176241 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00

176241 00 00 00 00 00 00 00 00 00 00 00 00 00

This is all I can tell you from my experiences and hopefully you can comment, or advise me or some things we can try out. If there's anything more you need to know, please feel free to ask me anytime/or e-mail.

Daytime e-mail: niko@orbit-groundschool.nl

Thank you in advance so much for your help/advise.

Hope to get a reply from you soon:-)

Best regards,

Niko

[Pete Dowson]

When FS2002 is "completely" started (on the ramp, dark cockpit, weather injected) then immediately afterthis within a split second (probably while searching for the wideserver.dll file?) I get an error stating:

--------------------------------------------

WIDESERVER ERROR

ipx/spx socket{} failed [Error=10044]

Socket type not supported

--------------------------------------------

Is this error appearing in a Message Box on screen? It is okay it appearing in the Log file -- it just means you haven't got IPX/SPX installed. WideServer can continue with TCP/IP. However, if it is appearing in a Message Box, there is certainly something wrong.

This is with FS2002 on a Windows 98SE system isn't it? I'll try to set something up here to see if I can reproduce it. Maybe the error is not one I would normally expect for a protocol missing.

Have you tried installing IPX/SPX at all? You don't need to use it, just add it and bind it to your adapter. If that gets over the problem then let me know immediately as it will be a good clue for me to work out what is happening.

Here downunder also a filecheck (after system crash):

What's a "filecheck"?

Something is wrong with your hard disk. It looks like you have badly crossed-tracks. The second part of the file you are showing is part of FSUIPC.LOG, not WideServer.LOG at all! I urge you to run the Windows disk check on this drive and get rid of any cross-tracked files before things get worse! It will play havoc else, and will certainly make FS crashes more and more likely.

Regards,

Pete

[avioniko]

Hi Peter,

Yes it is appearing in a Messagebox.

It's also W98SE with FS2002 indeed:-)

More info about the setup:

We use an Intel P-IV 3,0Ghz, LAN onboard etc. 2x SCSI HDD, on which the first one is partitioned in C:\ part with W98SE and D:\ part with FS2002.

The Filecheck is something produced FROM this D:\ partition after the crash, after resetting, the Microsoft scandisk automatically produces this.

Harddisks are formatted FAT32 by the way.

I agree with you it's odd, it states wideserver log or something...

Let me jump back in all the manuals and docs I have, about installing network, tcp/ip and ip/spx and all and I come back to you with more info.

By the way, the FS PC-server is with W98SE, rest of all the clients Win XP Pro.

Also trying to obtain of this W98SE machine it's servernode to implent in the wideclient.ini's, but no luck unfortunally ):-

Best regards,

Niko

[Pete Dowson]

Further to my last message, I've now managed to reproduce the 10044 error message box, on a Win98SE installation with FS2002.

This occurs only with IPX/SPX not installed. Oddly, the error message on Windows 98SE is different to the one I get on Windows XP, which is why it isn't trapped as such and simply logged rather than produce a message box.

However, subsequently, after OKaying out of that message box, FS2002 continued and operated perfectly.

So, it doesn't really answer your questions. I will deal with the 10044 error correctly in version 6.45 (imminent), which will stop the incorrect Message Box appearing, and will stop it retrying after the first error, but it won't necessarily stop your FS crashes as we currently don't know what is causing them.

There are a couple of possibilities I can think of

1. The way it is, because the 10044 error wasn't one which logically tells WideServer that there is no IPX/SPX installed, the module keeps retrying at intervals. I think it only does this until there's actually a connecting Client, however. Do you have a connecting client which is working?

Maybe there's something about the drivers for your specific Network which gets upset at the retries (even though these are at only 11-12 second intervals).

2. The cross-tracks on your hard drive are causing the problem of FS crashing.

You can eliminate the former by installing IPX/SPX, even if you don't use it. You can fix the latter by running the appropriate Windows check-and-fix (right click on the Drive in Explorer, select Properties, Tools, Check Now).

If you still get FS crashing, and still only with WideServer installed, then I think there's certainly some problem with the Network or its drivers. You could try uninstalling the Network card and re-installing it. Check also that it isn't sharing IRQs with anything else (especially not the video card) -- you may have to move it to a different PCI slot.

Regards,

Pete

[avioniko]

Hi Pete,

I tried to install IPX/SPX, set bindings and all, everything ok.

Started FS2002 and got ridd of the Message Box with that error we discussed.

Now I am going to rerun, recheck and start trying a client pc as well.

Keep you posted, thanx in advance so far:-)

Best rgrds,

NG

[Pete Dowson]

Also trying to obtain of this W98SE machine it's servernode to implent in the wideclient.ini's, but no luck unfortunally ):-

You only use the ServerNode if you are running IPX/SPX. If you install IPX/SPX on the Server then WideServer will tell you the ServerNode in its Log.

If you are using TCP/IP then you only need specify the Server NAME in the Client INI files.

Regards,

Pete

[avioniko]

Hello, Good morning Pete,

The ServerNode issue came up by a friend in Belgium who is even using that on an overall Win XP Pro network. This, in conjuction of course of either ServerName OR ServerIPAddr (the latter I use).

Also I did a scandisk check in Win98SE on all local HDD's; result was no errors found nor fixed. Afterall, it's a new computer, with all hardware new. No hardware yellow signs in hardwarelist nor IRQ conflicts! If there would be IRQ or any hardware conflicts, FS would crash with or without WideFS. So, more and more it comes down to the network card and it's issues:-)

I can confirm, when IPX/SPX installed on the server W98SE machine, the Message Box with the 10044 error dissappears indeed :-)

Overall I can say, the network is running fine and very smooth, except when FS2002 is coming around. As long as the FS-server machine is running (no clients running), with FS2002 AND FSUIPC 3.44 it runs forever!!! (did a long endurance test last night). When Wideserver.dll and ini files are implaced, the system crashes within 1-5 minutes somewhere down the line.

I am abroad for the weekend, but when I am back Monday afternoon, I jump back in the mystery. If you have other thoughts please share with me and I look into it Monday when back.

Another thought regarding the network card; -> switch off the onboard Yukon chipset one with it's respective correct drivers in the BIOS, put in an old temporarily PCI-networkcard, install and setup correctly and off we go?

Take care, have a great weekend!

Best regards,

Niko

[Pete Dowson]

I can confirm, when IPX/SPX installed on the server W98SE machine, the Message Box with the 10044 error dissappears indeed :-)

Overall I can say, the network is running fine and very smooth, except when FS2002 is coming around. As long as the FS-server machine is running (no clients running), with FS2002 AND FSUIPC 3.44 it runs forever!!! (did a long endurance test last night). When Wideserver.dll and ini files are implaced, the system crashes within 1-5 minutes somewhere down the line.

Okay. This simply proves, as I thought, that the crashing problem isn't due to the error messages which were occurring.

The main difference when running FS is that it drives the graphics heavily. Did you check that the network card doesn't share an IRQ with anything else, especially not the video card? This is very important on Windows 98SE especially -- Windows XP is rather better at sharting IRQs (though it still can reduce performance and reliability in my opinion).

If the network card in in the slot next to the video card it will certainly be using the same IRQ, but it may be doing so in any case.

Another thought regarding the network card; -> switch off the onboard Yukon chipset one with it's respective correct drivers in the BIOS, put in an old temporarily PCI-networkcard, install and setup correctly and off we go?

Oh, I hadn't realised it was an on-board network. That makes moving it to a different slot rather difficult! :(

Yes, by all means try a PCI network card if you have one. I use relatively cheap ones quite successfully. Of the three I've had fail on me in six years, two were expensive ones in any case!

Also search for new drivers for the on-board one -- go to the website of the mobo manufacturer and check. Even if there are no new drivers it may be a good idea to find the drivers disk which came with the mobo and re-install.

Finally, is there any good reason you are using Win98SE on the server and WinXP on the Clients? That does seem a little bit the wrong way round. If not Win98SE all round, why not WinXP all round?

Regards,

Pete

[avioniko]

Hi Pete,

Unfortunally in a nutshell, bad news. Problems are not solved...at all ):-

To comment about W98SE (server) with WinXP Pro on client pc's, I thought it was more than possible, due to the fact TCPIP protocol has nothing to do at all with the OS.

Anyway, one of the things I tested was disabling the onboard LAN-adapter and putting in a cheap Realtek ethernet card, always worked fine.

Yesterday I flew, Amsterdam -> Madrid let's say 1:30, no problems

This morning Rotterdam -> Girona and after 50 minutes, server hung.

Overall reset, after putting in that Realtek card, and after 45 minutes server hung again.

So the crash occurs now more later in flight...still no good.

My conclusion so far, it wasn't the onboard LAN at all.

Now, I let just the server (W98SE & FS2002) run, with NO hardware connected whatsoever, no CPFlight stuff, no USB throtles, no nothing, except 3 client pc's with just and only Project Magenta...

Took a default MSFS B737-400, used that Flight Planner thing and of we go...afte 20 minutes, crash again, server hung.

Now, I just let the server run, no clients, WideServer "is waiting for clients", I use now our PMDG B737-700 with no AP/panel and all...and it's still running!!!

Do you have any tips, suggestions what to check and to make my weekend a good one?

Take care, hope to get a reply soon.

Best regards,

Niko

p.s. I cannot give you wideserver.log files after crashing, it just doesn't save it.

[Pete Dowson]

My conclusion so far, it wasn't the onboard LAN at all.

But related to the networking operations, none the less.

Did you check the IRQ assignments? Win98SE is very poor as sharing them.

server hung.

When you say "server hung" what is hanging? The whole system, or only FS? What exactly do you see? If the PC is hung it is almost certainly some driver level clash.

Do you have any tips, suggestions what to check and to make my weekend a good one?

Not really. I am still very very suspicious of mixing Win98SE and WinXP on the same Network, most especially when the Win98SE one is the Server. I had a load of problems which were unsolved till I changed the Server. It seems to work okay the other way round (i.e. one or more clients being Win98SE).

Have you considered upgrading that PC to WinXP?

p.s. I cannot give you wideserver.log files after crashing, it just doesn't save it.

Well, it creates a log file as soon as it is started. If that file isn't entering the file system on hard disk it certainly does sound like the whole PC is crashing, as otherwise the caching in memory would be flushed when the process closes/dies. I think you can tell Windows not to cache writes. It slows things up a bit but does ensure data isn't lost on crashes.

BTW I don't know whether you've noticed, but the current supported versions are FSUIPC 3.45 and WideFS 6.45.

Regards,

Pete