You don't need to ask or bet. As I described in my lengthy 30/06/2005 posting:

> I did a complete coherent build using a veeeery long command line:
> KIX32_540rc1.EXE pre\foo.kix dep\bar.kix post\baz.kix .... etc ... /t
> And now it works fine.

I disliked that brute-force mass pretokenization very much - at least for its result with exploding file sizes. With final 4.50 the individual pretokenization works perfect. I immediately switched back to my previously used makescript technique with single-file pretokenization for touched (aka: freshly edited) files as described a few lines earlier in the mentioned posting.

Good news: I assigned the pretokenized scripts to some unsuspecting but generally alert volunteers in my department and until now I haven't heard of any loginscript misbehaviour. ;-)

OldFart