Herman Veerbeek

Dear Pete, I'm happy to say everything is solved. Via wireless it gives problems, because on servercomp you have to put a IP address (192-168-1-93 for me) and then internet won't work, so that's no option.. widefs is doing well then.... I took the crosscable, configured the IP op the LAN on server to 192.168.1.93 and the LAN of the client to 192.1.92 and now WideFS is via crosscable very happy, internet is wireless very happy and me too :-) kind regards and thanks for your quick reactions.... Herman

Here's the log: ********* WideClient Log [version 6.86] Class=FS98MAIN ********* Date (dmy): 02/07/11, Time 15:14:42.704: Client name is PC_VAN_HERMAN 359 LUA: "C:\fsc\Initial.LUA": not found 422 Attempting to connect now 1266 Server = HERMAN-LAPTOP 1281 Trying TCP/IP host "HERMAN-LAPTOP" port 8002 ... 1281 ... Okay, IP Address = 192.168.1.93 7547 ****** End of session performance summary ****** 7547 Total time connected = 0 seconds 7547 Reception maximum: 0 frames/sec, 0 bytes/sec 7547 Transmission maximum: 0 frames/sec, 0 bytes/sec 7547 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 7547 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* I hace a crossed cable, maybe try it... kind regards, Herman

I'm geting this line in the log: LUA: "C:\fsc\Initial.LUA": not found (C:\fsc is the map wideclient is started) kind regards, Herman

I'm a registrered user of FSUPC and Wide FS, using it on FSX, Windows 7.... servercomputer is laptop, client desktop. I've installed FSCommander there. FSCommander succeeded in updating airportdsata fron servercomputer.... I put Wideclient.exe en cgf in the FSCommander map and added in cfg file a RUN1 to start FScommander. No problems with that. But when i first start FSX and then Wideclient they don't see eachother... In FSX I enabled Widefs... Hope you have some suggestions... network is wireless... Kind regards, Herman