M
Markus
Hello!
I just installed XP Pro a couple of days ago, on a machine that previously
ran allright under 2k, but now I'm having a problem that's really annoying
as can be:
Everytime I try to start a new program via Start > Programs > ... or through
the QuickLaunch bar, the icon or menu entry stays "marked" - but nothing
ever happens! It's only after what appears as a "minute's silence" of some
20-40 sec. that the program opens up as usual - no error messages, no event
mgr entries.
Interestingly, the program that I was working with when I tried to start
another one works continues to work alright during that period of time. I
can also access the "windows security" popup by pressing CTRL-ALT-DEL during
that 20-40 sec., but when I try to start the Task Manager I get the exact
same problem. And - like I said: After this "break", all programs I clicked
on pop up and start running as if nothing ever happened.
The problem seems to occur less frequent when the machine has just been
rebooted a while ago, and it seems to become more frequent when the machine
has been running for quite some hours.
Any hint/help is greatly appreciated.
Thanks a lot in advance!!
cheers,
Markus Grein
I just installed XP Pro a couple of days ago, on a machine that previously
ran allright under 2k, but now I'm having a problem that's really annoying
as can be:
Everytime I try to start a new program via Start > Programs > ... or through
the QuickLaunch bar, the icon or menu entry stays "marked" - but nothing
ever happens! It's only after what appears as a "minute's silence" of some
20-40 sec. that the program opens up as usual - no error messages, no event
mgr entries.
Interestingly, the program that I was working with when I tried to start
another one works continues to work alright during that period of time. I
can also access the "windows security" popup by pressing CTRL-ALT-DEL during
that 20-40 sec., but when I try to start the Task Manager I get the exact
same problem. And - like I said: After this "break", all programs I clicked
on pop up and start running as if nothing ever happened.
The problem seems to occur less frequent when the machine has just been
rebooted a while ago, and it seems to become more frequent when the machine
has been running for quite some hours.
Any hint/help is greatly appreciated.
Thanks a lot in advance!!
cheers,
Markus Grein