Tag Archives: windows 10

Kore: How to Solve Can’t Find Kodi Media Center on Windows 10 Tips, Tricks and Tutorials 19 AUG 2015

I’ve mentioned the official Kore Android remote control for Kodi media centers before, and it remains my favourite Kodi/XBMC remote by far!

I did however encounter a small problem.

I’ve moved things around a little, shifting the Kodibuntu linux box away from the TV and closer to the router so that a) it’s out of the way, and b) it gains from the better Ethernet connection. This simple old PC box hosts all of our media content, which is then shared via UPnP and Samba shares. I’ve installed Kodi on both Chantelle and my laptops (both are Windows 10), and set their movie and TV sources to the SMB shares. (Works a charm!)

Also, the two laptops and one desktop all have static IPs assigned through my ancient Mega 105WR Telkom router (you know, I really should get that upgraded some day…).

Anyway, the problem is that Kore can see the Kodibuntu box with no hassle, but not a chance can it spot either of the Windows 10 laptops on the network – which is exactly what this post is all about solving then!

eminence theme on kodi xbmc media center

Kodi and Kore require Zeroconf (aka Bonjour), a group of technologies to “automagically” discover systems and services on a local area network, to communicate with one another, and naturally (because Bonjour is an Apple implementation) Windows doesn’t have Zeroconf support out of the box.

Now some popular applications ship with it slipped in for their own purposes, and installing them should technically grant you access to Zeroconf on your system (like Skype, iTunes and Photoshop), but if you’re just looking for a basic, older version without the need to install yet another unused full application on your system, your best bet would be to download the small Bonjour Print Services for Windows v2.0.2 package from Apple.

Install that, ensure that the Zeroconf option is enabled under Kodi’s services/network menu option, and you should be good to go: Kore will now quite helpfully pick up your Kodi instances in its search!

Related Link: Kore | Kodi | Zeroconf | Bonjour Print Services

Windows 10 and XAMPP: Port 80 in use by “Unable to open process” Tips, Tricks and Tutorials 01 AUG 2015

Originally the plan was to wait for Windows 10 to be a little more established before I took the jump and upgraded my work laptop (Windows 7) to Microsoft’s latest wunderkind (Windows 10). However, I got a little too excited (plus, free is always so attractive, isn’t it?), that I ended up jumping in and doing the upgrade as soon as my notification arrived! (So much for self control in other words).

(For interest’s sake, the upgrade went smoothly, though I had to uninstall a few applications and switch off a few startup apps for the best result. First impression? I really, really like it.)

Anyway, I did immediately hit my first snag when firing up XAMPP – the web server Apache failed to load, with the resulting message appearing in the console: Port 80 in use by “Unable to open process”.

netstat wasn’t much better at identifying the process locking up port 80 (also reporting “unable to identify process owner”), though the PID of 4 it returned did give a clue that it was probably a service currently using the port.

So I fired up the Services control panel (search “Services” using the search button next to the Windows button) and narrowed my search to all automated start services seeing as port 80 seemed to be locked at Windows start up already.

Knowing that port 80 is usually an internet related port, the services listing quickly threw up a likely suspect: W3SVC, otherwise known as World Wide Web Publishing Service.

It’s the service that provides the connectivity for Microsoft’s built in Internet Information Services Manager, but seeing as I want to use Apache for my web server, it’s quite safe to disable it.

Or as I did in my case, simply stop it and switch it’s startup type to manual.

Firing up XAMPP’s control panel confirmed that all was now well as Apache happily and greedily gobbled up port 80 as it started up!

disable World Wide Web Publishing Service Properties service

Related Link: XAMPP