UWIN
Computer software package for Unix programs on Windows
UWIN is a computer software package created by David Korn which allows programs written for the operating system Unix to be built and run on Microsoft Windows with few, if any, changes. Some of the software development was subcontracted to Wipro, India. References, correct or not, to the software as U/Win and AT&T Unix for Windows can be found in some cases, especially from the early days of its existence.
UWIN source is available under the open source Eclipse Public License 1.0 at AT&T's AST/UWIN repositories on GitHub.
UWIN 5 is distributed with the FireCMD enhanced Windows shell with the Korn Shell thereof as one of three default shells present at install, the others being the FireCMD scripting language and the default Windows command shell cmd.exe. Other UWIN shells like csh and tclsh and those of other interoperability suites like MKS Toolkit and other shells like those that come with Tcl, Lua, Python and Ruby distributions inter alia can be added to the menu by the user/administrator.
Technical details
Technically, it is an X/Open library for the Windows 32-bit application programming interface (API), called Win32.
UWIN contains:
Libraries that emulate a Unix environment by implementing the Unix API
Include files and development tools such as cc(1), yacc(1), lex(1), and make(1).
ksh(1) (the Korn Shell) and over 250 utilities such as ls(1), sed(1), cp(1), stty(1), etc.
Most of the Unix API is implemented by the POSIX.DLL dynamically loaded (shared) library.
Begin with the source’s own compact description: “UWIN” is computer software package for Unix programs on Windows. The dossier treats that line as a proposition to test through UWIN, Computer and software, not as a finished interpretation.
Why this record matters
The phrase “computer software package for Unix programs on Windows” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Datasets, specimens, observations and peer-reviewed methods provide the appropriate test for the technical claims summarized here. The source revision retrieved here is dated Sep 12, 2026. The linked authority identifier is Q1922446. None of the 0 selected statements returned an explicit reference.
Current terminology should not be projected backward without checking the classification used when the underlying evidence was created. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.
- Current terminology
- Classification context
- Finding cited technical literature
Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.
Three-step research path
- Establish the record: confirm the title “UWIN”, its source revision and the description used here.
- Expand the search: follow UWIN primary sources, UWIN archive and UWIN research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “UWIN”?
- Has classification or technical consensus changed since the cited source?
- Is the terminology current, historical or disputed?
Search terms from this dossier
This entry incorporates text from “UWIN” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.