Title: Windows 95 system programming big mystery (a) (Windows 95 SystemProgramming SECRETS) Author: Matt Pietrek Translator: Hou Junjie trimmer: High Yongqing (Dalian Institute of Light Industry Total 982)
Summary 1. Windows 95 has three very basic core components: 16-bit KRNL386, 32-bit kernel32, and RING0 VWIN32.VXD. If you put them together, you get vwinkernel32386.2. If you want to fully understand Windows 95, you must understand the Portable Executable (PE) file format.
Chapter 1 Perspective Windows 951. This new executable format is called the PE (Portable Executable) format, which is derived from the common object file format v (coff) of the UNIX system. 2. The main goal of Windows NT is in strong With transplantability (portable to other hardware platforms). Most of the codes are completed in C and C (rather than combined languages). 3. NT is stable, one main reason is its "protected subsystem) architecture. In this subsystem, the system code of the API is implemented, and it is performed in the location space different from the application. 4. NT races 16-bit yuan in the so-called WOW (Windows On Windows) stroke. 5. Win32S is limited. The first is also the biggest limit is that it does not support it. The second is that it puts all Win16 programs and Win32 programs in the same address space. The third disadvantage is that Win32S lacks a DLL data space exclusive for every stroke. Another problem with Win32S is the scheduling and message delivery system. 6. The bottom layer of Windows 95 is Ring0 system code, including virtual machine manager (VMM), and auxiliary VXDS. The code that is executed in CPU Ring0 is the most stable and most reliable. So it burdens more systematic materials and hardware processing. 7. Whether it is the NE file of Win16 or the Win32 PE file, it contains a DOS program called a Dosstub program. Your "This Program Requires Microsoft Windows" seen under Windows 3.1 is a masterpiece of the DOS Stub.
