Revision as of 13:07, 19 November 2019 edit InternetArchiveBot (talk \| contribs) Bots, Pending changes reviewers 5,671,925 edits Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0 ← Previous edit		Revision as of 14:51, 15 February 2020 edit undo Matthiaspaul (talk \| contribs) Autopatrolled, Extended confirmed users, Page movers, New page reviewers, Pending changes reviewers, Rollbackers, Template editors 137,876 edits →The DOS API and Windows: CE, DOS is far more than a boot loader in Windows 9x, even at runtime the protected mode portion of the system vitally depends on it and could not function without it Next edit →
Line 7: ==The DOS API and Windows== In [[Windows 9x]], DOS ~~was generally used as a bootloader which~~ loaded the protected-mode ~~operating~~ system and graphical shell. DOS was usually accessed from a [[virtual DOS machine]] (VDM) but it was also possible to boot directly to real mode MS-DOS 7.0 without loading Windows. The DOS API was extended with enhanced internationalization support and [[long filename]] support, though the long filename support was only available in a VDM. With [[Windows 95]] OSR2, DOS was updated to 7.1, which added [[FAT32]] support, and functions were added to the DOS API to support this. [[Windows 98]] and [[Windows ME]] also implement the MS-DOS 7.1 API, though Windows ME reports itself as MS-DOS 8.0. [[Windows NT]] and the systems based on it (e.g. [[Windows XP]] and [[Windows Vista]]) are not based on MS-DOS, but use a [[virtual machine]], [[NTVDM]], to handle the DOS API. NTVDM works by running a DOS program in [[virtual 8086 mode]] (an emulation of [[real mode]] within [[protected mode]] available on [[Intel 80386\|80386]] and higher processors). NTVDM supports the DOS 5.0 API. [[DOSEMU]] for [[Linux]] uses a similar approach.

DOS API: Difference between revisions