Archive for the ‘Windows’ Category

How-To Install an Apple (Wireless and USB) Keyboard in Windows 7

Friday, February 15th, 2013

I recently discovered a new small utility that helps to use a Apple Keyboard and most of its special ‘Fn’ keys with Windows.

This utility is called AppleWirelessKeyboard that you can download from this link:

Despite it’s name (that specifically mentions ‘Wireless’) I found that this utility makes also Apple USB keyboards to work properly.

I have tested it with Windows 7 and a (not so recent) Apple USB Keyboard without a numeric pad.


  1. Create a folder called AppleWirelessKeyboard in
    C:\Program Files\AppleWirelessKeyboard\
  2. Download the AppleWirelessKeyboard.exe utility into the AppleWirelessKeyboard folder.
  3. Create a link for the downloaded AppleWirelessKeyboard.exe to
    C:\Users\<your user>\AppData\Microsoft\Windows\Start Menu\Programs\Startup
  4. now you can manually launch the utility and at any following system start-up the utility will be automatically activated.

Please leave comments with your testimonials about what models and what systems the utility is compatible with.


How-To Redirect PATHINFO (Almost Pretty) Permalinks To Pretty Permalinks

Wednesday, March 21st, 2012

This post is about supporting your former PATHINFO Permalinks structure (a.k.a. Almost-Pretty-Permalinks), on your new web-site using Pretty-Permalinks.

 Redirect 301 /index.php/
 RewriteRule . /index.php [L]

These are the lines of Apache’s configuration that must be present in the website’s main .htaccess file:

 <IfModule mod_rewrite.c>
 RewriteEngine On
 RewriteBase /
 Redirect 301 /index.php/
 RewriteCond %{REQUEST_FILENAME} !-f
 RewriteCond %{REQUEST_FILENAME} !-d
 RewriteRule . /index.php [L]

This case applies to those websites formerly configured to use PATHINFO Permalinks and for which all the old posts and pages have been indexed by the Web Search Engines (Google, Yahoo, Bing, etc) using the former structure that included the HORRIBLE! “/index.php” string in their URIs, i.e.:

When these sites finally migrate to the Pretty-Permaling structure, the one that does NOT include the  horrifying “/index.php” piece, i.e.:

it happens that all the search engines’ indexes will result suddently outdated, and that will penalise the sites at least in two ways:

  1. It will cause a loss of accesses because the back-links to the sites that are present on other blogs or in people’s favourites and bookmarks, or in the search engines’ indexes will be ‘broken’ (old) and the people will be unable to access the pages or posts unless browsing from the homepage.
  2. It will cause a loss of ranking in the search engines’ databases (S.E.O. perspective) because the sites will result ‘broken (unaccessible) and in some cases may even result like sites with duplicated content because the search engines’ spiders will index the pages as NEW pages (due to their new URIs) and the content will match the caches indexed with the old URIs (at least until the caches expire).

To prevent such mayhem you need to put in place a 301 (permanent) redirection that will tell the search engines that all the requests to URIs containing the ‘/index.php’ bit have to redirected to similar URIs not containing it, i.e.:

Redirect 301 /index.php/

This string gives instructions to the web server about what to communicate to the Search Engines when a PATHINFO request is received.

Most importantly the 301 redirection will instruct the search engines that the URIs containing “/index.php” have to be considered deprecated and that from now on, the site will not use it anymore. This is fundamental to avoid the search engines to consider the content of the site as a duplicated content.

Secondly you will need to put in place also a generic rewrite instruction that will tell the local web server (Apache) to accept all the incoming requests to URIs with a PATHINFO format and return the content of the new and purged URIs:

RewriteRule . /index.php [L]

This string gives instructions to the web server on what it must to do when a PATHINFO request is received.

I did use these redirection settings for my WordPress blog when I did migrate to a full L.A.M.P. server (GNU/Linux, Apache, MySQL, PHP) from the former Windows Server hosting service running Microsoft IIS and that did not support ‘.htaccess’ files but exclusively PATHINFO directives and for which I did not have access to the server’s core configurations, therefore I was forced to use “/index.php” in my permalinks.

