BenV's notes

Seems like they released a new patch for World of Warcraft, increasing the version to 4.3.3 build 15354.
Obviously this broke on my wine64 installation of the game:
* Start wine64 Wow-64.exe
* Login
* “Patch required” -> OK
* “Downloading Update” -> OK

Patch 4.3.3 under wine64

My windows partition was low on free disk space so I looked around for what game to remove.
Until I noticed C:\hiberfil.sys taking a whopping 12 GIGABYTES of disk space.
For a feature that I never use. (I either play games on windows or don’t run it at all, sleep mode etc was already disabled).
Seems like turning off the hiberfil.sys takes more effort than in XP (where it was a checkbox hidden in the power management options).

To disable it:
1. Start a command prompt as administrator
2. powercfg -H off

Voila, diskspace.

Last week we bought a new toy — a Canon EOS 600D (including a lens with about the same pricetag). So far I’m happy with it, it’s nice to play with a ‘real’ camera for a change. (our previous one is a simple Samsung TL205. Apples and oranges.) (continue reading…)

Earlier I reported on my first World of Warcraft under 64 bits wine experience. It somewhat worked but couldn’t play the game because it got stuck on the loading screen.
Just now I decided to give it another shot and pulled the latest wine from git. Currently we’re on wine version 1.4-rc4. Before building that I upgraded my NVIDIA driver to their latest as well, 295.20.

After compiling and installing the new wine release candidate the results are in:

World of Warcraft on 64 bits Wine (1.4rc4)

So it seems like the guys working on Wine did some good work!
Loading the initial screen is still a bit slower than the 32 bit version, but apart from the it seems good. Haven’t tried any dungeons yet, so I have no reports on ingame performance, but I might complain on that later if it sucks 🙂
If not I have another reason to move my old 32 bits slackware partition to the shredder.

Today I wanted ipsec-tools on my Slackware64 (v13.37) domU.
Sounds simple: figure out where they host the stuff, download, configure ; make ; package, install. Right?
*BZZZZZ* WRONG! (continue reading…)

In an attempt to try out the latest DRBD version (8.4.1 atm) on a new Xen installation, I ran into some issues.
Initially I built the kernel with the included DRBD module, but I soon realized that this version was older than I wanted to play with (the included version was 8.3.11), so I grabbed the source and tried to build it myself. (continue reading…)

With the release of patch 4.3.2 the still biggest MMORPG they finally decided to go the 64 bit route.
Through the forums a 64 bit client can be downloaded and placed next to the normal one, with a bunch of warnings and stuff that doesn’t yet work obviously. Yay. (continue reading…)

While updating wine-1.4-rc1 I thought it would be interesting to see if I could get their OpenCL stuff to work. The lack of information on how to do so is really annyoing, so here’s what I did to get it to compile. (continue reading…)

After setting up a new trac installation (v0.12 stable) I tried to get notifications up and running.
I’ve done this plenty times already so you’d think this should be easy.
Edit the trac/conf/trac.ini, set smtp_enabled=true and make sure the smtp settings and always_cc address make sense.

However, this time it just wouldn’t work for some reason. No errors, nothing in the trac log, but no emails on ticket changes. (continue reading…)

This morning my mailbox opened up with an email inviting me to the Diablo 3 Beta. After checking the headers
to make sure it wasn’t another battlenet phishing scam I noticed that the Received headers really came from blizzard.com, and they even signed the mail with a domainkey. Also they didn’t include some link but simply told me to go to battle net and get the goods there.

Diablo 3 Beta Invite

We also invite you to share your Diablo III beta experience with the world! All participants can take screen shots, capture video, and/or publicly disclose information about their beta test experience.

(instead of the usual non-disclosure agreement). So thanks Blizzard and a friend who works there who is no doubt responsible for getting me this invite in the first place 🙂 (continue reading…)