|
|
|||||||
When starting kix32.exe on our Windows 2000 terminal servers with Citrix MF XPA 1.0 there's a delay of about 2 seconds before the script is processed. Even when starting kix32.exe without parameters the 2 seconds delay is there before showing the syntax. NTFileMon shows a delay processing the various paths in the %path% environment. Typing set path= before starting kix32 brings the delay down to about 0.5 - 1.0 second. We notice no delay starting the same kix32.exe from any other computer. The Citrix servers are equipped with dual 2.8ghz Xeons, 2gb RAM and RAID1 U320 SCSI. The actual processing of the scripts goes very fast. Anybody got a idea ? |
||||||||
|
|
|||||||
no, but I have seen this on my logonscript and it has nothing to do with citrix or terminals. think it's something about kixtart structure but how to debug that??? how you call the script? |
||||||||
|
|
|||||||
Login script name for the users is logon.bat The content of logon.bat in \\server\netlogon is: code:The way the script is called doesn't seem to make a difference. If I logon to a citrix server and CD to d:\environment\scripts and run kix32.exe without parameters, there's still a delay of two seconds before the syntax is shown. Copying kix32.exe to c:\ and starting from there doesn't make a difference. creating a kixtart.kix file with ? 'test' from the directory where kix32 is started runs the script but still with the delay. NTFILEMON shows the following behaviour when kix32.exe is started: - kix32 queries the following directories for information: - the directory where kix32 is started (2x) - c:\winnt\system32 - c:\winnt\system - c:\winnt - all directories in the PATH environment - each query takes 70 - 80ms - each query's result is SUCCESS - each query returns Attributes: D or Attributes: DA Starting KIX32 from my workstation (Windows XP) and debugging with ntfilemon shows completely different queries from the kix32.exe process. Can this be because of prefetching feature in WinXP ? Is this a bug in kixtart 4.20 ? Does anybody experience the same problems ? Does anybody know a fix / workaround ? |
||||||||
|
|
|||||||
it is kinda a behaviour, but really annoying one. does it really happen just the same if you start kixtart with full-path to the script? |
||||||||
|
|
|||||||
Yes, starting: c:\kix32.exe c:\test.kix gives the same behaviour. |