mark44 Posted November 29, 2003 Report Share Posted November 29, 2003 Hi, I have just registered both FSUIPC (ver 3.125) and WIDEFS (ver 6.101). After installing them I noticed that FS2004 consistently locked-up after several seconds of selecting a flight. The image freezes but the sound continues playing. I naturally updated all drivers and even re-installed Win XP and FS2004 but to no avail. However, after several hours of trial and error I have noticed that the lock-ups only occur when I copy wideserver.dll and wideserver.ini to the FS2004 modules folder (this is even before I run wideclient on my laptop). If I remove the wideserver files and only keep fsuipc.dll all is fine. My widerserver ini file is: ================================================== [Config] Port=8002 UseTCPIP=Yes ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== and mywideclient ini is: ===================================================== [Config] Port=8002 UseTCPIP=Yes ServerName=MARK Window=32000,32000,160,34 Visible=Yes ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== The wideserver log reads: ********* WideServer.DLL Log [version 6.101] ********* Using blocksize guide of 4096 bytes Date (dmy): 29/11/03, Time 19:57:19.828: Server name is MARK Apologies if I have overlooked something very basic but I just can't get it to run. Any help would be much appreciated. Regards, Mark Link to comment Share on other sites More sharing options...
Pete Dowson Posted November 29, 2003 Report Share Posted November 29, 2003 I have just registered both FSUIPC (ver 3.125) and WIDEFS (ver 6.101). After installing them I noticed that FS2004 consistently locked-up after several seconds of selecting a flight. The image freezes but the sound continues playing. I naturally updated all drivers and even re-installed Win XP and FS2004 but to no avail. However, after several hours of trial and error I have noticed that the lock-ups only occur when I copy wideserver.dll and wideserver.ini to the FS2004 modules folder (this is even before I run wideclient on my laptop). Ouch. It sounds (and looks) like something is wrong with the Network installation. Does your Network behave well in all other respects? Can you share folders and so on with Windows Explorer? The only thing peculiar that WideServer is doing is trying to open a serving port on the Network. There's nothing of a low enough level in any of FSUIPC or WideServer to lock things up. Please see if you can check out your Network first, then get back to me and we'll figure out the next step. I'm afraid I don't really know much about Networks, it's all trial and error for me to get them working. The Network code in WideFS is straightout of Microsoft examples and has been virtually unchanged now for five or six years. Regards, Pete Link to comment Share on other sites More sharing options...
mark44 Posted November 29, 2003 Author Report Share Posted November 29, 2003 Hi Pete, Thanks for the quick reply. The network between my PC and laptop seems ok. I can access and transfer files both ways. The network card on my PC has the following installed: Client for Microsoft Networks File and Printer Sharing for Microsoft Networks QOS Packet Scheduler Internet protocol (TCP/IP) The card on my laptop has all the above installed except QOS Packet Scheduler. These are the default installations when I set up my home network. Hopefully someone else has experienced this and can let me know what I have done wrong. Regards, Mark Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now