Re: Default directory

On 2012-09-15, at 1:00 PM, wdsci-l-request@xxxxxxxxxxxx wrote:

Just my CDN$0.02, not the opinion of my employer, etc., etc...

The default install works exactly as intended, the product and config is
in the protected directories and needs an administrator to modify it yet
the product can be run by a user.

I'll take your Cdn$0.02 and raise you Mike.

I know it is _supposed_ to work this way but that was not my experience.

When I did an install using the defaults (it was my first on Win 7 and I had no clue what these funky directories were about) it didn't perform as well as I had expected but I put it down to the VM performance with Win 7. When I came to try to install updates it would just blow up (something to do with being unable to delete stuff if I recall). The messages indicated that I did not have enough authority. Since I was the Administrator that was tough to find a way round.

I searched various forums and posted questions here and the suggestion I got was to avoid these "protected" directories and reinstall in my own directory. Not only did this solve the update problem but it seemed to run better.

Since then I have installed a couple of times for customers using the defaults and in about 50% of the cases have experienced the same problem, which again was cured by using a different directory. As a result we now routinely advise customers to install in their own directory (We usually call it IBM or RDP) because we see little value in the protected directory status but we do see problems when we use them.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com