Can someone please explain what Microsoft means in this article?

http://support.microsoft.com/?scid=3...PA=3D1&SD=3DH=
SCH

It says this issue can happen when, "This issue can occur if you applied =
the hotfix that is described in
the following Microsoft Knowledge Base article: 260067 Windows Stops =
Responding During=20
Shutdown with Mapped Drives"

The article they point to is he

http://support.microsoft.com/?scid=3...PA=3D1&SD=3DH=
SCH

Well I have this TaskBar Screen Saver Ghost Icon issue and I have not =
applied this hotfix 280722. It
seems to have started when I mapped some other machines to Windows 98 =
using Microsoft Sharing
Files and Printers.and Microsoft Client Networks. But I do NOT have =
this notorious shutdown issue
in Windows 98.

Now the first article says, "I can get these ghost icons on the taskbar =
which say 'Screen Saver' if I
apply the shutdown issue hotfix." That's all well and good that may be =
sufficient but I can tell you it is
NOT necessary. I have the issue of the ghost icons Screen Saver in the =
taskbar and I have NOT applied this hotfix. But the article goes on, "

RESOLUTION
To resolve this issue, remove the hotfix. To do this, follow these =
steps:1. Click Start, click Find, and then click Files or Folders.=20
2. In the Named box, type "260067.inf" (without the quotation marks), =
and then click Find now.=20
3. Right-click the file name, click Install, and then follow the =
instructions. "

and here is where I get the heeby-jeebies. For it says to "remove" the =
hotfix by right-clicking on the inf
and choose "Install."

Now I thought there was a difference between Remove aka Uninstall and =
Install aka Not Remove???=20
So which is it? Do we install the hotfix that causes the problem to =
stop the problem or do we uninstall
the hotfix that causes the problem to keep the problem or do we keep the =
problem by installing the
hotfix which is suppose to fix a problem or do we have a problem and =
say, Microsoft WHAT ARE
YOU TALKING ABOUT?=20

--=20
George Hester
_________________________________

The article does not suggest that this is the only cause of this problem. If
you have not installed the hotfix, then you can assume it's not the cause.
There are a number of other possible causes. See, for instance:
http://support.microsoft.com/?kbid=214655
PRB: Closed Application Appears As Gray Box in Taskbar

Also, there are other updates that can create the same result, including the
May 22, 2000 Critical Update or the Windows 98 SE 1394 Storage Supplement

If you do have the 260067.INF file then to uninstall the hotfix you should
right-click the file and choose the install option. This option is used to
both install and uninstall the hotfix. If this seems counterintuitive, just
think of it as 'Process' or 'Execute' rather than 'Install'.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"George Hester" wrote in message
...
http://support.microsoft.com/?scid=k...1&PA=1&SD=HSCH

It says this issue can happen when, "This issue can occur if you applied the
hotfix that is described in
the following Microsoft Knowledge Base article: 260067 Windows Stops
Responding During
Shutdown with Mapped Drives"

The article they point to is he

http://support.microsoft.com/?scid=k...1&PA=1&SD=HSCH

Well I have this TaskBar Screen Saver Ghost Icon issue and I have not
applied this hotfix 280722. It
seems to have started when I mapped some other machines to Windows 98 using
Microsoft Sharing
Files and Printers.and Microsoft Client Networks. But I do NOT have this
notorious shutdown issue
in Windows 98.

Now the first article says, "I can get these ghost icons on the taskbar
which say 'Screen Saver' if I
apply the shutdown issue hotfix." That's all well and good that may be
sufficient but I can tell you it is
NOT necessary. I have the issue of the ghost icons Screen Saver in the
taskbar and I have NOT applied this hotfix. But the article goes on, "

RESOLUTION
To resolve this issue, remove the hotfix. To do this, follow these steps:1.
Click Start, click Find, and then click Files or Folders.
2. In the Named box, type "260067.inf" (without the quotation marks), and
then click Find now.
3. Right-click the file name, click Install, and then follow the
instructions. "

and here is where I get the heeby-jeebies. For it says to "remove" the
hotfix by right-clicking on the inf
and choose "Install."

