Recent content by Sebastianem

You've got to let [H] know what hardware you're dealing with. Wired or wireless. If wireless, what are NIC are you running and what is your WAP maker/model? It's a bad deal that your connection drops out like that as I've never had an issue like this one. Help [H] help you!

As an owner of a first-gen M11x, I wondered if my fan was doing its thing, so here's what I found and it verified my fan was operational: http://www.alienwarearena.com/forums/topic/8836/hardware/-guide-unofficial-aw-fan-control-/ I then looked around and the fan can be found in a few places, to...

It sounds like a fantastic build for your purposes. It's a similar build I've done for a customer and It's worked for him with nary a hiccup!

Is it possible to connect it to your wired network? All of my devices can access my HP Photosmart 7500 connected via a wired connection either wireless/wired as they are all in the same subnet. If not, go with klank's suggestion.

Since you've got two PCIe x1 cards to use, I suggest what DeChache thought although with a small change. Install the USB 3.0 card in the black PCIe x16 slot and the SB in the first PCIe x1. The USB 3.0 card is fairly small and *shouldn't* interrupt your airflow to the 6870 too bad, if at all...

According to the manual (page 2-21), the first PCIx16 (blue) always runs at x16. The second PCIe x16 slot (black) runs at x4/x2 to allow your 2 x1 slots to function. If SLI/XFire setups are used, the remaining PCIe x1 slots are disabled. Why not install the SB card in PCIEX1_1 (the first PCIe...

If the card is installed in the first x16 slot on the MB it *should* be fine. I'm at a loss! I'm really hoping that another [H] member has a clue for this issue. I do know that until drivers are installed the Device Manager will name the card "Generic VGA". Are you overclocking? That has been...

I've never seen this problem, but let's go ahead and start with the standards: BIOS, all drivers, and Windows is fully updated. Ensure BIOS is set to stock clocks. Hope that points you in a direction because I would be ALL kinds of mad if that happened to me!

No problem! Glad you were able to get back up and running.

Wow. I should spell check before I post :D

Alright, here's what I recommend ([H]'ers, please add to with your experiences): Let's assume a standard Class C address space (192.168.1.0 / 255.255.255.0) One router with a repeater (Verizon and WRT parts) The Verizon part has an admin IP of 192.168.1.1 and the repeater could be 192.168.1.2...

Your DDWRT is not a router any longer with your topology. It's a switch. The exit interface would be the wireless AP on the DDWRT as it's a repeater. Anything connected to it MUST go through the wireless to get to your Verizon part. It can get awkward to configure it. I had a hell of a time...

Which router has DHCP? Only one of the routers can be "in charge". Also ensure that the other router has its exit interface pointing at the Verizon router and that NAT is only available on the Verizon part. Your WRT is really acting only as a switch at this point.

It has been stated that Intel would go BGA for 'mainstream' boards but still produce and support sockets for the high-end boards.

As an aside, Forceman may have already said what I'm thinking.