About Text Editors

Graphical Vim

Download and install from their site.

Notepad++

Download and install from their site.
set NOTEPADPP_PATH=D:\Program Files (x86)\Notepad++\notepad++.exe
set %PATH%=%NOTEPADPP_PATH%;%PATH%

7Edit (HL7 editor)

Download and install it from their site.

UltraEdit

Download and install from their site.

HexEdit

Download and install from their site.

DanSharp-XmlViewer

Download and install from their site.

DanSharp-XmlViewer

Download and install from their site.

XmlCopyEditor

Download and install from their site.

XmlNotepad

Download and install from their site.

YAML for .NET

Download and install from their site.

About Code Comparison

Code Compare 2

Download and install it from the site.

P4 Merge

Please refer to http://www.perforce.com/perforce/products/merge.html

KDiff 3

Download and install from their site.

About Time Tracker

Grindstone 2

You may try to download and install it from their site.

About Windows Services for UNIX SFU or Subsystem for UNIX-based Applications SUA

Windows Subsystem for UNIX-based Applications

It runs on Windows 2000, 2000 Service Pack 3, 2000 Service Pack 4, Server 2003 & Windows XP.
Download from its site.
When installed on C:\ it creates automatically the following environment variables:
set INTERIX_ROOT_WIN=C:\SFU\
set SFUDIR=C:\SFU\
set INTERIX_ROOT=/dev/fs/C/SFU/
set OPENNT_ROOT=/dev/fs/C/SFU/

set SFUDIR_INTERIX=/dev/fs/C/SFU/
set LD_LIBRARY_PATH=/usr/lib:/usr/X11R6/lib
set XAPPLRESDIR=/usr/X11R6/lib/X11/app-defaults
set XCMSDB=/usr/X11R6/lib/X11/Xcms.txt
set XKEYSYMDB=/usr/X11R6/lib/X11/XKeysymDB
set XNLSPATH=/usr/X11R6/lib/X11/locale

About Case sensitivity & security for SUA Programs

When installing Utilities and SDK for Subsystem for UNIX-based Applications, you might want to choose whether to change the default behavior of object names such as file names to being case sensitive. The choice you make will affect system security as well as how Subsystem for UNIX-based Applications functions.

In Windows, the names of most objects (such as files and directories) are case preserving, but case insensitive. That means you can use uppercase and lowercase characters when naming such objects, but Windows does not distinguish between names based on case alone. For example, you cannot have two files in the same directory named sample.txt and Sample.txt because Windows regards the names to be identical for the purposes of identifying files. The UNIX operating system, on the other hand, is fully case sensitive, and so UNIX computers distinguish between object names when the only difference between those names is the case of characters used in the object names. On most UNIX computers, therefore, sample.txt and Sample.txt could appear in the same directory, and the UNIX computer would distinguish between them when performing operations on the files. For example, the command rm S*.txt would delete Sample.txt but not sample.txt.

In order to implement typical UNIX behavior, the SUA subsystem is normally case sensitive when working with file names. This can present security issues, particularly for Windows users who are accustomed to the case-insensitive conventions of Windows. For example, a Trojan horse version of edit.exe named EDIT.EXE could be stored in the same directory as edit.exe. If a user were to type edit at a Windows command prompt, the Trojan horse version (EDIT.EXE) could be executed instead of the standard version. If case sensitivity is enabled, Windows users should be made aware of this possibility.

In Windows Server 2003, the default behavior of subsystems other than the Win32 subsystem is to be case preserving but case insensitive; in previous versions of Windows, such subsystems were fully case sensitive by default. In order to support standard UNIX behavior, you have to do the following to enable Case sensitivity.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To enable Case-Sensitivity:

    click Start -> Run. type regedit.

    traverse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\kernel

    Double Click on obcaseinsensitive -> Set the value to 0.

To disable Case-Sensitivity:

    click Start -> Run. type regedit.

    traverse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\kernel

    Double Click on obcaseinsensitive -> Set the value to 1.

 Notes:

•     you need administrator privileges to do this.
•     You will have to restart the machine for this setting to take effect.

About setuid behavior for (chown & chmod) SUA programs

According to the POSIX standard, a file has permissions that include bits to set a UID (setuid) and set a GID (setgid) when the file is executed. If either or both bits are set on a file, and a process executes that file, the process gains the UID or GID of the file. When used carefully, this mechanism allows a nonprivileged user to execute programs that run with the higher privileges of the file's owner or group. When used incorrectly, however, this can present security risks by allowing nonprivileged users to perform actions that should only be performed by an administrator. For this reason, Utilities and SDK for Subsystem for UNIX-based Applications Setup does not enable support for this mechanism by default.

You should enable support for setuid behavior only if you are sure you will be running programs that require support for this behavior. Even if you do not enable support for setuid behavior when installing Utilities and SDK for Subsystem for UNIX-based Applications, you can enable it later.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To enable Setuid:

    click Start -> Run. type regedit.

    traverse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SUA

    Double Click on EnableSetuidBinaries -> Set the value to 1.

To disable Setuid:

    click Start -> Run. type regedit.

    traverse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SUA

    Double Click on EnableSetuidBinaries -> Set the value to 0.

Notes:

•     you need administrator privileges to do this.
•     You will have to restart the machine for this setting to take effect.
•     This is deprecated for the current release, since this has a security impact.

About Console2

Installation

Refer to their web site.

Environment Variables

You can add to PATH the installation path using CONSOLE_PATH:
set CONSOLE_PATH=D:\Console2\