«

On 23/01/2010 7:24 p.m., peterwn wrote:
> On Jan 23, 5:42 pm, "impossible"<impossi...@nospam.net> wrote:
>> "victor"<u...@example.net> wrote in message

>> news:hjdudn$7fb$...

>>>> "peterwn"<pmiln...@gmail.com> wrote in message
>>>> news:e35e7945-6db8-4d26-9210-...
>>>>> Had to load a friend's notebook from scratch. Installed (presumably
>>>>> reimaged) XP from rescue disc, then applied SP2& SP3. Also installed
>>>>> Office (OEM from discs originally supplied with computer). In other
>>>>> words everything is squeaky clean from the 'genuine' point of view.
>>>>> Applied all essential updates to present as pretty well required by
>>>>> Microsoft. Now I get a message that Office Genuine Advantage is
>>>>> closing down because of an error. Rebooted twice more and keep
>>>>> getting it. Seems my efforts are down the gurgler.

>>>>> Anyone have any ideas what I can do about it?

Do the install again.

Most problems with computers are caused by the user, not the software or
hardware.

BTW what was the error that caused MS Office to close?

Reading the eror message(s) should (at the very least) give you some
information about the cause of the (install) failure.

--


Found Images
http://homepages.paradise.net.nz/~mlvburke

Sweetpea wrote:
> On Sat, 23 Jan 2010 22:46:07 +1300, victor wrote:
>
>> The office eraser tool is on Microsoft's site.
>
> Why doesn't Micro$oft simply fix the uninstallation tool so that when
> MS Office is removed it does so cleanly?
>
One reason is the millions of copies out there already. To fix the tool
for the few that may want to remove Office by an update to Office would
mean millions of unnecessary updates for those that never intend to
remove Office.

Cheers,

Cliff

--

The Internet is interesting in that although the nicknames may change,
the same old personalities show through.

In message <>, Sweetpea wrote:

> On Sat, 23 Jan 2010 22:46:07 +1300, victor wrote:
>
>> The office eraser tool is on Microsoft's site.
>
> Why doesn't Micro$oft simply fix the uninstallation tool so that when MS
> Office is removed it does so cleanly?

Because MS Office is such an orgasmically wonderful piece of software, they
can’t imagine anyone would ever want to uninstall it.

In message <hjfonb$ibc$>, victor wrote:

> Sweetpea wrote:
>
>> On Sat, 23 Jan 2010 22:46:07 +1300, victor wrote:
>>
>>> The office eraser tool is on Microsoft's site.
>>
>> Why doesn't Micro$oft simply fix the uninstallation tool so that when MS
>> Office is removed it does so cleanly?
>>
>>
> There are many reasons that I can think of.

Name one.

> How about you have a little think yourself, instead of kneejerk posting
> every time you get irrationally enraged by someone mentioning Microsoft.

I don’t see anything “enraged� about asking a simple question. Particularly
one about a problem that shouldn’t have been allowed to arise in the first
place.

Lawrence D'Oliveiro wrote:
> In message <hjfonb$ibc$>, victor wrote:
>
>> Sweetpea wrote:
>>
>>> On Sat, 23 Jan 2010 22:46:07 +1300, victor wrote:
>>>
>>>> The office eraser tool is on Microsoft's site.
>>> Why doesn't Micro$oft simply fix the uninstallation tool so that when MS
>>> Office is removed it does so cleanly?
>>>
>>>
>> There are many reasons that I can think of.
>
> Name one.
>
To retain settings.
Just the same as in Linux deb installations, settings that you might
wish to retain in an upgrade will be retained unless you go out of your
way to purge them.

Lawrence D'Oliveiro wrote:
> In message <>, Sweetpea wrote:
>
>> On Sat, 23 Jan 2010 22:46:07 +1300, victor wrote:
>>
>>> The office eraser tool is on Microsoft's site.
>> Why doesn't Micro$oft simply fix the uninstallation tool so that when MS
>> Office is removed it does so cleanly?
>
> Because MS Office is such an orgasmically wonderful piece of software, they
> can’t imagine anyone would ever want to uninstall it.
>
There is a grain of truth in what you say. A home user probably won't
worry about bits left lying around after an install and in a corporate
environment that is properly locked down, the user won't be allowed to
remove it.

