The VMRC connection could not be established because protocol version 3.6 or later is required.

If you try to connect to a VNC Server using VNC viewer, and you get the following error message:

The VMRC connection could not be established because protocol version 3.6 or later is required.

Maybe you are running Microsoft Virtual Server and VNC server at the same time on your server machine. So you have to resolve a simple port conflict (both uses 5900).

Solution: change the incoming port of VNC Server [Right click on VNC tray icon]


How to fix hal.dll missing or corrupt error message during bootstrap.

Suppose you have reconfigured your partitions using Partition Magic or GPart.
Suppose you delete partition #1 and your Windows starts from partition #2.
When you will reboot 99% you will get a:
windows root\system32\hal.dll is missing or corrupt, please re-install
error message.

The problem is that the partition number for the Windows Boot entry in BOOT.INI is wrong and you have to fix it.

NO PANIC, here’s what to do:

  • Insert your Windows XP CD and boot from it
  • Wait the option menu and choose R for Repair pressing R key
  • Select the installation to repair (maybe #1)
  • type bootcfg /REBUILD giving a name and blank options
  • reboot from HD

Cerca una parola o una frase in un file su Windows non funziona?

Spesso quando fate Cerca di una parola o frase all’interno di un File nelle cartelle di Windows 2000 o XP il risultato della ricerca non è corretto, nel senso che spessissimo sembra che torni meno risultati del dovuto.

E’ verissimo, però c’è una soluzione:

  1. Fare clic sul pulsante Start, quindi scegliere Cerca.
  2. Fare clic su Cambia preferenze, quindi su Con Servizio di indicizzazione (per ricerche locali più rapide).
  3. Fare clic su Cambia le impostazioni di Servizio di indicizzazione (Avanzate). Non è necessario attivare il Servizio di indicizzazione.
  4. Sulla barra degli strumenti fare clic su Mostra/nascondi struttura console.
  5. Nel riquadro sinistro fare clic con il pulsante destro del mouse su Servizio Indicizzazione su computer locale, quindi scegliere Proprietà.
  6. Nella scheda Generazione selezionare la casella di controllo Indicizza file con estensioni sconosciute, quindi scegliere OK.
  7. Chiudere la console del Servizio di indicizzazione.

EXPLORER.exe CRASH – RESTART del Desktop senza riavviare la macchina

Quante volte vi sarà successo che Explorer.exe, l’eseguibile responsabile del disegno e della gestione del desktop, vi sia andato in crash? Molte!

Spesso la soluzione di molti era spegnere e riaccendere la macchina, riavviare e cose simili, ovvero perdere il lavoro e le finestre aperte in quel momento.

Esistono due metodi per ovviare al problema:

  1. CTRL-ALT-DEL per far comparire la Protezione di Windows e poi cliccare sul bottone “Task Manager”
  2. Dal Menu Principale del Task Manager selezionare File -> Nuova Operazione (New Task)
  3. Nel campo Apri (Open) scrivere explorer.exe e premere OK

Il secondo metodo è quello di rendere automatico il riavviamento di explorer.exe dopo un suo crash, per fare ciò bisogna intervenire sul registry aggiungendo o modificando (se esiste già) la chiave:

  • Key: KEY_CURRENT_USER \Software \Microsoft \WindowsNT \CurrentVersion \Winlogon
  • Name: AutoRestartShell
  • Type: REG_DWORD
  • Value: 1

Access Denied issue when exec xp_cmdshell on a UNC pathname

Suppose you use a Sql Server user to execute a shell command on a remote shared folder

exec xp_cmdshell 'command UNC path'

and you get an Access Denied error.

This is because MSSQLSERVER, SQLSERVERAGENT services run as Local System Account that is not recognized on the remote machine you are pointing by the UNC path.


  • go to Control Panel, Administrative Tools, Services 
  • change Logon as user from local system to This User, specifying an administrative account that is the same on the two machine and with the same password (be aware changing it).
  • give privileges to that account to the remote shared folder
  • retry the exec xp_cmdshell

Stopping Windows Vista adoption by promoting free software

Bad Vista - Jump to Free SoftwareFirst of all go to the sub domain: and read carefully all the interesting things the Free Software Foundation says about Vista, DRM, Trusted Computing, etc. and your (digital) freedom.

In synthesis:

  • Microsoft’s new Windows Vista operating system is a giant step backward for your freedoms
  • Vista has DRM: digital rights management
  • These features will make your computer less reliable and less secure
  • Digital rights management (DRM) features built into Vista at the behest of the entertainment industry – And you don’t get to refuse them
  • Vista decide which programs you can and can’t use on your computer
  • Vista decide which features of your computer or software you can use at any given moment
  • Vista force you to install new programs even when you don’t want to (and, of course, pay for the privilege)
  • Vista restrict your access to certain programs and even to your own data files
  • Vista and its Defender is free to delete files on your PC
  • Vista and its Genuine Advantage decide what to do (install or not) with thirdy party developed software
  • DRM is enforced by technological barriers
  • Your computer has to be constantly monitoring what you are doing consuming a lot of resources (disk space, cpu time)
  • Microsoft and other computer companies sometimes refer to these restrictions as “Trusted Computing.” Given that they are designed to make it so that your computer stops trusting you and starts trusting Microsoft, these restrictions are more appropriately called “Treacherous Computing”.

Other links:

About Vista “security and reliability”:

Save your freedom! Save your money.
It’s time to jump to free software.

How to register already installed ASP.NET framework on a new IIS installation

Dot Net LogoIf you install the .NET Framework on a system that has IIS already installed, IIS is automatically configured to handle requests to ASP.NET pages, and to redirect the execution to the ASP.NET runtime. However, it may happen that you installed the framework on a Windows 2000 Professional system where IIS was not already present, and just later decided to add IIS.

Registering ASP.NET on IIS is not just a matter of associating the various .aspx, .asmx, .axd, .ashx and the other ASP.NET extensions to the aspnet_isapi.dll ISAPI, more has to be done to create the ASP.NET account and to set it for ASP.NET requests, register the ISAPI itself and other stuff.

Doing all this manually can be a difficult operation, and requires a good understanding of many details. Fortunately there is an utility, shipped with the .NET Framework but not documented, that can take care of these configuration chores for you.

The utility is


it is located under


and you should call it with the -i parameter:

aspnet_regiis.exe -i