Now I thought there was a difference between Remove aka Uninstall and
Install aka Not Remove???
So which is it? Do we install the hotfix that causes the problem to stop
the problem or do we uninstall
the hotfix that causes the problem to keep the problem or do we keep the
problem by installing the
hotfix which is suppose to fix a problem or do we have a problem and say,
Microsoft WHAT ARE
YOU TALKING ABOUT?

"George Hester" wrote in message ...
http://support.microsoft.com/?scid=k...FR=1&PA=1&SD=H
SCH

It says this issue can happen when, "This issue can occur if you applied
the hotfix that is described in
the following Microsoft Knowledge Base article: 260067 Windows Stops
Responding During
Shutdown with Mapped Drives"

The article they point to is he

http://support.microsoft.com/?scid=k...FR=1&PA=1&SD=H
SCH

Well I have this TaskBar Screen Saver Ghost Icon issue and I have not
applied this hotfix 280722. It
seems to have started when I mapped some other machines to Windows 98
using Microsoft Sharing
Files and Printers.and Microsoft Client Networks. But I do NOT have
this notorious shutdown issue
in Windows 98.

Now the first article says, "I can get these ghost icons on the taskbar
which say 'Screen Saver' if I
apply the shutdown issue hotfix." That's all well and good that may be
sufficient but I can tell you it is
NOT necessary. I have the issue of the ghost icons Screen Saver in the
taskbar and I have NOT applied this hotfix. But the article goes on, "

RESOLUTION
To resolve this issue, remove the hotfix. To do this, follow these
steps:1. Click Start, click Find, and then click Files or Folders.
2. In the Named box, type "260067.inf" (without the quotation marks),
and then click Find now.
3. Right-click the file name, click Install, and then follow the
instructions. "

and here is where I get the heeby-jeebies. For it says to "remove" the
hotfix by right-clicking on the inf
and choose "Install."

Now I thought there was a difference between Remove aka Uninstall and
Install aka Not Remove???
So which is it? Do we install the hotfix that causes the problem to
stop the problem or do we uninstall
the hotfix that causes the problem to keep the problem or do we keep the
problem by installing the
hotfix which is suppose to fix a problem or do we have a problem and
say, Microsoft WHAT ARE
YOU TALKING ABOUT?

Confusion understandable and certainly a line or two from MS on
the page outlining the removal advice a great oversight. But
if you will notice the inf file to right click and 'Install'
is named 260067un.inf, the 'un' part denoting that it has been
written such as to uninstall when the [DefaultInstall] section
is called. Add to that, the right click option is written to
only invoke the [DefaultInstall] section and a light can be
seen at the end of the tunnel and it's not the train.

And of course you wouldn't know about the 'un' part of the
inf file's name until you installed the update in the first
place, which is also somewhat confusing, no? The 260067un.inf
file is copied to the C:\WINDOWS\INF\QFE\W98.SE folder for
use in uninstalling the update. Which should also be in the
KB article.

Yes thanks Lee. Unfortunately I have not installed this update because =
I don't have the Shutdown issue. I also have the problem Ghost icon the =
article 260067 talks about EXACTLY. I am at a loss what to do with this =
issue and cannot determine when it started. All I know is it didn't =
happen; I got Microsoft Network File sharing going; now I have this =
problem

--=20
George Hester
_________________________________
"Lee" wrote in message =
om...
"George Hester" wrote in message =
...
=
http://support.microsoft.com/?scid=3...PA=3D1&SD=3DH=

SCH
=20
It says this issue can happen when, "This issue can occur if you =
applied=20
the hotfix that is described in
the following Microsoft Knowledge Base article: 260067 Windows Stops =

Responding During=20
Shutdown with Mapped Drives"
=20
The article they point to is he
=20
=
http://support.microsoft.com/?scid=3...PA=3D1&SD=3DH=

SCH
=20
Well I have this TaskBar Screen Saver Ghost Icon issue and I have =
not=20
applied this hotfix 280722. It
seems to have started when I mapped some other machines to Windows =
98=20
using Microsoft Sharing
Files and Printers.and Microsoft Client Networks. But I do NOT have =

