The development environment included support for C, C++ and Fortran. Threading was supported using the Pthreads model.
Additional languages could be obtained (Python, Ruby, Tcl, etc.). Unix-based software packaging and build tools were available for installing or creating pre-build software packages.
Starting with release 5.2 (Server 2003/R2) the following capabilities were added:[6]
"Mixed mode" for linking Unix programs with Windows DLLs
Traditional support was provided by Microsoft for a fee or service contract, though released hotfixes can usually be obtained free of charge from Microsoft. Previously, free support could be found via the forums at the SUA Community site[7] and with the FAQ,[8] however this appears to have been withdrawn.
Additional pre-built applications and development libraries could be obtained for free from the SUA Community site, the Gentoo-prefix site and the Debian-Interix site. These included commonly used applications not part of the Microsoft installation such as OpenSSH, Git, Python and bash.
The SUA Community site included for developers of Interix and the site has been contracted by Microsoft for several Interix and SUA updates of utilities and documentation.
This product began to be developed in 1996 under the product name OpenNT by Softway Systems, Inc. before the name was changed to Interix in 1998. The last release by Softway Systems was release 2.2. Softway Systems had virtually completed the next release code-named Firebrand in 1999 which became the basis of Interix 3.0.
The Interix interoperability suite developed by Softway Systems Inc., included substantial code from OpenBSD,.[9][10] Microsoft acquired Interix in 1999.[11][12]
Microsoft continued to distribute Interix 2.2 as a standalone product until 2002.
Interix release 3.0 was released as component of Windows Services for Unix (SFU) 3.0 in 2002. Interix release 3.5 was released as component of SFU 3.5 in January, 2004.
Microsoft announced in 2011 that Interix would not be included in Windows versions after Windows 8 and customers should start migrating their applications to an alternative solution.[13]
Walli, Stephen R. (August 1997). "OPENNT: UNIX application portability to Windows NT via an alternative environment subsystem". In Lazowska, Ed; Jones, Michael B. (eds.). Proceedings of the USENIX Windows NT Symposium. 1997. Berkeley, CA: USENIX Association.