81RED: Hehe, I administer a rather large network on a daily basis, and am used to being logged in with various semi-dangerous levels of privileges. That mindset has spilled onto my private machines as well, even though I do run "suspicious" stuff sandboxed whenever necessary.
well, im in more of the unix mindset on a day-to-day basis... the idea of logging in as root is just... a bad idea. thats what sudo is for, and UAC works reasonably well as a... err... pseudo-sudo :)
81RED: Anyway, isn't this Vista virtualization somehow flawed if it creates a "shadow" copy automatically, but forgets to delete it when the "master" copy gets destroyed?
not really... the idea of the virtualization is that the stuff in the user-level virtualstore overrides the stuff at the root level... and, under NORMAL circumstances, a file in the "real" program files dir would not be summarily deleted by an admin. the problem comes up when a user with a virtualized install of a program (me) steps outside the virtualized environment and uses sudo/UAC to elevate and delete one of the "real" files, without having the good sense to also delete any corresponding virtualized files.
had the deletion occurred though "normal" channels, ie, at the hands of the (virtualized) application, the problem would not have occured. the problem isnt with vista, UAC, or the virtualization... the problem was with ME, because im the one that waved the magic root wand and started deleting files, im the one that got the virtualized stuff out of sync, and im the one that failed to fix it :)
ill grant that the whole UAC/virtualization setup in vista is not a "simple" system... but from my perspective, its a GOOD one... and its light-years ahead of the utter lunacy of making all interactive users root which all the windows OSs suffered from pre-vista.
edit: and while this does solve the technical issues with flatout, it doesnt help with the fact that i cant finish a damn one of the gold level races. those tracks are BRUTAL...