Jonathan -
(First of all, ignore previous APPARENT 9/11/07 reply from me -- that wasn't
what I sent, but is just a quote of your previous reply to me. When I sent
my response there was VERY LONG delay and then I had to sign in again, and
then I got the message indicating my reply had gone through; but obviously it
didn't. Fortunately, I saved a copy of the text of my reply, which I now
post again below. Hopefully it comes through correctly this time...and sorry
for the trouble.)
Thanks for your reply. I had to leave town late Friday afternoon (9/7/07)
b4 you posted it, so I finally went ahead and cancelled the installation of
v8.1, thinking I'd hear from someone eventually and try again. When I
cancelled the installation, I got following message, with error code (which
may or may not be useful):
Windows Live Messenger setup has failed with error code: '1603'.
Please go to the Windows Live Messenger website
http://messenger.live.com
to download the latest version of Windows Live Messenger.
Also, when I cancelled the installation, I immediately got an eMachines
BigFix (eMachines pre-installed update tracking software) notice about a
critical update for MSN Messenger 6_2 (I assume because it somehow tracks
installations and detected the rollback to v6.2). I downloaded & installed
that update, which turned out to be v6.2.0.208, and this version seemed to
install and work OK.
However, the key I mentioned earlier:
\SYSTEM\CurrentControlSet\Services\EventLog\Applic ation\usnjsvc
still does not exist. I did check the permissions for:
\SYSTEM\CurrentControlSet\Services\EventLog\Applic ation\
as you suggested, but that stretches me into new territory, and I don't know
what the permissions "should" be. And since I may have to upgrade to v8.1
anyway (see "Forced, XP-only Windows Live Messenger 8.1 update" at
http://www.mess.be/) I may still have to get the permissions straightened out.
In the bigger picture (and perhaps somewhat off-topic for this newsgroup),
I've been having serious Windows Update problems (currently about 73 critical
updates I can't install after computer was unused for about 10 months) and
many other programs I can't install (e.g., most antivirus programs, Spybot,
Windows Defender, etc), all of which, as far as I can tell, are running into
"permissions" problems (and/or "ownership" problems???). Sometimes the error
popups refer directly to "permissions," or directly/indirectly state/imply I
need to be in an Administrator account; but they often refer to "insufficient
resources," sometimes with error codes (e.g. in Windows Updates) that point
back to permissions. As I mentioned, I'm running in the Owner/Administrator
account, and I have 512MB of RAM, but I get these "insufficient resources"
messages even if no other programs are running.
So I really want to learn more about appropriate permissions settings in
general, and how to change them to appropriate settings. With that in mind:
1. Can you clarify what they "should" be in Owner/Administrator account for
the Application registry key mentioned above?
2. Can you steer me to any clear general introductions/summaries regarding
proper (or default?) permissions settings for an Owner/Administrator account
and a normal User account?
3. Finally, and of less immediate importance, do you know if there are any
particularly important differences in typical permissions settings between
WinXP Home and Pro (with or without Tablet PC). (I also have a Tablet PC
with WinXP Pro Tablet Edition, but haven't been having ANY of the permissions
or installation problems on it.)
I apologize if any of this is too far off-topic, but any guidance you can
offer would be greatly appreciated!!!
"Jonathan Kay [MVP]" wrote:
....> It does sound like something has broken permissions in your registry.
Instead of using
> SubInACL, go into the registry to this key (or at least the Application key), right-click and
> choose Permissions. You'll then be able to see exactly what's going on registry
> permission-wise. My apologies if you've already done this.
^^^ (Believe me, NO apology needed on this <g> ---gdv) ^^^