Symbol PDT 3400 Series Product Reference Manual

PDT 3400 Series

Product Reference Guide

PDT 3400 Product Reference Guide

70-32643-01

Revision A — May 1998

2

Symbol Technologies, Inc. One Symbol Plaza, Holtsville N.Y. 11742

PDT 3400

Product Reference Guide

70-32643-01

Revision A

May 1998



1998

by Symbol Technologies, Inc. All rights reserved.

No part of this publication may be reproduced or used in any form, or by any electrical or
mechanical means, without permission in writing from Symbol. This includes electronic or
mechanical means, such as photocopying, recording, or information storage and retrieval
systems. The material in this manual is subject to change without notice.

The software is provided strictly on an “as is” basis. All software, including firmware,
furnished to the user is on a licensed basis. Symbol grants to the user a non-transferable and
non-exclusive license to use each software or firmware program delivered hereunder (licensed
program). Except as noted below, such license may not be assigned, sublicensed, or otherwise
transferred by the user without prior written consent of Symbol. No right to copy a licensed
program in whole or in part is granted, except as permitted under copyright law. The user
shall not modify, merge, or incorporate any form or portion of a licensed program with other
program material, create a derivative work from a licensed program, or use a licensed
program in a network without written permission from Symbol. The user agrees to maintain
Symbol’s copyright notice on the licensed programs delivered hereunder, and to include the
same on any authorized copies it makes, in whole or in part. The user agrees not to
decompile, disassemble, decode, or reverse engineer any licensed program delivered to the
user or any portion thereof.

Symbol reserves the right to make changes to any software or product to improve reliability,
function, or design.

Symbol does not assume any product liability arising out of, or in connection with, the
application or use of any product, circuit, or application described herein.

No license is granted, either expressly or by implication, estoppel, or otherwise under any
Symbol Technologies, Inc., intellectual property rights. An implied license only exists for
equipment, circuits, and subsystems contained in Symbol products.

Symbol, Spectrum One, and Spectrum24 are registered trademarks of Symbol Technologies,
Inc. Other product names mentioned in this manual may be trademarks or registered
trademarks of their respective companies and are hereby acknowledged.

Symbol Technologies, Inc.
One Symbol Plaza
Holtsville, New York 11742-1300
http://www.symbol.com

ii

Contents

About This Manual

Notational Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Documents Available from Symbol Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

External Documents and Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Symbol Support Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

USA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Canada . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Europe. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Asia. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Chapter 1. Getting Started with the PDT 3400

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Unpacking the PDT 3400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Parts of the PDT 3400. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Accessories/Peripherals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Development PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Cradles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Holster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Batteries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Battery Chargers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

SDK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Other Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Before You Use the PDT 3400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Charge and Install the Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Configure the PDT 3400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

iii

PDT 3400 Product Reference Guide

Chapter 2. Software Installation on Development PC

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

DOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Stacker Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Installing the SDK on the Development PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Stacker Post Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

1. Create Your Compressed Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

2. Load Stacker (Mount the Compressed Volume(s)) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

3. Inform TCM of Compressed Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Installing Other Development Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Chapter 3. Installing the Hardware

Office Cradle (CRD 3400). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Parts of the CRD 3400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Desk Mounting the CRD 3400. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Wall Mounting the CRD 3400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Vehicle Cradle (VCD 3400). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Parts of the VCD 3400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6

