On 2012-10-18, at 4:26 PM, wdsci-l-request@xxxxxxxxxxxx wrote:
Imagine the average user being able to install a new release of IBM i,
or even run PTFs. It's almost unthinkable, right? You need *ALLOBJ to
do that sort of thing... well, why are we getting upset when Windows
requires the same thing?
I'm really not upset with MS - as you say - it is about time they did something to fix it. Although I think they could have done a better job of somehow telling you that although you are logged in as Admin you really aren't. On IBM i if I'm logged in with SECOFR (or have *ALLOBJ for some other reason) then all I do is covered by that. There's no - "well you are not _really_ an administrator at this time." It was the omission of that information that caused me to waste so much time.
I was however upset with IBM.
On my original install I simply launched the install as normal. There was nothing that I saw with the 8.0 or 8.5 docs or in the wizard that said anything about "run as administrator" so I just went ahead and installed as normal using the defaults. After all I was an Admin. It worked fine - although there were a few rather odd messages every time it started running anything new for a while.
Then I tried to apply updates. It failed and there was nothing on IBM's site that explained. I found nothing in searching MS sites that explained it. I did eventually find info that mentioned "Run As Administrator" but as far as I could see there was no obvious way to apply fixes that way. After wasting a lot of time I finally decided to try the approach that David and others suggested and do a reinstall using my own directory and not one of the special protected ones. Since then it has all worked fine.
As you know I use Mac - the only reason I use Windows at all is for RDP so I have not done extensive research on the latest Windows vagaries. Mea culpa.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.