If you did like this post leave a comment in sign of appreciation, ad if you are Facebook please consider to ‘Like’ page. Check the FB banner on the right widgets column of this page …     ========================================>>

I did take inspiration for this post at following this thread:

How-To Set Up a Continuos Synchronization on The Background With Windows 7 and The Group Policy Editor

Saturday, September 3rd, 2011

Using the Offline Files in Windows Vista or Windows 7 is not always a smooth process and can cause a lot of Offline Folders And Files Synchronization Errors.

Offline Files synchronization errors

Offline Files synchronization errors

I found the latest generation of Windows to be very sensitive in the process to keep synchronized the Offline Files and folders copy with the  remote share.

Depending on the quality of the network you rely or the quality of the link to the share the Windows 7 (or VISTA) clients may think that the share is temporarily unavailable and stop synchronizing the Offline Folder while leaving temporary files on the server.
That may confuse some applications, especially Microsoft Office making them believing that a file you just edited and closed is still opened by another application and will refuse to open such file again.

I.E.. I have a very unadvisable configuration where a Linux server is providing an NFS share to a Mac OS X Snow Leopard server, and that server is then re-sharing via SMB and AFP that share to Windows and Mac OS X clients. I have experienced problem with Windows Clients stopping to synchronize files without any reasonable motivation.

I understood that because of an obvious delay on the communication from the Windows client through the Mac OS X server (via SMB)  to the Linux server (via NFS) would make the Windows client believe that the share was offline with many unconfortable conseguences.

I have found a workaround to this problem playing a little with the Windows’s Group Policy Editor.

As I don’t have a Windows Domain in place I couldn’t generate a policy file to be pushed once for all to all the clients so I had to manually start and configure the Group Policy Editor on each single Window VISTA and Windows 7 machine.

This is how to set up a continuos synchronization on the background with the Local Group Policy Editor:

  1. Start the Local Group Policy Editor

    Launch The Local Group Policy Editor

    Launch The Local Group Policy Editor

  2. Expand the Computer Configuration policies to ‘Network -> Offline Files’
    Group Policy Editor

    Group Policy Editor

    Slow Link Speed

    Slow Link Speed

  3. Access the ‘Configure Backgraund Sync’ option to enable the background sync

    Configure Background Sync

    Configure Background Sync

  4. Activate the ‘Enable Transparent Caching’ option

    Enable Transparent Caching

    Enable Transparent Caching

  5. Access the ‘Configure slow-link mode’ option to enable the support for slow-link networks

    Slow Link Mode

    Slow Link Mode

  6. Access the ‘Configure slow-link speed’ to configure the latency level to detect weather the connection get slow.
    Follow the suggestions shown in the LGPE to calculate the appropriate value.

    Configure Slow Link Speed

    Configure Slow Link Speed

These settings should avoid many of your problems and so far they did not create any additional issue.

Please comment and post your experience about any problems with the use of Offline Files and Folders.

How-To fix pGina: “Warning: Current plugin selected could not be loaded!”

Thursday, September 1st, 2011

After installing pGina and the chosen plugins (i.e. LDAP Auth, LDAP Group, RADIUS) on Windows Vista or Windows 7, it may happen that trying to access the plugin configuration it results in an error loading the plugin with the following error message being returned:

"Warning: Current plugin selected could nor be loaded!
You may not be able to login using pGina!"
Warning: current plugin selected could not be loaded

Warning: current plugin selected could not be loaded

The most common reasons for such error are:


  1. The installed plugin is for a different architecture:According to your system you must choose to install the x86 (32 bits) or
    x64 (64 bits) version of the plugin.
    Some plugin may be released on a single version but this doesn’t imply that it will work for both the architectures.
  2. Otherwise it most probably happens the you are missing the installation of the Visual C++ 9.0 (2008) runtime libraries (VC90.CRT 2008):In this case you need simply to download the Microsoft Installer package from Microsoft’s site at


Applying one of these two fixes you should have resolved your problems otherwise you may consider to check the file permissions on the plugin files.