As it turns out, it’s much simpler than that. Apache was sending the file to PHP to be parsed, but PHP was ignoring my code. Why? WAMP Server 2 comes with “short open tags” turned off (this may be a general PHP or PHP 5 thing, though not sure). Click WAMP -> PHP -> php.ini to edit the aforementioned file and find the line:

short_open_tag = Off

Replace Off with On et voila.

The ‘more correct’ though long-winded solution is to replace all your <? opening tags with <?php if you’re really keen (though that’ll also mean replacing <?= with <? echo). Me, I think I like my short tags.

Anyway, that meant manually creating the accounts, setting up the mail accounts and subdomains in them, extracting the root folders (public_html, mail etc) individually and manually importing the SQL backup. Everything was relatively painless (if dull) however Fantastico wouldn’t recognise my WordPress installations (I had two). To persuade Fantastico that there really were a couple of WordPress blogs I had to do two things:

1. Extract the \.fantasticodata\WordPress files from the zip (in this case it was called nerd.steveferson.com| ) and upload it to the same location in the FTP server. Of course that bar | made Windows barf, so you’d need to rename it (e.g. using an underscore instead) and replace the bar after uploading it via the FTP client (FileZilla didn’t seem to have a problem doing this).
2. I think this is might be because the blog’s in the root of a subdomain, but I also had to upload a file called installed_in_root.php from \.fantasticodata to that location on the server.

Once I did this, Fantastico picked up the blog and allowed me to upgrade WordPress to 2.5.1 – no hassle.

1. Review: Why the Netgear WG311 v3 Sucks (72)
   Slightly dodgy network card that Netgear don’t seem that fussed about fixing. Bad on XP, it got worse on Vista (see number 4).
   
2. Playing iPod Video on Your TV (45)
   Seems to be a lot of people looking for instructions for the iPod Classic. Here’s a tip: sell it.
3. Server application unavailable: installing IIS on .NET 2.0 (44)
   Seems to be a common problem. Sadly Microsoft’s error message is about as relevant as ever.
   
4. Installing Vista (AKA More Netgear WG311 Misery) (31)
   Even more messed up. Thank goodness for Linksys!
   
5. Thunderbird/Outlook/Google Calendar Integration (25)
   How to integrate your Thunderbird calendar at home with your Outlook in work, via Google Calendar.
   
6. Orange Answerphone (Voicemail) Number for PAYG (23)
   Such a simple problem. Who knew it would be so hard to find?
   
7. Stop Monitor.exe Hogging CPU (20)
   Why can’t people just give you a standard installation instead of trying to do everything for you? Help sounds good, until their useful tools start killing your PC.
   
8. How to run IIS Web Server in Windows XP Home (20)
   Microsoft’s official line is it can’t be done, but it’s not that tricky.
   
9. Making Firefox Scroll With Syanptics TouchPad (19)
   Discovering the solution to making Firefox scroll on my Acer Aspire laptop.
   
10. NAS or Home Server (17)
    I deliberate over whether I can justify spending the extra to build or buy a home server before eventually deciding that a Linkstation Live will meet my needs for less than half the price.
    

Just now I’ve used the same tool to fix a similar (I think) problem on IIS7 on Vista. I was trying to get some practice with ASP.NET. I’ve already got IIS7 and I’ve already got the .NET Framework 2.0 installed. However it seemed, again, that IIS wasn’t aware of the Framework’s existence. When I tried to browse to a simple Hello World page I was greeted with an HTTP 404 (404.3 to be precise) informing me that:

“The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.”

Despite the different error messages it appeared to be a similar problem. Apparently it was. That wonderful little solution again:

1. Start -> Cmd
2. Navigate to your .NET Framework directory (e.g. C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727)
3. Run the command “aspnet_regiis.exe -i”
4. Wait…

I already had the .NET 2.0 framework on my XP machine so went straight to installing IIS (5.1 comes with XP Pro). It installed easily enough and my hello world html file was served without any major problems (actually that’s not true, before I copied my own files across I tried to check the IIS default pages served ok only to discover, through more googling, that if I used IE instead of Firefox that annoying box asking me for a password would go away).

Now my ASP.NET issue. I got a Server application unavailable error message in big red letters when I tried to run any .aspx (ASP.NET) scripts and couldn’t figure out for the life of me why. The Event Viewer, where IIS errors are logged, gave little more by way of help: Failed to initialize the AppDomain:/LM/W3SVC/1/ROOT

Err… What?! I worked out that it wasn’t affecting html pages, just ASP ones – and only .aspx ones at that, suggesting it was .NET-related.

As it turns out the problem was that I had installed .NET before IIS. It’s easy enough to fix, but it took 20 solid minutes of googling to find the solution in a Microsoft community newsgroup (and then realise that I’d have found it already if I’d just read to the bottom of a 4 year old forum post I’d already found).

Anyway, what you need to do if you’re getting this “Server application unavailable” message is navigate to your .NET directory (something like C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727) in a command prompt and run the command aspnet_regiis.exe -i which will register ASP.NET with IIS. If that still doesn’t work, there’s always PHP.net