Win16 and Win32 APIs differ in their component architecture. Win16 uses USER.EXE, GDI.EXE and KRNL386.EXE to handle window management, graphics drawing, and core OS functions respectively. Win32 replaced these executables with dynamically loaded libraries - USER32.DLL handles windows, GDI32.EXE manages graphics, and KERNEL32.DLL controls memory, tasks and resources.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
31 views1 page
Difference Between Win16 and Win 32 APIs
Win16 and Win32 APIs differ in their component architecture. Win16 uses USER.EXE, GDI.EXE and KRNL386.EXE to handle window management, graphics drawing, and core OS functions respectively. Win32 replaced these executables with dynamically loaded libraries - USER32.DLL handles windows, GDI32.EXE manages graphics, and KERNEL32.DLL controls memory, tasks and resources.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1
Difference between Win16 and Win 32 APIs?
Win16 API Win 32 API Description
USER.EXE USER32.DLL The user component is responsible for window management, including messages, menus, cursors communications, timmer etc. GDI.EXE GDI32.EXE The GDI component is the Graphics Device Interface; it takes care of the user interface and graphics drawing, including Windows metafiles, bitmaps, device contests and fonts. KRNL386.EXE KERNEL32.DLL The KERNEL component handles the low-level functions of memory, task and resource management that are the heart of Windows