To summarize what the video says, Battle.net will be just like steam, with a friends list and invites. Your achievements will be new avatar pictures, how cool!!!! (not. unless you like pokemans). And you’ll pretty much need to be online, even if you are playing single player; the reasoning for this is that your stats and saved games will be stored with battle.net, that you’ll be able to talk with your firendslist, and that whatever points you earn will go toward a new avatar (basically a 128×128 gif).

In the past, Battle.net was presented as a multiplayer option off to the side, off of the main menu of Blizzard Entertainment titles. That is all changing. With the new Battle.net experience, the service and the game are now interwoven into one experience. Whether you are in single-player or multiplayer StarCraft II, you are always connected, and enjoy a bevy of new and enhanced functionality.

Battle.net and StarCraft II are designed to be seamlessly connected. That means even if you’re playing solo you will still view the latest news, receive game and content updates, and be able to see your friends’ status and chat with them. But this new interconnectivity between the game and the service goes even deeper than that. Now, each player will create a StarCraft II Battle.net character. This character serves as your single persistent identity across the service. Everything you do in the game — win/loss record, achievements, unlockable rewards, friends list, and more — will be saved to your character profile for you and your friends to see. Even your save game progress in the campaign can be synched to Battle.net. Say you upgrade your computer and re-install the game; once you connect to Battle.net, you can continue the campaign right where you left off. This is especially useful if you play on more than one computer, because all your data will be carried over for you via Battle.net.

UPDATE:

• 12/18/09): Patch Released:

Apparently missing the point, or facing an improbable time frame, pandemic has released the patch which still requires it to run under a single core…

If you are using Windows 7 you have to do this:

1.) Boot the game.
2.) Wait for the main menu to load, then press Ctrl-Alt-Delete.
3.) Select Start Task Manager.
4.) If the game is visible, press Alt-Tab, otherwise continue to the next step.
5.) Inside the Task Manager, go to the Processes tab.
6.) Find Saboteur.exe, right-click it, and select Set Affinity…
7.) De-select CPU 2 and CPU 3.
8.) Click OK.

In any case, grab the patch here, be sure to get the latest latest ATI drivers here,

• (12/11/09): Real patch is now in internal testing.

We are currently digging into the issue at hand & are working as fast as possible to find a solution. In some of our tests we have found one workaround that seems to allow users to run the game. Some have posted adjusting the affinity process via “Task Manager” but our fix truly puts the system in a 1 core mode and will allow you to run the game. Overall this is not a final fix, nor a perfectly stable fix, but it will allow you to run the game. This work around is entirely base upon CPU processing power & will possibly only work for certain systems.

Steps to turn off cores: (For Windows 7)
1.) Open MSCONFIG (You can open it by entering MSCONFIG in the search bar)
2.) Select the “Boot” tab
3.) Click on “Advanced Options”
4.) Check “Number of Processors”
5.) Select “1” from dropdown menu
6.) Click “Apply”
7.) Restart machine

Steps to turn off cores: (For Windows Vista)
1.) Open MSCONFIG – Start> Run > Type MSCONFIG
2.) Select the “BOOT.INI” tab
3.) Click on “Advanced Options…”
4.) Select the check box for /NUMPROC= set it to 1 & click “OK”
5.) Click “Apply”
6.) Restart machine

Thanks, GameGuru

Opinion: EA’s business strategy seems to depend on pushing release dates. Game developers don’t have the time they need to smooth out bugs and finish testing, and consumers are paying for it by buying an incomplete product.

Check the original post for further information:

http://www.modernwarfare2.com/forum/viewtopic.php?f=24&t=181646

Not only unsupported, Mobility Radeons are further crippled by their drivers. Laptop distributors (HP, Dell, Lenovo, etc) limit the clocks on the bundled video cards and restrict access to the GPU BIOS. There are a number of logical reasons behind this, namely warranty overheating issues.

There are a number of ways to work around these restrictions, the best likely being a BIOS mod, as it would allow fluent clock changing through ATT, or other programs. However, some GPUs have their BIOS read and write protected, making the process rather futile.

Another, simpler, method is using a specific driver version. 8.9 and 8.10 Catalysts allow you to overclock when used in conjunction with AMD GPU Clock Tool.

So before we begin, these are the ingredients you want:

*optional components

To begin, uninstall your current drivers. If you have the Catalyst bundle installed, go to control panel, remove programs, ATI uninstall – remove CCC, Install manager, and Display Driver, reboot.

If you are running Windows 7, load up DSEO and enable Testing Mode, reboot computer.

If you do not have an ATI entry to uninstall in remove programs then head over to device manager (Run “devmgmt.msc”), select your display adapter, right click on it and select uninstall. Your screen will probably flash.

At this point you have the option of booting into safe mode, by pressing f8 repeatedly in between bios loading screen and the windows logo, and running Driver Sweeper to wipe all traces of ATI from your computer.

When this is done boot back to windows and extract the 8.10 drivers you just downloaded. Now run Mobility Modder, point it to the ATI directory that was created, and click Modify.

For Windows 7, there is an extra step. Skip this if you are not running Win7.

Locate atikmdag.sy_ in the ATI folder, use

DSEO to sign the file.

Now go back to device manager by running devmgmt.msc , select your display adapter, and press Update Driver. Navigate to Browse fo r File, Pick from list of drivers, select Have Disk, navigate to the ATI directory which was created *\ATI\Packages\Drivers\Display\LH6A_INF and press OK.

You may be prompted whether you wish to install an unsigned driver, press yes. If you have Windows 7, you have one more step. Use DSEO to s ign the “atikmdag.sys” in your /windows/system32/drivers folder. Now you can reboot.

When windows boots back up, you can use the AMD GPU Clock Tool to change your clocks.

When installing ATT, make sure to check Disable Overclocking, as it will not function properly. Read these notes if installing ATT on Windows 7.