- Jun 14, 2005
- 2
- 0
- 0
Hi All,
I have just recently upgraded my PC and I now have the following setup:-
Athlon 64 3700+
A8N-SLI Deluxe MB
512mb RAM (2x256)
X700 Pro PCIe
1x 36gb Western Digital Raptor SATA HD (plugged into NV SATA Ports)
1x Maxtor 120gb SATA (plugged into NV SATA Ports)
2x120gb Western Digital SATA (plugged into Silicon SATA Ports using RAID)
I installed Windows XP Sp2, all the updates etc etc and now in the bottom left hand corner of the screen, on the task bar next to the time, I have a "Safely Remove Hardware" icon which is telling me I can remove the 36gb Raptor and the Maxtor drive. These are the drives which are plugged into the Nvidia SATA ports and are non raid. Is there a way to stop this icon from appearing.. have I triggered something in the bios by mistake perhaps..
It's very annoying when you use a memory key and you click safely remove and choose your C or D
Drive!!!
Any help would be appreciated!
Thanks
Ian
ps
Apologies if I have posted this in the wrong forum.. as I only saw this problem since purchasing my new MB, I assumed it was MB related in some way.
I have just recently upgraded my PC and I now have the following setup:-
Athlon 64 3700+
A8N-SLI Deluxe MB
512mb RAM (2x256)
X700 Pro PCIe
1x 36gb Western Digital Raptor SATA HD (plugged into NV SATA Ports)
1x Maxtor 120gb SATA (plugged into NV SATA Ports)
2x120gb Western Digital SATA (plugged into Silicon SATA Ports using RAID)
I installed Windows XP Sp2, all the updates etc etc and now in the bottom left hand corner of the screen, on the task bar next to the time, I have a "Safely Remove Hardware" icon which is telling me I can remove the 36gb Raptor and the Maxtor drive. These are the drives which are plugged into the Nvidia SATA ports and are non raid. Is there a way to stop this icon from appearing.. have I triggered something in the bios by mistake perhaps..
It's very annoying when you use a memory key and you click safely remove and choose your C or D
Any help would be appreciated!
Thanks
Ian
ps
Apologies if I have posted this in the wrong forum.. as I only saw this problem since purchasing my new MB, I assumed it was MB related in some way.
