Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hi,

I would like to know if WideFS works on NT4 SP6a server because when I load the client, an error window that can be seen in the attached file pops up.

Thanks in advance.

post-2756-128688951274_thumb.jpg

Posted
I would like to know if WideFS works on NT4 SP6a server because when I load the client, an error window that can be seen in the attached file pops up.

No, sorry. You need Win2000 or Win98, or later.

Pete

Posted

If it is only WideClient (NOT FS and the Server part) you want to run on NT4, then just possibly the attached version of WideClient (5.53) will do the job. I've provided an option to bypass the use of ToolHelp (it was only being used to log the names of Client programs). Just edit the INI file, adding "IdentifyClients=No" to the [user] section.

I cannot say for sure whether it will then work -- maybe other things will conspire to stop it. Let me know.

Pete

WideClient553.zip

Posted

Pete,

First of all, thank you very much for taking the time in helping me with this issue as well as for all that you are doing for the flightsim community.

Yes, you are right, I only want to run the client on the NT server. I have downloaded WC 5.53 and edit the .ini file, bu it is still showing the same error message.

Best Regards,

Gig

Posted
Yes, you are right, I only want to run the client on the NT server. I have downloaded WC 5.53 and edit the .ini file, bu it is still showing the same error message.

Ah yes, sorryI now see that it is much more complicated than I thought. I needed to re-code some of it to use run-time linking -- currently it needs that entry as a bound-in link, which is what is causing the error.

Sorry. forget that parameter altogether. It is gone. This version 5.531 sees if it can use the routines (they are in NT's Kernel32.dll) and if it can, it does, if it can't, it doesn't.

Pete

WideClient5531.zip

Posted

Hi Pete,

Thank you very much again for your patience and help. With the latest .exe we have moved one step forward as the WideClient is up and running. Now the second phase: test it to see if it works. I let you know about it.

Regards.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • 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.