Buy your mobo's locally. I quit buying mobo's thru the Net a few years ago for just that reason. Mobo makers give crappy support. So I found a local store owned by two brothers and they get all my mobo business. If they don't stock it, they'll order it. And their service is great. Sure, I pay a little more, but it is well worth it. How much is peace of mind worth to you?;)
You're not alone. @home is my only choice for high speed Internet access here in rural Tennessee (near Nashville), and their Tech Support is AWFUL. They screwed up some DNS maintenance back in February and knocked me off for a few days. When I called Tech Support, they assumed it HAD to be a problem on my end.:( Of course, no amount of twiddling my PC did any good. My service just suddenly started working the next day - no phone call or email from them to explain or apologize. Networking is not my gig, but discussions with co-workers after the fact confirmed the problem was @home. And I've had other problems with @home. This is just the most recent one. Their main problem seems to be they are so big and disorganized and bureaucratic.
Slashdot Mirror
Buy your mobo's locally. I quit buying mobo's thru the Net a few years ago for just that reason. Mobo makers give crappy support. So I found a local store owned by two brothers and they get all my mobo business. If they don't stock it, they'll order it. And their service is great. Sure, I pay a little more, but it is well worth it. How much is peace of mind worth to you? ;)
You're not alone. @home is my only choice for high speed Internet access here in rural Tennessee (near Nashville), and their Tech Support is AWFUL. They screwed up some DNS maintenance back in February and knocked me off for a few days. When I called Tech Support, they assumed it HAD to be a problem on my end. :( Of course, no amount of twiddling my PC did any good. My service just suddenly started working the next day - no phone call or email from them to explain or apologize. Networking is not my gig, but discussions with co-workers after the fact confirmed the problem was @home. And I've had other problems with @home. This is just the most recent one. Their main problem seems to be they are so big and disorganized and bureaucratic.