this notorious shutdown issue
in Windows 98.
=20
Now the first article says, "I can get these ghost icons on the =
taskbar=20
which say 'Screen Saver' if I
apply the shutdown issue hotfix." That's all well and good that may =
be=20
sufficient but I can tell you it is
NOT necessary. I have the issue of the ghost icons Screen Saver in =
the=20
taskbar and I have NOT applied this hotfix. But the article goes =
on, "
=20
RESOLUTION
To resolve this issue, remove the hotfix. To do this, follow these=20
steps:1. Click Start, click Find, and then click Files or Folders.=20
2. In the Named box, type "260067.inf" (without the quotation =
marks),=20
and then click Find now.=20
3. Right-click the file name, click Install, and then follow the=20
instructions. "
=20
and here is where I get the heeby-jeebies. For it says to "remove" =
the=20
hotfix by right-clicking on the inf
and choose "Install."
=20
Now I thought there was a difference between Remove aka Uninstall =
and=20
Install aka Not Remove???=20
So which is it? Do we install the hotfix that causes the problem to =

stop the problem or do we uninstall
the hotfix that causes the problem to keep the problem or do we keep =
the=20
problem by installing the
hotfix which is suppose to fix a problem or do we have a problem and =

say, Microsoft WHAT ARE
YOU TALKING ABOUT?
=20
Confusion understandable and certainly a line or two from MS on
the page outlining the removal advice a great oversight. But
if you will notice the inf file to right click and 'Install'
is named 260067un.inf, the 'un' part denoting that it has been
written such as to uninstall when the [DefaultInstall] section
is called. Add to that, the right click option is written to
only invoke the [DefaultInstall] section and a light can be
seen at the end of the tunnel and it's not the train.
=20
And of course you wouldn't know about the 'un' part of the
inf file's name until you installed the update in the first
place, which is also somewhat confusing, no? The 260067un.inf
file is copied to the C:\WINDOWS\INF\QFE\W98.SE folder for
use in uninstalling the update. Which should also be in the
KB article.

"George Hester" wrote in message ...
Yes thanks Lee. Unfortunately I have not installed this update because
I don't have the Shutdown issue. I also have the problem Ghost icon the
article 260067 talks about EXACTLY. I am at a loss what to do with this
issue and cannot determine when it started. All I know is it didn't
happen; I got Microsoft Network File sharing going; now I have this
problem

--
George Hester


If instead you meant this article about the ghost you should know that
there is no solution other than to get code writer for the application
that causes the ghost to rewrite his garbage code such that it doesn't
do that. I have it too with an app that I can't even remember at the
moment and as I don't use it that much I don't really care about getting
somebody to rewrite their code. According to the article, Network File
Sharing is changing a view setting somewhere, maybe you can set it to
not do that? Or remove it and reinstall it? If that is under the
Network applet in the Control Panel, I would remove everything and
reboot. Then only add in the barest minimum required to get you what
you need there - sometimes works wonders.
http://support.microsoft.com/?kbid=214655

I'm sorry it was this issue I have exactly:

http://support.microsoft.com/?scid=3...PA=3D1&SD=3DH=
SCH

Icon is displayed on the Taskbar after closing the screen saver

Actually I just wiggle the mouse so that the screen saver stops. I get =
the ghost icon. I've tried many of the screen savers in Windows 98. =
They all do this. I am going through my Windows Update history and =
remove the updates that I can remove to see if I can put my finger on =
the update that caused this. I know it was one of them because prior to =
installing these updates I didn't have the issue.

--=20
George Hester
_________________________________
"Lee" wrote in message =
m...
"George Hester" wrote in message =
...
Yes thanks Lee. Unfortunately I have not installed this update =
because=20
I don't have the Shutdown issue. I also have the problem Ghost icon =
the=20
article 260067 talks about EXACTLY. I am at a loss what to do with =
this=20
issue and cannot determine when it started. All I know is it didn't =

