eriko :
RESPONSE>
Horse ***.
What does the physical makeup of the hard disk make to the problem?
And even if an 'entry-level' cpu is present, does it not choose to start B Ops 2 because of that?
I"m running 3920XM, twin SSDs in RAID0, and 16GB of 1866MHz RAM, so tell me why I can't also find any matches to join?
BTW, as network engineer, I can tell you there is nothing wrong my connection...
Please switch off your PC, go out into the street and give it to the first person you see....
Wow, I'll do that but first, let me explain my logic...to you Mr Engineer (I'm also a computer engineer, a professional programmer, and a consultant...if wanna go into a "Title" war)...
You may have skipped the little part where I say "Your problem should be fixed now... *** ...
If you're still experiencing this issue..."
There are several factors to consider here.
1 - Loading time caused by "slow" reads from hard drive, which causes the host to kick player for inactivity (this would be both a hardware and software issue). Hardware being the read/load time is too slow for the host and therefor getting the boot; Software: the way Treyarch programmed it's time delay before host kicks "inactive" players.
2 - Connectivity/bandwith: If the map loads right away but he gets booted out (after map is loaded), then he's not "connecting" to the host. Could be his internet connection or other factors such as Firewall or port blocks from ISP.
3 - User's settings: Treyarch has a criteria setting for the type of "NAD" or games where the user may have chosen only "very good" or surrounding games. By selecting that option, your game will refuse to connect to hosts that aren't in your neighborhood or with good enough connection. Changing that setting will obviously change the amount of games it finds.
So, I'm assuming his problem's fixed now (most likely the code related to host & clients needed to be tweaked by Treyarch).