🚀 go-pugleaf

Andrzej Niemiec wrote:
> 
> Czy ktos zna referencje do mozliwie najdokladniejszego opisu startu W95
> (co sie i kiedy uruchamia, ktore zbiory sie otwaieraja i po co itp...
C:\bootlog.txt :)))) Nie jest tylko napisane po co. 
> ---> Andrzej Niemiec <---

__
Stefan - Tomasz Stafinski
Politechnika Lubelska
E-mail:stefan@pluton.pol.lublin.pl

Tomasz Stafinski <stefan@pluton.pol.lublin.pl> wrote in article 
> > Czy ktos zna referencje do mozliwie najdokladniejszego opisu startu W95
> C:\bootlog.txt :)))) Nie jest tylko napisane po co. 


Ani nie wiadomo , co robia i za co sa odpowiedzialne poszczegolne systemy,
ani tez,
co dzieje sie w sytuacji awaryjnej- por. opis startu systemow typu MVS,
Georg3, UNIX,  VM, i podobnych- w koncu W95 potrzebuje wiecej zasobow niz
mial dobry stary komputer typu IBM4381 i podobne
Ponawiam prosbe.

Ponizej pare wyciec z MS Windows 95 Resource Kit:

Setup Technical Discussion
  Windows 95 Startup Process

Windows 95 includes new system files, Plug and Play mechanisms, and various
options for starting the operating system. This section describes the
Windows 95 system startup sequence.
During the real-mode startup process, devices use only static
configurations; that is, no dynamic resource allocation or arbitration is
provided. When the system startup process switches to protected mode,
Configuration Manager ensures all devices are configured properly, as
described in Windows 95 Architecture.

The system startup includes four phases:

ˇ	Bootstrapping the system with BIOS in control
ˇ	Loading MS-DOS drivers and TSRs for compatibility
ˇ	Initializing static VxDs in real mode 
ˇ	Putting the protected-mode operating system in control and loading the
remaining VxDs



Setup Technical Discussion
  Windows 95 Startup Process
    Bootstrapping in the BIOS Phase

Microsoft worked with several hardware manufacturers to define a new Plug
and Play BIOS specification, which defines the interactions among a Plug
and Play BIOS, Plug and Play devices, and option ROMs (sometimes called
adapter ROMs). The Plug and Play BIOS enables and configures Plug and Play
boot devices. The Plug and Play BIOS also passes configuration information
to Configuration Manager in Windows 95 for configuring the remaining
adapters and devices.

Setup Technical Discussion
  Windows 95 Startup Process
    Bootstrapping in the BIOS Phase
      Booting with a Legacy BIOS

For legacy computers that do not have Plug and Play BIOS, the BIOS enables
all devices on the ISA bus. A Plug and Play ISA card that has an option ROM
must start up when the computer is turned on with the option ROM enabled. 

Setup Technical Discussion
  Windows 95 Startup Process
    Bootstrapping in the BIOS Phase
      Booting with a Plug and Play BIOS

A Plug and Play BIOS accesses nonvolatile RAM to determine which Plug and
Play ISA cards should be enabled, where their option ROMs should be mapped,
and what I/O, DMA, and other assignments are to be given to the cards. 
The BIOS then programs the Plug and Play cards before the power-on
self-test (POST). All cards that do not have configurations stored in the
BIOS are disabled completely, reducing the chance of a conflict. 
The Plug and Play BIOS also configures all devices on the motherboard. Some
devices might have been disabled or assigned to different I/O addresses,
IRQ settings, and so on, by Configuration Manager.

Setup Technical Discussion
  Windows 95 Startup Process
    Loading Hardware Profiles and Real-Mode Drivers

After BIOS initialization, the operating system attempts to determine the
current configuration, including whether the computer is a docking station.
This is done by using a hardware profile that Windows 95 selects before
CONFIG.SYS is processed. The hardware profile is built by a detection
process that collects information about interrupt usage, BIOS serial and
parallel ports, BIOS computer identification, Plug and Play BIOS
docking-station data, and, if possible, docking-station data that is unique
to each OEM. Then the detection process builds a 2-byte value known as the
current hardware profile (or the current configuration).

Each hardware profile has a name that matches a top-level menu item in a
multiconfigured CONFIG.SYS file (that is, the long text in the menu, not
the section name enclosed in square brackets). Windows 95 automatically
selects that multiconfiguration menu item and processes the corresponding
section of CONFIG.SYS. 
CONFIG.SYS and AUTOEXEC.BAT are processed at this point. Although these
files are not required for Windows 95, they are used for backward
compatibility with applications created for MS-DOS or Windows 3.x. In
Windows 95, CONFIG.SYS and AUTOEXEC.BAT are processed much like they are
processed under MS-DOS 6.x. Drivers and TSRs specified in these files are
loaded in real mode. 

For more information, see System Startup Files.



Note  The real-mode MS-DOS errors are standard, as documented in the MS-DOS
6.0 Programmer’s Reference.



Setup Technical Discussion
  Windows 95 Startup Process
    Initializing Static VxDs at Startup

Windows 95 supports static VxDs that load during system startup in the same
way as Windows 3.x VxDs, and it also supports dynamically loaded VxDs.
VMM32.VXD includes the real-mode loader, the executable Virtual Machine
Manager, and common static VxDs. Notice, however, that if a VxD file is in
the Windows SYSTEM\VMM32 directory, Windows 95 loads it in addition to the
combined VxDs in MRCI2.VXD.



Note  If you want to update a VxD that has been bound into the monolithic
VMM32.VXD, place the VxD file in the SYSTEM\VMM32 directory. Windows 95
always checks that directory and uses any individual VxDs it finds instead
of loading those bound in VMM32.VXD.



