Wideclient DelayReady?

[StuartWhelan]

I am trying to use the delayready facility and am having problems.

I am using Wideclient 550 on WinXP with FS2K2 over IPX.

In the user section of my wideclient.ini I have:

[user]

Log=Errors+

DelayReady1=60

RunReady1=c:\code\projects\eicas\eicas.exe

But Eicas.exe starts straight away.

In the log I get:

********* WideClient.DLL Log [version 5.50] *********

Date (dmy): 14/06/03, Time 17:58:06.359: Client name is BEASTIE

47 Attempting to connect now

63 Connection made okay!

219 New Client Application: "eicas" (Id=3264)

3969 Reception maximum achieved: 0 frames/sec, 0 bytes/sec

3969 Reception average achieved whilst connected: 1 frames/sec, 243 bytes/sec

3969 Max receive buffer = 296, Max send depth = 0

3969 ********* Log file closed (Buffers: MaxUsed 1, Alloc 23 Freed 23 Refused 0) *********

Any ideas?

[Pete Dowson]

I am trying to use the delayready facility and am having problemsBut Eicas.exe starts straight away.

Please see the documentation, where it says:

"These optionally define delays, in seconds, to be executed after the corresponding RunReady parameter, above."

See the word "after"?

The facility is intended only to separate multiple loads. There is no point in a delay for a single program being loaded. It achieves nothing. What are you trying to do with it anyway?

I added this to separate some programs which take a while to initialise and seem to take far too long when starting together -- several components of Project Magenta on the same PC, for example, or FSMeteo and Radar Contact on the same PC. I really see no point in delaying the first and only program being loaded. The "Ready" action already stops it loading till FS is ready.

Regards,

Pete

[StuartWhelan]

I am trying to use the delayready facility and am having problemsBut Eicas.exe starts straight away.

See the word "after"?

Doh. :)

What are you trying to do with it anyway?

I was having problems with an application failing to make its very first read from FSUIPC, and I thought delaying its startup may help. It turned out to be a timing issue within my appilcation, so the problem has been resolved.

Thanks!