Цитата(/Geo @ 4.5.2016, 19:55)
это всё прекрасно, только сложно и на тоненького.
давайте проще - ДОС без Вин95 работает? Вин95 без ДОС запустится?
но если хотите и настаиваете, то я не прочь, Вы правы.
Для меня os это прежде всего управление запускаемыми приложениями, предоставление приложениям процессорного времени, памяти, доступ к тем же дискам дело вторичное. Есть системы(например встроенные ) где никаких дисков, пользовательского интерфейса нет в принципе - из флеша загружается OS и приложения, которые крутятся и управляют разными девайсами.
на сколько я помню в вин 95 была возможность загрузки доса до загрузки винды. и по команде win загружалась уже винда. При этом dos оставался в памяти , хотя и использовался в основном для совсместимости.
опять же из wiki про win 95
Цитата
Dependence on MS-DOS[edit]
To end-users, MS-DOS appears as an underlying component of Windows 95. For example, it is possible to prevent loading the graphical user interface and boot the system into a real-mode MS-DOS environment. This sparked debate amongst users and professionals over the question of to what extent Windows 95 is an operating system or merely a graphical shell running on top of MS-DOS.[14][15][16]
When the graphical user interface is started, the virtual machine manager takes over the filesystem-related and disk-related functionality. MS-DOS itself is demoted to a compatibility layer for 16-bit device drivers.[17] This contrasts with earlier versions of Windows which relies on MS-DOS to perform file and disk access (Windows for Workgroups 3.11 could also largely bypass MS-DOS when 32-bit file access and 32-bit disk access were enabled). Keeping MS-DOS in memory allows Windows 95 to use DOS device drivers when suitable Windows drivers are unavailable. Windows 95 is capable of using all 16-bit Windows 3.x drivers.
Contrary to Windows 3.1x, DOS programs running in Windows 95 do not need DOS drivers for mouse, CD-ROM access and sound card; Windows drivers are used instead. HIMEM.SYS is still required to boot Windows 95. EMM386 and other memory managers, however, are only used by legacy DOS programs. In addition, CONFIG.SYS and AUTOEXEC.BAT settings (aside from HIMEM.SYS) have no effect on Windows programs. DOS games, which could not be executed on Windows 3.x, can run inside Windows 95. (Games tended to lock up Windows 3.x or cause other problems). As with Windows 3.x, DOS programs that use EGA or VGA graphics modes run in windowed mode (CGA and text mode programs can continue to run).
On startup, the MS-DOS component in Windows 95 responds to a pressed F8 key by temporarily pausing the default boot process and presenting the DOS boot options menu, allowing the user to continue starting Windows normally, start Windows in safe mode or exit to the DOS prompt.[14] As in previous versions of MS-DOS, there is no 32-bit support and DOS drivers must be loaded for mice and other hardware.
As a consequence of being DOS-based, Windows 95 has to keep internal DOS data structures synchronized with those of Windows 95. When starting a program, even a native 32-bit Windows program, MS-DOS momentarily executes to create a data structure known as the Program Segment Prefix. It is even possible for MS-DOS to run out of conventional memory while doing so, preventing the program from launching.[14] Windows 3.x allocated fixed segments in conventional memory first. Since the segments were allocated as fixed, Windows could not move them, which would prevent any more programs from launching.
Microsoft partially removed support for File Control Blocks (an API hold-over of DOS 1.x and CP/M) in Windows 95 OSR 2, [OEM Service Release 2, where OEM stands for Original Equipment Manufacturer]. FCB functions cannot write to FAT32 volumes, only read them.