Cheers,

Cliff

--

The Internet is interesting in that although the nicknames may change,
the same old personalities show through.

On Jan 23, 9:52*pm, peterwn <pmiln...@gmail.com> wrote:

>
> > I recall that running an "office eraser" cleanup utility was required to
> > remove the residue in the registry after the removal before doing a
> > clean re-install.
> > I don't know if that is still the case though.
>
> Thanks EMB and Victor. I will try this and see what happens. If the
> worse comes to the worse I will have to start over.

I have embarked on a re-install and have so far brought XP up to date
with no apparent problem. Next stage wil be to install Office.

I now think I know what the problem was. I executed SP3 from an
external USB hard drive and noticed when reinstalling that SP3 writes
its temporary files to the USB drive. It appears the drive needs to
be left connected during the subsequent reboot to complete
installation. Anyway I realise now I disconnected it prematurely
which appears to have corrupted the SP3 installs which indirectly set
the scene for Office Genuine Advantage to fail. This incidentally is
executed after login but before any attempt to invoke Office - I
remember now that Office gets itself partly running in anticipation of
being explicitly or implicitly called by the user, otherwise users
would perceive that Office takes unacceptably long to get going.

I am confident the rest of the install will now go OK.

In message <hjftat$glh$>, victor wrote:

> Lawrence D'Oliveiro wrote:
>
>> In message <hjfonb$ibc$>, victor wrote:
>>
>>> Sweetpea wrote:
>>>
>>>> On Sat, 23 Jan 2010 22:46:07 +1300, victor wrote:
>>>>
>>>>> The office eraser tool is on Microsoft's site.
>>>>
>>>> Why doesn't Micro$oft simply fix the uninstallation tool so that when
>>>> MS Office is removed it does so cleanly?
>>>>
>>> There are many reasons that I can think of.
>>
>> Name one.
>>
> To retain settings.
> Just the same as in Linux deb installations, settings that you might
> wish to retain in an upgrade will be retained unless you go out of your
> way to purge them.

But Debian’s package management system, for example, provides a “purge�
option (remove leftover config files) as an integrated part of the system,
you don’t need to download and run a separate “app eraser� tool to perform
that function. The question is: why doesn’t Microsoft provide such a
function integrated into its installation/uninstallation system?

Particularly since such leftover data seems to cause installation hiccups
with Microsoft’s software, as in this case. Which is something I’ve never
seen happen under Linux.

In message <16782b2d-
da7d-48c7-8563->, peterwn wrote:

> I executed SP3 from an external USB hard drive and noticed when
> reinstalling that SP3 writes its temporary files to the USB drive. It
> appears the drive needs to be left connected during the subsequent reboot
> to complete installation.

Do you see what your problem was? Expecting Dimdows to behave rationally. I
thought this was something all seasoned Dimdows users had hammered into them
NOT to expect...

> Anyway I realise now I disconnected it prematurely
> which appears to have corrupted the SP3 installs which indirectly set
> the scene for Office Genuine Advantage to fail. This incidentally is
> executed after login but before any attempt to invoke Office - I
> remember now that Office gets itself partly running in anticipation of
> being explicitly or implicitly called by the user, otherwise users
> would perceive that Office takes unacceptably long to get going.

Do third-party packages get to insinuate themselves into Dimdows the same
way, to mask their long startup times and lengthy “Genuine Advantage�
checks? Or is this something only available to Microsoft?

On Sun, 24 Jan 2010 11:30:50 +1300, victor wrote:

>> Name one.
>
> To retain settings.

User settings should be in their profile, not in the Registry.

Now name another two reasons from among your "many".


--
"Filtering the Internet is like trying to boil the ocean"