If you are one of two million people who played the Diablo 3 beta, you must totally uninstall the beta -- and delete the folders -- before installing the full game.The folder can be found in the following locations: C:\Documents and Settings\All Users\Application Data\C:\Program Data\/Users/Shared/Once this folder and all other beta files are removed, run the installer.Two of the more popular error messages are 37 and 12.Error 37 simply means: "The service is undergoing maintenance, please try again later." Error 12 is caused by "the Global Play feature being disabled until all regions are active".I am installing by the file at /media/Diablo3/Diablo III It's been at "Updating Setup Files" for about 5 minutes, can't tell if it is hanging or if its suppose to do that. Blizzard suport recomends to check if the firewalls are blocking the game ports, and to flush DNS cache. As far i could see, the 3007 error is an generic error for conection lost.
As thousands struggle to play Diablo 3 and servers buckle under the strain, Blizzard has explained the various error messages players are receiving as they attempt to log-in - and offered advice on how to deal with them.If it works and you can play but graphics quality low - go to next step. If you should be using nvidia drivers and don't see it there, either download the drivers straight from their website (and buy painkillers) or use the Ubuntu repo.Many recent notebooks with a discrete n Vidia card in it and an i3/i5/i7 processor use the n Vidia Optimus technology to improve battery life. Diablo III was originally installed using Play On Linux’s Diablo III installer which installs the game under a custom version of Wine 1.5.5.The 2.0.1 update not only upgrades the game but also updates the Diablo launcher to the new launcher. What ever happend to the good old simple game installs, without the need for intenet, or stupid updates for a brand new game, before you can play it, or even install it... servers are still too busy (which would truly suck) 3. I am having a similar problem where no matter what I do, i get stuck on "authenticating credentials" till it kicks me out with error 3007 (basically "you took too long"). Always suck if you can't play after buying a game... I've installed everything correctly (with the online installer) , but can't login to the game (error #3007). I'm using an older Play On Linux version: 4.0.14, which comes with Ubuntu 2.No mention of the issue yet on the forums so I’ve started a thread on the Diablo III forum which can be found at [UPDATE]: Thanks to luke10 for posting a link to a thread on the Play On Linux forums regarding the dbghelp library this has also been discussed in the thread on the Diablo III forum too.Running the launcher (and Diablo III under a later version of Wine) fixes the Crypt32 error and delays the launcher from crashing long enough to allow you to launch a game.First impressions of the game after the big update were great which worked flawlessly.When exiting Diablo III following the update and restarting you are then prompted to install an update to the launcher, after the launcher update it crashes preventing you from being able to launch the game.