[Bold_Fortune]

jstangroome, on Mar 5 2006, 13:19, said:

I think that rather than looking at a way to hide or kill the SRH icon we should be questioning why it only shows it for particular hardware.
- Jason

What he said.

[+spenser.d]

I'm not sure that it can be removed...I would just go into taskbar customizations and choose always hide...then you never see it anyhow.

-Spenser

[Slimy]

I don't have mine anymore, go figure, I believe I installed some driver that I didn't have before. I'm not complaining though

[jstangroome]

I have done some research. The SRH icon is getting information from the registry under the key HKLM\SYSTEM\ControlSetxxx\Enum\. For my Matshu****a DVD drive there are keys under IDE\Matsu****a\Modelxxxx\. The particular value that is relevant is the Capabilities DWORD which contains several flags ORed together. The value 2 means Eject Supported (eject hardware not media) and the value 4 means Removable so my Matsu****a has 6 in the Capabilities field.

I tried changing the permissions on this registry key and changing the Capabilities to zero but after a reboot the value had reverted back to 6 and the SRH icon was still there. I'm guessing these registry keys are just a cache for the real data that is coming from some other file or is being reported directly by the driver itself.

Guess I'll have to poke around some more.

- Jason

[DigeratiPrime]

not that thing again
http://www.msfn.org/...pic=34987&st=20

Also you can create a shortcut to open the Dialog box Without using the Tray Icon.
Just create a shortcut to:
%windir%\System32\RUNDLL32.EXE shell32.dll,Control_RunDLL hotplug.dll

[molitar]

Please re-up HideSRHi.zip the one on here is corrupt and I had a major HD crash lost my entire C drive and getting everything reinstalled that I do have. But I can't find another copy of HideSRHi.exe at all.

[Slimy]

^ Unnecessary.
DigeratiPrime's post (#35) in the thread linked by him above says:

Quote

Just go into the System32 folder and rename batmeter.dll to batmeter.bak

[Colin-uk]

slimy, on Jun 30 2006, 18:43, said:

^ Unnecessary.
DigeratiPrime's post (#35) in the thread linked by him above says:

Further down the thread it also says, that this method also remove the sound icon from the tray, so if you dont mind loosing that too, then use this method




im in the same situation looking for a solution, atm im currently running HideSRHI.exe manually after login

[Nevermind2006]

Thanks ALOT, man!!

I spent 2 days digging Inet trying to find SELECTIVE fix for SRH problem - just to disable SRH for SOME of my SATA drives (need nForce drivers to make RAID working). Unfortunately, my raid is not where Windows boots from, so it just let to remove any of raid disks on the fly. It's BAD in my case, 'cose dumb users can easily crash raid in this way And hiding SRH icon is not a solution for me - i need it to remove other devices.

So my idea is (based on your research):

1. Change permissions to registry key you mentioned allowing write "Capabilities" value
2. Make small .bat file setting desired "Capabilities" and put it to startup

In this way I got normal SRH icon with NO SATA RAID DISK in it!!! Just happy now )

Cheers!

jstangroome, on Mar 6 2006, 04:21, said:

I have done some research. The SRH icon is getting information from the registry under the key HKLM\SYSTEM\ControlSetxxx\Enum\. For my Matshu****a DVD drive there are keys under IDE\Matsu****a\Modelxxxx\. The particular value that is relevant is the Capabilities DWORD which contains several flags ORed together. The value 2 means Eject Supported (eject hardware not media) and the value 4 means Removable so my Matsu****a has 6 in the Capabilities field.

I tried changing the permissions on this registry key and changing the Capabilities to zero but after a reboot the value had reverted back to 6 and the SRH icon was still there. I'm guessing these registry keys are just a cache for the real data that is coming from some other file or is being reported directly by the driver itself.

Guess I'll have to poke around some more.

- Jason

[Blazkowicz]

the hideSRHI.exe method sucks. my safely remove hardware icon is here for the USB wifi key (which I don't plan to ever unplug for the incoming monthes). hideSHRI launches at startup, displays some annoying error message ; then later my network connection and remove icon show up and stay there.

that's how it is for me
so, I did the replace stobject.dll with dud.exe : safely remove hardware goes away, along with task manager's CPU meter and wireless connection status. CPU meter is not a problem, as long as my task manager is always running in the background (it's run minimized at startup). wifi connection was useful (it's an adhoc network) but I can live without it.

it's really nice to have only two useful tray icons at launch (and one more when I launch Gaim)

[Trong]

So you could have just unplugged it and hid the wireless connection icon... You, my friend, make things too complicated. And yes, you can have a wireless connection RUNNING without the icon.

[Blazkowicz]

complicate life to simplify it, I often do that.
but I'm the kind of guy to think editing a few files and replacing dll is rather simple afterall.

I know about the "Show icon in notification area when connected" checkbox, but windows doesn't seem to care about it and this was not what I was after.

[Blazkowicz]

to quickly know about the connection status when you no longer have the icons : I remembered there's a network tab in task manager . add "bytes sent " and "bytes received" columns (view menu) and you're set.

[savesheep]

I found a fix for it.

Its because they are SATA drives. (atleast for me they are.) Sata are actually removable devices, so we have to tell windows not to allow them to be removable.

Go here in the registry:
HKLM\SYSTEM\CurrentControlSet\Services\nvata - 32bit
HKLM\SYSTEM\CurrentControlSet\Services\nvata64 - 64bit

and create a DWORD value called DisableRemovable with value 1.

Restart and you're good to go!

[slippery]

For the life of me I cannot understand why theres so many people making a mountain out of a mole hill. The problem lies in the drivers installed from the mobo setup disc. Go to "add/remove" and uninstall the ide drivers loaded by the setup disc, and let windows use its own set of device drivers to handle it. This is so old its not funny, I researched this years ago and found this fix. No problems whatsoever afterwards, honest.