I think the point there is MSFT is telling you that you don't need bluetooth on a server right?
Bluetooth mouse. Sometimes, you have to work directly on the server. Not all of the servers are configured remotely. I'm sure there are some people wanting to sync data using a bluetooth device to their server too. It must not be very common, but so are bluetooth devices.I haven't been able to think up any uses for Bluetooth on a server. What are yours?
I haven't been able to think up any uses for Bluetooth on a server. What are yours?
Regardless, having the feature would be nice for you; I do understand that, but can also understand why it's not implemented.
Not to defend Microsoft, but that sounds like a crappy device driver to me. My reasoning ....
1: the card is the same one as he card in your R60.
It has the same Intel dual band wireless card in it
SP1 info for those that were holding out till SP1
http://windowsteamblog.com/blogs/wi...for-windows-7-and-windows-server-2008-r2.aspx
I decided to stay with the moveable drives. Cat 5 is giving me about 5-7 mb/sec. OK for most stuff.
If not, I can load it on to a removeable drive, move it, and solve the problem, in about 30 seconds...
A 1000 GT on even a 32bit/33MHz PCI bus should give you 90+MB/sec transfers. Of course once Windows has it's way with it it won't be that high but we are talking orders of magnitude here. For a potential investment of $34+shipping.
http://www.newegg.com/Product/Product.aspx?Item=N82E16833106123
You should only need the one for your PCI-X based machine, any mobo with PCI-E slots should have onboard gigabit Ethernet. That and a run of Cat 6 and you should be good to go.
Just an FYI, if you're doing GigE to GigE I don't think you need a special crossover cable. A normal CAT 5e or better should work fine.
I remember having serious smb performance issues when I first tested Vista with my server and I can't remember exactly why. I think it was related to security configuration and backwards compatibility with old versions of Windows and some config changes fixed it.