The following list shows the VxDs typically combined to create VMM32.VXD.
(A custom list is built for each computer.) These drivers used to be
specified in the [386enh] section of SYSTEM.INI.

Typical VxDs Combined to Create VMM32.VXD

		
*biosxlat
*configmg
*dynapage
*ebios
*ifsmgr
*int13	*ios
*parity
*reboot
*vcache
*vcomm
*vcond	*vdd
*vdef
*vfat
*vfbackup
*vkd
*vmcpd	*vmouse
*vmpoll
*vsd
*vtdapi
*vwin32
*vxdldr
VMM32 loads VxDs in three steps:

ˇ	VMM32 loads base drivers specified in the Registry, which contains
entries for every VxD not directly associated with any hardware. VxDs are
located in this branch of the Registry:

Hkey_Local_Machine\System\CurrentControlSet\Services\VxD 


ˇ	If VMM32 finds a value StaticVxD= in any Registry key, it loads that VxD
and runs its real-mode initialization. For example, the following entry
loads *V86MMGR:

SYSTEM\CurrentControlSet\Services\VxD\V86MemoryManger
	Description=MS-DOS Virtual 8086 Memory Manager
	Manufacturer=Microsoft
	StaticVxD=*V86MMGR
	EMMEXCLUDE=E000-EFFF


ˇ	VMM32 loads the static VxDs specified in the device=*VxD lines in the
[386enh] section of SYSTEM.INI. These VxDs are actually loaded from VMM32,
and appear in SYSTEM.INI only for backward compatibility.

If a specific device conflicts with a device loaded from the Registry, the
device specified in SYSTEM.INI takes precedence. However, if the device
specified in SYSTEM.INI cannot be found, an error will occur.
Many Windows 95 driver models, such as IOS (for disk drivers) and the
network, support dynamically loaded device drivers. These VxDs are not
loaded by the VMM32 real-mode loader, but are loaded by a device loader
that is responsible for loading and initializing the drivers at the correct
time and in the correct order. 

For example, for SCSI adapter miniport drivers, the device loader is *IOS.
The entries for a SCSI adapter are found in this Registry key:

Hkey_Local_Machine\System\CurrentControlSet\Services\Class


Because there is no StaticVxD=xxx line in this Registry entry, the VMM32
real-mode loader does nothing when Windows 95 identifies this device. 
Configuration Manager attempts to find any device node that has a
DevLoader= entry in the Registry. The device loader (in the previous
example, *IOS) examines the Registry, finds the PortDriver= entry, loads
the driver and any associated support drivers, and initializes the adapter.


Setup Technical Discussion
  Windows 95 Startup Process
    Loading the Protected-Mode Operating System at Startup

In the previous phase, these elements of the operating system were loaded:

ˇ	WIN.COM, which controls the initial checks and loading of the core
Windows 95 components
ˇ	VMM32.VXD, which creates virtual machines and initiates VxD loading
ˇ	SYSTEM.INI, which is read for entries that differ from Registry entries

After all static VxDs are loaded, VMM32.VXD switches the processor to
operate in protected mode, and the last phase of the boot process begins.
This phase involves loading the protected-mode components of the operating
system. 

Setup Technical Discussion
  Windows 95 Startup Process
    Loading the Protected-Mode Operating System at Startup
      Loading Protected-Mode VxDs at Startup

The protected-mode Configuration Manager is initialized for importing
configuration information from a Plug and Play BIOS (if available);
otherwise, it develops the Plug and Play hardware tree by enumerating
devices and loading dynamically loadable device drivers. These device
drivers are identified by loading drivers from a specific directory. 
The next phase resolves device resource conflicts for every device in the
tree and then informs the devices of their configuration. When all devices
have been enumerated, all conflicts have been resolved, and all devices
have been initialized, Windows 95 is ready to be used. 

Setup Technical Discussion
  Windows 95 Startup Process
    Loading the Protected-Mode Operating System at Startup
      Loading the Final System Components at Startup

The remaining Windows 95 system components are loaded in the following
sequence:

ˇ	KERNEL32.DLL provides the main Windows components, and KRNL386.EXE loads
the Windows device drivers
ˇ	GDI.EXE and GDI32.EXE provide the graphic device interface code 
ˇ	USER.EXE and USER32.EXE provide the user interface code
ˇ	Associated resources, such as fonts, are loaded
ˇ	WIN.INI values are checked
ˇ	The shell and desktop components are loaded

At this point, a prompt appears so that you can log on by typing a user
name and a password. After you log on, Windows 95 can process user-specific
configuration information. If you do not log on, default settings are used.
If Windows 95 is configured for network logon, the unified Windows 95 logon
can be used to log on to the network during this process.
After Windows 95 is loaded and you log on, the STARTUP directory is
processed.


Andrzej Niemiec <prim@infonet.wroc.pl> wrote in article
<01bc032d$68375680$d01bb5c2@primppp.infonet.wroc.pl>...
> 
> 
> Tomasz Stafinski <stefan@pluton.pol.lublin.pl> wrote in article 
> > > Czy ktos zna referencje do mozliwie najdokladniejszego opisu startu
W95
> > C:\bootlog.txt :)))) Nie jest tylko napisane po co. 
> 
> 
> Ani nie wiadomo , co robia i za co sa odpowiedzialne poszczegolne
systemy,
> ani tez,
> co dzieje sie w sytuacji awaryjnej- por. opis startu systemow typu MVS,
> Georg3, UNIX,  VM, i podobnych- w koncu W95 potrzebuje wiecej zasobow niz
> mial dobry stary komputer typu IBM4381 i podobne
> Ponawiam prosbe.
>