This is also a good question.
http://www.kixtart.org/board/ultimatebb.php?ubb=get_topic;f=14;t=001160;p=1#000000
I have experienced a delay (really annoying) at start up of a Kix32 script invoke in a CMD session in a no network condition. I contacted Ruud sometime ago but have not had a reply if a fix would be forth coming for W2K.
Howard's comments:
quote:
; --code start--
? "Hello World"
;--code end-
The execution of the script shown above is substantially delayed at startup when the network/domain is unavailable.
Why does KiXtart even attempt to communicate with the domain if no network information is requested or called in the script?
I have attached two network monitor traces that capture the communications caused by KiXtart 4.21. Notice the long delay caused when the network/domain is not available. Can this be corrected? This is very disturbing when trying to test new code locally on a network disconnected computer.
Ruud's comments:
quote:
On XP, KiXtart produces 0 network requests with the network cable removed. On 2000, it can produce 'NetrGetAnyDCName' requests (because 2000 handles the logonserver property differently).
[ 30. September 2003, 19:25: Message edited by: Howard Bullock ]
