Desktop

Ask something
Discussion Locked

Is changing MS install dirs problematic

0 helpful
1 reply

by simon2305

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

What is the conventional wisdom regarding the installation of Microsoft 32bit software O/S & otherwise in directories that are not the MS default?
For example
Would using non default directories provide an extra level of security against virii?
Could it provide extra protection from malicious HTML?
Can the directory names indicate to end users that they really shouldn't be exploring this folder?
Do non-default names make for technical nightmares? If so how?

Any views are appreciated

1 reply

by krm

It shouldn't really make any difference.

It would probably be useless against virii, as most viral code I've seen (and that ain't much) uses more of a \%systemroot%\filename structure and so the registry points them to the OS directory, even if it's named "e:\bob" rather than "C:\windows" or "C:\winnt".

Technical nightmares? Only if they aren't documented for your techs usage.

As far as directory names indicating to users not to explore, the Windows folder and Program Files (under 2000 at least) warn users not to mess with them before showing them any files (although this can be disabled).

Informing the users not to touch certain directories would probably be more effectinve anyway.

This discussion is closed to new replies.