I was just trying to connect my AudioTron to a Vista machine that has my music collection on it. The network connection didn’t work, because the Audiotron is using an old version of the relevant network protocols. This is just a “note to self” type post to remind me what I needed to change in the security policy of the Vista machine to make it work:

• LAN Manager authentication level set to Send LM and NTLM responses
• Do not store LAN Manager hash value on next password change set to Disabled
• Change the password back and forth if set before, so that the LAN Manager hash value can be updated

Done.

I did a presentation recently at the NxtGenUG in Oxford, where I introduced WPF and WCF in a combined session. I created a network enabled implementation of Connect Four to do this. Here’s the download of the demo solution, as requested by some of the attendees:

  ConnectFour.zip (30668 bytes)

If you missed my presentation in Oxford, I suggest you keep an eye on the DDD 5 agenda voting page. I submitted the same session there and as soon as their voting opens, you can vote for the same session there and come see it at DDD 5 - assuming it gets selected, of course

I was trying to run the default website in a default installation of IIS on Vista, and I got this error message:

What the …? Who comes up with crap like this? Unbelievable… even the error code is useless to search for, as apparently there are hundreds of other error conditions in Windows that bring up the same error result. Does Windows have so many error conditions that the value range of a 4 byte uint is no longer large enough?

So what was the problem? Very simple: another application was already listening on ports 80 and 443 (Skype - does that by default, thank you very much). Apparently it’s really hard to have an error message like “Another application (Skype, PID: XXX) is already listening on port 80.”, or at least “Error trying to listen on port 80.” Well, it’s only IIS 7 - maybe they’ll get it right for version 22 or so.

Just came across this, and I thought I’d document it for myself and others. I was trying to install SnagIt on a newly installed Vista system and every time the installation just stopped right after the first wizard page, giving me a “Fatal Error Message” with the detail information “Installation ended prematurely because of an error.” I had already installed Camtasia before SnagIt, so I thought this was rather weird - seemed like if the installer worked for one of the products, it should work for the other just as well.

I searched the TechSmith forums and quickly found a link to a page where they already describe a solution to the problem. Now, the funny thing is that I already knew about that problem, having encountered in recently when installing the BlackBerry desktop on Vista, and I had already applied the solution on that machine.

Well, I did the “regsvr32 …” step once more, and it seemed to work - I was able to run the wizard and get past the point where it had previously stopped working. A few pages later is where the license key is requested, and I had to tab over to another app to find where I had stored the email with the key, and open it in an editor. I copied the license key, pasted it back in the SnagIt installation wizard, clicked Next, and …. I got the same Fatal Error message once more. Looks like somehow the VBScript runtime got unregistered on my system while I was looking for the license key.

I registered VBScript yet another time and ran the wizard. I still had the license key in the clipboard and I was careful to step through all the pages without doing anything else. As a result, everything went just like it should, and I got SnagIt installed. I don’t currently have any idea what caused the problem… I’m using more or less the same set of applications that I already had running on an old Vista installation, and on that system I had never had any problems with the SnagIt installer.

In any case that VBScript thing seems to be a running gag in Vista… I really wonder why it’s not registered by default, this seems to cause quite a few problems.

Update: I just found that Corel Draw 12 has the exact same problem, and once more VBScript had been uninstalled on my machine… guess I should figure out why the uninstalling happens all the time.

Wow, Microsoft learns! It’s taken them awhile, but now they got it (nearly) right: Expression Web is now part of all Premium level subscriptions. In case you hadn’t heard, it came at an extra cost so far, regardless of what you were already paying for your existing subscription, with Microsoft arguing that it wasn’t meant to be a developer tool and so it shouldn’t be part of their developer subscription package.

Apparently Blend will be handled in the same way once it goes RTM, which is a blessing. Apparently Design and Media are still something special though - I’m not sure if that’s the right decision once more. They will be available as part of the Expression Studio (the package of all four products), and that will be part of the Team Suite subscriptions, but not the Professional ones. I’m thinking that if I’m part of a big team, it’s rather probable that there will be designers involved in my WPF development effort. On the other hand, if I’m a single guy or a small team and I’m using a Professional level subscription, that’s exactly when I’d really like to have those tools included in the package because more likely than not I’m doing all the graphics stuff on my products myself, even if I’m not an expert on that.

Well, let’s be thankful for what we get and see about the rest later. Kudos to Microsoft for listening!

Heard this today: I have received Microsoft’s MVP award “Visual Developer - Visual C#” this year. Thanks to Microsoft, and also thanks to everybody who helped this along, you know who you are.

Now I just have to wait and see whether I’m still an MVP tomorrow, or rather an April’s fool…