Uh oh – I borked my dapper dist-upgrade. Whilst the upgrade was underway I was prompted a few times with “overwrite this file?”, “overwrite that file?” questions. Seems like I stuffed it…
Below is just a little reminder of where my windows boot loader is for when I do a clean install of Ubuntu Dapper 6.06 LTS:
# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda1
title Microsoft Windows 2000 Professional
I purchased two LCD Topguns (review here) a while back. I think I mentioned them in a previous post. They are great. Although getting two to work at once might be difficult. Games like Operation Wolf are great using a gun.
Alos got myselft a scrappy old coin door that I’ll polish up with some autosol to make it look respectable. I donlt know if I will make the mame cab use coins to start games or just have the coin door for effect…
1. Coin door does nothing but look realistic.
2. Coin door uses coins to insert credits into games.
3. Coin door coin-return button used to insert credits.
I think I like option three better. That way I can get rid of two buttons on the control panel – keeping the CP true-to-form of a real arcade machine.
I’ll post some pics shortly so I can keep track of how it looked before and after I polished it up.
For three days my local web server was not responding. You know, I’d point my browser (Firefox) at http://localhost/ and I’d get nothing.
After a while it dawned on me that I had recently installed a big Microsoft Tuesday patch session. Perhaps my default web site had been stopped? I fired up the the IIS management console to find that my default website was indeed stopped. Simple solution for sure – right-click and select Start. Nope – what I got told was “the network request is not supported” WTF!
So I uninstalled and re-installed IIS. Did that fix the problem? No – different error though – “Location already in use”. I figured this meant something was already using port 80. But what? To confirm my suspicions I made my default web site use port 81. Pointing my browser to http://localhost:81/ resulted in my web pages appearing again. Now I knew for sure that some program had snatched port 80 away from IIS without my knowledge! The hunt was on.
I grabbed TcpView from SysInternals and fired it up. What do you know? Bloody Skype had snatched port 80, and was listening away! I shut down Skype and re-configured IIS to use port 80 and my local web server was all happy again.
Bloody skype! How rude. I had to go into the Skype settings and disable “Use port 80 and 443 as alternatives for incoming connections”.
I think that with the recent patch IIS must be starting up a bit later, giving Skype the opportunity to nab port 80 first. That should not matter now that I have disbaled port 80 for Skype.