SECTION 1
Getting Started
PEN*KEY
R
6200/6300 Hand-Held Computer Programmer’s Reference Guide 1-5
Toolkit for 6200/6300 Computers
General Information
The file complement in the toolkit for the 6200 or 6300 Series computer differs
from one release to the next. For an accurate list of toolkit files, see the
RELNOTES.TXT file, included in the toolkit distribution package.
The following available toolkits contain DOS and Windows resources for
configuration, power management, communications, and peripherals:
Part Number
Description
P/N 215Ć452Ć001
6200/6300 DOS (only) toolkit
P/N 215Ć455Ć001
6300 DOS and Windows toolkit
The files and documentation in the toolkit are available to those who hold
licenses for the operating systems for the 6200 or 6300 Series computers.
As shipped from the factory, flash memory in the 6200 and 6300 Computers are
preloaded with files for booting and telecommunicating. At a minimum, ROM
DOS 5 is preloaded in flash memory. To create the environment required by your
application software, select any other system files needed from the toolkit and
copy them to the HHC.
Some files mentioned in this publication may not exist in flash memory. Most of
these files are in the toolkit. If not, try one of the BBS Product Forums. The
toolkit does not include application software. You may obtain such software from
Intermec, from thirdĆparty suppliers, or design your own.
The files necessary to run Windows and the application software are often loaded
onto the RAM drive. The instructions included in the toolkit assume that you
will install all files on the RAM drive. Other methods of arranging files are
possible. And in some cases, this requires substitution of the appropriate drive
letter in place of the drive letter of the RAM drive.
File Integrity Verification Utility: CRC32.EXE
The toolkit contains a utility, CRC32.EXE, for verifying the integrity of the files
provided on the toolkit disks. CRC32.EXE calculates a 32Ćbit CRC value for a
file. This value may then be compared with the factory CRC value for the file.
Usage is as follows:
CRC32 [filename | pathname] [/s]
where:
filename
is the name of the file on which the CRC is calculated. One or more
files or directories can be processed at one time.
pathname
is the location of the
filename
to be processed. Wildcard processing
is not allowed, either in the pathname specified after the @" symbol, nor any of
the pathnames within the argument file. An example of a valid argument file is
the same as those used by the IPLFMT program.
/s
indicates that all subdirectories should be searched for matching file names.
@
is (optionally) included in front of a filename to indicate that it is an argument
file, containing names of files to be checked by CRC32.EXE.
There is a list of the factory CRC values for the released files included in the
RELNOTES.TXT file in the toolkit.
1. Getting Started