Diablo III Battle. net launcher crash

[slopoke]

I've been gone for awhile due to family issues. Now that I'm back, I tried the 2.0.1 update to Diable III. It comes with a new launcher from Battle.net. The launcher crashes almost instantly with "An unexpected error has occurred in AGT:2600". I put in a ticket with Blizzard and did everything they said to do except one thing I couldn't do. They want the "Secondary logon" service enabled. That must be possible because other Wine users are playing. Does someone know how to do this? I do have Wine 1.7.14 and winecfg is set to XP.

Thanks

[Bob Wya]

@slopoke,

Looks like there is an (extensive!!) workaround for this issue on the AppDB page for Diablo III.

Don't own the game myself - but the test submission by andrew m appears to cover all the bases!

Bob

[phantom]

The andrew_m's solution eliminates the crash indeed, but the Battle.net launcher still doesn't work properly; it shows the same error AGT: 2600 immediately after trying to start downloading the update, and then nothing happens forever.

I'm using 64-bit Debian and wine-unstable 1.7.14 downloaded from http://dev.carbon-project.org/debian/wine-unstable/

Thanks

[slopoke]

phantom is correct. I went back to the appdb and double checked andrew_m's instructions. I did it correctly.

I still think this has something to do with the "secondary logon" service that Blizzard insists on having enabled.