On Tue, 23 Sep 2008, Ben Burnett wrote:
This is not true in the general case. If there is already something whose 8.3 name is PROGRA~1 in the same directory as "Program Files", that was created _before_ the "Program Files" directory, then "Program Files" will have a different 8.3 name. This is certainly an unlikely circumstance, but I have come across at least 2 machines where it was the case.Interesting, I've never run into this. Under what circumstances did you encounter the directory "Program Files" not being mapped to "PROGRA~1"? I figured that since the directory it is put in place during an install, it would always be this way, except possibly on customized installation.
In one case my conclusion was that it happened because the machine's administrator had moved the "Program Files" directory to a different partition (which already existed and had other directories in it) AFTER the original install.
In the other case it seemed to be because the installation was an update/upgrade onto a partition which already had data on it, and the partition was not first reformatted/trashed.
I guess you could regard both of those as "customized installations". :)These were some time ago, so these details are from my (unreliable) memory. And, of course, there may be other circumstances in which it can happen as well - these are just the ones I 've come across.
The reason I came across the first one was because there was something using PROGRA~1 in its path and this turned out to NOT map to the "Program Files" directory... worse, the whole path mapped to an existing (but unwanted) path, which made debugging it painful. (Which is why I remember it!) :(
-- Bruce -- Bruce Beckles, e-Science Specialist, University of Cambridge Computing Service.