On Thu, 26 Mar 1998, Bradley, Greg wrote:
>> How? The kernel starts init (
>Before we can load the kernel, we need a bootstrap in the bios. Is this
>part of the operating system as well?
No, it's part of the BIOS.
>> Huh?
>The program, init, is a user input. Put a different program there called
>init and something different happens, according the the users input,
>ie the program init.
Put a different kernel there and something completely different happens.
Is the kernel then not part of the operating system?
[...]
>No program defines the Windows 95 operating system because Windows 95
>is NOT an operating system. Windows 95 is an application running on the
>msdos OPERATING SYSTEM.
Then what one program defines MS-DOS? COMMAND.COM?
>MSDOS boots, manages memory, peripherals and accepts and acts on user
>input. It can do all of these things without any of the windows 95
>application in place.
Odd. If I "exit" Windows 95 to a DOS prompt, I can no longer access
my CD-ROM and have to load a driver for my sound card. Similarly,
if I boot to a command line rather than going into "the Windows 95
application running on top of MS-DOS", I also cannot access various
components of my hardware. Apparently MS-DOS is incapable of managing
these peripherals on its own.
>Windows 95 on the other hand can do nothing if I remove the msdos
>operating system from underneath it. I can however unplug msdos and
>replace it with some other OPERATING SYSTEM and windows will work fine.
First you need to identify what it is you're replacing. What ONE FILE
are you replacing?
And I also speculate that the Windows 95 virtual machine assumes control
of the system once Windows 95 starts. MS-DOS 7 only acts as a overpowered
boot loader.
--
Steve Coile
[EMAIL PROTECTED]
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.