Mounting the VCD 3400. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Connecting the Cradle(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-10

To the Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

Connecting the CRD 3400 to Other Cradle Chains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Chapter 4. Terminal Configuration Issues

Memory Available Versus Program Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Configuration Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

On Board RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

On Board Flash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

Application Size Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3

Matching Software Requirements to the Hardware Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Overview: Terminal Configuration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Chapter 5. Terminal Configuration: Edit the Configuration Files

Setup/Edit DOS Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

CONFIG.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Symbol-Provided Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

AUTOEXEC.BAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Symbol-Supplied TSRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

iv

Contents

Chapter 6. Terminal Configuration:

Building and Sending the Hex Image

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Starting Terminal Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Confirmation Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Creating the Script for the Hex Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

Open a New or Existing Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

Copy Components to the Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7

Edit the System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

Set the Script Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12

Set the System Boot File Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16

Set the Communications Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16

Save the Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17

Reviewing a Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19

Building the Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22

If the Build Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25

Sending the Hex Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26

Preparing for the Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26

Exit IPL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-32

Exiting TCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-32

Exiting HEX2TERM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-32

Special Note: TCM and Stacker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-33

How TCM and Stacker Work Together . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-33

Chapter 7. Terminal Configuration: Loading a RAM Disk

Loading a RAM Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Protected RAM Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Using EMSALLOC.SYS to Increase Size of RAM Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Using Stacker to Extend RAM Disk Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

Chapter 8. Terminal Configuration: Running BIOS Setup

PDT 3400 BIOS Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Running Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Default Configuration Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

Chapter 9. Operating the Terminal

Powering the PDT 3400 On and Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Booting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Adjusting the Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Turning Backlight On/Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

v

PDT 3400 Product Reference Guide

Changing Beeper Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-2

Installing the Handstrap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-2

Using the Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-4

Keyboard State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6

Using the Integrated Scanner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7

Running Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8

With the Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8

With Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8

In a WWAN Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8

Using Signature Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9

Calibrating the Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9

Chapter 10. Maintenance

Batteries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Battery Life. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Backup Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Battery Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Cursor Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Installing New or Recharged Batteries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4

Charging the Batteries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6

Cleaning the Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-7

Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7

Chapter 11. Troubleshooting

Appendix A. Specifications

Operating Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Performance Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Decode Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

SE 1200 Standard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Appendix B. Keyboard Definitions

Appendix C. PDT 3400 Demo Program

PDT 3400 Demo Program Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Operating Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

PDT 3400 Features Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

The Font Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

The Signature Capture Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

The Scan Only Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

vi

Contents

The Data Entry Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

The Radio Demo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

The Diagnostics Demo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4

PDT 3400 Demo Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6

vii

PDT 3400 Product Reference Guide

viii

About This Manual

The

PDT 3400 Product Reference Guide

t

general information about the PDT 3400 and accessories

t

software and hardware installation procedures

t

discussion of configuration issues

t

configuration instructions

t

operating and maintenance instructions

t

assistance with troubleshooting set-up and operating problems

t

demo program instructions and database.

This manual is intended for use by:

System Administrators who: get equipment ready for use

provides:

Application Developers who: need to understand PDT 3400 operator requirements

obtain and configure applications

test applications that work on the PDT 3400

deliver PDT 3400s to operators and provide support.

need to understand the PDT 3400 system administrator’s
operating needs and specifications

develop applications that meet operating specifications
required by the system administrator and that work
effectively on the PDT 3400.

ix

PDT 3400 Product Reference Guide

Notational Conventions

The following conventions are used in this document:

t

"Operator" and "User" refer to anyone using an application on a PDT 3400 series.

t

"PC" refers to the IBM personal computer or compatible system that you are using

to develop applications.

t

"Terminal" or “hand-held computer" refers to a PDT 3400.

t

"You" refers to the administrator who is using this manual as a reference aid to

install, configure, operate, maintain, and troubleshoot the PDT 3400.

t

Keystrokes in bold type indicate non-alphanumeric keystrokes on the PC. For

example:

Select the <F1> key to access on-line help.

t

Bold

type is used to identify menu items and input or text fields on a PDT 3400

screen

t

Italics

s

are used:

for the names of parameters in function prototypes and variable names in usage
and syntax descriptions

s

to highlight specific items in the general text

s

to identify chapters and sections in this and related documents

t

Square brackets [] in a command line enclose optional command line parameters.

t

The piping symbol | has the effect of "or" when it is used to separate inline

parameters on a command line; i.e., it separates alternative values for parameters.

t

Bullets (•) indicate:

s

action items

s

lists of alternatives

s

lists of required steps that are not necessarily sequential

t

Sequential lists (e.g., those that describe step-by-step procedures) appear as

numbered lists.

x

About this Manual

Related Publications

The following is a list of documents and publications that you may find useful if you want to
know more about the PDT 3400 itself or about the tools and utilities that are available for
writing applications for the PDT 3400.

Documents Available from Symbol Technologies

t

PDT 3400 System Software Manual

p/n 70-33290-XX

t

PDT 3400 Quick Reference Guide

p/n 70-32642-XX

t

CRD 3400/VCD 3400 Cradles Quick Reference Guide

p/n 70-32810-XX

t

PDT 3430 Developer’s Guide for the Motorola® DataTAC® Wireless Wide Area
Network (WWAN)

p/n 70-33291-XX

t

PDT 3433 Developer’s Guide for the INET Spider CDPD Wireless Wide Area
Network (WWAN)

p/n 70-33749-XX

External Documents and Publications

t

Microsoft Windows & MS-DOS User’s Guide

xi

PDT 3400 Product Reference Guide

Service Information

If you have a problem with your equipment, contact the Symbol Support Center. Before
calling, have the model number, serial number, and (if necessary) several of your bar code

symbols at hand.

Call the Support Center from a phone near the equipment so that the service person can try
to talk you through your problem. If the equipment is found to be working properly and the
problem is symbol readability, the Support Center will request samples of your bar codes for
analysis at our plant.

If your problem cannot be solved over the phone, you may need to return your equipment
for servicing. If that is necessary, you will be given specific directions.

Note: Symbol Technologies is not responsible for any damages incurred during

shipment if the approved shipping container is not used. Shipping the units
improperly can possibly void the warranty. If the original shipping
container was not kept, contact Symbol to have another sent to you.

Symbol Support Center

For service information, warranty information or technical assistance, call:

USA

SYMBOL SUPPORT CENTER

1-800-653-5350

Canada

Mississauga, Ontario
Canadian Headquarters
[phone]

Europe

Symbol Place
Winnersh Triangle
Berskshire RG4 5TP
United Kingdom
[phone](outside UK)
0 1189 45 7222 (inside UK)

xii

About this Manual

Asia

Singapore
Symbol Technologies Asia, Inc.
337-6588 (Inside Singapore)
[phone] (Outside Singapore)

If you purchased your Symbol product from a Symbol Business Partner, contact that Business
Partner for service.

xiii

PDT 3400 Product Reference Guide

xiv

Chapter 1

Getting Started with the PDT 3400

Introduction

The PDT 3400 is a hand-held computer which combines a PC-standard architecture (16-bit
VG-230), Microsoft MS-DOS, integrated scanning capability, signature capture, 47-key data
input, PCMCIA capability, an IrDA-compliant interface for printing and communications,
and several Wireless Wide Area Network (WWAN) radio network options.

The PDT 3400 uses a standard MS-DOS 6.22 operating environment and software tools such
as C/C++ for DOS and Microsoft® Visual C++ for Windows for application development.

Power for the PDT 3400 is provided by a rechargeable NiMH battery pack, which can be
ordered from Symbol Technologies.

Symbol provides TSR extensions for non-PC peripherals (RF, scanning, power management,
flash management, signature capture, etc.). To assist in downloading system software and
applications to the PDT 3400 terminal, Symbol provides the Windows-based Terminal
Configuration Manager (TCM) for use on the development PC. TCM assists the system
administrator/application developer in building hex images and transferring hex images to
the PDT 3400.

Unpacking the PDT 3400

Carefully remove all protective material from around the terminal and other equipment and
save the shipping containers for later storage and shipping.

Verify that you received all equipment listed on the packing slip and inspect the equipment
for damage. If you find any damaged or missing items, contact the Symbol Support Center at
[phone] immediately.

1-1

PDT 3400 Product Reference Guide

Parts of the PDT 3400

Beeper

Charging LED

Scan Window

Display

Scan Bar

Keyboard

Regulatory Label

^F6

%F5

$F4

Front View

Scan LED

T op View

IrDA Interface

(Communications Port)

Charging

Contacts

Base View

Battery Latch

Battery

1-2

Handstrap

Handstrap Button

Back View

Getting Started with the PDT 3400

Parts of the PDT 3400 (cont.)

Processing Capability. 8 16 MHz, VG-230 PC with up to 4.5 MB flash for BIOS, DOS,

and program storage and up to 4 MB of RAM for data and/or program storage.

Operating System. MS-DOS 6.22.

Application Development Tools. DOS application development tools include C/C++

for DOS and Microsoft Visual C++ for Windows. Symbol provides TSRs for a DOS

environment (scanning, RF, power management, flash management, etc.).

Accessories/Peripherals

Development PC

With operating system of DOS 6.22 or greater.

Cradles

The CRD 3400 office cradle and VCD 3400 vehicle cradle provide battery charging,
communications, and safe storage for the PDT 3400.

Holster

Provides a way to carry the terminal, as well as convenient storage and protection for the
PDT 3400 when not in use.

Batteries

Primary power for the PDT 3400 is provided by a 2100 mAh or 1300 mAh Nickel Metal
Hydride (NiMH) battery pack.

Battery Chargers

NiMH batteries can be charged in a PDT 3400 seated in the CRD 3400 or VCD 3400, or
externally through a UBC 2000 charger with adapter. Refer to Chapter 10, Maintenance, for
instructions.

1-3

PDT 3400 Product Reference Guide

Cables

An RS-232 communications cable and a null-modem cable are required for connecting the
CRD 3400/VCD 34XX to a host computer. An RS-232 communications cable is required for
linking one cradle to another cradle. Other interconnect cables may be required for
connecting a 3400 cradle chain to another Symbol cradle chain. Refer to Chapter 3, Installing
the Hardware, for more information.

SDK

The PDT 3400 Software Development Kit (SDK) contains all software and documentation to
assist you in developing applications to run on the PDT 3400.

You will need one or more application development environments (ADEs) from other
vendors to develop applications for the PDT 3400. Some examples are Microsoft or Borland
C/C++ for DOS.

Other Software

An OEM version of Stacker is supplied for use on both the development PC and the PDT
3400 for extending your storage capacity. Refer to Chapter 4, Terminal Configuration Issues,
for information on Stacker.

1-4

Getting Started with the PDT 3400

Before You Use the PDT 3400

Charge and Install the Battery

Prior to using the PDT 3400 for the first time, install and, if necessary, charge the NiMH
battery. The battery can be charged externally before installation or after installation in the
PDT 3400.

Refer to Chapter 10, Maintenance, for instructions on charging and installing the battery.

Configure the PDT 3400

Configuration consists of loading the software and applications in the PDT 3400’s flash,
creating and loading a RAM disk, and setting the PDT 3400’s operating parameters. For a
discussion of configuration issues/considerations and an overview of the process, refer to
Chapter 4, Terminal Configuration Issues. For instructions on how to edit the configuration
files, load software, create a RAM disk, and set parameters, refer to Chapters 5-8.

1-5

PDT 3400 Product Reference Guide

1-6

Chapter 2

Software Installation on Development PC

Overview

The PDT 3400 software development kit (SDK) is available for developing applications to
run on the PDT 3400. This kit includes:

t MS DOS 6.22 (kernel files only)

t Symbol-provided DOS files (TSRs)

t Stacker 4.1

t Default hex image

t TCM scripts

t Sample files

DOS

MS DOS 6.22, while recommended and supplied with the PDT 3400 SDK, is not required
for use on the development PC. Any version of MS DOS 5.0 or greater is acceptable. The SDK
installation program loads the required MS DOS 6.22 components on the development PC
used to create the hex files (via Terminal Configuration Manager) for download to the
terminal.

Note: The copy of MS DOS 6.22 (kernel files only) supplied in the SDK is

for use on the PDT 3400 ONLY. No license is included in the PDT
3400 SDK for using MS DOS on the development PC; you must have
your own valid MS DOS license (preferably for MS DOS 6.22) for the
development PC to use the SDK.

2-1

PDT 3400 Product Reference Guide

The PDT 3400 is designed to run MS DOS 6.22, and all of the programs provided by Symbol
for the PDT 3400 are based on MS DOS 6.22. If you use any other version of DOS in the
PDT 3400, Symbol cannot guarantee that all of the terminal’s features will function properly.

Stacker Installation

Stacker version 4.1 from Stac Electronics is provided with the SDK for use on both the
development PC and the PDT 3400 terminal. Each SDK comes with a single user license for
using Stacker on a single development PC. Each PDT 3400 terminal comes with a single user
license for Stacker for that terminal.

Note: Stacker is only certified for use with Windows 3.1.

Stacker is NOT required to use the PDT 3400. However, if you plan to use Stacker to
compress the terminal’s ROM disk, then Stacker must be used on the development PC as well.

Note: You can use Stacker to compress the terminal’s RAM disk without

compressing your development PC’s hard drive, but the Stacker
installation files must be on the development PC.

When installing Stacker, first decide what you intend to use it for:

t If you use Stacker to increase the drive space on your development PC, then you must

inform the Stacker installation program (Custom Installation Option) to leave at

least 10 MB of your hard drive uncompressed and available for use in creating

compressed volumes for the PDT 3400.

t If you use Stacker to compress the PDT 3400’s ROM disk, then you need only create

a volume to suit the size of the ROM disk you intend to compress.

t If you only use Stacker to compress the PDT 3400’s RAM drive, you must install all

of the Stacker files on the development PC, but do not need to create a compressed

volume.

Note: When installing Stacker, accept the default path of C:\STACKER.

2-2

Software Installation on Development PC

Installing the SDK on the Development PC

The SDK is installed through Windows using Program Manager. The SDK uses directory
C:\SYMSDK by default unless you change it.

SDK Installation Procedure

1. Insert installation disk labelled “Disk 1” in drive A: or B: on the development PC.

2. From the Program Manager’s File Menu, choose Run.

3. On the command line, type:

A:SETUP or B:SETUP

and press ENTER.

4. Follow the installation prompts that follow.

Note: To ensure the best operation of the SDK, do not change the base path

set up in the installation.

Once installation of the SDK is complete, change to the C:\SYMSDK directory and check for
the directories shown in Figure 2-1.

2-3

PDT 3400 Product Reference Guide

SYMSDK SDK3400

DOSSAMP

BIN

GPSCR

SCRIPTS

TERMINAL

SCAN1D

MANUAL

PDTDEMO

PDTSET

PENSAMP

SUB

DOS

TSRS

Figure 2-1. PDT 3400 SDK Directories

PCMCIA

UTILS

2-4

Software Installation on Development PC

Stacker Post Installation

After installing Stacker and the SDK, use Stacker to create one or more compressed volumes
on your hard disk, if not already done during installation.

Note: If a compressed volume of the desired size was created during Stacker

installation, you must (1) modify the STACKER.INI file to reflect the
correct volume name, which is explained in step 2, and (2) create a
STACVOL.XXX file to inform TCM of the compressed drive
location.

If no compressed drive is created on installation, create your compressed volume(s), mount
the compressed volume(s), and inform TCM of the location, volume name, and drive letter
of your compressed volume(s). These steps are detailed below.

IMPORTANT: These steps must all be done from the DOS command line prompt,

outside of Windows.

1. Create Your Compressed Volumes

Use the following DOS command line to create compressed volumes:

CREATE C:\STACVOL.XXX /S=YYY

where:

XXX is 46C for compressed volumes to be used on C: ROM disks, or 46D for

compressed volumes to be used on D: ROM disks.

YYY is the size in 0.1 MB (e.g., 0.5, 0.8, etc.) to allocate to the compressed

volume.

For the sample scripts supplied with the SDK2100, PDTDEMOD.TCM and DOS-D.TCM,
use the following syntax:

CREATE C:\STACVOL.46C /S=0.6

2-5

PDT 3400 Product Reference Guide

2. Load Stacker (Mount the Compressed Volume(s))

If the drive you created is not mounted, modify CONFIG.SYS as follows to load Stacker as
a device driver:

DEVICE=C:\STACKER\DPMS.EXE
DEVICE=C:\STACKER\STACKER.COM

The STACKER.INI file is used by device driver STACKER.COM when loaded in
CONFIG.SYS. If necessary, edit STACKER.INI to add or modify lines.

Note: STACKER.INI may be set with DOS attributes of hidden, system,

and read-only. To see this file via DOS’s DIR command, use the /AH
switch.

To modify the file’s attributes so it can be edited with a standard text editor, use the DOS
ATTRIB command with the following command line:

ATTRIB -R -S -H C:\STACKER.INI

Once the modification is complete, use the command line above with +R, +S, and +H to
append the attributes back to the file.

After loading Stacker (via CONFIG.SYS) and setting STACKER.INI properly, reboot your
development PC for a proper setup. Then use the following command line to find out what
drive letters Stacker assigned to your compressed drives:

STACKER

Stacker displays information similar to the following:

Stacker drive map:

Drive A was drive A at boot time
Drive B was drive B at boot time
Drive C was drive C at boot time
Drive D was drive D at boot time
Drive E was drive E at boot time
Drive F was drive F at boot time [C:\STACVOL.46C = 0.5MB]

2-6

Software Installation on Development PC

3. Inform TCM of Compressed Volumes

For each compressed volume (46C and46D), use a text editor to create a file in C:\ called
STACINFO.46C or STACINFO.46D, respectively. The files each should contain a single line
of the following form:

Drive X was drive X at boot time [C:\STACVOL.YYY=ZZZMB]

where:

X is the drive letter assigned to the compressed volume.

YYY is 46C or 46D, as appropriate.

ZZZ is the size of the compressed volume as listed by Stacker.

All of this information can be obtained from the output of the STACKER command (given
in step 2). By redirecting the output of the Stacker command to a file, you can edit the output
file and copy the selected lines from the Stacker output to STACINFO.46C or
STACINFO.46D. Use the following command line to create the Stacker map output file:

STACKER > STACMAP.OUT

Note: Remove any leading blanks from the line extracted from

STACMAP.OUT when placing the line in STACINFO.46C or
STACINFO.46D.

Installing Other Development Software

Developing applications for the PDT 3400 may require installing other development software
such as application development environments (e.g., Visual C++) on the development PC.
Follow the installation instructions provided with this software.

2-7

PDT 3400 Product Reference Guide

2-8

Chapter 3

Installing the Hardware

The cradles are devices used for charging the terminal’s battery and for communicating with
the host PC or with other cradle chains. The PDT 3400 offers two cradle configurations: a
standard, office-style cradle which can be tabletop- or wall-mounted (CRD 3400), and a
vehicle cradle (VCD 3400).

This chapter provides instructions for mounting and connecting the cradles.

Office Cradle (CRD 3400)

Before attempting to mount or connect the cradle, verify that you have the following parts:

t Front Housing Assembly

t Back Housing

t Power Supply

s US: p/n 50-14000-045 with power cord 23844-00-00
s International: p/n 50-14000-045

t RS-232 Serial Communications Cable

t Null Modem Cable, p/n 25-19299-01

t Mounting Screws (not provided by Symbol)

3-1

PDT 3400 Product Reference Guide

Parts of the CRD 3400

Figure 3-1 shows the parts of the CRD 3400.

Front Housing

Power

Connector

Communication LED

Chaining Connector

(Female Pins)

Front View Back View

Back Housing

Snap

Snap

Mounting Holes

Connector to Host

(Male Pins)

Front View Back View

Figure 3-1. Parts of the CRD 3400

3-2

Installing the Hardware

Desk Mounting the CRD 3400

To mount the CRD 3400 on a desk:

1. Feed the communications and power cables through the back housing’s opening.

2. Plug the DB-25 cable connector into the cradle’s communications port.

3. Plug the power supply jack in the cradle’s power port.

Power Supply Communications Cable

Figure 3-2. Connecting Communications Cable and Power Cord

4. Slide the cradle’s front housing over the hook at the top of the back housing.

Hook

Front HousingBack Housing

Snaps

Figure 3-3. Installing Front and Back Housing

5. Press the front housing against the snaps in the back housing’s base to secure.

6. Connect the cables to the host as described in Connecting the Cradle(s) to the Host.

7. Connect the cable to another cradle in a chain as directed in Connecting the CRD
3400 to Other Cradle Chains.

3-3

PDT 3400 Product Reference Guide

Wall Mounting the CRD 3400

The back housing of the CRD 3400 also serves as a wall mounting bracket. To mount the
CRD 3400 on a wall:

1. Position the cradle’s back housing against the wall and mark the top hole’s position
(Figure 3-4). Remove the back housing.

Mounting

Holes

Figure 3-4. Positioning the CRD 3400 for Wall Mounting

2. Insert the appropriate type of screw for the wall into the marked hole and fasten for
position. Do not tighten yet.

3. Feed the communications and power cables through the back housing and connect
to the ports as directed in steps 1-3 for Desk Mounting the CRD 3400 on page 3-3.

4. Place the back housing on the wall over the top screw installed in step 2 and tighten
the screw to secure.

5. Insert the two additional screws and tighten to secure.

6. Slide the cradle’s front housing over the “hook” at the top of the back housing.

7. Press the front housing against the snaps in the back housing’s base to secure.

8. Connect the cables to the host as described in Connecting the Cradle(s) to the Host.

3-4

Installing the Hardware

Vehicle Cradle (VCD 3400)

Before attempting to mount or connect the VCD 3400, verify that you have the following
parts:

t Cradle Assembly
t Power Supply, p/n 50-14000-056
t RS-232 Communications Cable
t Null Modem Cable, p/n 25-19299-01
t Mounting Screws (not provided)
t Optional External Vehicle Antenna
t Optional Mounting Plates/Screws

3-5

PDT 3400 Product Reference Guide

Parts of the VCD 3400

Figure 3-5 shows the parts of the VCD 3400.

Mounting Holes

Terminal Retainers

Back Housing

Cup

Housing

Communications LED

Power Connector

Front View

Figure 3-5. Parts of the VCD 3400

Mounting the VCD 3400

Mounting Holes

RF Connector for
External Vehicle
Antenna

Connector to Host

Back View

The vehicle cradle can be mounted to the dash of a truck or other vehicle. Each cradle
operates with an optional vehicle power supply capable of power conditioning in an
operating range of 10-48 volts.

To install the vehicle cradle:

1. Feed the communications and power cables through the back housing’s opening.

2. Install the power jack coupler on the power cord.

3-6

Installing the Hardware

a. Slide the cap over the power jack and on to the power cable (Figure 3-6).

Power Jack

Cap

Cable

Figure 3-6. Installing Cap on Power Jack

b. Slip the washer on the cable and slide it to fit against the back of the power jack

(Figure 3-7).

Back of

Power Jack

Washer

Figure 3-7. Installing Washer on Power Jack

c. Insert the power jack in the power cord retainer on the back of the vehicle cradle

(Figure 3-8).

Retainer

Power Jack

Figure 3-8. Installing Power Jack in Retainer

3-7

PDT 3400 Product Reference Guide

d. Slide the cap up the cable, over the power jack to the retainer and tighten by hand

until secure (Figure 3-9).

Retainer

Power Jack

Cable

Cap

Figure 3-9. Securing Power Jack

3. Install the communications cable connector in the RS-232 communications port.

Communications Cable Null Modem Cable

Figure 3-10. Installing Communications Cable

4. Install the cradle on the dash or other appropriate mounting surface using the
appropriate hardware.

5. Connect the communications cable to the host as directed in the section Connecting

the Cradle(s): To the Host.

3-8

Installing the Hardware

6. If the power connector is equipped with a cigarette adapter (10-48V), plug the

adapter into the cigarette lighter receptacle.
If the power connector is equipped with a standard 10-48V wire connect, connect

the cable directly to a fuse panel.

Note: This must be performed by a qualified installer.

The cradle’s Communications LED lights for 4 seconds on power up, blinks 7 times,
then goes out if the cradle passes a self test.

If the light continues flashing, check the cable connections and ensure they are secure.
If the problem persists, contact the Symbol Support Center.

3-9

PDT 3400 Product Reference Guide

Connecting the Cradle(s)

To the Host

To connect the cradle to the host:

1. Connect the RS-232 cable and power supply to the cradle as described previously.

2. Plug a null modem cable in the host’s COM port.

3. Plug the null modem cable’s other connector to the RS-232 cable already connected
to the cradle (Figure 3-11).

Power Supply

Null Modem CableCommunications Cable

Figure 3-11. Connecting the Cradle to the Host

4. Insert the power plug in a standard electrical outlet (CRD 3400) or connect as
directed in the section Mounting the VCD 3400 on page 3-6.

5. The cradle’s Communications LED lights for 4 seconds on power up, blinks 7 times,
then goes out if the cradle passes a self test.

If the light continues flashing, check the cable connections and ensure they are secure.
If the problem persists, contact the Symbol Support Center.

3-10

Installing the Hardware

Connecting the CRD 3400 to Other Cradle Chains

The CRD 3400 cradle can be chained to:

t another CRD 3400
t a Series 3000 cradle chain (31XX, 38XX, 33XX)
t a CRD 4600 cradle chain.

Up to 96 CRD 3400’s can be chained together. If the CRD 3400 is chained in combination
with other cradle chains, the total number of linked cradles is limited by the constraints of
the other cradle chains. For example, a CRD 4600 cradle chain is limited to 59 slave cradles
depending from a single master cradle.

To connect one or more CRD 3400s in a chain (refer to Figure 3-12):

1. Disconnect the power jack from the power source for all cradles included in the

chain.

2. Connect Cradle 1 to the host as described on page 3-10.

3. Remove Cradle 2’s back housing.

4. Plug an RS-232 cable’s male DB-25 connector in Cradle 1’s chaining port.

5. Plug the RS-232’s female DB-25 connector in the Cradle 2’s interconnect (host) port.

6. Plug the power supply jack in Cradle 2’s power port.

7. Replace the back housing on each Cradle.

8. Repeat the process for each CRD 3400 in the chain.

Interconnect

Port

Cradle 2Cradle 3

Cradle 1

Figure 3-12. Connecting a CRD 3400 Chain

Chaining Port

3-11

PDT 3400 Product Reference Guide

9. When all the cradles are chained, connect the power plug for each cradle in the chain
to a power source.

Note: Each cradle in the chain has its own power supply. Be sure to connect all

power supplies for chained cradles to a power strip connected to a standard
electrical source. Then power the power strip on and off, not each cradle.

When chaining cradles together, only the cradle closest to the host blinks 7
times. The LEDs on all other cradles in the chain go out after the 4-second
ON period. If these cradles blink 7 times, there is a cradle problem.

If you are connecting the CRD 3400 cradle chain to a Series 3000 cradle chain (e.g., 31XX
or 38XX cradles), the cradles can be linked in any order.

If you are connecting a CRD 3400 cradle chain to a CRD 4600 cradle chain:

1. Position the master CRD 4600 at the end of the 3400 cradle chain, with any slave
4600 cradles following the master cradle.

2. Use the RS-232 Null Modem DB-25 Male to DB-25 Female Cradle Interconnect
Cable (p/n 25-15749-01) to connect between the last CRD 3400 in the chain and the
master CRD 4600.

Slave

CRD 3400

CRD 3400

Chain

RS-232

Interconnect

Cable

CRD 4600

Chain

Slave

CRD 3400

Master 3400

Host

Figure 3-13. Connecting a CRD 3400 Chain to a CRD 4600 Chain

3-12

Master CRD 4600 Slave CRD 4600

Installing the Hardware

3. On the master CRD 4600, set the switch for Host/3000.

Refer to the CRD 4600 Cradle Quick Reference Guide for more information.

4. On power up for the chained cradles, all of the 3400 cradles’ LEDs light for 3

seconds. The LED on the Master CRD 3400 (see Figure 3-13) blinks 7 times, then
goes out.

If the LEDs for more than one CRD 3400 blink 7 times, there is a problem with the
interconnecting cables. Power the cradles down and verify that the interconnect
cables are correctly connected before reapplying power.

3-13

PDT 3400 Product Reference Guide

3-14

Chapter 4

Terminal Configuration Issues

Memory Available Versus Program Requirements

The PDT 3400 memory configuration required depends on the operating system or systems
and the application(s) you intend to run on the terminal.

Configuration Options

The terminal’s on-board RAM and on-board Flash configuration determines what software
can be loaded on the terminal. Configuration options of up to 4.5 MB of Flash, and up to 4
MB of RAM are available.

On Board RAM

Up to 4 MB of RAM is available for a RAM disk on the PDT 3400. One option for increasing
the amount of RAM available is to use the compression utility Stacker, which is included with
the PDT 3400 SDK. Based on a compression rate of 1.8 to 2.5, Stacker can expand a 0.5 MB
RAM disk up to 1.25 MB.

On Board Flash

Up to 4.5 MB of on-board Flash is available for the PDT 3400. To obtain more “disk”
storage, one alternative is to use Stacker.

The amount of on-board Flash required depends on what you plan to load into “ROM disk”.
Some possibilities are DOS, applications, and other user files. On-board Flash is divided into
“segments”, with segment divisions falling on 64K or 128K boundaries (refer to Figure 4-1).
It is not possible to update a portion of a segment; the full segment must be updated as a unit.

4-1

PDT 3400 Product Reference Guide

The segments in on-board Flash are grouped into “areas”, with each area consisting of one
or more segments. Typically, all segments in an area are erased and updated together. The
supported areas are IPL, BIOS, C:, D:, and user space.

128K

512 KB Flash
memory device (128
KB boundaries

Flash - 128K

2 MB (4 MB) Flash
memory device(s)
(64KB boundaries)

Note: This illustration shows a C: drive which exists totally in the 512 KB Flash device (128

KB boundaries). The D: drive and user space exists in the 2 MB (or 4 MB) Flash
device (64 KB boundaries).

IPL

BIOS

C:

D:

User Space

D: drive begins on
next boundary
after C: drive.

User space
begins on next
boundary after D:
drive.

Figure 4-1. Flash Memory Allocations

It is possible to erase and update an application stored in D: without updating the IPL, BIOS,
or C: drive. It is NOT possible, however, to update C: without updating D:. Because the
starting segment for D: falls on the next boundary after C: and that boundary is changeable,
updating C: means that D: must also be erased and updated. The user space likewise is
updated if C: or D: are updated, as the user space falls on the next boundary after D: (or C:,
if D: doesn’t exist). The IPL and BIOS can be updated independent of C: and D: because they
are always the same size and are always loaded in the same location.

For the PDT 3400, the IPL and BIOS are always loaded in the first two areas (the first 128K
segment) as shown in Figure 4-1. The third area, C:, is commonly used to store the DOS
operating system and common components such as scanning, RF, etc. The fourth area, D:,
can be used to store applications or data files. Any segments remaining comprise the user
space area and can be programmed individually as desired using the “Flash API”.

In calculating Flash requirements, remember that code such as DOS and applications can
only be stored in Flash. Applications and operating systems cannot execute out of Flash;
instead, they load from Flash into RAM and execute out of RAM.

4-2

Terminal Configuration Issues

Application Size Considerations

DOS applications often include an entire support infrastructure with them (aside from DOS
and BIOS calls, and various APIs supplied by TSRs). The need to include graphics support
code within DOS applications results in large, sophisticated, graphical DOS programs. This
often means that multiple applications carry multiple copies of such code. Some DOS
development systems allow applications to share code, but that is the exception. Where
possible, make use of shared code to save memory.

Matching Software Requirements to the Hardware
Available

In this chapter, we’ve discussed issues specifically related to ROM disk, RAM disk, and
applications. How does all of this information fit together?

There are a number of ways to configure your application based on the amount of Flash and
RAM as detailed below.

The configuration is set up as follows:

t 0.5 MB, 2.5 MB, or 4.5 MB Flash
t 2 or 4 MB RAM
t DOS, TSRs, application(s), and constant data are stored in ROM Disk.
t PDT 3400 boots from ROM Disk.

To meet additional software and data storage needs:

t Use Stacker to compress the ROM Disk and extend program and constant data

storage

t Add additional Flash (up to 4.5 MB) to meet program and constant data storage

needs

t Use Stacker to compress the RAM Disk
t Use EMSALLOC.SYS to reapportion the amount of RAM memory used for DOS

and as EMS memory used for RAM disk storage. Refer to the description of
EMSALLOC.SYS in the section Symbol-Provided Drivers in Chapter 5 for more
information on reapportioning RAM memory.

4-3

PDT 3400 Product Reference Guide

Overview: Terminal Configuration Process

Setting up and initializing the PDT 3400 requires performing one or more of a series of
procedures listed below. Refer to the following chapters for information on a specific process:

t Creating the applications — refer to the manuals listed in Related Documents and

included with the SDK for more information

t Setting up the terminal’s operating system files (covered in Chapter 5)

s Editing the DOS configuration files

t Building the hex image via TCM (covered in Chapter 6)

s Creating the hex image
s Downloading the ROM disk image(s)

t Loading RAM disk (covered in Chapter 7)
t Running BIOS Setup (covered in Chapter 8)
t Using Stacker to compress files to extend Flash and RAM Storage (discussed in each

chapter, as applicable).

4-4

Chapter 5 Terminal Configuration:

Edit the Configuration Files

Setup/Edit DOS Configuration Files

This section details the recommended edits of DOS system files.

Note: For more information on editing the DOS system files covered in this

section, please refer to the Microsoft® MS-DOS User’s Guide.

CONFIG.SYS

DOS Settings

BREAK = [ON | OFF]

Controls whether or not extended CTRL+C checking is enabled. Off is the default setting,
and this command is not required unless this feature is being enabled.

BUFFERS = n[,m] 1≤n≤99 0≤m≤8

Specifies the number of disk buffers to be allocated for use by DOS. The default value for the
PDT 3400 is n=15 and m=0. Many applications and environments request a larger setting.

COUNTRY = XXX[,YYY]

Specifies the country-specific settings. The default is U.S. This command is required only for
a different country setting.

5-1

PDT 3400 Product Reference Guide

DEVICE = driver.ext

This command causes a device driver to be loaded either low (into TPA) or high (into UMBs).

FILES = n 8≤n≤255

Controls the number of files that DOS can open at once. The larger this number, the more
memory DOS allocates for file handles. The default is 8, which is generally inadequate for
most applications and environments. Allocating too many files wastes memory; allocating
too few files may cause an application or environment to fail if it attempts to open too many
files. Unless there is a specific requirement for more files, we recommend using a value of
n=20.

INSTALL = file.ext

This command loads a TSR from CONFIG.SYS. This command can be used to load TSRs
(low only) that go along with drivers (as a convenience). Note that DOS does not load the
TSRs until the end of CONFIG.SYS (as opposed to where they appear). If you use your
application as a shell (see SHELL=), you can use this command to load TSRs prior to
execution of the application as the shell.

LASTDRIVE = x

Specifies the number of drives owned by DOS. Any device driver loaded which creates a new
drive letter begins at the next drive letter after the drive letter specified in this command.

This command is necessary only if the number of drive letters automatically served by DOS
must be increased. DOS automatically allocates A: and B:, plus C: and possibly D: if ROM
disk(s) are present. The RAM disk driver and Stacker are examples of drivers that allocate
drive letters starting with the next available drive letter. One common use of this command
is to ensure that the RAM disk driver and Stacker use the same drive letters, regardless of how
many ROM disks are loaded (e.g., LASTDRIVE = D: causes the first installable drive letter
to be E:, regardless of whether C: and D: are present or not).

Another possible use of this command is to reserve one or more drive letters for use by the
DOS SUBST command.

5-2

Terminal Configuration: Edit the Configuration Files

SET

This command sets environment variables in CONFIG.SYS instead of in AUTOEXEC.BAT.

Note: Environment variables are set in CONFIG.SYS only at the end of

CONFIG.SYS, regardless of where the SET command occurs.
Consequently, these settings cannot be used by device drivers, and this
command is generally only used if environment variables are required
by TSRs loaded via the INSTALL= command, or if the application is
being used as a command shell (e.g., turn-key application).

SET COMSPEC=

This command specifies the drive and path where the shell can be found. Use this command
only if the SHELL= command is used to select a program other than COMMAND.COM as
the shell, or if the shell is located in a directory other than the root directory of the boot drive.

SHELL = file.ext

This command specifies the command shell to be used. The default command shell is
COMMAND.COM from the boot drive’s root directory. Reasons for using this command
include:

t To increase the size of the environment table when running COMMAND.COM as

the shell.

Note: The recommended command line for this is:

SHELL=C:\COMMAND.COM/P/E:1024

For additional information, consult the MS-DOS User’s Guide.

t To run (and store) COMMAND.COM in a directory other than the root directory

(see also SET COMSPEC= above)

Note: TCM automatically puts COMMAND.COM in the root directory of

a ROM disk marked as bootable, so this should seldom be needed.

t To use an application other than COMMAND.COM as the shell.

5-3

PDT 3400 Product Reference Guide

STACKS = n, s n=0 and 8≤n≤64, s=0 and 32≤s≤512

This command controls the number and size of the DOS stacks used to service hardware
interrupts. Unless there is a specific requirement otherwise, we recommend using a value of
n=0 and s=0 to save memory.

Symbol-Provided Drivers

RDISK21T.SYS

This RAM disk driver provides the ability to create a simulated disk drive in RAM memory.
This driver is similar to the DOS RAMDRIVE.SYS driver; however, this driver adds the
ability to protect the RAM disk contents against accidental erasure or damage. Additionally,
RDISK21T allows RAM disk contents to be preserved across a Warm Boot.

This driver only supports creation of RAM disks using expanded(EMS) memory, not
transient program area (TPA) or extended (XMS) memory. RDISK21T.SYS can be used to
create more than one RAM disk (by loading it multiple times). Protection implies both write
protection and preservation across a Warm Boot. The /NOPROTECT switch can be used to
allow unprotected RAM disks to be created using RDISK21T.SYS. To create a protected
RAM Disk, add the following line to CONFIG.SYS:

DEVICE=RDISK21T.SYS XXXX

where XXXX is the number of KB (in decimal) you want your RAM Disk to be. If this
parameter is omitted, all available EMS memory is used for the RAM Disk. For an
unprotected RAM Disk, the command line would be:

DEVICE=RDISK21T.SYS XXXX /NOPROTECT

Note: Place this line after EMSALLOC.SYS and after VG230EMS.SYS.

When using RDISK21T.SYS without the /NOPROTECT switch (creating a protected RAM
disk), use VG230EMS.SYS with the /T:OFF switch. If you don’t, the RAM disk contents are
destroyed when the EMS driver loads. Refer to the sections on EMSALLOC.SYS and VG­230EMS in this chapter.

5-4

Terminal Configuration: Edit the Configuration Files

VG230EMS.SYS

The VG230EMS.SYS driver is an Expanded Memory Manager (EMM) that conforms to the
Lotus/Intel/Microsoft (LIM) version 4.0 Expanded Memory Specification (EMS). The driver
provides an interface for applications to access Expanded Memory. Currently, the Symbol­provided RAM Disk driver, RDISK21T, is the only application which uses Expanded
Memory on the PDT 3400.

To load the EMS driver, add the following line to CONFIG.SYS:

DEVICE=VG230EMS.SYS /t:off /f:D0-DC

Note: The /t:off option specifies that the EMS driver perform a non-

destructive test of memory. This option must be used if RAM Disk
contents are to be preserved across a warm reboot.

The /f:D0-DC option specifies the page frame to use to map in the
EMS memory. Under normal circumstances, this option should not be
changed.

EMSALLOC.SYS

The EMSALLOC.SYS driver is an optional utility that allows for adjusting the boundary
between the end of the DOS Transient Program Area (TPA) and the beginning of memory
used as Expanded Memory. The driver allows a minimum of 256K and a maximum of 640K
to be allocated as DOS TPA memory.

To load the EMSALLOC.SYS driver, add the following line to CONFIG.SYS:

DEVICE=EMSALLOC.SYS xxx

where xxx is the amount of memory in KB to allocate as EMS memory. The driver fails to
load if the amount allocated as EMS memory leaves less than 256K for DOS TPA memory.
Additionally, as the maximum amount of memory that DOS can directly use is 640K, any
requests that would leave more than 640K for DOS are adjusted to leave 640K for DOS and
allocate all additional memory as EMS memory.

Note: If used, the EMSALLOC.SYS driver MUST be loaded prior to the

VG230EMS.SYS driver.

5-5

PDT 3400 Product Reference Guide

PEN34T.SYS

The PDT 3400 Pen Driver provides a DOS mouse driver-compatible software interface for
reading coordinates and callback routines, and is used for running signature capture
applications on the PDT 3400.

The Pen driver maintains calibration data for the resistive screen overlay in CMOS memory.
If invalid calibration data is found in CMOS when the driver is loaded, a calibration utility
is automatically run to calibrate the screen.

Note: It is imperative that you load PEN34T.SYS before loading

IRCOMM.SYS. These two functions share a common interrupt line
(IRQ5) and require a specific loading order.

To load the driver, add the following line to CONFIG. SYS:

DEVICE = PEN34T.SYS

IRCOMM.SYS

Symbol provides an IrDA-compliant infrared software stack and an API for developing
applications that use the stack to communicate with remote IrCOMM devices.

IR COMM.SYS is required for performing cradle communications.

Note: If PEN34T.SYS is present, it is imperative that IRCOMM.SYS be

loaded AFTER PEN34T.SYS. These two functions share a common
interrupt line and require a specific loading order.

To load the IrDA driver, add the following line to CONFIG.SYS:

DEVICE=IRCOMM.SYS COM2 LPTn IRQ5 DONG3400 EJTx IRTOy

where:

COM2 routes data for COM2 to IrDA hardware.

LPTn routes data for LPT1, 2, 3, or 4 to IrDA hardware.

IRQ5 IR COM IRQ.

DONG3400 specific for the PDT 3400.

5-6

Terminal Configuration: Edit the Configuration Files

EJTx end of job timeout (between 1-255). Amount of time in seconds after

transaction is complete that the IrDA session is closed (INT 14/INT 17 API
only).

IRT0y Infrared link timeout (3, 8, 12, 16, 20, 25, 30, or 40 seconds). The amount of

time in seconds after loss or blockage of IR beam that the IrDA session is closed.

Note: When setting EJT and IRT0, EJT must be less than LRTO.

The application programmer should only modify the following parameters:

t LTPn
t EJTx
t IRT0y.

5-7

PDT 3400 Product Reference Guide

AUTOEXEC.BAT

Note: AUTOEXEC.BAT is processed by COMMAND.COM and has no

meaning if another program is used as a shell (see the section SHELL=
above).

DOS Settings

ECHO [ON | OFF | TEXT]

This command (which is commonly used in batch files, especially AUTOEXEC.BAT) displays
a text string (the TEXT option), or enable/disable the echoing of commands in the batch file
as it is executed. When a batch file is used to execute a program, it gives a more “transparent”
look if the commands which “set up” the applications’s execution are hidden. To prevent the
ECHO OFF command from itself echoing, precede it with an @ sign (e.g., @ECHO OFF).

MODE

This command sets up and/or configures various drivers. Refer to the MS-DOS User’s
Manual for more information.

PATH

This command sets the path(s) used to find executable programs.

PROMPT

This command modifies the DOS COMMAND.COM shell prompt.

SET

This command sets environment variables. This is normally used to set up environment
variables required by TSRs or applications/environments.

Symbol-Supplied TSRs

Symbol has provided the following device drivers and TSRs for use with the PDT 3400. For
information on loading the TSRs device drivers, and on the APIs supported by each device
driver or TSR, refer to the PDT 3400 System Software Manual, p/n 70-33290-XX.

5-8

Terminal Configuration: Edit the Configuration Files

FLASHPCT.EXE

The Flash Management Services TSR API is for debugging use on the development PC only.
It is not designed for use on the PDT 3400 terminal. This TSR allows developing and testing
of applications which use the Flash Management API.

POWER34T.EXE

The Power Management Driver TSR API provides operating-system level power
management. Use this TSR instead of the POWER.EXE TSR supplied with MS-DOS. While
POWER.EXE can be used on the PDT 3400, it cannot be used in conjunction with
POWER34T.EXE, and does not provide as efficient a power management. POWER34T.EXE
requires that XBIOS34T.EXE or XBIOSPCT.EXE be loaded first and will not load unless one
of these two files is present. When used on the development PC with XBIOSPCT.EXE, this
TSR can be used for testing power management functionality of an application on the
development PC.

XBIOS34T.EXE, XBIOSPCT.EXE

These TSRs provide extended BIOS-level functionality specific to PDT 3400 features. Load
XBIOS34T.EXE on the PDT 3400 terminal ONLY as it uses PDT 3400-specific hardware.
XBIOSPCT.EXE can be loaded on the development PC for use in testing and debugging PDT
3400 applications on the development PC. Although the API for the two TSRs is the same,
XBIOSPCT.EXE does not act on certain commands because the required hardware is not
present. The return values, however, fall within those defined for XBIOS34T.EXE, allowing
useful testing and debug.

SCN1D21T.EXE

The DOS Scanner API provides one-dimensional bar code scanning support and supplies an
API for controlling scanning from an application. This TSR requires the presence of
POWER34T.EXE and XBIOS34T.EXE to load. Additionally, this driver requires the presence
of PDT 3400-specific hardware, and cannot be loaded on the development PC (even if
XBIOSPCT.EXE is loaded instead of XBIOS34T.EXE).

5-9

PDT 3400 Product Reference Guide

5-10

Chapter 6

Terminal Configuration:

Building and Sending the Hex Image

Overview

To assist in setting up the ROM Disk image, Symbol includes a Windows utility in the SDK,
Terminal Configuration Manager (TCM), to simplify building and downloading the hex
image to the PDT 3400.

Note: An MS-DOS utility, HEX2TERM, is also included for downloading

hex images to the PDT 3400.

In TCM, you create a script that contains the information (commands to copy files and
scripts) for building the image. TCM works with directory windows, which display the
directory structure of your script and the source directories, files, and scripts. You can open
multiple scripts, drag and drop items from a drive/directory to the script, rename and delete
files in the script, etc. On building the image, TCM adds all the files, directories, and scripts
referenced in the script to the image.

The SDK includes a number of standard scripts, demos/samples, foundation scripts, and
component scripts, for you to use as a base for creating your own scripts. These scripts can
be found in the SYMSDK\SDK3400\SCRIPTS directory.

Note: Before you begin creating a script to build a hex image, take the time

to identify the files required (system files, drivers, applications, etc.)
and to locate the files’ source directories to make the script building
process easier.

6-1

PDT 3400 Product Reference Guide

The required processes for building a hex image in TCM include:

t Starting TCM
t Creating or modifying a script
t Building the hex image
t Sending the hex image

Each process is described below.

Note: Full on-line help is available for the Terminal Configuration Manager

by pressing F1 while in the TCM screen, or by clicking on the Help
Menu and choosing Index, or by clicking on the button on the
Menu bar and pointing to the item in question on the screen.

For information on using Stacker to compress a ROM Disk built in TCM, refer to the special
note on TCM and Stacker at the end of this chapter.

6-2

Terminal Configuration: Building and Sending the Hex Image

Starting Terminal Configuration Manager

To start TCM, double click on the TCM icon in the SDK3400 group.

When started, the screen shown in Figure 6-1 appears, displaying three directory windows.
Each of the directory windows is split, with the left half (or pane) of the window displaying
the directory tree for the current drive, and the right half displaying the directory contents for
the current drive.

Figure 6-1. Terminal Configuration Manager Initial Screen

6-3

PDT 3400 Product Reference Guide

Table 6-1 lists the components of the TCM start-up screen.

Table 6-1. TCM Screen Components

Component Description

Script Window Associated with a script file containing the information to create a ROM

Disk image. This window is the target window, or the primary TCM
window in which you can create a script or change a script file’s contents
by copying, deleting, and renaming files and directories. More than one
script window can be open at a time.

The Script Window consists of two panes, the Directory Tree Pane on the
left and the Directory Contents Pane on the right. Directories added to the
script are listed alphabetically by volume in the Directory Tree Pane.
Subordinate directories, files, and scripts of each volume are listed in the
Directory Contents Pane.

Script Browser A read-only source window for copying scripts to a master script. Only one

Script Browser window can be open at a time.

File Browser A read-only source window for files and/or directories to include in the

script being built. Only one File Browser window can be open at a time.

Tool Bar Contains the tools for taking action on a script. The tools allow you to

create a new script, open a script, copy a file, copy a script, delete and
rename a file, create a directory, view object properties, view script
properties, update the open directory, and check, build, and send the hex
image.

Button Bar Displays the drive icons available on the development PC, network drives

you are connected to, CD-ROM drives, etc., from which you can pull
source files and scripts.

Confirmation Messages

TCM automatically displays confirmation messages for specific actions, such as:

t copying a file or directory to a script
t deleting a file or directory from a script
t renaming a file or directory in a script
t adding an existing script to a master script
t erasing a compressed drive as part of a build
t reviewing edits made to system files during a build

6-4

Terminal Configuration: Building and Sending the Hex Image

The confirmation messages by default are on. To clear or restore previously cleared
confirmation messages:

1. Click on the Options Menu and choose Confirmations to display the Confirmations

check list.

2. Click in the check box for the message you wish to clear or restore.

Note: Clearing the Review Edits During Build check box has the same effect

as accepting edits to the system files without further review (Yes to All
button). Refer to Step 5 in Building the Image for more information
on edits to system files during a build.

Note: We recommend building a few compressed drives and becoming

comfortable with using Stacker before clearing the Erase Stacker
Drive Warning check box. Refer to Step 8 in Building the Image for
more information on erasing the compressed drive.

3. Click the OK button to exit.

6-5

PDT 3400 Product Reference Guide

Creating the Script for the Hex Image

On start-up, TCM displays the screen shown in Figure 6-1, with the Script Browser window
and File Browser window pointing to the SDK3400\SCRIPTS directory and the SDK3400
directory. The Script Window directory pane displays two volumes: VOLUMELABEL, the
uncompressed volume, and <CMP:>, the compressed volume.

To set up a new script:

t Create a new script file or open an existing script
t Drag and drop existing scripts to that “master” script
t Drag and drop existing files and/or directories to the master script
t Edit the system files for the script
t Set the script parameters
t Set the system boot file path (for a bootable image) if necessary
t Save the script
t Review and modify the script.

Each process is described in the sections that follow.

Open a New or Existing Script

Scripts are created in the Script Window.

To open a new script:

t Choose File | New from the menu bar.
t OR select the New button from the tool bar.

To open an existing script (e.g., a standard script provided in the SDK):

t Choose File | Open from the menu bar and select the script file name.
t OR select the Open button from the toolbar and select the script file name.
t OR double click on an existing script in the Script Browser window.

Note: If you open and make changes to an existing script, saving the changes

writes over the existing script. If you wish to use an original or
Symbol-supplied standard script as a base and save the changes in a
new script, use Save As instead of Save after making the changes.

6-6

Terminal Configuration: Building and Sending the Hex Image

Copy Components to the Script

Copy files or scripts from the Browser Windows to the Script Window using the drag and
drop method with the mouse or the Copy command.

Note: To check a file’s statistics before including it in a script, right-click on

the file. TCM displays the File Statistics screen which includes the
path, file size, time-date stamp, and attributes of the file (refer to
Figure 6-2).

Figure 6-2. Files Statistics Screen

To copy files to the script:

1. Click on the File Browser Window to make it the active window.

2. Click on the source directory in the Directory Tree Pane.

3. TCM displays the directory contents in the Contents Pane.

4. Click on the file(s) and/or directory in File Browser.

Note: Optionally, use the standard Windows Shift+Left-click and

Control+Left-click features to select multiple files and directories.

5. Drag and drop the selected file(s) and/or directory from File Browser to the target

directory in the Script Window.
OR click on the target directory and select File Browser Copy from the File Menu.

OR click on the target directory and select the File Browser Copy icon from the
toolbar.

6-7

PDT 3400 Product Reference Guide

6. TCM displays a confirmation message asking if you want to copy the files to the
directory (if enabled in the Communications screen — available from the Options
menu).

7. Choose the Yes button to complete the copy.

It is possible to invoke an application from the File Browser window. Files with an .exe
extension run automatically; for other files, TCM checks the Windows file manager
association list to determine which application to run. An example: running Notepad and
checking the contents of a file before including it in a script.

To invoke an application from within TCM, double-click on the file name in the File Browser
window.

To copy (include) existing script files to the script being built:

1. Click on the Script Browser Window to make it the active window.

2. Click on the source directory in the Directory Tree Pane.
TCM displays the directory contents in the Contents Pane.

3. Click on the script in the Script Browser Window.

4. Drag and drop the selected script from Script Browser to the target directory in the
Script Window.

OR click on the target directory and select File | Script Browser Copy from the menu
bar.

OR click on the target directory and select the Script Browser Copy icon from the
toolbar.

5. TCM displays a confirmation message asking if you want to copy the script to the
directory. Choose the Yes button to complete the copy.

Edit the System Files

For the applications to work on the PDT 3400, you must modify the DOS system files. TCM
includes an automated process, System File Edits, for including the information needed to run
the applications on the PDT 3400 in the system files.

How System File Edit Works

You create the system files (AUTOEXEC.BAT and CONFIG.SYS) and/or add edits to existing
system files, via the System File Edit screen, while creating the script.

TCM associates the edits to the system files with that script. When TCM builds the hex
image, it appends your edits to the system files in the order the edits were made.

6-8

Terminal Configuration: Building and Sending the Hex Image

t If you didn’t include a system file in the script, but include edits to the file, TCM adds

an “empty” file to the root directory at build time and appends the edits to that file.

t If you build a master script using multiple subscripts as components, TCM first

appends edits specified by the subscripts in the order the subscripts were added.
TCM then appends the master script’s edits to the system files after adding the
subscript edits.

To edit the system files for a script:

1. Select the Script Window for the script to be edited.

2. Choose Script | System File Edits from the menu bar.

OR on the toolbar, choose the System File Edits button.

Figure 6-3. System File Edits Screen

3. In the file field, type in the name of the system file you want to edit:

s AUTOEXEC.BAT
s CONFIG.SYS
s Any other text file requiring edits.

Note: The file field’s drop-down list is empty (refer to Figure 6-3) until you

add system files to it. Once you’ve entered edits to a system file in the
System File Edit screen, that file is listed in the drop-down list (refer
to Figure 6-4) and can be selected for additional edits.

6-9

PDT 3400 Product Reference Guide

4. Enter the lines to be appended to the system file in the text-editor box.

Figure 6-4. System File Edits Screen, with Edits

s To delete a line, highlight the line and press the Delete key on your keyboard.
s To delete the file, click on the Delete button.

5. Choose the OK button to save and exit.

6-10

Terminal Configuration: Building and Sending the Hex Image

Making the Most of System File Edit

You have several options for setting up and maintaining the system files for a hex image. To
make the most of TCM’s System File Edit requires planning, but reduces the maintenance
effort.

Option 1: Update Outside TCM. You can establish and update the system files outside TCM,
using any text editor, and include the files in the script. In that case, TCM treats these system
files solely as components to be added to the hex image, not as system files. The system file
edit function is not invoked when the hex image is built. This method does not allow for on­the-fly edits to the system files to accommodate last-minute changes to the script contents.
Going outside TCM to maintain the files increases the possibility that the script’s contents
and the system files may not match.

Option 2: A Simple Use of System File Edit. A simple use involves creating the system files in
TCM without using a base file as a starting point, and making only the master script’s edits
to the system files.

1. Create the script.

2. Set up all edits in the master script System File Edits screen.

3. TCM automatically includes the empty system files, enters the edits to those files, and

builds the resulting files into the image.

This option is best suited to small scripts that have few subcomponents, each requiring
individual edits.

Option 3: Using System File to Full Advantage.

1. In your script, include base system files containing standard file contents that you

want all scripts to include.

2. Add the subscripts in the order you want them included in the hex image.

Note: Each subscript may include system file edits. The order in which a

subscript is added is the order in which the subscript’s system file edits
are appended to the master script’s system files during the build.

3. Edit the system file edits for the master script.

4. Save the script.

5. Run Build.

6-11

PDT 3400 Product Reference Guide

During the build, TCM starts with the base file and appends each subscript’s system
file edits, in the order the subscripts are added to the master script, then appends the
master script’s edits.

6. TCM presents an edit box displaying the resulting contents of each system file built.
If you did not include a base system file, TCM displays the file as Created. If you
included a base system file and specified edits to the file, TCM displays the file as
Built.

7. If necessary, alter the contents of the system file to correct for order dependency. You
can move lines, delete lines, etc., in the edit box.

s To accept the file as is, choose the OK button.
s To accept this file and all other system files without further edits, choose the Yes

to All button.

Choose Cancel to exit the build.

8. If you edited the system file, the buttons change.

s To accept the file with the changes just entered, choose the Accept button.
s To undo the system file build and return to the file’s original state before any edits

were appended, choose the Reject button.

s To exit the build, choose the Cancel button.

9. If you accepted changes made in the review box, TCM saves the edits to the current
build.

On the next build, TCM will display the system file as Saved.

10. To accept the saved system file, choose the OK button.
To delete the hand edits from step 7 and build the file as new, choose the Rebuild

button.

Set the Script Parameters

TCM uses the script parameters to set up the hex image.

To set the script parameters for a specific script:

1. Click on the script in the Script Browser window to select it.
OR double-click on the script to make it the active script in the Script Window.

2. Choose Script | Script Properties from the menu bar.
OR choose the Script Properties button from the toolbar.

6-12

Terminal Configuration: Building and Sending the Hex Image

3. In the Script Properties window (refer to Figure 6-5), set the terminal type to PDT

3400.

Figure 6-5. Script Properties Sheet

4. Select the hex image to be built. The choices are:

s C: (ROM Disk 1)
s D: (ROM Disk 2)

5. Set the maximum size of the image (the amount of flash space available for

directories and files included by the script). The total contents of the image include:
s the hidden system files automatically included for a bootable ROM Disk (C:

ROM Disk; see Step 6 below)

s the files and directories included in the uncompressed volume by the script
s the files and directories included in the compressed volume (e.g., STACVOL.46C

or STACVOL.46D) by the script.

To see all the directories and files a script places in the uncompressed volume, double
click on the VOLUMELABEL: indicator in the left-hand pane of the Script Window.

6-13

PDT 3400 Product Reference Guide

To see all the directories and files a script places in the compressed volume, double
click on the CMP: indicator in the left-hand pane of the Script Window.

If only a C: ROM Disk is used (no D: ROM Disk or User Space), set the image size
to the maximum size possible for the configuration’s flash chip (393216 for .5 MB
flash, 2490368 for 2.5 MB, or 4587520 for 4.5 MB Flash). Set the image size for the
C: ROM Disk image size smaller if a D: ROM Disk and/or a User Space will be used.

Note: For the first build, we recommend setting the image size to the

maximum size allowed, and resetting (downsizing) the size later when
the actual image size is known.

The hex file resulting from the build is normally larger than the image;
do not use the hex file size as a guide for determining the hex image
size.

6. If the image is bootable, check the box. If the image is not bootable, clear the check
box.

Set the C: drive to be bootable. The D: drive cannot be bootable. TCM ignores a
bootable setting for the D: drive.

7. Determine whether the output from a build is a hex file or a “build” to a disk
(directory) on the development PC.

If you choose to build to disk, verify that the directory where the build will be placed
is empty. The build to disk deletes any files in the directory selected.

a. If Hex File is chosen, select the hex file format used to encode the image for

transfer to the PDT 3400. The hex file choices are:

- Standard

- Compressed

- Binary

- Transparent.

6-14

Terminal Configuration: Building and Sending the Hex Image

Table 6-2 provides information on each of the hex file formats.

Table 6-2. Hex File Formats

Flow

Hex File Format

Standard 7-bit ASCII Y 7 2.8 Produces the largest file with the

Compressed 7-bit ASCII with

runlength coding
compression

Binary 8-bit ASCII with

runlength coding
compression

Transparent Raw N 8 1.14 Produces one of the smallest, but

Control

Y 7 1.71 High compatibility with most

Y 8 1.04 Less compatible for porting to other

Data

Bits

File

Size* Comments

slowest transmission speed, but
offers the best portability to other
hosts. Can be treated as a text file.

ASCII-oriented hosts. Can be treated
as a text file.

hosts than Standard or Compressed
format. Can be treated as a text file.
Produces a small hex file.

For very compressible data, this
option may produce the best results

also the least compatible hex files for
porting to other hosts. Does not use
compression. Cannot be treated as a
text file. For images that don’t
compress easily, is best choice for
size and transfer speed using direct
serial link. Use Transparent if you
plan to create your own program
loader for transferring the hex file to
the PDT 3400 and don’t need
software flow control.

* Approximate hex file size as a multiple of the image size.

b. If Disk Build is selected, TCM copies all of the files included in the script to the

location specified in the Path: field.

8. Choose the OK button to save the parameters and exit.

6-15

PDT 3400 Product Reference Guide

Set the System Boot File Path

If you set the hex image as bootable, TCM automatically includes the DOS boot files
(IO.SYS, MSDOS.SYS, COMMAND.COM) in the hex image. Set the boot file path telling
TCM where to find the files.

To enter a system file path:

1. Choose Option | Paths from the menu bar.

2. In the System boot files field, type in the full path for the boot files, e.g.,
C:\SYMSDK\SDK3400\TERMINAL\DOS.

3. Choose the OK button to save and exit.

Set the Communications Parameters

Note: This procedure is applicable only if you plan to build a hex file and

transmit it to the PDT 3400.

Set the parameters for the device (cradle or other direct serial link) connecting the PDT 3400
and the development PC.

To set the communication parameters:

1. Choose Options | Communications from the menu bar.

2. In the Port field, select the serial port being used on the development PC
(default = COM1).

3. In the Baud Rate field, set the data transfer rate (default = 38400).

Note: For a faster download, a baud rate of 115200 works on most

development PCs.

4. In the Parity field, set the error checking value (default = None).

5. In the Data Bits field, set the number of data bits used for each character
(default = 8).

Note: For Standard and Compressed hex files, set Data Bits to 7.

For Binary and Transparent hex files, set Data Bits to 8.

6-16

Terminal Configuration: Building and Sending the Hex Image

Figure 6-6. Setting the Communications Parameters

6. In the Stop Bits field, set the time between transmitted characters (default = 1).

7. In the Flow Control field, set the method of controlling data flow (default = None).

Note: Transparent hex files cannot use software flow control. All of the hex

files can use hardware flow if the correct cable is attached and
software honoring hardware flow control is loaded on the PDT 3400.

8. Choose the OK button to save the parameters and exit.

Save the Script

To save the changes to a new script:

1. Choose File | Save As from the menu bar.

OR on the toolbar, choose the Save button.

2. Enter the path and file name. TCM appends a .TCM extension to the script.

3. Choose the OK button.

Note: If you save an untitled script, TCM by default saves the script to the

directory that the Script Browser is pointing to.

6-17

PDT 3400 Product Reference Guide

To save changes to an existing script:

t Choose File | Save from the menu bar.
t OR on the toolbar, choose the Save button.

Note: If you open and make changes to an existing script, saving the changes

writes over the existing script.

If you wish to use an original or Symbol-supplied standard script as a
base and save the changes in a new script, use Save As instead of Save
after making the changes.

6-18

Terminal Configuration: Building and Sending the Hex Image

Reviewing a Script

To review a script’s commands for building the hex image, use the Script Commands Sheet.
The Script Commands Sheet displays the commands in the script that record editing changes
made to the scripts, files, and directories in the script, in the order the edits occurred.

In Script Commands, you can check the properties of a specific file, add a script, bring up the
Script Window for a script listed in the files added, and delete a script.

To review the script properties for the current script:

1. Click on the Script Window to make it the active window.

2. Choose Script | Script Commands from the menu bar.

3. TCM displays the commands, in the order entered, that added files, directories, and

scripts (Figure 6-7).

Figure 6-7. TCM Script Commands Sheet

6-19

PDT 3400 Product Reference Guide

Figure 6-8. File Properties Sheet

To view the properties of a file listed in the script:

1. Select the file or script in the script listing.

2. Choose the Properties button.

3. TCM displays the File Properties window (refer to Figure 6-8).
The File Properties window lists the source directory, destination, file description,

and script that included the file in the master script. The source file specifications
(drive, path, filename, and extension) are editable. The destination and script cannot
be changed.

To view the Script Window for a subscript added to the script:

1. In the Script Commands Sheet, select the command adding the subscript in the
listing.

2. Choose the View button.

3. TCM displays the Script Window for the selected subscript.

To delete a command that edited the script:

1. In the Script Commands Sheet, select the command in the listing.

2. Choose the Delete button.

3. Choose the OK button.

6-20

Terminal Configuration: Building and Sending the Hex Image

Figure 6-9. Copying a Script

To copy (include) a subscript to the script listing:

1. In the Script Commands Sheet, choose the Copy Script button (refer to Figure 6-7).

2. TCM displays the Select Script File window (refer to Figure 6-9).

3. Point to the drive and directory where the script is located, then select the script to

be added.

4. Choose the OK button.

5. TCM appends a command to include the script to the end of the list in the Script

Commands Sheet.

To exit the Script Commands Sheet, choose the OK button.

6-21

PDT 3400 Product Reference Guide

Building the Image

As part of the build, TCM automatically performs a check on the script. The check includes
verifying that all files referenced in the script actually exist. If the image is bootable, TCM
verifies that the boot files are available. If the image includes a compressed volume, TCM
checks for the Stacker volume and information files on the hard disk.

If all the referenced files are found, TCM also compares the date-time stamp of the script and
referenced files and subscripts against the time-date stamp for the existing hex image (if a hex
image was built previously). If the hex file does not exist or if the script or any referenced file
or subscript has a newer date-time stamp than the existing image, TCM builds a new image.

Note: Performing a check is more important for previously existing scripts

to ensure that files referenced in the script are still in the designated
locations.

To check a script:

1. In the Script Window, select the script.

2. Save the script, if not already saved.

3. Choose Script Menu | Check from the menu bar.
OR on the toolbar, choose the Check button.

4. TCM verifies that files referenced in the script exist on available drives and lists an
error message in the Errors found box for any missing files (refer to Figure 6-10).

5. Choose the OK button to exit.

6-22

Terminal Configuration: Building and Sending the Hex Image

Figure 6-10. Errors Found Listing from a Script Check

To build a script:

1. In the Script Window, select the script to be built.

2. Choose Script | Build from the menu bar.

OR on the toolbar, select the Build button.

3. TCM requests that you save the script if it was modified since the last save.

4. TCM performs a check.

s If the script has no errors, TCM proceeds with the build.
s If a file is missing, TCM lists the error in the Errors found box and halts the build.

6-23

PDT 3400 Product Reference Guide

5. If you used System File Edit to set up the system files, TCM presents a dialog box
displaying the contents of each system file built (refer to Figure 6-11).

/RP=2
/P=10
C:\STACVOL.46C

21

Figure 6-11. System File Edits Dialog Box

s Review and, if necessary, alter the contents of the system file to correct the order.

You can move lines, delete lines, etc., in the edit box.

s To accept the file as is, choose the OK button.
s To accept the first file and all other system files without further edits, choose the

Yes to All button.

s Choose Cancel to exit the build.

6. If you edit the file, the button choices change.

s To accept the file with the changes just entered, choose the Accept button.
s To undo the system file build and return to the file’s original state before any edits

were appended, choose the Reject button.

s To exit the build, choose the Cancel button.

7. If you accepted changes made in the review box, TCM saves the edits to the current
build in progress. On the next build, TCM will display the system file as Saved.

s To accept the saved system file, choose the OK button.
s To delete the hand edits and build the file as new, choose the Rebuild button.

8. If you accepted the edits, TCM proceeds to build the hex image and create the hex
file.

6-24

Terminal Configuration: Building and Sending the Hex Image

Note: If you place files in the compressed drive <CMP>: during the build,

TCM displays the message:

About to complete erase drive X

warning that the contents of drive <x:> will be erased. Verify that the
drive letter listed is the correct Stacker drive and NOT your hard
drive!

If the hard drive is listed (or a drive other than the expected Stacker
drive), press the Cancel button to cancel the build and refer to the
section Stacker Post Installation in Chapter 2 for information on
properly setting up Stacker.

During the build, TCM copies the “hidden system” files, the compressed volume files, and
the uncompressed volume files, in that order.

If the build is successful, TCM displays the elapsed time, hex file size (flash space used by the
script), end segment address, and image size. To calculate the amount of flash remaining,
subtract the hex file size from the Image Size set in the Script Properties Window.

If the Build Fails

If the build fails, TCM displays a series of messages. The first describes what caused the build
to fail, the second states that the build failed.

If the total amount of flash required by the script exceeds the image size, a TCM error results
and the build fails. To correct this situation, reduce the number of files in the uncompressed
volume or reduce the size of the compressed volume. Refer to the section Set the Script
Parameters in this chapter for more information on setting the image size appropriately.

6-25

PDT 3400 Product Reference Guide

Sending the Hex Image

Once the hex file is built, you are ready to download it to the PDT 3400. A Hex image
download requires a program loader stored on the PDT 3400 and either TCM or
HEX2TERM running on the development PC. The PDT 3400 comes with a program loading
utility, Initial Program Loader (IPL), stored in write-protected flash. To run IPL, the PDT
3400 must be connected to a host PC by direct serial connection (COM1).

You have the option of creating your own program loader using the Flash API (it does not
replace the IPL). Refer to the PDT 3400 System Software Manual for DOS Applications for
more information on the Flash API.

Loading the BIOS

Uploading a new BIOS erases only the segment of Flash where BIOS is stored. While IPL is
updating the BIOS, the BIOS image is saved in memory until the entire BIOS is received and
verified. The ROM Disk image and application storage area are unaffected.

Loading a ROM Disk

The PDT 3400’s ROM Disk is organized as two separate drives instead of the conventional
hard disk. This separation allows for updating a section without erasing the entire disk.

If ROM Disk 1 (C:) is updated, IPL erases from the specified start of ROM Disk 1 to the end
of Flash ROM, including ROM Disk 2 and user space (application storage). If ROM Disk 2
(D:) is selected, ROM after Disk 1 is erased, including ROM Disk 2 and user space.

Preparing for the Download

Connect the PDT 3400 and Development PC

To send the hex file to the PDT 3400 requires placing the PDT 3400 in a cradle linked to the
development PC. Refer to Chapter 3, Installing the Hardware, for information on connecting
the cradle to the PC.

Setup for Download Using TCM

Note: If you made changes to the script since saving it, save the script again.

1. Select the script so that the script is active in the Script Window.

2. Choose Script | Send from the menu bar.

6-26

Terminal Configuration: Building and Sending the Hex Image

OR on the toolbar, choose the Send button.

Note: TCM checks the script and builds the image, if the timestamp changed

since the last build, before preparing to send the resulting hex file. To
transfer the hex file without performing these steps again, select
Transmit from the File Menu. The steps for Transmit are the same as
for Send.

3. TCM checks for a connection to the PDT 3400 and waits for IPL on the PDT 3400.

4. Go to the section IPL Setup.

Setup for Download Using HEX2TERM

HEX2TERM is a MS-DOS utility which can be used in place of TCM for transferring hex
files from a PC to the PDT 3400. The hex file can be either a BIOS update or a ROM disk
image.

To run HEX2TERM:

1. On the development PC, type:

HEX2TERM filename [baud] [port]

where:

filename Specifies the name of the hex file being transferred to the PDT 3400.

[baud] Is the baud rate. The baud rate defaults to 9600. Possible values are

2400, 4800, 9600, 19200, 38400, 57600, or 115200 (default).

[port] Is the COM port designation: COM1 (default) or COM2.

The default COMM parameters are as follows:

9600 baud
COM1
8-bit data
no parity
Xon/Xoff flow control

2. Go to IPL Setup.

6-27

PDT 3400 Product Reference Guide

IPL Setup

To set up IPL for the transfer on the PDT 3400:

1. Boot to IPL.
a. Press and hold C+M+PWR for 12 seconds or the reset time specified in Setup until

the PDT 3400 reboots.

b. Release C+M+PWR.

The PDT 3400 displays a banner message identifying the program title, version,
copyright, and checking ROM Disk(s) message.

2. The PDT 3400 displays the IPL Screen (refer to Figure 6-12). To navigate through
the IPL screen:

s Press to scroll down through the available selections for each field; press to

ê

scroll up through the selections.

s Press the Scan Bar to select a value.

EIPL Ver.3.04

BIOS

ROM DISK #1

NOT AVAILABLE

USER AREA

IPL

Figure 6-12. IPL Screen

3. Select the update area from the following:

s BIOS
s ROM Disk 1 (default)
s USER AREA

é

Note: ROM Disk 1 MUST be present to load the User Area. If ROM Disk

1 is not present or is corrupt, the User Area cannot be selected.

6-28

Terminal Configuration: Building and Sending the Hex Image

IPL proceeds to the Transfer Port Selection Menu shown in Figure 6-13.

Select Xfer Por

IR Port

Serial Port

Figure 6-13. Select Transfer Port

4. Select the port (default = IR Port) and press the Scan Bar.

IPL proceeds to the Baud Rate Selection Menu shown in Figure 6-14.

ROM 512KB

Prev.Menu

9600
19200
38400
57600

115200

Figure 6-14. Baud Rate Selection Menu

5. Select the baud rate (default = 115200) and press the Scan Bar. The other parameters
are fixed at no parity, 8 data bits, and 1 stop bit.

To return to the previous menu, press the Scan Bar with Prev. Menu selected.

Note: The baud rate selected in IPL must match the baud rate selected in

HEX2TERM or TCM.

6. When you select the baud rate, IPL checks for the terminal in the CRD 3400. If is
not detected, the terminal displays the prompt:

Insert in

Office Cradle!

or Hold PWR Key

5 Secs to

Exit IPL Mode!

6-29

PDT 3400 Product Reference Guide

7. Place the PDT 3400 in a CRD 3400 office cradle.
When the office cradle is detected, IPL communicates with the cradle and sets it up

for IPL mode. The cradle LED should be blinking at this point.

8. IPL proceeds to erase the selected area and display the prompt:

Waiting to REC
ROM Disk X
115200

to indicate that the PDT 3400 is ready to receive data, and 115200 is an example of
the baud rate selected.

Continue the Send on the PC

1. If you are using TCM, choose the OK button to proceed with the send.
If you are using HEX2TERM, press <Enter> on the PC to begin the transfer. Don’t

wait longer than 5 minutes to press the key or a time-out occurs and you will have
to start the process over again.

2. The PDT 3400 displays the following screen:

RECEIVING XXXX

where XXXX is the byte count transferred.

When the BIOS or ROM Disk is loaded, the PDT 3400 displays the following
message:

CHECKING DISK X

Download Successful

If the download is successful, the PDT 3400 displays:

DOWNLOAD DONE

HIT TRIG KEY
FOR IPL MODE

The cradle re-initializes and stops blinking

6-30

Terminal Configuration: Building and Sending the Hex Image

Download Failure

If the download fails, the PDT 3400 displays the message:

“Download Failed!
ROMDISK #1

and includes a message indicating what the error was. These error messages include:

Error Message Action to Take

Erase Error Previous contents in flash not erased. Reattempt the download.

Line Stat Err Reattempt the download.

Baud Too High Change the baud rate to a lower setting and reattempt the download. See

Set the Communications Parameters for information on setting the baud
rate for a particular script in TCM; see IPL Setup or Setup for Download
Using HEX2TERM for setting the baud rate in IPL or HEX2TERM.

Image Corrupt Retry the download. If download fails again, bring up the script in TCM

and run Build again, then reattempt the download. If you continue getting
the error, call the Symbol Support Center for assistance.

Wrong Area You may be attempting to download a BIOS to an area in flash other than

the one reserved for the BIOS, or a hex image to the area reserved for the
BIOS. Verify the type of image being downloaded and target area in flash,
then reattempt the download.

Image Too Big File exceeds the flash capacity. Review the hex image contents, resize the

image (see Set the Script Parameters), run build again, and reattempt the
download.

Not Hex File Verify that the file being sent is a hex file and reattempt the download.

Write Error Reattempt the download.

Checksum Error Reattempt the download.

Verify Failed Reattempt the download.

Unable to Contact
Cradle

Check the cradle’s power connector and reattempt the download.

Press <Enter> to return to the IPL Main Menu.

6-31

PDT 3400 Product Reference Guide

Exit IPL

Press and hold PWR for 4 seconds to exit IPL and boot the PDT 3400.

Exiting TCM

To exit TCM:

t Choose File | Exit from the menu bar.
t OR press <Alt+F4>.
t OR double-click the close box.

Exiting HEX2TERM

To exit HEX2TERM:

Press <Ctrl-C>.

6-32

Terminal Configuration: Building and Sending the Hex Image

Special Note: TCM and Stacker

To build ROM Disk images with TCM and use Stacker to compress the ROM Disk, follow
these steps:

1. Ensure that Stacker is installed as directed in Chapter 2, Software Installation on the

Development PC.

2. Ensure that the Stacker post-installation is completed as directed in Chapter 2,

Software Installation on the Development PC

3. Place files to be located on the compressed drive in the <CMP> section of the script.

The compressed volume used to build a script must be large enough to hold all of the
directories and files placed in it by the script. To see these directories and files, double
click on the <CMP>: indicator in the left-hand pane of the Script Window.

4. Load the appropriate Stacker files.

Note: Use the supplied script file (e.g., STACK.TCM) as an example of how

to load Stacker for use in a ROM Disk.

How TCM and Stacker Work Together

TCM operates on the compressed volume using the development PC drive letter on which the
compressed volume was mounted.

During the build process, TCM erases all contents of the compressed volume (if any exist
from a previous build), then copies the directories and files included in the script into the
compressed volume. Stacker compresses the files as they are copied, adjusting the remaining
space based on the actual compression ratio achieved.

If Files Exceed Compressed Volume Size

If the total size of the files and directories that the script attempts to place in the compressed
volume exceeds the volume’s capacity, a TCM error results and the build fails. To correct this
situation, reduce the number of files and directories placed by the script into the compressed
volume or increase the size of the compressed volume.

Adding Files to a Compressed Volume After a Build

Following a successful build, TCM displays the amount of free space that Stacker reports is
remaining in the compressed volume. You can examine the compressed volume directly on
the development PC drive letter on which it was mounted using Windows File Manager or

6-33

PDT 3400 Product Reference Guide

the DOS DIR command. You can also experiment with adding files to the compressed volume
to see if they will fit; if they do, update the script to include these files in the compressed
volume and rebuild the script.

6-34

Chapter 7

Terminal Configuration: Loading a RAM Disk

Loading a RAM Disk

RAM disks allow the PDT 3400’s RAM to be organized as a simulated disk to allow writable
data storage. To create one or more RAM disks, use the Symbol RAM disk driver
RDISK34T.SYS which is included as part of the Symbol PDT 3400 SDK.

Protected RAM Disk

Symbol’s RAM disk driver (RDISK34T.SYS) provides the capability to create a protected
RAM Disk in expanded memory.

Note: The Expanded Memory Manager, VG230EMS.SYS, must be loaded

before RDISK34T.SYS to provide EMS memory for use by the RAM
Disk. For details on loading the Expanded Memory Manager, refer to
the section VG230EMS.SYS in Chapter 4.

To create a RAM Disk using RDISK34T.SYS, add the following line to CONFIG.SYS:

DEVICE=RDISK34T.SYS xxx

where xxx is the RAM Disk’s decimal size in kilobytes. This size is rounded up to the nearest
16K, but does not exceed the amount of available expanded memory. If the size parameter is
omitted, all available expanded memory is used by the RAM Disk.

Include the /NOPROTECT switch following the size to specify that the RAM Disk is not to
be preserved across warm reboots or protected from corruption by errant programs.

7-1

PDT 3400 Product Reference Guide

A protected RAM Disk survives a warm reboot, keeping all files stored on the disk intact.
RAM Disk can be preserved following a cold reboot IF power was not removed for more
than 15 minutes AND the EMSALLOC.SYS driver was not used to increase the RAM Disk
size (see section Using EMSALLOC.SYS to Increase Size of RAM Disk for more
information). Additionally, the Symbol RAM Disk driver takes precautions to protect the
data stored on a protected RAM disk from accidental corruption.

By default, RAM disks created by RDISK34T.SYS are protected. To create a RAM Disk that
is not protected, use the /NOPROTECT switch on the command line.

Include the /CLEARONCOLD switch on the command line to specify that the RAM Disk is
not to be preserved across cold reboots, even if power to memory is retained.

Using EMSALLOC.SYS to Increase Size of RAM Disk

By default, all RAM up to 640K is allocated to MS-DOS. Any additional RAM, less16K that
is used as Video RAM, is allocated as EMS memory. The RAM allocation on a PDT 3400
with 2 MB of RAM is as follows:

MS-DOS 640 KB
EMS Memory 1392 KB
Video Memory 16 KB

Total 2048 KB (2 MB)

The RAM allocation on a PDT 3400 with 4 MB of RAM is as follows:

MS-DOS 640 KB
EMS Memory 3440 KB
Video Memory 16 KB

Total 4096 KB (4 MB)

To allow more flexibility in allocating RAM memory, Symbol supplies an EMS Allocation
utility, EMSALLOC.SYS. This utility allows you to allocate less memory to MS-DOS, leaving
additional memory available for use as EMS memory. The RAM allocation for MS-DOS can
be adjusted from the default 640 KB down to a minimum of 256 KB. This adjustment can
result in a RAM allocation for EMS memory of up to 1446 KB on a PDT 3400 with 2 MB
of RAM, or up to 3824 KB on a PDT 3400 with 4 MB of RAM.

7-2

Terminal Configuration: Loading a RAM Disk

Note: The amount of EMS memory and RAM Disk allocated must be

balanced by the amount of RAM required by MS-DOS, by
applications, and by Symbol-supplied drivers.

For information on loading the EMSALLOC.SYS driver, refer to the section
EMSALLOC.SYS in Chapter 4.

Using Stacker to Extend RAM Disk Storage

If you choose to use a RAM Disk, you can compress the RAM Disk to increase disk storage.
Because RAM is static (e.g., is lost when no voltage is present or after a Cold Boot), the
volume must be created on boot-up. This is done by adding the following line in the
CONFIG.SYS file:

DEVICE = SCREATE.SYS X:

where X is the drive letter assigned to the RAM Disk (RDISK34T.SYS).

Note: Ensure that this line is before DEVICE=C:\STACKER.COM if

mounting both ROM and RAM Disks.

Once this line is added, the volume is created on boot-up but still needs to be mounted. This
is accomplished by one of two methods defined below.

1. Mounting Compressed ROM Disk and RAM Disk

If you compress both the ROM Disk and the RAM Disk, mounting the volumes is very
similar. Add a line in the STACKER.INI file (refer to Chapter 2 for information on editing
STACKER.INI) to reflect the new volume (e.g., D:\STACVOL.DSK,RP). The RP after the
volume name, indicating Replacement, allows the drive letter the volume is on (e.g., D:) to be
the drive letter of the compressed drive. When the line DEVICE=C:\STACKER.COM is
executed in CONFIG.SYS, it mounts all of the volumes including the volume on RAM Disk.

Note: You can also use the command supplied in method 2 when

compressing both the ROM and RAM Disks.

7-3

PDT 3400 Product Reference Guide

2. Mounting Compressed RAM Disk without Compressed ROM Disk

If you are compressing only the RAM Disk, add the following line to the AUTOEXEC.BAT
FILE:

STACKER 2X:\STACKVOL.DSK

where X is the drive letter assigned to the RAM Disk (RDISK34T.SYS).

Note: Ensure that STACKER.OOM is on your ROM Dis, even though you

are not compressing the ROM Disk. If STACKER.COM is not on the
drive during run-time, executing the above statement results in a File
Not Found error.

7-4

Chapter 8

Terminal Configuration: Running BIOS Setup

PDT 3400 BIOS Utility

Run the Setup Utility in the following circumstances:

t out of the box, when CMOS is empty and the default parameters set by the BIOS are

not satisfactory.

t once all software is loaded, to review the PDT 3400’s operating parameters.
t when power (battery or power supply) is removed for more than 15 minutes, because

the PDT 3400 returns to “out of box” default values.

The Setup Utility is incorporated in the Flash ROM BIOS and performs a standard and a
default setup function.

8-1

PDT 3400 Product Reference Guide

Running Setup

To run Setup:

1. Boot the PDT 3400 by pressing and holding the PWR button for 12 seconds or the
value specified in Setup.

2. During the boot process, press the Scan Bar when the PDT 3400 displays the prompt:

Trig Skips Test

3. Press and hold the Scan Bar when the PDT 3400 displays the message:

Trig Runs Setup

until Setup displays the screen shown in Figure 8-1:

SETUP 1.0

STANDARD

DEFAULT
EXIT

Figure 8-1. BIOS Setup Screen

a. To change the BIOS settings, press the Scan Bar with STANDARD highlighted

and proceed to step 4.

b. To reset the BIOS to the default settings, scroll down to DEFAULT using and

press the Scan Bar. The default settings are provided in Default Configuration
Parameters in this chapter for reference.

c. To exit the Setup screen, scroll down to EXIT using and press the Scan Bar.

ê

4. If you selected STANDARD, the Main Menu (Figure 8-2) is displayed:

MAIN MENU

TIME 00 :00:00

DATE 01/01/96
CONTRAST 3

KEYCLICK
SUSPEND

RESET
BOOT SEQ

ON

30

12

C

ê

Figure 8-2. BIOS Setup Main Menu

8-2

Terminal Configuration: Running BIOS Setup

Note: Only four lines of the Menu are displayed at a time. Use the and

keys to scroll up and down through the fields.

ê

é

The PDT 3400 times out if no entries are detected. Press PWR to
restore the Setup screen.

5. To change the values in a field, press the Scan Bar which scrolls forward through the

range of possible values.
a. Time. In 24-hour format. To set hours or minutes, highlight the appropriate 00

and press the Scan Bar to increment hours/minutes until the correct time is
displayed.

b. Date. Enter a date in MM/DD/YY format. Setup scrolls through each segment of

the field in sequence. To change a segment, press the Scan Bar while that segment
is highlighted to increment the month, day, and year until the correct date is
displayed.

c. Contrast. Range is 0 - 7. Values at either end of the range (0 or 7) can make the

screen difficult to read. Default is 3.

d. Keyclick. Determines whether the keyboard “clicks” each time a key is pressed.

Default is ON.

e. Suspend. Sets the time in which the display times out if no activity is detected, in

increments of 5 seconds. Range is 0 -1275. A value of 0 disables the timer. Default
is 30 seconds.

f. Reset. Sets the length of time that the Power key must be pressed to cold boot the

PDT 3400 in increments of 4 seconds. Range 4 - 64. Default is 12 seconds.

g. Boot Sequence. Sets the default boot sequence. The choices are C: (ROM Disk)

or A:. Default is C.
h. Volume. Sets the beeper volume. The choices are low or high. Default is low.
i. Lamp. Sets the backlight on or off. Default is off.

6. Once all parameters are set, highlight MAIN MENU and press Scan Bar to exit.

7. From the Setup Menu, select EXIT.

8-3

PDT 3400 Product Reference Guide

From the Exit Menu (Figure 8-3), you have the following options:

EXIT NO SAVE

EXIT SAVE
MAIN MENU

Figure 8-3. BIOS Setup Exit Menu

a. To exit without saving any of the changes and revert to the default parameters,

select EXIT NO SAVE and press the Scan Bar. The PDT 3400 reboots
automatically.

b. To save the parameters to CMOS and cold boot the terminal, select EXIT SAVE

and press the Scan Bar.

c. Select MAIN MENU to re-enter Setup.

Default Configuration Parameters

The Default Setup restores all the default configuration data without requiring the operator
to reset each field. Refer to Table 8-1 for default configuration information.

Table 8-1. PDT 3400 Default Configuration Values

Configuration Value Default

Contrast 3

Keyclick On

Suspend Timeout 30 seconds

Reset Time 12

Boot Sequence Checks C:, then A:

Volume Low

Lamp Off

8-4