I have a small util that I use to "freeze" files on a fileserver, it re-arranges the bytes so that it can't be loaded /edited using Excel or Autocad, and will put them back in place when needed.
I have set this up for fast access .. right clicking a file and choosing to run that util from the context menu on the chosen file. Additionally, a star wrapped TCL script is actually called first, as it will display TK popup warnings of overwrites, and then call the main util to do the scrambling unless aborted. Both the scrambling util and the TCL wrap that calls it reside on local computer in the path.
I have drive mapped the fileserver, but several people who also use this util simply have a shortcut to the unc address of the fileserver, and we've noticed that, if the util is run against any file on the local computer or on a mapped drive, it run instantly, but if it's run against a file on a unc path, the util will think about things for about ten seconds before doing it's thing.
Additionally, I've done some testing that produces odd results:
* If I modify the context menu to run only the scrambling util and not the overwrite checker that calls the scrambling util. it will run instantly on files on a unc path.
- however -
* If I run the overwrite checker (that will call the main util) from a cmd window with a unc path file as the argument, (as what happens in the context menu) it will also run instantly.
So, only when run from the context menu will this exhibit the roughly ten second pause. Moreover, I have another entry in the context menu that calls on a custom compression util, that uses the _exact same_ TCL overwrite checker, and that util will run without pause on unc drive files. The only difference being that with the scrambling util, the TCL overwrite checker will call the scrambling util which is compiled D code, and the with the compression util, it calls on Ruby to run a short script.
Any help in solving this mystery would be appreciated, thanks,
