Diablo Auction House Error 31073

I've currently getting error code 31073 when creating any auction on the Diablo 3 gold and real money auction house on the EU servers. I've submitted a support ticket to Blizzard:

Hello Blizzard,

I'm getting error code 31073 when creating auctions on EU gold and EU real money auction houses. Is there anything I can do to avoid this error when creating auctions?

Thanks

/Roger

I'll keep you posted when the customer support reply to the ticket.

Diablo launcher stuck initializing on the Mac

Does your Diablo Launcher hang at "Initializing" on your Mac after downloading the critical launcher update this morning? This is a work-around which will help you play the game until Blizzard comes up with a real fix. 1. Start the Diablo launcher. 2. When it asks you for your Mac admin password to make some system changes, click Cancel instead of OK. 3. The launcher continues without hanging on"Initializing" and the Play button is enable. 4. Press Play. Did that solve the problem?

Scrolls - Game play capture

Game play capture from Scrolls - the upcoming game from Mojang. In this movie capture I play a match against the medium level AI. The capture is from a pre-alpha build.

Hope you will enjoy this game as much as I do.

Scrolls - A first look at Mojang's next game

I'm currently playing the pre-alpha of Scrolls, which is Mojang's upcoming card game. I'm figuring out how to best play the game by doing quick matches against the AI. The Easy and Medium difficult level was no problem to beat, but Jon Kågström's Hard level AI wipes the floor with me. Good job Jon!

Want to test the Alpha? Sign up here.

Update: 2012-06-17: Posted more screenshots upon request.

Screenshots

The scrolls configuration startup screen

The login screen

Choose single- or multi-player matches.

The Deck Builder

The tutorial

Gameplay against medium level AI

Gameplay: AI Great Wolf attacking

Me getting my ass kicked at hard level

How to avoid loud fans when playing World of Warcraft on the 2011 MacBook Pro 13"

Some time ago I retired my old Dell XPS laptop for a 2011 MacBook Pro 13" with a solid state drive. I don't have much time for gaming these days, but from time to time I would like to cast some holy paladin heals in the Warsong Gulch battleground in World of Warcraft.

I was worried that WOW would be to tough for the Intel HD Graphics 3000 card, but to my surprise it ran in 60 fps when running around in Goldshire:

There was a problem though, when running up to Stormwind to search for some new gear and enchants at the auction house there was a major increase in the fan speed. The auction house area is quite crowded on the Silvermoon server. The previously silent Mac was not so silent anymore :(

After some searches I found the follow work-around: The console in WOW allows you to limit the frame rate of the game with the maxfps console command. I created two macros, one that sets the frame rate to 5 which I use when I'm in the crowded Stormwind area, and another macro which limits the frame rate to 30 which I use inside the battlegrounds. Here's a screenshot of how I set up the 5 fps macro:

With these two macros I can play the battlegrounds with a reasonable frame rate and visit the city centers without having the Mac noticeable increasing its fan speed.

Did this solve the loud fan problem when you play World of Warcraft on your Mac?

Loading seems to be taking a while

I've been getting the "Loading seems to be taking a while" error message when clicking on the @Connect tab on Twitter for about a month now. Pretty annoying. Anyone found a solutions for this?

Windows 8, VMWare, HAL_INITIALIZATION_FAILED, VirtualBox and broken network bridging

A couple of days ago I downloaded Windows 8 to port my C++ code to this new platform. I tried to install
Windows 8 into my good old VMWare Workstation 5.5.9 where I run my other virtual machines, but ended up getting a HAL_INITIALIZATION_FAILED error message when booting from the .iso:

But since word was on the street that VirtualBox 4.1.2 could handle Windows 8 I gave that a try.
Unfortunately the Windows installer kept hanging while "Expanding Windows Files" while installing it onto
the VirtualBox virtual machine.

After some trial and error I changed the number of processors/cores in the VirtualBox virtual machine settings to the same number of processors/cores as on the host system, in my case two. This change seemed to do the trick and the installation completed without any other issues.

When I went back to run my VMWare virtual machines I noticed that their brigded networking was no longer working :( Switching to NAT and it worked fine, back to bridged and no network connection. For some reason the installation of VirtualBox caused my existing bridged connection to fail. Anyway, the solution was to explicitly set the network adapter VMWare should bridge with, in my case the Wireless adapter:

Hope this helped someone. Now I'm going to try the 64-bit version of Windows 8.