>>No, I meant a small exe which would copy the big exe (or .app, doesn't matter) from the server if newer than local (or local is missing), then would run the local. Each user pulls each version of the exe exactly once from the server. May take a hit when new version is up, but that's actually staggered (unless they all log in at the same time).
>
>Okay, now I understand. The principle is known to me, but it's not an option here, unless of course it can be proven that it boosts performance. :)

Just run filemon on the server and count how many times do parts of the exe go over the cable. With a loader, that would be local, and would go trough the cable only once per version per workstation.

>Still the question is: Is a readonly drive/folder enough or should the file too be readonly? If you don't have a clue, I'll maybe try some tests next week.

I tried it only with a readonly exe. Readonly directory or disks weren't an option back then, and folders didn't even exist (though I did have them... at home, on my Atari :).

>Now it's bedtime. Tomorrow a meeting with a new potential customer. ;)

Good :).