I'm having a few issues with Wc3 randomly wanting to drop me while I'm on Bnet. It only happens on my main computer, but doesn't happen when I'm playing on my laptop. I'm running Windows 7 on both of them.
Here are a few of the problems that arise:

1. Sometimes it works fine for a few games, other times it wants to drop me 30 seconds after I log onto bnet.
2. This is where it gets strange. If I get the "Press to Disconnect" box and I alt-tab, then the game runs fine in the background. How do I know this? Because if alt-tab for 5 minutes, and tab back in, I haven't been dropped yet, and for a split second or two the game works fine. Also, such as in a TD, the waves will have progressed. So if it had the box first appear at wave 3, but then I alt tab, when I tab back in it may be on wave 10. However, the box comes back after about half a second once I have tabbed back in.
3. Sometimes if I alt-tab when it's having issues it will go to a black screen and my computer will pretty much become unresponsive. The only way to fix this is to press the reset button on the computer.

Can anyone think of what the issues may be?
I don't think it's my internet connection, though I'm not sure. Games like L4D2 and TF2 seem to work fine. I don't think it's my router since my laptop doesn't seem to have the same issues. (However, my router has been kinda screwy the past few months. But like I said, other games seem to be fine.) I have windows completely updated, and I have all my drivers updated etc. Also, this is practically a clean install of windows and Wc3. So while it may seem like it could be a software issue, I don't think that's it either. This is because wc3 was doing similar things before I reinstalled windows and wc3.

Comp specs:
OS: Windows 7 64-bit
MB: Asus P5K-E wifi-ap
CPU: Intel Core 2 Duo E6700 2.66GHz
Video Card: Radeon HD4870
HDD: Two 160GB Raid-0
Memory: 2GB DDR2

Solutions I have tried:
1. Tried using -opengl mode and compatibility mode with Windows XP Service Pack 2
2. Tried reinstalling Wc3

Solutions that semi-work:
1. If I run Wc3 in -windowed mode, then everything works fine. It connects to Battlenet correctly etc. However, I don't like playing in -windowed mode; I would prefer a different solution.

Any suggestions?

EDIT: Someone suggested I delete all .mpq files in my wc3 folder. I tried this, but when launching the game it asks me to insert a disc. I don't have a disc, I downloaded the installer from Battlenet.

---

Q u o t e:

EDIT: Someone suggested I delete all .mpq files in my wc3 folder. I tried this, but when launching the game it asks me to insert a disc. I don't have a disc, I downloaded the installer from Battlenet.

---

Did you restart your computer?

That didn't work either. Now I think it may have IP banned me or something for trying to connect too many times. The IP bans for too many connection attempts only lasts about 30 minutes, right?

---

Q u o t e:


Did you run the repair utility after you deleted the files?

---

Where is that located? After I deleted the files, I tried to run wc3. I was told that it would run the repair utility when I tried to launch Wc3. This didn't happen, however, and instead it asks me to insert my Wc3 Disc. I don't have a Wc3 disc, I downloaded the installer from Battle.net.

About the raid-0:
I have actually noticed a non-negligible amount of performance increase by running it in Raid-0 (I did compare results by running windows and my games on a single drive and then reinstalling in Raid-0, though I didn't use timers or anything, so my results aren't concrete).

What a mystery

Ok as of this posting I may have figured it out, though I still don't understand it. My monitor does 1920x1080 resolution. Because Wc3 seems to work in windowed mode, I decided to mess around with the Video settings. If I try running Wc3 in 1600x1200 or 1400x1050, it won't connect to Bnet. However, it seems to run fine at 1280x1024 or lower resolutions. I'm not sure if this is actually true though, because like I have said it seems to sometimes work and sometimes doesn't. This may be just one of those times that it happens to work, so I'll have to stay logged in for a while to see if it kicks me at all. If the resolution does happen to be the issue, would anyone happen to know what may cause that? Like I said, I run plenty of other games in 1920x1080 resolution etc.

---

Q u o t e:
anecdotal, and selective perception

also there's no way your monitor resolution is affecting your ability to connect to bnet

---

@the first part:
Not necessarily. I have noticed shorter load times. Especially since they have the bots that can tell you how long it took you to load, and compare it to everyone else. I'm almost always the fastest person to load, even faster than people with a slightly better single HDD. I'm not saying that you're wrong, it very well could be selective perception. There's plenty of literature around the internet that says Raid-0 does help, and plenty that says it doesn't. Let me ask you this: Are you one of those people who think defragmenting a Raid-0 array is a bad idea?

