Autarchy of the Private Cave

Linux users are not affected with a plethora of autorun.inf “viruses”, but that seems to be a real plague for Windows users.

Ideologically correct solution is offered by Panda software – a free Panda USB and AutoRun Vaccine. It can do two things for your Windows box:

1. with a single click disable auto-execution of programs from USB sticks and CDs/DVDs, and
2. with one more click – make the autorun.inf file on your pendrive inaccessible, so as to prevent infecting your USB stick with an “autorun.inf virus”.

Program does not require installation, but requires Administrator privileges. It supports FAT/FAT32 pendrives, but NTFS-enabled version is being tested and should be made available shortly.

Note, that if you perform step 2, re-enabling access to autorun.inf may require pendrive formatting. Also, after step 1 your favourite CDs and DVDs won’t start automatically anymore – but you will be able to start them manually.

And, of course, Linux users have nothing to worry about (yet).

One of the benefits, offered exclusively by the Windows Vista Ultimate (not even by the Windows Vista Business), is

running UNIX applications (via SUA, Subsystem for UNIX Applications) , which provides higher flexibility for Windows workstations.

Where is the world going?

And how soon will all the Windows users (not only Ultimate Users) benefit from the higher flexibility by running UNIX applications?

It is possible to install gpedit.msc snap-in for MMC in Windows XP Home Edition. I found the list of necessary files on pagesperso-orange.fr (in French), which also had the archive of all the necessary (again, French) files and the installation batch-file.

Warning: you proceed at your own risk. If you do not know what you are doing – please don’t

Download (original) French gpedit-pour-xp-home.zip.

Download English gpedit for windows xp home.zip (also in 7zip archive).

Here are instructions for manual MMC snap-in installation. Original French-version archive had a batch file which does installation automatically, which I also added to the English archive (gpedinst.bat). But you must manually verify that batch file fits your system before running it! It might be safer to follow the instructions manually.

• Put these files:
  

  appmgmts.dll
  appmgr.dll
  fde.dll
  fdeploy.dll
  gpedit.msc
  gpedit.dll
  gptext.dll

  into %SystemRoot%\system32 folder (most often it’s just c:\windows\system32)

• put these files:
  

  system.adm
  inetres.adm
  conf.adm

  into %SystemRoot%\system32\GroupPolicy\ADM\ (create if this folder doesn’t exist)

• finally, run these commands one by one in the CMD window:
  

  regsvr32 gpedit.dll
  regsvr32 fde.dll
  regsvr32 gptext.dll
  regsvr32 appmgr.dll
  regsvr32 fdeploy.dll

That should make gpedit.msc callable as Start -> Run -> gpedit.msc.

Other language versions of the necessary files can be retrieved from corresponding-language installations of WinXP Professional; English version can also be downloaded directly from Microsoft website ( e.g. here , or search for “Group Policy ADM Files” at microsoft.com). Also, you can extract necessary files from available Windows distributions: just don’t forget, that “filename.dl_” is a compressed version of “filename.dll”, and can be uncompressed by using XP-bundled extract command.

See also this comment for alternative gpedit installation (get the file from badongo first), and also this comment for one more explanation of manual installation.

Geeks corner:

1. a comprehensive list of the “Group Policy/User Configuration/Administrative Templates” settings in Windows XP Home Edition
2. an extremely comprehensive Excel sheet, which maps numerous *.adm-file options to their registry equivalents – Group Policy Settings Reference (PolicySettings.xls). This file is for Windows 2000, Windows XP, and Windows 2003

Disclaimer: I do not know if modifying (e.g. by adding gpedit) your WinXP HE is a violation of any EULAs. It’s your own responsibility to check this out and comply with any such regulations. Also, be advised that modifying any settings using gpedit.msc on WinXP HE may render some parts of the OS inoperable (in my opinion). You have been warned!

Get the driver!

There’s also another one, but provides read-only support.

Topologilinux ‘BSOD at launch’ problem solution is at the end of this post.

Topologilinux is a special linux flavour, which is especially fit for the newcomers to the *nix world. The motto of Topologilunux is ‘Running Linux inside Windows’ – and that is what it does. Even more – you can run it inside windows, or you can boot into it and work Linux-only – in both cases the system is the same.
Personally, I consider this kind of setup extremely useful for users who are strongly used to working in Windows (or just stuck with windows for too long), but at the same time are inclined to script a bit (be it bash, Perl, PHP or Python), to run server applications, write cross-platform programs, to test something or just play with software. With Topologilunux, it’s perfectly fine to work in DreamWeaver on your windows machine, and launch Topologilinux with apache+php+mysql to serve as a testing server – on that same machine. You can easily replicate the needed server config, and play with it the way you wouldn’t if that was the production server.
Read the rest of this entry »