Everything, Everything

2024: J F M A M J J A S O N
2023: J F M A M J J A S O N D
2022: J F M A M J J A S O N D
2021: J F M A M J J A S O N D
2020: J F M A M J J A S O N D
2019: J F M A M J J A S O N D
2018: J F M A M J J A S O N D
2017: J F M A M J J A S O N D
2016: J F M A M J J A S O N D
2015: J F M A M J J A S O N D
2014: J F M A M J J A S O N D
2013: J F M A M J J A S O N D
2012: J F M A M J J A S O N D
2011: J F M A M J J A S O N D
2010: J F M A M J J A S O N D
2009: J F M A M J J A S O N D
2008: J F M A M J J A S O N D
2007: J F M A M J J A S O N D
2006: J F M A M J J A S O N D
2005: J F M A M J J A S O N D
2004: J F M A M J J A S O N D
Damn Thank You Netgear
Tuesday 2nd December, 2008 09:43 Comments: 4
My Netgear wireless card supports Vista as of the version 2.0 drivers. They claim to support Vista x86 and x64. Given that Server 2008 is practically identical to Vista x64 SP1 (same codebase, same build number), why doesn't my wireless card work on 2008? It seems to crash due to a missing DLL, and after copying it across from the x86 machine to the right location for x64 I no longer get the crashes, but it doesn't launch the wizard, and although the card now uses a Marvell driver (I think it's the correct one) it's unable to see any networks to connect to. I'm wondering if they've taken out wireless support for Server 2008? This would be a pain, as it means I'll probably have to run a cable down the stairs (which Cheryl isn't keen on) until we put some holes in walls to wire the house up (which probably won't happen anytime soon). So I might have to turn the fileserver off :( (unless I can do something clever with the wireless card and my PC, but that might mean leaving 3 computers on all day).

In better news, at least both arrays were fine after I turned on the computer. Considering how I rewired, moved disks and transported it from my flat to its new home, I'm a bit surprised it's okay. The PSU fans are definitely knackered though, so I'll order a new PSU today. The hard disks are a little noisy too, but there's not much more I can do about that (I've put a towel under the wheels of the server to dampen the vibration).

EDIT: Updated title, it turns out Netgear's drivers are fine. I'm impressed, a wireless card that works fine with Windows Server 2008 x64!
Avatar Fab - Tuesday 2nd December, 2008 10:15
Why not use homeplug? If you pay for the expensive one, you don't even get much of a performance hit on the transfer speeds as opposed to using cable. Either way it is meant to be faster than the wireless.
Avatar Robert - Tuesday 2nd December, 2008 10:27
I'd need to work out the rings first, as it might not be possible. The issue is I'd want to connect the sockets on the left hand side of the house on the ground floor with some sockets near the right hand side of the house on the first floor.

Looking at the fuse box, I have separate switches for \"Up Sockets\" \"Down Sockets\" and \"Sockets\" so I get the impression I have a ring for each floor.
Avatar Fab - Tuesday 2nd December, 2008 16:29
Get yer drill out! :p
Avatar Robert - Tuesday 2nd December, 2008 19:36
Even better/easier, I installed the \"Wireless LAN Service\" feature and then everything works fine. The Netgear setup program no longer crashes, and I can see and connect to my wireless access point. The cable down the stairs has now gone! It's not as fast, but it should be fast enough to handle DNS requests and the DC hub.
© Robert Nicholls 2002-2024
The views and opinions expressed on this site do not represent the views of my employer.
HTML5 / CSS3