Kerry-I thought it was 'intuitively obvious' what I meant by Hazardous.
Putting software into c:/Program Files means that when you add files to your
directory, you cannot view them without clicking on something called
'compatibility files'. This is unnatural to me and easy to miss. This
redefines what a file is. It means I have to remember that I am not in my
own directory anymore and overly complicates the process of just wanting to
view a file. When I stumble around for hours trying to find my files only to
finally discover that I've been fooled once again, then I stop doing that.
Note: I do not have a problem with other computers except to warn my
customers to stay out of c:/Program Files unless of course they want to
stumble around for awhile and waste their time.
I simply learned my lesson.
Note: my pc has one user-me. It is an engineering/Software development
machine and is not used to download pictures, movies, music, etc etc. Just
to do work.
"Kerry Brown" wrote:
> In another post you specifically say you warn your customers not to install
> your program in the Program Files directory. This is what I was talking
> about. If you don't want then to install into the Program Files directory
> then your installation program has to make this change. During the
> installation you'd create the directory wherever you want and set the ACLs
> to whatever you want. I'd argue that this non-standard practice isn't
> necessary but there could be a valid reason why you want to do this. So far
> all you've done is say that it's hazardous and you couldn't find the files
> because they were somewhere else. If you told us where the somewhere is was
> someone may be able to help. I'm still confused as to what you actually
> trying to do. It sounds like you have two problems, one on your personal
> computer, and one when installing your software on other computers.
> Kerry Brown
> Microsoft MVP - Shell/User