All posts by Emil

Service VMware Authorization Service (VMAuthdService) failed to start

When installing VMware.

You will get the error “Service VMware Authorization Service (VMAuthdService) failed to start.” when installing VMware (I’ve tried Player and Workstation) and have Avast installed.

Disabling Avast will not do any difference. Uninstalling Avast will work, but there is an easier solution.

 

In Avast click Settings and then Troubleshooting. There uncheck “Enable hardware-assisted virtualization”. After that you have to reboot your computer.

 

Remote Debugging ASP.NET Development Server with SPI Port Forward

If you try to connect to the ASP.NET Development Server included in Visual Studio from another computer, you simply just can’t.

It’s a safety feature from the Visual Studio team, but also a big headache for many developers. If you want to test a PDA connecting to a web service on ASP.NET Development Server it is not even possible to run the test software locally on the same computer as the server.

After searching the web I found this question (and solution) on stackoverflow: http://stackoverflow.com/questions/1730280/accessing-asp-net-development-server-from-another-pc-on-the-network.

But since the answer on stackoverflow is linking to download.com, downloading the SPI Port Forward program is another headache. After the download the file is well hidden in some temp folder far away. So I added a download here.

Download SPI Port Forward here

After starting the program. You enter the port number you want to remote connect to your local ASP.NET Development Server with in Local port. Enter localhost as Remote host. And enter the port that the ASP.NET Development Server is using as Remote port. Then Activate to enable the port forward.

Now you can connect to your local ASP.NET Development Server by connecting to: 192.168.1.15:12345. Where 192.168.1.15 is your local computer (with server) IP. And 12345 is the port you entered in Local port.

 

How long does it take to get listed at DMOZ.org?

It’s a well known secret that being listed at DMOZ.org is one of the most important things when getting high ranks in Google. If a site is listed at DMOZ.org, it has been checked by a DMOZ editor and can therefore be believed to have high quality. The DMOZ directory was also mirrored to http://directory.google.com (but that has been discontinued), and if a site was listed in the DMOZ directory the classification was displayed in the Google search result (apparently also discontinued).

But according to the Goggle Webmaster video at the bottom of this post, there are no extra benefits from being in the DMOZ directory, not more than a link from any other site. But DMOZ tends to have a high pagerank and the directory is also mirrored to many other sites which will build pagerank.

Back to the question.

How long does it take to get listed at DMOZ.org?

Well, the quick answer is that it depends. It depends on which category and how active the editors are in that category. If you want to add your site to the “right” category it can take about a month. If you want to add your site to the “wrong” category, I’ve read in the DMOZ forum about people waiting for 2-3 years!

I’ve experienced this myself.

Some years (more than five I guess) ago I added a several sites to the DMOZ directory and I think I had to wait a few months for each to be added. Then I created a new site and submitted it to the DMOZ directory. I waited for months and months. Then I created a subdomain to the site with content that would fit better in a different category than the rest of the site. After submitting the subdomain to another category in DMOZ it was added in about a month. The first submission is still not added after waiting more than a year. So you have to be “lucky” and have a site goes into the “right” category.

Although Google does not give any extra credit for being in the DMOZ directory, it can’t be a bad since according to this list the directory is mirrored to almost 100 different sites.

http://www.dmoz.org/Computers/Internet/Searching/Directories/Open_Directory_Project/Sites_Using_ODP_Data/full-index.html