Table of Contents
Advertisement
¥ CONFIG.SAF, the second Þle in the safe-boot sequence
¥ CONFIG.SYS, the second Þle in the boot sequence
¥ COREUPD.COM, the utility that updates the Þrmware image
¥ DECODE.SYS, the bar code decoding device driver
¥ FLASHDSK.SYS, the resident ßash disk device driver
¥ FORMAT.COM, the disk-reformatting utility
¥ FUNCTEST.COM, the functional test for system components
¥ LD.BAT, the batch Þle for RESPONSE.BAT processing
¥ LOCK.COM, the utility for locking or unlocking the resident ßash disk and RAM
disk
¥ ORGANIZE.COM, the utility for reorganizing ßash disk data
¥ PM.COM, the power-management utility
¥ VDISK.SYS, the RAM disk device driver
¥ XFER.EXE, the serial transfer utility
The CONFIG.SYS Þle (see Figure 1-4) will load the FLASHDSK.SYS driver to create the C
drive and the VDISK.SYS driver to create the D drive. It will then load DECODE.SYS and
CFGDEV.SYS before chaining to its counterpart on drive C. The AUTOEXEC.BAT Þle (see
Figure 1-5) will chain to its counterpart on drive C, except during a safe boot.
The purpose of the CONFIG.SAF Þle (see Figure 1-6) is to provide a minimal boot conÞg-
uration that preserves the ßash and RAM drives. When the safe-boot sequence is initiated,
the CONFIG.SAF Þle is processed instead of the CONFIG.SYS Þle. This prevents chaining
into the drive C initialization Þles by omitting the NEWFILE = C:\CONFIG.SYS com-
mand. It also eliminates the loading of the DECODE.SYS and CFGDEV.SYS drivers.
Chapter 1: Default Disk Driver Organization and Unit Configurations
1-5
Advertisement
Table of Contents
