DM3Z Advice Needed for weak wireless signal

I have gone through some very frustrating customer support with HP so far trying to resolve my issue with weak wireless signal with no resolution.

Configuration:
AMD Turion X2 L625
4GB
ATI Switchable 3200/4350
320 Gb hard drive
Wireless N Atheros
Windows 7 Home 64-bit

Issue:

- Over a 2 weak period, my wireless signal went from 5 bars to 1-3 bars with the internet cutting off occasionally when the signal is only 1 bar strong.
Note: The problem did not occur for the previous 9 months. Other computers placed at the same location get full signal strength. Also note that I universally get weak signal with any wireless networks - at home, at school etc.

HP Support suggested:

- Upgrading to the newest wireless driver => Issue was not resolved.
- Rolling back the wireless driver upgrade => Issue was not resolved.
- Restarting the router (done via remote connection) => Issue was not resolved.
- Increasing buffer size for the wireless card (done via remote connection) => Issue was not resolved
- Restoring the operating system to 2 weeks prior to when the problem happened. => Issue was not resolved.
- Doing a complete Windows 7 factory condition reset => Issue was not resolved.
- They took the computer in for "repairs", and instead of trying to fix the problem, they reinstalled Windows 7 to factory conditions - wiping all my data in the process (fortunately, I have backup data) => Issue was not resolved.
- They sent me a wireless replacement card => Issue was not resolved.
- They requested that I reinstall Windows 7 to resolve the issue. At this point, I have told them that if really needed I will do it, but I do not think that it will solve the issue based on prior experience.

I have spent more than 20 hours with them on technical support. The computer was gone for 10 days despite the promised 3-5 day turn around time. I have never needed technical support before this laptop but so far it has been extremely frustrating. My patience is being tested to the limits because with each call I get a new technician, who do not fully read the case file associated with my case. I have to repeat myself again to prevent going through the above steps AGAIN!!! They promise to call back, then I do not get phone calls. I have to call them back, and the above procedure starts again.

I am writing here to find out if anyone had similar problems? If so what was the problem? What advice you can give me to get this issue resolved?

 

I have an ultimate solution, though you may not like it.

But it truly is the ultimate solution.

Amazon.com: 1000mW 1W 802.11g/n High Gain USB Wireless G / N Long-Rang WiFi Network Adapter - Dongle With Original Alfa 5dBi and 9dBi Rubber Antenna *Strongest on the Market*: Electronics

 

can you get them to replace the entire mobo under warranty? that's is probably the only way to fix it at this point

it could also be something weird like the antennas, but that is very unlikely...

 

All i can think of is the pigtail antennas could be frayed.

 

What about sending it in?

 

Actually, I did send it in once. HP technical support seems to think that all problems are solved by a reinstall of Windows 7. I am very reluctant (but not opposed to send it in again) because they might just do the same thing over again with no result.

 

In an ongoing story, I called last Friday. For the second time a reinstall was suggested to solve the problem. I demanded to speak to a case manager. The customer service representative said there was nothing further he could do. He put in a request for a case manager, and said that the case manager will take care of my case and that he would call Monday.

Today is Tuesday. No phone call has been received.

It looks like I will have to call them again.

 

To document my experience with HP's technical support further, after a full week, there is still no call back. I had to call in a third time. The service representative claimed that there was a problem with the phone number. No case manager was available. A call back was scheduled. I am continuing the waiting game. The issue has still not been resolved.