Wideclient doesn't start and automatically deleted

[sdlc]

Hello Pete,

today i tried to update wideclient from 6.9.9.930 to 7.1.5.6 . The problem is when i click to start wideclient.exe the file is automatically deleted and i have a message from widows  "impossible to acces to file bla bla bla. Windows defender is off and same problem with the firewall and antivirus off and as administrator.

In the properties of windeclient.exe i have "this file comes from another computer and may be blocked".  No change when unblocked. Every time wideclient.exe is deleted.

an idea ? 

Thanks

BR 

Stephane

 

 

 

[Thomas Richter]

Hi,

if it gets deleted it gets deleted by a antivirus program. But it is a false positive, if you downloaded here from this place (Download Links -> Udated Modules)

WideClient 7.156 WideClient 7.156

Thomas

[sdlc]

Hi Thomas,

Thanks ! Very simple error from my side .... Antivirus was deactivated but not antivirus function of Comodo Firewall....

Thanks again

 

Stephane

 

[sdlc]

hello,

 

After one month without problem, i have a new problem now :

When i start widefs client, it starts and just after the connection the program is closed without error message. See below the log. I have made no change instead windows updates.....

 

Stephane

 

 

 

 

********* WideClient Log [version 7.156] Class=FS98MAIN *********
Date (dmy): 22/12/19, Time 14:33:19.927: Client name is DLC-CLT2

      109 Timing Thread Started <M1:L0:C0:H169>

      141 KeyHook added: 259=0,0,FS98MAIN, <M0:L0:C0:H226>
      141 KeyHook added: 260=0,0,FS98MAIN, <M0:L0:C0:H226>

      156 LUA: "C:\Program Files (x86)\wideclient\Initial.LUA": not found <M0:L1:C0:H233>
      156 In MessageLoop <M0:L1:C0:H233>
      156 SendReq Thread Started <M0:L1:C0:H237>

      156 In MessageLoop <M0:L0:C0:H237>

      203 WM_MYTIMER still okay in LAN thread <M0:L1:C0:H244>
      203 RECONN Entry <M0:L1:C0:H244>
      203 Attempting to connect now <M0:L1:C0:H244>
      203 Mailslot being created ...  <M0:L1:C0:H244>
      203 Mailslot "\\.\MAILSLOT\MS_WideServer" created ok <M0:L1:C0:H245>
      203 Trying to locate server: Need details from Server Broadcast <M0:L1:C0:H245>
      203 Failed to connect: waiting to try again <M0:L1:C0:H245>

      234 In MessageLoop <M0:L0:C0:H245>

      437 WM_MYTIMER still okay in main thread <M1:L0:C0:H246>

      437 In MessageLoop <M0:L0:C0:H246>

     1203 RECONN Entry <M0:L1:C0:H246>
     1203 Attempting to connect now <M0:L1:C0:H246>

     1266 In MessageLoop <M0:L0:C0:H246>

     2203 RECONN Entry <M0:L1:C0:H246>
     2203 Server = DLC-CLT1 <M0:L1:C0:H246>
     2219 Trying TCP/IP host "DLC-CLT1" port 8002 ... <M0:L1:C0:H292>
     2219 ... Okay, IP Address = 192.168.0.3 <M0:L1:C0:H292>
     2219 RECONN Exit (ok) <M0:L1:C0:H297>

     2219 In MessageLoop <M0:L0:C0:H299>

     2219 WSA_CONNECT Entry <M0:L1:C0:H299>
     2219 Connection made okay! <M0:L1:C0:H299>
     2219 WSA_CONNECT Exit1 <M0:L1:C3:H299>

     2219 In MessageLoop <M0:L0:C3:H299>

     2219 WSA_READ Entry <M1:L1:C3:H299>
     2219 WSA_READ FD_WRITE <M1:L1:C3:H299>
     2219 WSA_READ Exit1 <M1:L1:C3:H299>

[Pete Dowson]

What logging are you enabling in Wideclient.INI? Best to leave it defaulted please. If we need special logging we'll say so.

More importantly, WideClient is only one end of the connection. You should show the WideServer.LOG from the server end too (in the same folder as FSUIPC). maybe the FSUIPC log too -- all of course relating to the same period.

Pete

 

[sdlc]

hi pete,

See the file attached

Thanks for your help

Stephane

 

FSUIPC5.zip

[Thomas Richter]

Hi,

as all files didn't finish, FSUIPC5.log included, we can guess that actually P3D crashed. If it it not that case then pleas run a session and after P3D has fully closed then send the files again, as there are important information at the end of those logfiles.

Thomas

[sdlc]

Thomas,

The logs with closing datas

Thanks

 

Stephane

 

FSUIPC5.zip

[Thomas Richter]

The WideClient is then crashed, not normal closed?

Is the client PC wired to the network or wireless?

In WideClient.ini you use one or the other, ServerName= or ServerIpAddr= , to select the server?

Thomas

[sdlc]

hi thomas,

-It looks like normal closing. No error message. It just closed just after "connected" displayed

-It's wired connection

-none

Stephane

 

[Thomas Richter]

Hi,

as the WideClient.log file is not fully written it is not a normal close.

A normal closed log file for WideClient would look like this example:

Quote

********* WideClient Log [version 7.156] Class=FS98MAIN01 *********
Date (dmy): 16/11/19, Time 08:55:18.983: Client name is TSR-DEV
      906 LUA: "F:\FSTools\WideFS\Initial.LUA": not found
      906 Attempting to connect now
      938 Trying TCP/IP host "TSR-DEV" port 8002 ...
      938 ... Okay, IP Address = 192.168.1.7
     2969 Error on client pre-Connection Select() [Error=10061] Connection refused
     2969 Ready to try connection again
     4016 Attempting to connect now

     7313 ****** End of session performance summary ******
     7313 Total time connected = 0 seconds
     7328 Reception maximum:  0 frames/sec, 0 bytes/sec
     7328 Transmission maximum:  0 frames/sec, 0 bytes/sec
     7328 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

     7328 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********

Thomas

[sdlc]

Hello

Since, I have let besides this problem  but with the confinement i have time to found the problem.

It was due to Comodo.... The firewal had classifed widefs as malicious....

But now widefs works but instead the small tab "wideClient FS98 Eliminator" on the screen i have 2 big rectangles grey and one purple....

 

Stéphane