happen; I got Microsoft Network File sharing going; now I have this=20
problem
=20
--=20
George Hester
=20
=20
If instead you meant this article about the ghost you should know that
there is no solution other than to get code writer for the application
that causes the ghost to rewrite his garbage code such that it doesn't
do that. I have it too with an app that I can't even remember at the
moment and as I don't use it that much I don't really care about =
getting
somebody to rewrite their code. According to the article, Network =
File
Sharing is changing a view setting somewhere, maybe you can set it to
not do that? Or remove it and reinstall it? If that is under the
Network applet in the Control Panel, I would remove everything and
reboot. Then only add in the barest minimum required to get you what
you need there - sometimes works wonders.
http://support.microsoft.com/?kbid=3D214655

There is only one screensavers worth using and it is called [None].
It turns the screen black, doesn't eat any resources and works as
advertised.
Delete all others and save some hard drive space.

"George Hester" wrote in message
...
I'm sorry it was this issue I have exactly:

http://support.microsoft.com/?scid=k...1&PA=1&SD=HSCH

Icon is displayed on the Taskbar after closing the screen saver

Actually I just wiggle the mouse so that the screen saver stops. I get the
ghost icon. I've tried many of the screen savers in Windows 98. They all
do this. I am going through my Windows Update history and remove the
updates that I can remove to see if I can put my finger on the update that
caused this. I know it was one of them because prior to installing these
updates I didn't have the issue.

--
George Hester
_________________________________
"Lee" wrote in message
m...
"George Hester" wrote in message
...
Yes thanks Lee. Unfortunately I have not installed this update because
I don't have the Shutdown issue. I also have the problem Ghost icon the
article 260067 talks about EXACTLY. I am at a loss what to do with this
issue and cannot determine when it started. All I know is it didn't
happen; I got Microsoft Network File sharing going; now I have this
problem

--
George Hester


If instead you meant this article about the ghost you should know that
there is no solution other than to get code writer for the application
that causes the ghost to rewrite his garbage code such that it doesn't
do that. I have it too with an app that I can't even remember at the
moment and as I don't use it that much I don't really care about getting
somebody to rewrite their code. According to the article, Network File
Sharing is changing a view setting somewhere, maybe you can set it to
not do that? Or remove it and reinstall it? If that is under the
Network applet in the Control Panel, I would remove everything and
reboot. Then only add in the barest minimum required to get you what
you need there - sometimes works wonders.
http://support.microsoft.com/?kbid=214655

That's one fix but not the one I was looking for. Thanks.

--=20
George Hester
_________________________________
"Bernie" wrote in message =
...
There is only one screensavers worth using and it is called [None].
It turns the screen black, doesn't eat any resources and works as
advertised.
Delete all others and save some hard drive space.
=20
"George Hester" wrote in message
...
I'm sorry it was this issue I have exactly:
=20
=
http://support.microsoft.com/?scid=3...PA=3D1&SD=3DH=
SCH
=20
Icon is displayed on the Taskbar after closing the screen saver
=20
Actually I just wiggle the mouse so that the screen saver stops. I =
get the
ghost icon. I've tried many of the screen savers in Windows 98. They =
all
do this. I am going through my Windows Update history and remove the
updates that I can remove to see if I can put my finger on the update =
that
caused this. I know it was one of them because prior to installing =
these
updates I didn't have the issue.
=20
--
George Hester
_________________________________
"Lee" wrote in message
m...
"George Hester" wrote in message
...
Yes thanks Lee. Unfortunately I have not installed this update =
because
I don't have the Shutdown issue. I also have the problem Ghost =
icon the
article 260067 talks about EXACTLY. I am at a loss what to do =
with this
issue and cannot determine when it started. All I know is it =
didn't
happen; I got Microsoft Network File sharing going; now I have =
this
problem

--
George Hester


If instead you meant this article about the ghost you should know =
that
there is no solution other than to get code writer for the =
application
that causes the ghost to rewrite his garbage code such that it =
doesn't
do that. I have it too with an app that I can't even remember at =
the
moment and as I don't use it that much I don't really care about =
getting
somebody to rewrite their code. According to the article, Network =
File
Sharing is changing a view setting somewhere, maybe you can set it =
to
not do that? Or remove it and reinstall it? If that is under the
Network applet in the Control Panel, I would remove everything and
reboot. Then only add in the barest minimum required to get you =
what
you need there - sometimes works wonders.
http://support.microsoft.com/?kbid=3D214655
=20
=20

