Ed,
I too was about to respond to Stephen regarding his
statement about "...cleaning up his machine..." and advise
that the registry is the source of 'all evil' when it comes
to trying to uninstall applications... but you beat me to
it.
However, your statement "...cleaned up the registry of
everything left over, and then reinstalled it. Ran like a
charm." is also somewhat misleading. "Cleaning up the
registry..." as you alluded to in your previous paragraph is
NOT for the faint of heart nor for anyone, who if they mess
it up isn't willing (and prepared with adequate backups of
the data they care about) to wipe the drive clean and start
again. As you know (but others may not) this is NOT a
Writelog issue, but rather is inherent in all Windows OS
based computers. The old saw about "...having all your eggs
in one basket..." applies to the Windows registry. Just take
a look at any MS Knowledgebase article that involves a
registry edit and MS states in bold print that this is a
potentially dangerous exercise. Even Microsoft's own
uninstaller code all too often fails to deal with the
registry left overs adequately and the folks who write that
code have access to all the 'insider secrets' that third
party vendors are denied.
Just a cautionary tale... editing the registry should be
undertaken with considerable caution and not without the
ability to start fresh and not lose data that you care about
if things go wrong.
73
Patrick
W7TMT
-----Original Message-----
From: writelog-bounces@contesting.com
[mailto:writelog-bounces@contesting.com] On Behalf Of K4SB
Sent: Thursday, November 04, 2004 20:32 PM
To: WriteLog Reflector
Subject: Re: [WriteLog] Trouble with 10.50D
"Stephen J. Schrack" wrote:
> Is anyone having a problem with Writelog rebooting their
machines? Specs are Windows > XP with SP2. SP2 is not the
cause because I was running it with previous version ok.
---------------
First of all, unless you did a registry edit and got rid of
the WL entries ( and there are probably a least 100 left
over ) you didn't clean our machine. Not WLs fault, just the
uninstaller.
This is just a wild guess, but has anyone tried installing
SP2 before WL?
I had a problem with Norton 2003 when SP2 was installed, and
simply couldn't fix it.
So, I took 2003 off the computer, cleaned up the registry of
everything left over, and then re installed it. Ran like a
charm. I also put WL on the XP disk after SP2 was downloaded
and it has run like a champ.
73
Ed
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|