Intermec 6100 Reference Guide

R

6. KRNL386.EXE now loads the Windows shell program.  In this case,

NORSHELL.EXE is loaded.

7. After referring to the WIN.INI initialization file, NORSHELL.EXE

launches the user application, which, in this case, is the Windows 3.1 File

Manager.  Windows startup is now complete and the File Manager is open.

As mentioned earlier, you can start Windows 3.1 standard mode by running

WIN.COM.
An alternative method is to run DOSX.EXE directly.  If run directly, the

WIN.COM and WSWAP.EXE files can be left out of the system to save space.

Note that the standard mode configuration does not support execution of DOS

programs.  For a more detailed discussion of Windows startup, refer to chapter 1

of the book Windows Internals, by Matt Pietrek, published by AddisonĆWesley.

The following tables list the Windows 3.1 files for 6100 Computer.  The table

titles indicate the category.  Files marked Optional may be deleted from the conĆ

figuration if the running applications do not need them.

Table 3Ć1 

Component

Description

WIN.COM 

DOS program that launches Windows.

Optional

WINTITLE.RLE  Default desktop wallpaper.  Displays Windows 3.1 logo.

Optional

NORSHELL.EXE Norand shell program.

Optional

WINFILE.EXE 

Windows File Manager shell, launched by NORSHELL.EXE.

Optional

Table 3Ć2 

Component

Description

SYSTEM.INI  Initialization file for Windows system and drivers.  [BOOT.DESCRIPTION]

section of this file has version strings for drivers and applications.

Required

WIN.INI 

Initialization file for Windows applications.

Required

WINFILE.INI Initialization file for WINFILE.EXE.

Optional

Table 3Ć3 

Component

Description

SYSTEM/DOSX.EXE 

DPMI server.

Required

SYSTEM/WSWAP.EXE

Swaps out standardĆmode Windows when a DOS application is run.

Optional

SYSTEM/KRNL386.EXE Windows 3.1 kernel for 32Ćbit systems.

Required

SYSTEM/GDI.EXE 

Windows 3.1 Graphical Device Interface code.

Required

SYSTEM/USER.EXE 

Windows 3.1 user interface.

Required