This is a response from Rick Rogers aka "Nutcase" MS-MVP, now North of =
the border in XP land:
These "ghost" buttons are often cured by updating the video drivers. =
They began appearing around the release of IE5.0. Changing screensavers =
can often help as well.

Other possibilities include:
1) The Win98SE Mapped drives Shutdown update
2) The Win98SE 1394 Storage Supplement

If you have installed any of these updates and don't actually need them, =
you can try uninstalling them through the .inf's they placed on your =
system. They would be:
1) 260067un.inf
2) 242975un.inf

Also, another method to try is to delete this key from the registry and =
reboot:
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\Stuc=
kRects

NOTE Please use caution when working within the registry. Changes made =
here are generally immediate. Making the wrong change or carelessly =
changing/deleting keys can render your system unbootable. If you are =
unsure about any change, don't do it. Before you make any changes to the =
registry, know how to backup and restore the current one from a command =
prompt.

How to Manually Restore the Windows 98 Registry
http://support.microsoft.com/default...;EN-US;q221512

And in addition, a response by (glee) Glen Ventura MS-MVP:
Some programs are just poorly-written, and a fault in the code will =
cause this to occur.

--=20

Brian A.

Conflicts start where information lacks.
http://www.dts-l.org/goodpost.htm


"George Hester" wrote in message =
...
http://support.microsoft.com/?scid=3...PA=3D1&SD=3DH=
SCH

It says this issue can happen when, "This issue can occur if you applied =
the hotfix that is described in
the following Microsoft Knowledge Base article: 260067 Windows Stops =
Responding During=20
Shutdown with Mapped Drives"

The article they point to is he

http://support.microsoft.com/?scid=3...PA=3D1&SD=3DH=
SCH

Well I have this TaskBar Screen Saver Ghost Icon issue and I have not =
applied this hotfix 280722. It
seems to have started when I mapped some other machines to Windows 98 =
using Microsoft Sharing
Files and Printers.and Microsoft Client Networks. But I do NOT have =
this notorious shutdown issue
in Windows 98.

Now the first article says, "I can get these ghost icons on the taskbar =
which say 'Screen Saver' if I
apply the shutdown issue hotfix." That's all well and good that may be =
sufficient but I can tell you it is
NOT necessary. I have the issue of the ghost icons Screen Saver in the =
taskbar and I have NOT applied this hotfix. But the article goes on, "

RESOLUTION
To resolve this issue, remove the hotfix. To do this, follow these =
steps:1. Click Start, click Find, and then click Files or Folders.=20
2. In the Named box, type "260067.inf" (without the quotation marks), =
and then click Find now.=20
3. Right-click the file name, click Install, and then follow the =
instructions. "

and here is where I get the heeby-jeebies. For it says to "remove" the =
hotfix by right-clicking on the inf
and choose "Install."

Now I thought there was a difference between Remove aka Uninstall and =
Install aka Not Remove???=20
So which is it? Do we install the hotfix that causes the problem to =
stop the problem or do we uninstall
the hotfix that causes the problem to keep the problem or do we keep the =
problem by installing the
hotfix which is suppose to fix a problem or do we have a problem and =
say, Microsoft WHAT ARE
YOU TALKING ABOUT?=20

--=20
George Hester
_________________________________

Just because that is an exact description of your problem, doesn't mean that
the cause is the one that's listed there. It could be a badly written
screen saver, as Lee is suggesting. If it's a badly written screen saver
you cannot fix it without a re-write.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"George Hester" wrote in message
...
I'm sorry it was this issue I have exactly:

http://support.microsoft.com/?scid=k...1&PA=1&SD=HSCH

Icon is displayed on the Taskbar after closing the screen saver

Actually I just wiggle the mouse so that the screen saver stops. I get the
ghost icon. I've tried many of the screen savers in Windows 98. They all
do this. I am going through my Windows Update history and remove the
updates that I can remove to see if I can put my finger on the update that
caused this. I know it was one of them because prior to installing these
updates I didn't have the issue.