(Reprinted
· Old Watt ·· Yesky)
Since Win 95, Microsoft adheres to the WIN 9X system kernel technology, and users are difficult to obtain a more underlying technical information of WIN 9X boot process. It is always a black process. Mastering the system's startup process is the key to the comprehensive control system and optimization system. Now, according to the disclosed technical data and practical experience, only from the application angle, for WIN 9X (including 95,96 (95osr1), 97 (95 OSR2.x), The startup process of 98,98se is fully revealed and the necessary descriptions are added to the details.
The WIN 9X family is mainly composed of four versions, of which Windows 95 is the first version, which has created a new era of PC, and pushed Bill Gates to the throne of the world. This version is not perfect, bugs are the most, starting to provide a correction package after launching more than a month.
Win 96 is the OSR1 version of Win 95 (called 96, because it is posted in 1996, 97), this version almost rewrites Win 95's kernel, correcting various issues in practical applications, Since the Win 95 is released too close, there is no energy.
Win 97 is OSR2.x, which has a qualitative leap, which provides a new disk format FAT 32, integrated Internet browser IE 3.0, which indicates that Microsoft's system development strategy begins to turn to the Internet . OSR2.X has three versions, namely OSR2.0, OSR2.1 and OSR2.5, where OSR2.1 supports USB and AGP graphics, OSR2.5 provides IE4.0. Since FAT 32 makes OSR2.x are not compatible with Win 95 and DOS, Microsoft only does it as an OEM product without providing retail versions, Win 97 is therefore the most popular version after WIN 95.
Win 98 is the last glory of the Windows series with DOS. It combines Internet technology and operating systems while providing IE4.0 and DirectX5.0, but there is no more exciting thing, it is more like Win 97's retail version.
Win 98 S is the second edition of Win 98, compared with WIN 98, but only provides IE5.0 and DirectX6.1a, there is no new meaning.
Windows 2000 is a Windows NT based network operating system, which is already very different from Win9x, and the new Windows Me is a replacement product of Windows 9X, but except for the interface of Windows 2000, there is no update. Discovery.
The WIN 9X version is complicated, but its core is maintained, there is no fundamental change, and the startup process is almost identical, which is the basis for this article.
First, Win 9X startup overview
The WIN 9X startup process inherits the tradition of DOS and has the necessary expansion, mainly composed of two phases, ie the extended DOS real mode start and GUI (ie graphic interface) 32-bit protection mode startup, Win 9X technology core concentration In the latter stage.
The startup process is in turn, which is completed by boot record, IO.sys, msdos.sys, command.com, config.sys, autoexec.bat, gui launch command win.com and other necessary related files, where the system files with DOS are completely the same name The file actually has a change in quality.
Win 95/96 provides a thorough dual boot function, that is, the user can start the system in two ways of WIN 95/96 and DOS (6.22) (6.22 or less), uninterrupted, solve the compatibility of the new and old system, and maximize the user Interests. However, in order to gradually get rid of the influence of backward DOS on the PC world, from Win 97, Microsoft tries to limit the dual boot function, so that the WIN 97/98 startup system must be modified to achieve dual boot. Currently, dual boot functions are actually less and less. Second, the role of boot recording boot record is to transfer the core file of the operating system into memory to start the system. Both all system boot records are located at the start of the disk. When the microcomputer is powered on, the boot record is transferred directly from the fixed position to the memory, and the boot system is started. The guidance records of different versions of the system are naturally different. The version of the DOS boot record is MSDOS 5.0, supporting FAT 12 (each version is used for hard disk or less than 16m hard drive), FAT 16 disk format, the specified system boot file is IO.SYS, MSDOS.SYS. Win 95/96 guidance records are fully compatible with DOS (6.22 stand-alone versions), version logo is mswin4.0, support FAT 12, FAT 16 disk format, support dual boot, the specified boot file is WinBoot.sys (IO. The file name when using the old version of DOS) and IO.SYS, MSDOS.sys. The guidance record of WIN 97/98 has the difference between DOS. The version mark is mswin4.1, using 32-bit instruction code, supports FAT 12, FAT 16 and FAT 32, fixed boot IO.SYS, which causes Without modification, Win 97/98 cannot directly support dual boot. WIN 97/98's new disk format FAT 32 can support large-capacity hard drives, canceled the capacity limit of FAT 16, is completely incompatible with traditional FAT 16, of course, cannot be identified for DOS, Windows 95/96. In this disk format, the original DOS, Windows 95/96 software can operate normally, but software such as disk tools such as disk tools, etc. cannot be continued. Since the mainstream hard disk capacity is more than 8.4g, the application of FAT 32 is getting wider and wider. Third, IO.SYS 1, IO.SYS's internal launch menu WIN 9X IO.SYS is merged by the original DOS system file IO.SYS, MSDOS.SYS, providing standard hardware input / output interface and DOS interrupt calls The function is fully enhanced, which basically controls the full startup process of WIN 9X, which is the core file of Windows DOS real mode. But it needs to achieve a normal startup process according to the setting of MSDOS.sys. IO.SYS can change the startup process by the startup function key, these function keys correspond to the startup menu:
The function key corresponds to the startup menu item F4: Previous MS-DOS VERSIONF5: SAFE MODESHIFT F5: COMMAND Prompt Only F6: Safe Mode with network supportf8: Start up the startup menu Shift F8: Step-by-step confirmation system startup "Starting Windows 95 ..." Press the function key to
IO.SYS provides the startup selection menu for easy users to select boot mode as needed: (1) Normal startup mode (default startup mode) When bootwin = 0 in MSDOS.sys, select this system will start the old version of DOS (2 )Logged (bootlog.txt ) Normal start mode, and simultaneously form bootlog.txt bootlog.txt recorded all situations occurring during the startup process, which is the only comprehensive diagnostic record of the Win 9X system startup process, which can check the problem during the startup process. (4Afe Mode) GUI of the security mode, the screen quarter is "safe mode" word does not load config.sys, autoexec.bat, nor load any programs in the startup program group, only load the most basic hardware configuration (standard VGA mode, no sound card, optical drive, etc.) The simplest GUI starts, for correcting the GUI startup problem caused by hardware configuration, and the like. When the problem occurs normally, in most cases, it will enter the launch mode, but the problem can be solved very limited, and the configuration system configuration for the display is mainly adjusted on the control panel. To enter the normal GUI, you must restart the ⑷step-by-step confirmation single-step execution of Windows boot to determine the startup failure caused by the corruption of the system file, this mode can only determine the system problem during the DOS startup process, mainly correct config.sys And the problems existing in AutoExec.bat To determine the problem during the GUI startup process, only the full real-in-instant DOS boot process can only be performed with the bootlog.txt file ⑸command prompt only, enter the pure DOS state to load all the DOS drivers that WIN boot It is mainly used to run only applications in pure DOS mode or solve serious system problems. You can use the command WIN to boot the normal GUI RAFE MODE COMMAND Prompt Only to start only the most basic IO.SYS, MSDOS. Sys and Command.com three system files, do not load the default driver (Himem.sys, ifshlp.exe, and setver.exe) and config.sys, autoexec.bat, other environment default values with Win 9X settings, The mode cannot continue to start the normal or secure mode of GUI, which is mainly used to process the most serious system failure. ⑺PREVIOS MS-DOS VERSION boots the old DOS, performs five original DOS system files saved in .dos as the extension in the root directory.
The appearance of this option is controlled by the parameter "bootmulti" in msdos.sys: When bootwin = 0 in MSDOS.sys, select this item will start the normal WIN 9X system ⑻safe mode with network support with the security of the mode network access Mode This option The appearance of this option is controlled by the parameter "network" in msdos.sys to troubleshoot the PC failure of the network system. You can obtain a larger system support by real mode network systems. 2. Extended DOS default configuration provided by IO.SYS. IO.SYS is at the maximum difference between DOS when starting, providing the default config.sys configuration that meets most DOS applications, can automatically load the necessary drivers to ensure that Win 9X is started normally, the specific content is as follows: Himem.sys : Supports more than 1M memory, providing extended memory (XMS) management to ensure that Win startup required file DBLBuff.sys: Dual Cache Driver, only load, more to support SCSI card ifshlp.exe: Enhanced file management driver, support WIN's VFAT system guarantees the required files setver.exe: version login service, eliminating version restrictions, using DBLSPACE.BIN: DOS 6.0 disk compression driver only on DOS, only load DRVSPACE.BIN when the hard disk is compressed: DOS 6.22 disk compression driver, with DOS = high, UMB: Move the DOS system into HMA to leave more conventional memory without any function, and the real file = 30: Maximum file that can be opened Number, can meet most applications only for DOS, WIN 9X does not need buffers = 30: Set the maximum number of disk buffers, can meet most applications only DOS, Win 9x does not need FCBS = 4: file control block Number, is now very small, only for DOS using LastDrive = Z: Maximum disk setting, this value is set too small, will not be able to load the optical drive stacks = 9,256: Set the number of stacks, size, this setting is used as the old program to use Win 9x The system does not need shell = command.com / P: Specifies the system environment settings provided by WIN 9X command line handler IO.sys as follows: Command Logging Path: Path = C: / Windows; C: / Windows / CommandDoS prompt: prompt = $ P $ G Time File Directory: Temp = TMP = C: / Windows / Temp Command line handler location: comsepc = c: /windows/command/command.comio.sys provides a relatively complete system configuration to cancel CONFIG.SYS, AUTOEXEC. BAT becomes possible. For compatibility, IO.SYS does not load the EMM386.EXE driver without providing expansion memory EMS and upper memory UMB. Emm386.exe may cause a system crash when searching for new hardware, and there is no problem in daily use.
3, IO.SYS Launch Process (1) When the system starts, IO.SYS displays "Starting Windows 95 ...", at which time the startup function key is selected. (2) I.sys Determine the start mode according to the configuration of the launch menu and the configuration of MSDos.sys. (3) If the original DOS system is used, IO.SYS automatically activates the DOS and WIN 9X system boot files, and then starts from the original DOS control system. (Ie the dual boot process of WIN 9X is ultimately completed by IO.SYS control, with guidance records, etc.) ⑷io.sys is first configured by config.sys first according to the start mode, if config.sys is not loaded in the win 9x start Required documents (such as Himem.sys, IFSHLP.exe, etc.), the system is automatically loaded according to the default settings. (If you want to load the driver using the extended memory, such as emm386.exe, you must add Himem.sys driver in the first line of Config.sys, otherwise, since the system does not provide extended memory, EMM386.exe and other programs will not be able to run After completing hardware configuration such as config.sys, IO.SYS calls AutoExec.bat through Command.com for software configuration. ⑹ The bootlog.txt of the root directory is completed by IO.SYS control, and some other log files are mostly established when installing the system. ⑺ Automatically call win.com and start the GUI after completing the DOS startup process. Fourth, MSDOS.SYS 1, MSDOS.sys role in WIN 9X, MSDOS.sys becomes a plain text system configuration file for controlling WIN. It can be released in DOS mode (read-only, hidden, system), as needed, as needed. Msdos.sys can be empty files, can even be deleted, of course, the system can only start with pure DOS mode and cannot enter the GUI system. MSDOS.sys default content in different ways, there are four, in which the first three methods have no configuration commands, almost empty files, only to retain one line of comments, this file formation, this Class files are more known in the system floppy disk. Different MSDOS.sys contents are as follows: 1) WIN installation system disk: WIN95EBO2) Format / S built system panel:; format3) SYS A: Pass establishment system disk:; sys4) Establish a system on the hard disk The MSDOS.sys system hard disk is complete, including the necessary startup configuration commands, the file length must be greater than 1024 bytes, which takes more than two disk sectors, this requirement is described in this file to ensure compatibility However, there is no more in-depth introduction. In fact, the document is less than 1024 bytes has no significant impact on the system, which is estimated to ensure that the system is compatible with the old DOS and Win 3.x, this is expected to advise. Use SYS to transfer the system to the hard disk to repair the boot file, will overwrite the boot record, IO.SYS and Command.com, the content of MSDOS.sys remains unchanged, ensuring that the system boot part is fixed, the entire system can still start normally, this Practice is very smart.
2, MSDOS.SYS configuration parameters MSDOS.sys consist of three sections, the configuration parameters are not sequential, the content is as follows: [Paths] Specifies the system file path of Windows WINDIR = Specify the Win 9X system file and its subdirectory Directory The path must include the registry file System.dat and Win 9X startup required drivers, such as WinBootDir, etc. WinBootdir, etc., specify the directory where Win 9X's GUI startup Win.com hostwinbootdrv = Specifies the drive where Win.com is located. No colon (:) uninstallDir = specify the directory where the original system is saved, the recovery of the original system is used to recover the original system in the WIN upgrade version [Options] Specifies the startup method of Windows, / the value of the default logo = 1/0 Allow / disable startup When the WIN 9X flag (LOGO) shields the screen sometimes solves the conflict caused by the third-party memory management program to see the prompt information that appears in the system startup process, which also causes the system to start slightly, start start The WIN 9X flag can be cleared by the ESC key, view the real mode startup information bootkeys = 1/0 Allow / prohibit the start button to change the start-up method to enter the default startup mode, can not use the boot hot key to convert BootGui = 1/0 Start graphics interface GUI / only start DOS 7.x, enter the DOS character interface to 0, which can be provided for DOS 7.x multiple boots, can further start the graphical interface bootwin = 1/0 Start Win 9x / boot old version of DOS, can be replaced as required System file When bootwin = 0, the old version of DOS is started by default. If you select the "Previous MS-DOS VERSION" start menu, you will start Win 9x Note: Bootwin level is higher than bootgui, both conflict, for the former, BootMulti = 0/1 Prohibition / Allow Double Starts, if the "Previous Vertion of MS" item appears in the startup menu, this item will automatically appear from the old DOS upgrade WIN 9X, and set to 1, but for WIN 97/98, if you do not modify the boot system, select this item will cause the system to start the bootMenu = 0/1 system startup whether the startup start selection menu is 1, when startup Will directly pop up the start-up option menu network = 0/1 Startup menu appears "Safe Mode With Network Support" item, "SAFE MODE WITWORK Support" item, "STARTING Windows 95 ..." time before booting The default is 2 seconds for use the start key to change the startup mode. When the value is 0, no prompts directly enter the default startup process, speed up the boot speed, but still use the boot hotkey to select the boot method bootmenudefault = Boot menu use by default Option, the default value is 1 bootmenudlay = Start menu Starts latency, default is 30, unit: second bootsafe =
0/1 The system starts in a secure mode, and the system is directly launched by the system in safe mode to start bootwarn = 1/0 to start when the system is started. When the system is not properly shut down, it is prompted to "should enter the security mode" actually The pattern solves the problem is very limited. The real system problem is unable to solve in this mode. If you don't enter, bootconfig = 1/0 can use single-step configuration mode, its effect is disablelog = 0/1 in "Step-by- STEP config "Does create bootlog.txt 1: Do not ask if" logged "does not ask if you do not create bootlog.txt 0: ask if you create a log file bootlog.txt systemReg = 1/0 system start WINDOWS 9X regist 1 : "STEP-BY-Step Config" Ask if you run the registrar other mode, automatically run the registrar 0: Do not run or ask if you run a Windows 9X registrar, the registrar is running first before the system starts, but runs No, there is no significant impact on the system, and it is unknown loadtop = 1/0 to load Command.com, drvspace.bin, dblspace.bin, etc., such as the memory address conflict in the startup, you can set this value to 0 Class conflicts are mostly loaded by config.sys, autoexec.bat causes autoscan = 1/0 to start SCANDISK (effective only if Win 97/98 is valid) cancels automatically detects the hard disk when it is started. Of course, it can be exempted from some troubles, but it does bring hidden dangers to the system, or don't close whether DoubleBuffers = 1/2/0 is loaded with bdlbuff.sys, provide dual cache support 0: No; 1: When needed, if necessary SCSI card, etc .; 2: Unconditionally provide dual cache dblspace = 1/0 Allow DBLSPACE.BIN compression drive (DOS6.0, 6.2) drvspace = 1/0 Allow DRVSPACE.BIN compression disk drive (DOS6.22) Win 9X) pressure The shrinkage reduces the overall performance of the system, more increased the risk of data in the hard disk capacity. Today, it is still not compressed as a wonderful note, FAT32 does not support any disk compression software Winver = indicates that the Windows version officially launched the third part Composed of any character with a semicolon ";", it is a notes line in MSDOS.sys, which is not worthwhile to ensure that the system is greater than 1024 bytes for the system. Most of the parameters provided by MSDOS.sys is used to adjust the system. For ordinary users, it is common to include several parameters before NetWork. V. Command.com command.com is the DOS Housle program (shell) in Windows 9x, which only adds some internal commands, no updated things than DOS 6.22.
IO.SYS has a fundamental change for the process of Command.com. When Win 9X loads EMM386.EXE driver in Config.sys, Command.com's residential part is loaded into the HMA, and the traffic part is loaded into the UMB. (In DOS6.22, Command.com can only load the resident part into the HMA), which will provide a greater regular memory for the DOS program, nor does it need to repeatedly restore the temporary part of the disable, effectively improve the system performance. Of course, if EMM386.exe is not loaded, the system does not provide UMB, and the temporary part of Command.com can only be placed on the high end of conventional memory as DOS6.22. Sixth, config.sys and autoexec.bat win 9x's Config.sys, Autoexec.Bat's roles are the same as DOS, used to assemble all DOS real mode drivers and applications, or modify the default configuration of IO.SYS. Among them, config.sys is primarily used for hardware configurations, and Autoexec.Bat is mainly used for software configuration, which is used in the I.SYS section during the startup process. After win 9X starts, the configuration of these two files is always reserved in the system under the system, which determines all DOS, Win 16 applications under WIN 9X. If there is no DOS global setting, the DOS application under the Windows window will use the default settings of WIN 9X, of course, can also be configured separately by the user. Note that the PATH, SET and other environment settings required by the DOS software can be set separately in the properties of the respective windows; the 16-bit Win 3.x software needs the PATH, SET and other environment settings that can only be set in AutoExec.bat. Win 9X has added a lot of configuration commands, making real mode DOS environments easier to optimize, each configuration command see system directory / Windows config.txt description, no longer said more. Win 9X is unified by VXD (Virtual Device Drive), DLL (Dynamic Link Library) and other protected mode drivers, hardware resources, basically no real mode program support. The real mode program is mainly reserved for some old devices. The presence of the real mode program makes WIN 9X frequently converts frequently between protection mode and real mode, which greatly reduces system performance, more damaged system stability, so we should try to install the real mode program when starting. Win 9X's default settings for the DOS environment can meet most DOS software needs, try to delete the contents of these two files after completing WIN 9X installation. Delete the real mode program, try to implement Win 9X protection mode driver, allowing Win 9X to be high performance, highly stable optimized operation. There is no CONFIG.SYS, and the DOS system of Autoexec.Bat is almost all, and there is no better Win 9X performance. In WIN 9X, they are mainly reserved for support for the original DOS software and an old device. At present, most newspapers are recommended to completely delete these two files, which is actually a problem, and the specific analysis see "Computer", computer master "'99, October. Seven, win.com win.com is Windows GUI start command, from the file name, this is a pure DOS command, which is also the only COM file in the GUI system. This command is the interface command of the DOS and GUI, which is mainly used to load the virtual device driver VMM32.vxd of the protection mode (which is combined by multiple subroutines, so that the CPU is running in the protection mode), and the GUI startup Various problems, it controls the entire transfer process of the system.
All kinds of startup switches provided by Win.com are mainly used to determine the system failure, which will reduce system performance: Win [/ d: [f] [M] [S] [V] [x]] / d When Windows is not normal Used to find a failure reason: f Turn off 32-bit disk access mode, which is used to set the 32-bit access hard disk equivalent to setting: 32bitDiskaccess = false.: M Pattern start, equivalent to using the function key F5 start: N Safety mode startup supported by real mode network, equivalent to using the function key F6 start: s Prohibition of Windows uses the ROM address space between F000: 0000 and 1 MB For breakpoints, the breakpoint is equivalent to setting: systemrombreakpoint = false.: V Specifies the startup time by the ROM routine to handle the hard disk controller interrupt is in the system.ini [386ENH] section Setting: VirtualHDIRQ = false.: X: Windows from using all high-end memory (from A000-FFF) to set up the memory conflict problem in system.ini [3861] section: EmmexClude = A000-FFF.
Eight, the GUI boot process of the GUI started WIN 9X is very complicated, and it is also the core secret of Microsoft, not known for the outsiders. For ordinary users, it is not necessary to fully master this complex and variable mechanism. Here is only a general description of the entire GUI startup mechanism. 1, the GUI configuration file, like all complex systems, WIN 9X is mainly based on system configuration files to combine systems to ensure the system is operating normally. The WIN 9X's GUI system configuration file is in the system registry as the core, in the INI file in each system directory as a secondary configuration. Grasping the system profile and master the core of the system. There are 5 core profiles of the GUI system, namely: Win.ini, System.ini, System.dat, User.Dat, and Polices.dat. Win.ini and System.ini are said to be reserved for Win 3.x's Win 16 Protection Mode Program, Win 3.x's settings in the two files in Win 9x have been moved into the system registry. Win 32 Protection Mode Program is mainly configured by system registry, and does not require support for both files. This approach specifies the development and use of the application, eliminating the confusion of the INI file, which is convenient for the WIN 9X unified management system to increase the stability of the system. But if you delete these two files, Win 9x system can't start, and prompt "I can't find the system.ini file", this shows that Win 9x is started or inseparable from these two files. Win.ini provides various information such as font settings and file associations required by Win 16, mainly completing the corresponding environmental configuration under the GUI, which does not have much impact on Win 9x applications. If this file is not available, Win 9x will automatically generate a simplest. Only a few lines of WIN.INI for configuring the command. System.ini is different, it is the system hardware profile of Win 16, and Win 9x has added some new settings to ensure WIN 16 and WIN 32 coordinated, so that Win 16 can call VXD drivers, this is in Win The system debug parameters provided by .com have been fully embodied. In addition, the driver of the GUI's shell (Shell, XI interface program), mouse, and a monitor, etc. must be loaded with System.ini settings, which determine that System.ini is absolutely unable to delete. This fully proves that Win 9X is a mixture of WIN 16 and WIN 32 and reveals the root cause of the innate fragility in Win 9X system. All settings in Win.ini, System.ini can be found in "New Trend Electronic Essence 1". System.dat and user.dat are so-called system registry files, which is the core file of Win 9x, and Windows is to manage the entire system through it. System.dat saves hardware configuration and software installation information, and user.dat saves information related to the user's personal settings, and the former can only have one, and the latter can have multiple. These two files work together, including all information about the system, when using the registry edit software (such as regedit.exe), the two files are all modified and cannot be separated. Their damage will cause the system to be completely paralyzed and cannot save. Unfortunately, the system registry is very fragile, lacks self-finishing and maintenance mechanism. When the system is run for a while, users often take the road of painful system reconstruction. In WIN 95/96/97, the backup of the registry is system.da0 and user.da0, saved under / windows; in Win 98, Win.ini, System.ini, SiStem.dat and User.dat four The file is merged back to a file RB00? CAB, save 5 under / windows / sysbckup, default to reserve 5.
Each GUI starts automatically updates the backup file, this processing lacks a security management mechanism, it is difficult to ensure that the backup file is not subject to error information, and the backup file is equivalent to the same virtual. Unfortunately, in addition to manual compilation registry software regedit.exe, Win 9X does not provide a more efficient registry maintenance tool. In Win 98, the registry detect software scanreg.exe and scanregw.exe are progress, but it can only process the physical failure of the registry, and cannot solve structural problems. How big is the reliability? Boda's registry should be paired with a monograph, and there is a simple introduction in "New Trend Electronic Essence 1". It will not explain a deeper explanation here. Polices.dat is Microsoft's MSN (Microsoft Network) registration support file, which has little domestic users, which is rarely used. Although there is no more direct information, there is a sufficient reason to prove that during the startup process of WIN 9X, the various INF files saved in the / windows / inflicity are the most powerful support files in the WIN 9X system. In the process of starting the system, Win 9x will call these files in a time to load the corresponding drivers. If there is no such file, Win 9X is also unable to start. In addition, Win 9X PNP technology is mainly installed by the INF file implementation. 2. The startup process of the GUI startup process is mainly composed of three phases: Wininit.exe phase, 16-bit protection mode start and 32-bit protection mode startup. (1) After Wininit.exe phase win.com starts running, first call the WinInit.exe under / windows, which is looking for wininit.ini in the same directory, if there is, according to the file, re-adjust or upgrade the system files to ensure The entire system driver can be updated in a timely manner. This is the main way for Windows systems support PNP technology to implement system drivers upgrade. This process is naturally completed in DOS state. (2) 16-bit protection mode After starting WIN.COM start execution, transfer in / windows / system VMM32.vxd, VMM32.vxd puts the processor in protection mode, start the GUI system according to the configuration of System.ini and the registry 16-bit protection mode. This ensures that the system supports Win16 software, more importantly, the PNP BIOS (Plug and Play BIOS) specification only provides 16-bit protection mode interface, WIN 9X, which is the core of the hardware technology, must directly receive the hardware provided by 16-bit mode Device information to configure the system, improve system start performance, otherwise the configuration of hardware must start in real mode. The GUI starts first loads the WIN 9X system driver, and then obtains hardware device information from the PNP BIOS. Load the PNP device driver VxD and support all 16-bit virtual protection mode drivers required to support non-PNP hardware VxD, allocate system resources. Avoid conflicts of the device and then initialize all drivers (including system drivers and device drivers) to complete the system hardware configuration. Finally, the 16-bit housing assembly USER.EXE, GUI.EXE, KRNL386.EXE, etc., forming the Win16 API, complete the 16-bit protection mode startup, at this time, each system component already exists, but not using the interface.
(32-bit protection mode starts after the 16-bit mode startup, the system calls 32-bit Housler Explorer, 16-bit kernel sees this call, first automatically load VWIN32.386, and load three 32-bit DLL library Document: User32.dll, gdi32.dll, kernel32.dll, forming Win32 API (this is the core of Win 9X), after Vwin32.386 completed this task, will control the control to 16-bit kernel, 16-bit kernel will The control is handed over to the 32-bit kernel and starts the 32-bit protection mode start. At this time, the system loads and initializes all 32-bit drivers, which is the same as 16-bit modes. Finally, run the GUI's shell (the shell program is set by "shell =" in system.ini, the default is the resource manager), complete the GUI startup. 3, the troubleshooting of the GUI startup GUI system is quite complicated, the relevant technical information is very small, which determines that the user cannot find the fault according to the startup process as in DOS. Win 9X has never provided a detailed description of the boot process of the GUI, providing a boot log file bootlog.txt in the root directory. This file records the loading of all program modules used in the startup process, which is the only basis for solving system problems. According to this record, you can fully understand the problems that occur during the GUI startup process. In the face of failure during the startup process, there are two processing methods, one is to override a problem with problems with a well-selected source, but the difficulty is how to find those packets, pay attention, pay attention, directly debugging The problem that repairs the problem is unimaginable under Win 9X; one is from the startup profile (config.sys, autoexec.bat, win.ini, system.ini, and registry) to delete the command to have problems modules. The latter is mainly used to solve problems with failure of a software uninstallation failure. In graphic mode GUI, it will be limited when the system problem is resolved, and the pure DOS mode is not subject to the system, and it is the door of the final system (for computer masters, DOS is still an eternal topic). The complexity of the Windows system determines the difficulty of excluding the inexplicable fault. If there is still no problem after several adjustments, the most insurance is also the fastest way is to reinstall the system. Perhaps this is Microsoft's only useful suggestions for users. Reinstall the system under Windows, to ensure the serial number of the product, otherwise the system may refuse to install.
Nine, WIN 9X startup order Summary This article is detailed in detail, complex parameters and technical analysis blurred the clear architecture, and now make a simple summary of the entire startup process, so that the reader according to the startup process The phenomenon can determine the startup process to better handle problems during the system startup process relatively accurately. (1) System power-on start, load expansion cards (including graphics, etc.), the BIOS program of the motherboard (this is independent of all operating systems (such as Win 9X, Linux, UNIX, OS / 2, etc.), complete the self-test process (2) Enter the main boot record of the hard disk, the partition boot record, automatically load IO.sys (3) I.sys Read the msdos.sys configuration, determine the startup mode, according to config.sys, do the hardware configuration ⑷io.sys According to Win 9X startup requirements, automatically load the necessary Default driver (Himem.sys, setver.exe, ifshlp.sys, etc.) ⑸io.sys Tumble to Command.com, explain execution of AutoExec.bat, performing software configuration ⑹io.sys to perform the necessary default environment settings ⑺ Automatically perform Win. COM, enter the GUI boot phase ⑻ Execute Wininit.exe, upgrade the system driver ⑼ Load system.ini [boot], [386ENH], [Devices] and other sections), according to System.ini, Win.ini And system registry for system combination, configuration, VXD file called when all types of startups are mainly stored in VMM32 and iOSubsys under the C: / Windows / System subdrafted the "shell =" specified in System.ini. HKEY_LOCAL_MACHINE → Software → Microsoft → Software → Microsoft → WINDWARE → Microsoft → WINDWARE → The application contained in Runonce (where runces included in RunOn "is automatically deleted after running once, and the key is mainly used for software installation, usually default Load the INTERNAT.EXE (input method), SYSTRAY.EXE (volume control) and WIN 98 ScanRegw.exe / Autorun. ⒀ When the user completes the identity login, the system executes HKEY_CURRENT_USER → Software → Microsoft → Windows → under the run, the application contained in Runonce is executed in WIN.Ini's LOAD = Run = loaded application ⒂⒂ ⒂⒂ ⒂⒂ ⒂⒂ Startup] The application contains the application ten, the startup process of the conclusion Win 9x is finally introduced. Due to the limitations of the author's knowledge and the limitations of the eye, there is still a lot of gaps to teach the masters. It is true that this process is originally a fairly old topic, but most introductions are limited to local skills, and there is a lot of octrolum. It is very simple to compare the system. This brings great confusion to the majority of computer enthusiasts. The show is ugly to correct some misunderstandings, so that computer enthusiasts have a relatively complete and clear grasp of Windows 9X.
