Hi!
Here is what happened after installing sp4 over sp3 to my
computer: If I go through the chain:
Start>>Help>>"Any Topics">>Related Topics, I am no
longer able to get anything out of RELATED TOPICS, insted
I always get a wrong message. I don't remember the
message because I am now going to uninstall sp4 Any help
woud be gratefuly appreciated. Thanks, N

Some help functionality was changed with recent hotfixes which prevent Help
from being exploited on your computer:

Links in HTML Help Topics Are Unavailable or No Longer Work
http://support.microsoft.com/default...roduct=win2000

You can always use the on-line Help:

http://support.microsoft.com/default...roduct=win2000


--
Scott Baldridge
Windows Server MVP, MCSE


> Here is what happened after installing sp4 over sp3 to my
> computer: If I go through the chain:
> Start>>Help>>"Any Topics">>Related Topics, I am no
> longer able to get anything out of RELATED TOPICS, insted
> I always get a wrong message. I don't remember the
> message because I am now going to uninstall sp4 Any help
> woud be gratefuly appreciated. Thanks, N

Nicole,

> Here is what happened after installing sp4 over sp3 to my
> computer: If I go through the chain:
> Start>>Help>>"Any Topics">>Related Topics, I am no
> longer able to get anything out of RELATED TOPICS, insted
> I always get a wrong message.

There's a good chance that you have a registry problem: the registry
entries for the HTML Help ActiveX control may be broken. A number of
the security patches and service packs that Microsoft released last
year are known to cause this problem, including the cumulative
security patches for Internet Explorer and SP4 for Windows 2000.

To fix this problem on a machine with Windows 2000 SP4 installed, open
a Command Prompt window and enter the following two commands:

regsvr32 /u <drive>:\winnt\system32\hhctrl.ocx
regsvr32 <drive>:\winnt\system32\hhctrl.ocx

The first command unregisters the ActiveX control; the second command
re-registers it, thereby fixing the broken registry entries that are
responsible for the problem.

--
Pete (Microsoft Help MVP)