@the second part:
I have no idea, I still haven't dropped from bnet yet. It could just be an extended period of I-got-lucky, which does happen sometimes. However, given the length of time it has still worked, I tend to think the resolution may have been the issue.

Let me elaborate further:
If I set the resolution to 1600x1200 and try to connect to bnet, it will not connect. I can press the "Connect to Battlenet" button 50 times in a row, and it won't connect. However, if I drop the resolution down to the lower res., it does work. I can then press the "Connect to Battlenet" button another 50 times, all of which work. If I raise the resolution again, it stops connecting. I admit, this could be a coincidence, which is why I am on battlenet right now trying to see if it'll drop me. (usually when I get lucky and it works, I get to stay on battlenet for a total of 10 minutes before I get disconnected).
What about running it in -windowed mode? Would you say that -windowed mode cannot possibly have an effect on whether or not I can log into Battlenet?
Because I can assure you, -windowed mode DOES fix it. It has never dropped me while I'm in windowed mode. If I go back to fullscreen, even if it was working perfectly fine in -windowed mode for the past 3 hours, chances are it won't connect.

I'm starting to come to the conclusion that you're trolling. If this is the case, I'd like to ask you to stop posting in this thread. If I'm mistaken then I apologize, but you need to keep an open mind. I've seen far stranger bugs/glitches etc. throughout the years on many different programs to rule-out the possibility that somehow Wc3 won't connect to battlenet because of my resolution.

1. I do understand computers. I'm currently a Sophomore, almost a junior, in college majoring in Software Engineering and Computational Mathematics. I'm also part-owner in a computer building and repair business. (Yes, I understand that is mostly software related, but that Raid-0 is hardware. I also admit that I don't know as much about hardware as I could, but that isn't to say I don't know a great deal about hardware).

2. Well, at least you got something right.

3. I was thinking of testing my ram.

Again, as of this post I still haven't dropped from Wc3. I did change my resolution again, however. I set it to my native 1920x1080 resolution, and it seems to be working fine. And yes, 1600x1200 still doesn't allow me to connect to Bnet.

Yeah... They were trolling... I hope you backed up your MPQ files. The game needs those to run. If you didn't, you're going to need to reinstall.

---

Q u o t e:
Yeah... They were trolling... I hope you backed up your MPQ files. The game needs those to run. If you didn't, you're going to need to reinstall.

---

Yeah, it's fine. I made sure to back them up since I didn't think the mpq files would be relevant. I did delete the bncache.dat, but that didn't fix the problem. As it stands, I seem to have fixed it by changing the game resolution. Why this has worked, I'm not sure.

Mmkay. Can you tell us more about your computer? The Direct X Diagnostic tool can display more system information.

Click on Start > Run > type in dxdiag
Hit Enter or Click OK.
If there is a Yes or No question, click Yes.

On the first tab, the System Tab, please post the following:

Operating System

System Manufacturer

System Model

Processor

Memory

Direct X Version

Click on the Display Tab

We need to know these items:

Name

Manufacturer

Chip Type

On the right side, in the Drivers section, we need to know:

Version

Date

Operating System: Windows 7 Professional 64-bit (6.1, Build 7600) (7600.win7_gdr.100226-1909)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer (Built the Computer myself)
System Model: P5K-E
BIOS: BIOS Date: 03/21/08 09:56:22 Ver: 08.00.12
Processor: Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz (2 CPUs), ~2.7GHz
Memory: 2048MB RAM
Available OS Memory: 2048MB RAM
DirectX Version: DirectX 11



Card name: ATI Radeon HD 4800 Series
Manufacturer: ATI Technologies Inc.
Chip type: ATI display adapter (0x9440)
DAC type: Internal DAC(400MHz)
Display Memory: 1274 MB
Dedicated Memory: 506 MB
Shared Memory: 767 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: DVI
Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Driver Version: 8.732.0.0
DDI Version: 10.1
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 5/4/2010 22:18:36, 584704 bytes

I'm not entirely sure what the rules are about double posting here, but I decided to make a new post in case you have already read my previous post and decided not to respond.

I did some searching around the internet for other cases of my problem (I had found a few before I created this thread, but none of them had a solution), and I came across this thread:
http://forums.battle.net/thread.html?topicId=18031081226&postId=182744233354&sid=3000#0
(Sadly I didn't find that thread before I found the solution myself. Would have saved me a lot of time.)
Apparently others have found that changing their resolution seems to fix the problem too. I'm not sure exactly why the resolution is an issue or who is capable of fixing the problem. (Though, it seems to me like it's something Blizzard could patch.) I would suggest that you at least add it to a list of possible problems and solutions etc., and suggest it to anyone you may come across that has a similar issue.