WideFS & SB3/FSINN Problem

[gcoyle]

Posting here in desperation, I've been trying to get the WideFS & SB3 combination working for a week now without success and having tried all suggestions in SB3 support forums.

The problem I'm having is that once I start SB3 (or FSINN) on the wideclient pc, WideClient goes to 90% CPU utilization and hangs.. As soon as I close SB3, WideClient comes back to life.

WideClient consistently works fine with Project Magenta and activesky, it appears to be only the pilot client apps. (SB3 & FSINN) that are causing problems.

I've tried changing WideFS to use the IPX/SPX protocol instead of TCP/IP but still epxerience the same problem.

Any ideas??

Greg

[Henning Huelsebusch]

Hm, I don't have an answer, SB3 with WideFS works more than fine here.

SB3 itselfs as modules-version works fine?

Henning

BTW, FSInn does not support FSUIPC or WideFS. FSInn works with FSCopilot, which has nothing to do with IPC nor WideFS. It ships it own possibility to use FSInn on another PC.

Henning

[Pete Dowson]

The problem I'm having is that once I start SB3 (or FSINN) on the wideclient pc, WideClient goes to 90% CPU utilization and hangs.. As soon as I close SB3, WideClient comes back to life.

That's suspicious, because FSINN isn't an FSUIPC application so it doesn't use WideFS.

If SB3 loops tight on Wideclient and allows nothing else to run, you can try slowing it down by setting the ApplicationDelay parameter in WideClient.INI. See the WideFS docs. Try 50 first, then reduce it. It really shouldn't be needed for well-behaved Windows programs which process messages. And it shouldn't be a problem on WinXP which is better at timeslicing. Are you using Win98 or WinMe perhaps?

WideClient consistently works fine with Project Magenta and activesky, it appears to be only the pilot client apps. (SB3 & FSINN) that are causing problems.

Again, I don't see how FSINN comes into it. If that creates the same problem then it is sounding more like a Network issue.

Regards

Pete

[gcoyle]

Thanks for the swift response. I'll try what you suggest with the ApplicationDelay parameter however, like you I tend to think it's a network issue but if so, it's specific to SB3 since the network behaves well in all other situations. I'll also try a different router and see if that makes any difference. The WideClient PC is running Win2000 with latest service pack. The SB3 and FSINN modules work fine when run on the FS machine.

I was sorta hoping this might be a known issue but it seems it's specific to my setup, I'll let you know the results of the above.

Greg