Page 1
PDT 3200
Technical
Reference
Guide
PDT 3200 Technical Reference Guide
Page 2
70-31468-01
Revision A — July, 1997
ii
Symbol Technologies, Inc. One Symbol Plaza, Holtsville N.Y. 11742
Page 3
PDT 3200
Technical Reference Guide
70-31468-01
Revision A
July, 1997
Page 4
1997
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 Þrmware,
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 Þrmware 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, N.Y. 11742
http://www.symbol.com
iv
Page 5
Contents
Chapter 1. Default Disk Driver Organization and
Unit Configurations
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
File System Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Drive A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Drive B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Drive C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Drive D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Drive E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
System Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
BIOS and DOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Device Drivers and Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
PC Card and RF Networking Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Unit Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
I/O PC Card Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Chapter 2. System Utilities
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
CFGDEV.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
DECODE.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
PM.COM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
FLASHDSK.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
LOCK.COM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
ORGANIZE.COM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
FORMAT.COM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
XFER.EXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
VDISK.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Chapter 3. Resetting the PDT 3200
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Warm Boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Cold Boot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Safe Boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Hardware Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Recommended Programming Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
v
Page 6
Chapter 4. Using PC Cards
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Configuring Your PC Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
PhoenixCARD Manager Plus (PCM+) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
ATA Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Fax/Modem Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
LAN Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
RF Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Chapter 5. ROM-DOS Commands
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Command Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
ROM-DOS vs. MS-DOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Command Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
@ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
; . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
ATTRIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
BREAK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
BUFFERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
CALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
CHDIR (CHange DIRectory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
CHKDSK (CHecK DiSK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
CLS (CLear Screen) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
COMMAND (Command Processor) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
COPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
COUNTRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
CTTY (Change TeleTYpe) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
DEL (DELete) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
DEVICEHIGH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
DIR (DIRectory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
DOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
ECHO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45
ERASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-47
EXIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49
FCBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
FIND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52
FOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
GOTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55
vi
Page 7
HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-56
IF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-57
INCLUDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-59
INSTALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61
LASTDRIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-62
LOADHIGH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-63
MENUCOLOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-64
MENUDEFAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-65
MENUITEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-67
MKDIR (Make DIRectory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-69
NEWFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70
NUMLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-71
PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-72
PAUSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73
PRINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-74
PROMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-76
REM (REMark) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-78
REN (REName) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-79
RMDIR (ReMove DIRectory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-80
SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-81
SHARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-82
SHELL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-83
SHIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-84
SORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-85
STACKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-86
SUBMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-87
SWITCHES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-89
TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-90
TREE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-92
TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-93
VER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-94
VERIFY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-95
VOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-96
XCOPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-97
XDEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-99
vii
Page 8
viii
Page 9
About This Manual
This manual is a supplement to the
a reference for system administrators, developers, and programmers who want to
create end-user solutions for the PDT 3200 terminal.
This reference guide contains technical information about the PDT 3200Õs system
conÞguration, disk drives, utilities, and DOS commands. It also provides information
about using PC cards with the PDT 3200 and resetting the unit.
PDT 3200 Product Reference Guide.
It is provided as
Related Publications
¥ PDT 3200 Quick Reference Guide, p/n 70-31467-xx
¥ PDT 3200 Product Reference Guide, p/n 70-31466-xx
¥ PDT 3200 Run Time Library Reference Manual, p/n 70-31577-xx
¥ CRD 3200 Cradle Quick Reference Guide, p/n 70-31469-xx
ix
Page 10
Conventions
Keystrokes are indicated with the angle brackets as follows:
ENTER
ALT+X
BKSP, SHIFT, ON
IdentiÞes a key.
IdentiÞes a simultaneous key combination.
IdentiÞes a key sequence.
Escape sequences described do not contain angle brackets characters. For example:
ESC[3;4f
Indicates the sequence: escape character, left bracket, numeral 3, semicolon,
numeral 4, and letter f.
Typeface conventions used include:
Italics
Syntax
Screen
Indicates Þrst time a new item is used. A deÞnition follows the italicized terms.
Italics also indicate book titles or information that must be replaced by an actual
value. Italics also express menu titles.
Indicates text entered by the user.
Indicates a text displayed on a screen or terminal.
Note:
Indicates tips or special requirements.
Caution
Indicates conditions that can cause equipment damage or data
loss.
WARNING
Warnings indicate procedures that are potentially dangerous
and should therefore be performed only by Symbol-authorized
repair personnel.
x
Page 11
Chapter 1 Default Disk Driver
Organization and Unit ConÞgurations
Chapter Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
File System Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Drive A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Drive B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Drive C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Drive D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Drive E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
System Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
BIOS and DOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Device Drivers and Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
PC Card and RF Networking Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Unit Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
I/O PC Card Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
1-1
Page 12
PDT 3200 Technical Reference Guide
1-2
Page 13
Chapter 1: Default Disk Driver Organization and Unit Configurations
Introduction
This chapter details the default contents of the disk drives and the organization of system
software on the PDT 3200.
File System Format
Overview
The PDT 3200Õs default Þle system format is as follows:
¥ Drive A is a read-only ßash drive. The contents of this drive cannot be changed.
¥ Drive B is a read-only ßash drive that you can update by using the core update
program, COREXFER.EXE, from a host machine. (Normal operation will not
require updating of this drive.)
¥ Drive C is a resident ßash disk drive that is accessed with the FLASHDSK.SYS
device driver. You can use this drive to store applications and data.
¥ Drive D is a RAM disk accessed with the VDISK.SYS device driver. This drive can
be used to store applications as well as data. However, you should take great care
in selecting Þles for this drive. As with any RAM drive, its contents will be lost if
power is removed.
¥ Additional drives are mapped to ATA ßash PC cards or to network drives via
radio frequency (RF).
This organization provides an easy-to-use, extensible system that allows a high degree of
performance, usability, and customization. The following sections more fully describe the
contents and intended uses of each of the PDT 3200Õs drives.
Drive A
Drive A is a disk image that is located in ßash along with the BIOS and ROM-DOS. A
read-only drive, it is intended to remain secure throughout the life of the unit. Drive A
contains the following Þles:
¥ AUTOEXEC.BAT, the Þrst Þle in the startup sequence
¥ COMMAND.COM, the DOS shell
¥ CONFIG.SAF, the Þrst Þle in the safe-boot sequence
¥ CONFIG.SYS, the Þrst Þle in the boot sequence
¥ REV.COM, the utility that reports the Þrmware revision
1-3
Page 14
PDT 3200 Technical Reference Guide
The CONFIG.SYS and AUTOEXEC.BAT Þles contain only basic commands that the unit
needs to run correctly (see Figure 1-1 and Figure 1-2). Both Þles chain to their respective
counterparts on the B drive, as described in the next section.
The CONFIG.SAF Þle (see Figure 1-3) is used in the safe-boot sequence. For more information about the CONFIG.SAF Þle, see page 1-5.
REM ************************************************
REM Initial CONFIG.SYS file for starting the system.
REM ************************************************
NEWFILE = B:\CONFIG.SYS
Figure 1-1. CONFIG.SYS File on Drive A
@echo off
REM **************************************************
REM Initial AUTOEXEC.BAT file for starting the system.
REM **************************************************
VER
PATH=A:\
B:\AUTOEXEC.BAT
Figure 1-2. AUTOEXEC.BAT File on Drive A
REM *********************************
REM Initial CONFIG.SYS for safe boot.
REM *********************************
NEWFILE = B:\CONFIG.SAF
Figure 1-3. CONFIG.SAF File on Drive A
Drive B
Drive B is a disk image that is located in ßash. A read-only drive, it is intended to be used
to store mandatory utilities and initialize the boot process. During normal use this drive
will not be updated. Drive B includes the following Þles:
¥ AUTOEXEC.BAT, the second Þle in the startup sequence
¥ CFGDEV.SYS, the system parameter conÞguration device driver
1-4
Page 15
Chapter 1: Default Disk Driver Organization and Unit Configurations
¥ CONFIG.SAF, the second Þle in the safe-boot sequence
¥ CONFIG.SYS, the second Þle in the boot sequence
¥ COREUPD.COM, the utility that updates the Þrmware image
¥ DECODE.SYS, the bar code decoding device driver
¥ FLASHDSK.SYS, the resident ßash disk device driver
¥ FORMAT.COM, the disk-reformatting utility
¥ FUNCTEST.COM, the functional test for system components
¥ LD.BAT, the batch Þle for RESPONSE.BAT processing
¥ LOCK.COM, the utility for locking or unlocking the resident ßash disk and RAM
disk
¥ ORGANIZE.COM, the utility for reorganizing ßash disk data
¥ PM.COM, the power-management utility
¥ VDISK.SYS, the RAM disk device driver
¥ XFER.EXE, the serial transfer utility
The CONFIG.SYS Þle (see Figure 1-4) will load the FLASHDSK.SYS driver to create the C
drive and the VDISK.SYS driver to create the D drive. It will then load DECODE.SYS and
CFGDEV.SYS before chaining to its counterpart on drive C. The AUTOEXEC.BAT Þle (see
Figure 1-5) will chain to its counterpart on drive C, except during a safe boot.
The purpose of the CONFIG.SAF Þle (see Figure 1-6) is to provide a minimal boot conÞguration that preserves the ßash and RAM drives. When the safe-boot sequence is initiated,
the CONFIG.SAF Þle is processed instead of the CONFIG.SYS Þle. This prevents chaining
into the drive C initialization Þles by omitting the NEWFILE = C:\CONFIG.SYS command. It also eliminates the loading of the DECODE.SYS and CFGDEV.SYS drivers.
1-5
Page 16
PDT 3200 Technical Reference Guide
REM ****************************************
REM Standard CONFIG.SYS for building system.
REM ****************************************
REM ***************************
REM Create flash and RAM drives
REM ***************************
DEVICE = B:\FLASHDSK.SYS 4096
DEVICE = B:=VDISK.SYS 4096 /e
REM *********************************
REM Load decode/configuration drivers
REM *********************************
DEVICE = B:\DECODE.SYS
DEVICE = B:\CFGDEV.SYS
NEWFILE = C:\CONFIG.SYS
Figure 1-4. CONFIG.SYS File on Drive B
@echo off
REM ******************************************
REM Standard AUTOEXEC.BAT for starting system.
REM ******************************************
PATH=%PATH%;B:\
C:
IF EXIST A:\CONFIG.SAF IF EXIST C:\AUTOEXEC.BAT C:\AUTOEXEC.BAT
1-6
Figure 1-5. AUTOEXEC.BAT File on Drive B
REM **********************************
REM Standard CONFIG.SYS for safe boot.
REM **********************************
REM ****************************
REM Recover flash and RAM drives
REM ****************************
DEVICE = B:\FLASHDSK.SYS 4096
DEVICE = B:\VDISK.SYS 4096 /e
Figure 1-6. CONFIG.SAF File on Drive B
Page 17
Chapter 1: Default Disk Driver Organization and Unit Configurations
Drive C
Drive C is a resident ßash disk drive that is accessed via the FLASHDSK.SYS device
driver. By default, this drive is conÞgured to have full read and write access. The default
CONFIG.SYS and AUTOEXEC.BAT Þles reside here. You can modify these Þles to customize the system for an application. They will be called after the CONFIG.SYS and
AUTOEXEC.BAT Þles on drives A and B are processed.
The PDT 3200 ConÞguration Utility gives you the ability to customize what software tools
and utilities are placed on the unit. By default, the utility installs this software to the C
drive. If the unit is intended to be used with PC cards, then the Phoenix PC card drivers
are installed in the PCM subdirectory on the C drive, and the proper entries will be transferred into the CONFIG.SYS and AUTOEXEC.BAT Þles. The exact conÞguration of Þles
and the contents of the CONFIG.SYS and AUTOEXEC.BAT Þles will change according to
the conÞguration of the unit.
For RF capability, additional Þles for network connectivity would be required. These
might include a Telnet program or peer-to-peer networking tools, depending on what you
choose to install.
If something happens to a unit and data integrity becomes questionable, use the CHKDSK
utility to detect and correct errors on drive C. (CHKDSK.COM does not come installed on
the PDT 3200. You can download it using XFER or the PDT 3200 ConÞguration Utility.)
You can also use ORGANIZE.COM to recover unused sectors.
Drive D
Drive D is a RAM disk drive. By default, this drive resides in extended memory and is
sized 1MB less than the total RAM in the PDT 3200 unit (either 1MB or 3MB).
Drive D can be used for short-term data storage. Programs that need to be loaded into
memory and then removed from memory quickly can also be located there. The drive can
also be used for scratch disk space or temporary Þles.
The PDT 3200 preserves the data on drive D between warm or cold boots by checking for
an existing RAM disk. However, only minimal checking is performed on any disk that is
found; if something happens to a unit and data integrity becomes questionable, you
should use the CHKDSK utility to detect and correct errors on drive D. (CHKDSK.COM
does not come installed on the PDT 3200. You can download it using XFER or the PDT
3200 ConÞguration Utility.)
1-7
Page 18
PDT 3200 Technical Reference Guide
Drive E
Drive E is the ATA ßash card. The PC card looks like a hard disk drive to the operating
system and the user. More ßexible than ßash disk drive C, it can be used for safer and
more permanent bulk storage of batch data than the RAM disk (drive D). This drive exists
only on systems conÞgured to use ATA ßash cards.
Drive E could also be a peer-to-peer or client-server network drive that is accessed
through an RF or Ethernet network card link. This option allows the developer to make
many network drives (drives E, F, etc.) available to applications.
1-8
Page 19
Chapter 1: Default Disk Driver Organization and Unit Configurations
System Software
BIOS and DOS
The PDT 3200 uses a modiÞed version of General SoftwareÕs BIOS with DatalightÕs ROMDOS. Both products are burned into system ßash in a single 256K image. The A drive is included in the image, physically addressed just below the BIOS image.
ROM-DOS uses the Datalight COMMAND.COM processor. This processor is fully Microsoft 6.2 compatible, except that it occupies about half the space in memory. In addition,
drive C contains Datalight DOS Þles in a DOS subdirectory.
Device Drivers and Utilities
The following device drivers are always present on the PDT 3200Õs drive B:
¥ CFGDEV.SYS
¥ DECODE.SYS
¥ FLASHDSK.SYS
¥ VDISK.SYS
The following utilities are always present on drive B:
¥ COREUPD.COM
¥ FORMAT.COM
¥ FUNCTEST.COM
¥ LOCK.COM
¥ ORGANIZE.COM
¥ PM.COM
¥ XFER.EXE
See page 1-5 for descriptions of these drivers and utilities. See chapter two for more information about them.
PC Card and RF Networking Software
PC card device drivers and utilities as well as RF networking solutions can be installed to
drive C (the ßash drive) or drive D (the RAM drive). You can use the PDT 3200 ConÞguration Utility to download the necessary Þles to the PDT 3200.
1-9
Page 20
PDT 3200 Technical Reference Guide
Unit Configurations
Several conÞgurations are possible for the system software on the unit, depending upon
the type of hardware that is to be supported. Two standard conÞgurations are listed below, along with directory structures and default CONFIG.SYS and AUTOEXEC.BAT Þle
descriptions.
Default Configuration
The conÞguration created by DEFAULT.CFG in the PDT 3200 ConÞguration Utility will
create a C drive that contains PALPRO.EXE, part of the Symbol Portable Applications Library (PAL). The data Þles will be stored on drive D. PC card drivers able to support ATA
cards will be loaded.
FILES = 30
REM --------------------------------------------------------REM --- Phoenix Card and Socket services for accessing PC Cards
REM --------------------------------------------------------device = c:\pcm\cnfignam.exe /NORMAL
device = c:\pcm\pcmssit.exe
device = c:\pcm\pcmcs.exe
device = c:\pcm\pcmata.sys
1-10
Figure 1-7. CONFIG.SYS File on Drive C for Default Configuration
REM --------------------------------------------------------REM --- The following lines set up default parameters for some
REM --- environment variables. These lines may be modified or
REM --- overridden in the USER section below.
REM ---------------------------------------------------------
set prompt=$p$g
set dircmd=/ogn /p
REM --------------------------------------------------------REM --- The following section is for customized user entries.
REM --------------------------------------------------------REM --------------------------------------------------------REM --- Insert user-specific options and commands here.
Page 21
Chapter 1: Default Disk Driver Organization and Unit Configurations
REM --------------------------------------------------------REM --------------------------------------------------------REM --- The following lines add system components to the PATH
REM --- and run the main application executable, if one was
REM --- specified.
REM --------------------------------------------------------IF EXIST c:\bparams.ini copy c:\bparams.ini PARAMS
set path=c:\;c:\dos;%path%
c:
cd\
upgstart
Figure 1-8. AUTOEXEC.BAT File on Drive C for Default Configuration
I/O PC Card Support
The PDT 3200 ConÞguration Utility has an option for support of I/O cards. This option
will download the Phoenix Super Client Driver (PCMSCD.EXE) to the C:\PCM subdirectory on the PDT 3200. It will also add the command for loading of this driver to the
CONFIG.SYS Þle. The CONFIG.SYS and AUTOEXEC.BAT Þles below were created by
eliminating ATA card support and adding I/O card support to DEFAULT.CFG.
FILES = 30
REM --------------------------------------------------------REM --- Phoenix Card and Socket services for accessing PC Cards
REM --------------------------------------------------------device = c:\pcm\cnfignam.exe /NORMAL
device = c:\pcm\pcmssit.exe
device = c:\pcm\pcmcs.exe
device = c:\pcm\pcmscd.exe
Figure 1-9. CONFIG.SYS File on Drive C for I/O Card Support
1-11
Page 22
PDT 3200 Technical Reference Guide
REM --------------------------------------------------------REM --- The following lines set up default parameters for some
REM --- environment variables. These lines may be modified or
REM --- overridden in the USER section below.
REM --------------------------------------------------------set prompt=$p$g
set dircmd=/ogn /p
REM --------------------------------------------------------REM --- The following section is for customized user entries.
REM --------------------------------------------------------REM --------------------------------------------------------REM --- Insert user-specific options and commands here.
REM --------------------------------------------------------REM --------------------------------------------------------REM --- The following lines adds system components to the PATH
REM --- and runs the main application executable, if one was
REM --- specified.
REM --------------------------------------------------------IF EXIST c:\bparams.ini copy c:\bparams.ini PARAMS
set path=c:\;c:\dos;%path%
c:
cd\
upgstart
1-12
Figure 1-10. AUTOEXEC.BAT File on Drive C for I/O Card Support
Page 23
Chapter 2 System Utilities
Chapter Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
CFGDEV.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
DECODE.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
PM.COM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
FLASHDSK.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
LOCK.COM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
ORGANIZE.COM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
FORMAT.COM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
XFER.EXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
VDISK.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
2-1
Page 24
PDT 3200 Technical Reference Guide
2-2
Page 25
Chapter 2: System Utilities
Introduction
This chapter describes the utilities that are designed to be run on a PDT 3200 unit. For
each device driver or executable Þle, a brief description is given, followed by any command line parameters and their meanings. Any parameters listed may be supplied using
either upper- or lowercase letters, and the hyphen (-) may be substituted for the forward
slash (/).
2-3
Page 26
PDT 3200 Technical Reference Guide
CFGDEV.SYS
CFGDEV.SYS is located on drive B of the PDT 3200 unit. When CFGDEV.SYS is loaded by
B:\CONFIG.SYS, a logical character-based device called PARAMS is created. This device
receives programming strings that modify the conÞguration parameters that control the
behavior of several system components. There are three ways for the developer to send
programming strings to the PARAMS device.
¥
Bar Code Scanning
with EE can be scanned using any bar code scanning device. The
Product Reference Guide
¥
File Copy
and copied to the PARAMS device. The PDT 3200 ConÞguration Utility creates a
Þle called BPARAMS.INI that contains all of the conÞguration settings.
C:\AUTOEXEC.BAT on the unit contains a command to copy this Þle to
PARAMS (IF EXIST c:\bparams.ini copy c:\bparams.ini PARAMS). You may
also create your own Þle containing conÞguration settings.
Example:
1. Create a MYPARAMS.INI Þle with the following text: $+$-D2E00EE. D2
2. Copy MYPARAMS.INI to the PARAMS device using the following DOS
¥
Developer's Toolkit API
two function calls that allow you to send conÞguration strings to the PARAMS
driver from within a C application. See CFG_Write() and CFG_Read() in the
Developer's Toolkit.
Attempts to create, delete, or modify a Þle called PARAMS will conßict with the PARAMS
device. You cannot eliminate the loading of CFGDEV.SYS except through the safe-boot
process.
Files containing the bar code programming strings can be created
Use D2 defaults with CTRL-ALT-DEL sequence disabled.
sets the D2 defaults, E00 disables CTRL-ALT-DEL.
command: COPY MYPARAMS.INI PARAMS
Special bar code labels beginning with $+$- and ending
PDT 3200
contains many useful labels.
The API in the PDT 3200 Developer's ToolKit contains
2-4
Page 27
Chapter 2: System Utilities
DECODE.SYS
This driver controls bar code scanning devices and decodes bar code labels into text. If
special programming bar codes are read, the decoded information will be sent to the
PARAMS device (see CFGDEV.SYS above). Otherwise, the resulting text is placed in the
keyboard buffer for reading by the application. DECODE.SYS is located on drive B of the
PDT 3200 unit and is loaded by the CONFIG.SYS Þle located on that drive. You cannot
eliminate the loading of DECODE.SYS except through the safe-boot process.
2-5
Page 28
PDT 3200 Technical Reference Guide
PM.COM
Use this utility to control various power-management features of the PDT 3200. You can
use it at the command line or in a batch Þle (including AUTOEXEC.BAT) to set or read
power-management settings.
Syntax
PM [/b#] [/f#] [/h] [/i] [/r] [/t#]
Options
/b#
Sets the automatic timeout for the backlight. Replace the # with the number of seconds to
wait after a keypress before automatically turning off the backlight. Each keypress restarts
the timeout countdown. The range of acceptable values for # is 0 (off) to 255; the default is
15 seconds.
/f
#
Sets the time interval for audio indication when the batteries are low. Replace the # with
the number of minutes between sounding of the tone. The tone will not sound until the
battery has been in the low state for the same number of minutes. The range of acceptable
values for # is 0 (off) to 255; this option is off by default.
Note:
The audio warning uses extra current, causing the
batteries to drain faster. Therefore, you might want to
set the interval for as long as possible or not use it at all.
/h
Displays a help Þle for the utility.
/i
Displays timer settings for auto-off, backlight timeout, and low-battery audio indication.
/r
Resets power management to the cold-boot defaults.
2-6
Page 29
Chapter 2: System Utilities
/t
#
Sets the auto-off timeout. Replace the # with the number of seconds of nonuse before the
unit should transition to its lowest power state. The range of acceptable values for # is 16
to 1032 or 0 for off; the default is 300 seconds (5 minutes).
2-7
Page 30
PDT 3200 Technical Reference Guide
FLASHDSK.SYS
This driver conÞgures all of the unitÕs available ßash memory as a read/write disk, called
a ßash disk. Reading from a ßash disk is fast, but writing can be somewhat slower. This
driver is located on the PDT 3200Õs drive B and is loaded by the CONFIG.SYS Þle located
on that drive. You cannot eliminate the loading of FLASHDSK.SYS.
2-8
Page 31
Chapter 2: System Utilities
LOCK.COM
Use this utility to enable or disable write protection on ßash or RAM drives. (This is the
software equivalent of the write-protect tab on a ßoppy disk.) You can use LOCK to protect against accidental erasure of all Þles stored on the ßash disk.
Whenever the PDT 3200 is rebooted, write protection on a drive will be disabled, which is
the default state. To lock the drive upon bootup, include a LOCK command in the AUTOEXEC.BAT Þle on drive C.
Syntax
LOCK [
drive
:] [/l] [/u] [/y]
Options
drive
SpeciÞes the drive letter of the drive which is to be locked or unlocked. If you do not specify a drive letter, the current drive is used.
/l (the letter L)
Lock the ßash drive to prevent further disk writes.
/u
Unlocks the ßash drive, allowing further disk writes.
/y
Suppresses output from being sent to the display.
Note:
If both the /l and /u options are given, the last option
speciÞed will take effect.
2-9
Page 32
PDT 3200 Technical Reference Guide
ORGANIZE.COM
This utility reorganizes sectors on a ßash drive to improve ßash disk access. Data is relocated so that all free sectors are grouped together, reducing the overhead of freeing space
for new data. ORGANIZE.COM has a greater effect on a ßash disk as the disk gets closer
to being full.
Note:
The only PDT 3200 drive you can organize with this
utility is the ßash disk created with the FLASHDSK.SYS
driver. ATA ßash drives will not respond properly to
this utility.
Syntax
ORGANIZE [
drive
:] [/y]
Options
drive
SpeciÞes the drive letter of the ßash drive which is to be reorganized. If a drive letter is not
given, the current drive will be used.
/y
Suppresses output from being sent to the display.
2-10
Page 33
Chapter 2: System Utilities
FORMAT.COM
Formats a read-write disk drive. Only the ßash and RAM drives may be formatted using
this command. FORMAT uses the existing drive parameters to recreate the drive, but
without any Þles stored on it. This provides a quick method for cleaning out an existing
drive.
Syntax
FORMAT [
Options
drive
SpeciÞes the letter of the drive to be formatted. If you do not specify a drive letter, the current drive is used.
/y
Suppresses output from being sent to the display, and bypasses the usual prompt to proceed with formatting.
drive
:] [/y]
2-11
Page 34
PDT 3200 Technical Reference Guide
XFER.EXE
The XFER utility gives you the ability to transfer Þles to and from a PC through the PDT
3200Õs serial port.
Syntax
XFER [/
Options
/1|2
Sets the communication port (COM1 or COM2) to use.
/a
Receives data and appends it to the speciÞed Þle. If you do not use this option, the Þle will
be overwritten. This option is available only when used with the /p option.
/b
#
SpeciÞes the baud rate. Acceptable settings are 2400, 4800, 9600, 19200, 38400, 57600, and
115200; the default is 19200.
option1
[/
option2
] ...]
filename
/d
#
If used with the /p option, this option speciÞes the receive timeout, in seconds. Replace
the # symbol with the desired number of seconds for the timeout.
If used with the /s option, this option speciÞes the delay between packets, in 55-millisecond intervals. Replace the # symbol with the desired number of delay intervals.
The range of acceptable values for # is 0 to 65,535. If neither /p nor /s is speciÞed, this option is ignored.
/h
Displays a help Þle for the XFER command.
/o
Overwrites the speciÞed Þle without prompting. If this option is not used and the Þlename exists, the following message and prompt will be displayed:
ÒThe file exists. Overwrite? (Y/N)Ó
2-12
Page 35
Chapter 2: System Utilities
/p
Uses Symbol ACK/NAK protocol for the transfer.
/q
Runs the transfer Òquietly.Ó If you use this option, only the Þlename and a ÒTransmitting...Ó or ÒReceiving...Ó message is displayed. If you do not use this option, additional information will be displayed.
/r
Receives the speciÞed Þle.
/s
Performs an ASCII dump. This can be speciÞed in transmit mode (/t) only.
/t
Transmit the speciÞed Þle. This is the default and does not need to be speciÞed.
/x
Uses Xmodem protocol for the transfer.
2-13
Page 36
PDT 3200 Technical Reference Guide
VDISK.SYS
This driver conÞgures all of the unitÕs available extended memory as a read/write disk,
called a RAM disk. This driver is located on drive B of the PDT 3200 unit and is loaded by
the CONFIG.SYS Þle located on that drive. You cannot conÞgure the parameters for this
driver.
2-14
Page 37
Chapter 3 Resetting the PDT 3200
Chapter Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Warm Boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Cold Boot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Safe Boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Hardware Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Recommended Programming Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
3-1
Page 38
PDT 3200 Technical Reference Guide
3-2
Page 39
Chapter 3: Resetting the PDT 3200
Introduction
One of the critical features of any portable data collection device is its ability to protect
against accidental data loss. In the event a PDT 3200 unit becomes Òlocked upÓ or otherwise in a state in which data can no longer be processed, you can use any of four methods
to reset the unit. This chapter describes these methods, with a focus on the degree of data
recovery that is available.
3-3
Page 40
PDT 3200 Technical Reference Guide
Warm Boot
The warm boot is one of two software methods for resetting a PDT 3200 unit. It is analogous to the CTRL-ALT-DEL key sequence available with IBM-compatible PCs, and the
same key sequence is used to force a warm boot on a PDT 3200 unit. This method of resetting a unit should be used Þrst to attempt to bring it back to a usable state.
Since a warm boot can be attempted only from a unit that has been turned on, certain assumptions are made. For example, the rigorous hardware tests that are performed as part
of the cold-reset boot sequence are not all necessary; this means the unit restarts faster
with a warm boot than with a cold boot.
During a warm boot, data written to the RAM drive (drive D), the ßash drive (drive C), or
an ATA ßash PC card will remain intact. However, if an application is running on a unit
before a warm boot, its state cannot be restored.
The CTRL-ALT-DEL key sequence can be disabled, making it difÞcult for an end user to
reset the unit.
3-4
Page 41
Chapter 3: Resetting the PDT 3200
Cold Boot
The second software method for resetting a PDT 3200 unit is the cold boot. A cold boot
should be used only if a warm boot is unsuccessful. A cold boot is analogous to the results
of pressing the Reset button on the front of many desktop PCs or to turning the power off
and then on.
To perform a cold boot on a PDT 3200 unit, Þrst turn it off. Then press and hold the ALT
and FN 2 buttons while pressing the power button. Release all three buttons simultaneously, and the unit resets.
Simply removing and inserting the battery pack does not force a cold boot, because the
backup battery can provide minimal power to sustain the unitÕs operating state. The exception to this is when the backup battery is drained of all power, a condition that you
should not let happen.
When a cold boot is performed, all transient data is lost, along with the state of any application that was running on the unit. Data written to the RAM drive (drive D), the ßash
drive (drive C), or an ATA ßash PC card will remain intact. If a cold boot happens because
of a dead backup battery, data written to a RAM drive may not be maintained.
A cold boot begins with a retesting of the hardware and then follows with the DOS boot
sequence. The unit reboots DOS under the same conditions you would expect from a
desktop PC: Device drivers included in the CONFIG.SYS Þle and applications included in
the AUTOEXEC.BAT Þle are automatically loaded as part of the boot process. Any other
programs that were loaded before the cold boot will not be reloaded automatically.
3-5
Page 42
PDT 3200 Technical Reference Guide
Safe Boot
During the DOS boot sequence, control is passed sequentially to the CONFIG.SYS Þles on
drives A, B, and C. A similar process is followed for the AUTOEXEC.BAT Þles on each
drive. (See Chapter 1 for more information.) It is possible for a driver or application loading from the CONFIG.SYS or AUTOEXEC.BAT Þle on drive C to hang the system. A cold
or warm boot of the unit will not directly correct the problem, because the troublesome
program will be started again as part of the boot sequence.
A method is required by which the CONFIG.SYS or AUTOEXEC.BAT Þle on drive C and
the loading of the CFGDEV.SYS and DECODE.SYS drivers can be taken out of the normal
boot sequence. This can be accomplished with the DOS Ctrl-C, F5, and F8 escape
sequences.
The PDT 3200 provides an alternative method that is less accessible to the end user. To bypass the CONFIG.SYS and AUTOEXEC.BAT Þles on drive C, reboot the unit (with either a
cold or warm boot), and when the message ÒWaitÉÓ appears on the display, immediately
press the ESC and DEL keys at the same time. This causes alternative CONFIG.SYS and
AUTOEXEC.BAT processing to take place on drives A and B without chaining into the
Þles on drive C. The unit indicates safe-boot mode by emitting a low tone followed by a
higher-pitched tone. The ßash drive (drive C) and the RAM drive (drive D) will be preserved, and the boot sequence will place the unit at the C:\> prompt.
3-6
Note: If you do not hear the two tones indicating the safe-boot
sequence, you probably did not press the ESC and DEL
keys quickly enough. Reboot the PDT 3200 and press the
two keys simultaneously as soon as you see the ÒWait...Ó
message on the display.
Page 43
Chapter 3: Resetting the PDT 3200
Hardware Reset
In the extremely rare situation where none of the rebooting methods is successful, you can
use a reset mechanism that is located under the PC card slot cover (see Figure 3-1). Touch
a metal device (such as a paper clip) to the two contacts on the reset mechanism. This will
cause the PDT 3200 to begin a cold boot.
Figure 3-1. Location of the Hardware Reset Mechanism
Reset
Switch
3-7
Page 44
PDT 3200 Technical Reference Guide
Recommended Programming Practices
The programming methodologies used to develop DOS applications for a desktop PC also
apply to creating applications for the PDT 3200. Some of these are more critical to success
on a PDT 3200 than on a PC, because of the hardware environment of the PDT 3200. The
following are some important guidelines for programming PDT 3200 applications:
¥ Always check for reported error conditions. Many of the BIOS and DOS service
routines are useful only if the calling application checks for any ßagged error
conditions that signal a failure to comply with the original request. For example,
not enough available memory or lack of disk storage space must be dealt with
immediately; otherwise data may be lost.
¥ Carefully choose how data will be stored. A PDT 3200 unit has a number of data-
storage options: RAM drive, ßash drive, ATA ßash PC card, remote storage via
RF, and other PC card possibilities. You should be aware of the strengths and
limitations of each storage method and plan to store critical and temporary data
in appropriate locations so as to maximize both system performance and data
security.
¥ Disable the CTRL-ALT-DEL key combination. The PDT 3200 allows for easy
rebooting during the development process. To prevent the end user from
resetting the unit in the Þeld, disable the CTRL-ALT-DEL key combination. You
can accomplish this by using bar code programming (see the PDT 3200 Product
Reference Guide) or by calling an API function (see the DeveloperÕs Toolkit).
3-8
Page 45
Chapter 4 Using PC Cards
Chapter Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Configuring Your PC Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
PhoenixCARD Manager Plus (PCM+) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
ATA Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Fax/Modem Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
LAN Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
RF Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4-1
Page 46
PDT 3200 Technical Reference Guide
4-2
Page 47
Chapter 4: Using PC Cards
Introduction
PC card support expands the feature set of the PDT 3200 to include:
¥ Supplemental storage capacity through ATA ßash cards
¥ Modem support
¥ LAN connectivity
¥ Radio frequency (RF) communications
PDT 3200 supports Type 1 and Type 2 PC cards. Only one card of either type can be installed in the unit at any one time.
This chapter describes the use of PC cards with the unit. It does not provide details about
speciÞc cards, such as communications protocols for fax/modem cards. This type of information should be available from the PC card vendor.
For information about opening the PC card slot cover, inserting and removing PC cards,
and card recognition, see the PDT 3200 Product Reference Guide.
4-3
Page 48
PDT 3200 Technical Reference Guide
Overview
The primary intended uses for PC cards with the PDT 3200 are expanded storage space
and radio frequency (RF) communications. Using ATA ßash memory cards enables you to
conÞgure a PDT 3200 for a theoretical maximum of 64MB of memory. The card appears as
a hard drive to the user. RF communications cards allow you to connect the portable PDT
3200 unit to a traditional network and to access shared network resources in a transparent
fashion. The PDT 3200 can also use network and fax/modem cards.
Use the PDT 3200 ConÞguration Utility to download the appropriate drivers for ATA and
generic I/O cards.
4-4
Page 49
Chapter 4: Using PC Cards
Configuring Your PC Card
PhoenixCARD Manager Plus (PCM+)
To attain compatibility with as many PC cards as possible, the PDT 3200 utilizes card and
socket services supplied by Phoenix Technologies. These card and socket services are implemented as installable device drivers and are loaded using the DEVICE= command in
the CONFIG.SYS Þle.
Table 4-1 identiÞes the PhoenixCARD Manager Plus (PCM+) drivers needed for each type
of card. Information about these drivers follows the table. Additional drivers or application programs may be required for some cards, particularly RF, LAN, and fax/modem
cards.
Table 4-1. PCM+ Drivers Required for PC Cards
PCM+ Driver ATA Fax/
Modem
CNFIGNAM.EXE XX XX
PCM.INI XX XX
PCMATA.SYS X
PCMCS.EXE XX XX
PCMSCD.EXE X See Below
PCMSS.EXE XX XX
¥ CNFIGNAM.EXE identiÞes the section in the PCM+ conÞguration Þle
(PCM.INI) that should be loaded as the default.
¥ PCM.INI is the conÞguration Þle for the PC cards.
¥ PCMATA.SYS is an ATA-IDE device driver. It communicates with the
PCMCS.EXE driver to allow the system to access ATA-conÞgured PC cards.
¥ PCMCS.EXE is the card-services driver. Required for all PC cards, it provides an
interface between applications and the socket services. It also manages resource
allocations for the PC cards.
¥ PCMSCD.EXE is referred to as the super client driver. It uses the PCM.INI Þle to
conÞgure and request system resources for generic PC cards as well as speciÞc
cards that have been included in the PCM.INI Þle. Some PC cards will have
LAN RF
4-5
Page 50
PDT 3200 Technical Reference Guide
speciÞc client drivers to handle conÞguration; PCMSCD.EXE should not be used
with those cards.
¥ PCMSS.EXE is the socket-services driver. Required for all PC cards, it provides
an interface to the PC card hardware.
ATA Cards
ATA cards are ßash memory cards that utilize the IDE interface. This allows the ßash to
appear as a hard drive. Any ATA PC card should work on the PDT 3200 unit with the appropriate drivers installed. The following ATA cards are approved for use on the PDT
3200:
¥ 2.6MB SunDisk Seagate FlashCard, Model ST72P5
¥ 4MB SanDisk PCMCIA PC CARD ATA
¥ 8MB SanDisk PCMCIA PC CARD ATA
Additional cards may be approved. Contact your Symbol Technologies representative for
information.
Fax/Modem Cards
The PDT 3200 should recognize any generic fax/modem PC card. Fax/modem PC cards
are conÞgured to use COM2, I/O address 2F8h, and IRQ 3. The following fax/modem
cards are approved for use on the PDT 3200:
¥ US Robotics Sportster 28.8 Faxmodem PC card with DataView Connector
¥ Xircom CreditCard Modem 28.8
Note: The PDT 3200 does not support fax/modem cards with
XJack connectors.
LAN Cards
LAN cards require assignment of an I/O window, a memory window, and an IRQ. If the
LAN card will be conÞgured by the super client driver (PCMSCD.EXE), additional entries
to the PCM.INI Þle will be necessary. Many LAN cards come with their own resourcemanagement system and do not require the PCMSCD.EXE driver.
Note: Because of the PDT 3200Õs memory-handling properties,
some LAN cards may not work. Please contact Symbol
Technologies before purchasing a LAN card.
4-6
Page 51
Chapter 4: Using PC Cards
RF Cards
Because of the special requirements of RF environments, Symbol Technologies is distributing PDT 3200 RF units to qualiÞed customers only. Please contact your representative to
see if you are qualiÞed.
4-7
Page 52
PDT 3200 Technical Reference Guide
4-8
Page 53
Chapter 5 ROM-DOS Commands
Chapter Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Command Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
ROM-DOS vs. MS-DOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Command Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
@ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
; . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
ATTRIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
BREAK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
BUFFERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
CALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
CHDIR (CHange DIRectory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
CHKDSK (CHecK DiSK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
CLS (CLear Screen) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
COMMAND (Command Processor) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
COPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
COUNTRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
CTTY (Change TeleTYpe) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
DATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
DEL (DELete) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
DEVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
DEVICEHIGH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
DIR (DIRectory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
DOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
ECHO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45
ERASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-47
EXIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49
FCBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50
FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51
FIND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52
FOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
GOTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55
HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
IF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-57
INCLUDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59
INSTALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61
5-1
Page 54
PDT 3200 Technical Reference Guide
LASTDRIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-62
LOADHIGH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-63
MENUCOLOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-64
MENUDEFAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-65
MENUITEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-67
MKDIR (Make DIRectory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-69
NEWFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70
NUMLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-71
PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-72
PAUSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73
PRINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-74
PROMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-76
REM (REMark) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-78
REN (REName) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-79
RMDIR (ReMove DIRectory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-80
SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-81
SHARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-82
SHELL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-83
SHIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-84
SORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-85
STACKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-86
SUBMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-87
SWITCHES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-89
TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-90
TREE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-92
TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-93
VER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-94
VERIFY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-95
VOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-96
XCOPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-97
XDEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-99
5-2
Page 55
Chapter 5: ROM DOS Commands
Introduction
This chapter lists the Datalight ROM-DOS commands that are available in the PDT 3200.
ROM-DOS commands that differ from their MS-DOS equivalents are identiÞed and described.
The information in this chapter is taken from DatalightÕs ROM-DOS 6.22 UserÕs Guide and
is used by permission.
5-3
Page 56
PDT 3200 Technical Reference Guide
Command Overview
Table 5-1 lists the Datalight ROM-DOS commands that are provided with the PDT 3200
and gives a brief description of each command.
Table 5-1. DOS Commands Used with the PDT 3200
Command Description
? CONFIG.SYS command. Directs ROM-DOS to
pause for conÞrmation before processing a
command.
@ Suppresses the display of a single batch Þle
command line.
; Same as REM. IdentiÞes nonexecuting lines.
ATTRIB Displays or modiÞes the attributes associated with
a Þle.
BREAK CONFIG.SYS command. Enables or disables the
ability to stop program execution at a non-I/O
point.
5-4
BUFFERS CONFIG.SYS command. Sets the number of
internal data buffers.
CALL Batch subcommand. Invokes execution of a
secondary batch Þle.
CHDIR CHange DIRectory (also CD). Changes the default
directory.
CHKDSK CHecK DiSK. Checks integrity of data on a disk.
Displays information.
CLS CLear Screen. Clears all information from the
viewport.
COMMAND Spawns a second DOS command processor.
COPY Copies Þles from one storage location to another.
CTTY Change TeleTYpe. Changes the default terminal
interacting with ROM-DOS.
Page 57
Chapter 5: ROM DOS Commands
Table 5-1. DOS Commands Used with the PDT 3200 (Continued)
Command Description
DATE Displays the date from the system's internal
calendar and allows revision.
DEL DELete. Deletes speciÞed Þles.
DEVICE CONFIG.SYS command. Installs a device driver
into ROM-DOS.
DOS CONFIG.SYS command. Installs ROM-DOS into
high-memory area (HMA).
ECHO Batch subcommand. Turns on the display of batch
execution on the viewport.
ERASE Same as DEL. Erases speciÞed Þles.
EXIT Exits ÒnestedÓ running of ROM-DOS within
another program.
FCBS CONFIG.SYS command. SpeciÞes the number of
Þle control blocks (FCBS) open at one time.
FILES CONFIG.SYS command. Sets the maximum
number of Þles that can be open at one time on the
system.
FIND Works as a Þlter to display only lines that contain a
speciÞed string.
FOR Batch subcommand. Performs one DOS command
on a set of Þles.
GOTO Batch subcommand. Moves control to a speciÞed
line in the batch Þle.
HELP Lists all available ROM-DOS commands along
with brief descriptions.
IF Batch subcommand. Performs a command based
on a speciÞed condition.
5-5
Page 58
PDT 3200 Technical Reference Guide
Table 5-1. DOS Commands Used with the PDT 3200 (Continued)
Command Description
INCLUDE CONFIG.SYS command. Allows instructions in
one conÞguration block to be included with
instructions in another conÞguration block.
INSTALL Loads terminate-and-stay resident (TSR) programs
during CONFIG.SYS processing.
LASTDRIVE Sets the maximum number of drives.
MENUDEFAULT Sets the default menu item choice and time-out
value for making a selection.
MENUITEM SpeciÞes an item to be placed in the startup menu
displayed during system boot.
MKDIR MaKe DIRectory (also MD). Creates a new
subdirectory.
NEWFILE Allows continuation of CONFIG.SYS processing
from a new Þle.
PATH Displays current command search path(s). A new
path line can be speciÞed.
5-6
PAUSE Batch subcommand. Causes execution to halt until
a key is pressed.
PRINT Prints a list of Þles, up to ten Þles.
PROMPT Resets the appearance of the system prompt line.
REM REMark. A batch subcommand for identifying
nonexecuting lines.
REN REName. Renames Þles.
RMDIR ReMove DIRectory (also RM). Deletes a speciÞed
subdirectory.
SET Sets environment variables and command
processor strings.
SHARE Installs the capabilities for Þle sharing and Þle
locking on your hard disk.
Page 59
Chapter 5: ROM DOS Commands
Table 5-1. DOS Commands Used with the PDT 3200 (Continued)
Command Description
SHELL Allows selections of an alternate boot program
other than the default COMMAND.COM
command processor.
SHIFT Batch subcommand. Shifts replaceable parameters
one position Òto the left.Ó
SORT Sorts a text Þle and displays the output to the
standard device.
STACKS Allows for the use of dynamic data stacks to
handle interrupts. Note: ROM-DOS does not
utilize this command.
SUBMENU DeÞnes a menu item that represents a secondary
menu.
SWITCHES Allows special CONFIG.SYS Þle options.
TIME Displays the current time from the system's
internal clock. Allows revision.
TREE Displays the path of each directory on a speciÞed
drive.
TYPE Displays the contents of a text Þle on the viewport.
VER Displays current version of ROM-DOS on the
viewport.
VERIFY Displays the current VERIFY state or sets the
VERIFY state to on or off.
VOL Displays the volume label on a disk.
XCOPY Copies multiple Þles and, optionally,
subdirectories.
XDEL Deletes Þles and subdirectories including empty
subdirectories.
5-7
Page 60
PDT 3200 Technical Reference Guide
ROM-DOS vs. MS-DOS
Table 5-2 identiÞes differences between ROM-DOS commands and their MS-DOS
equivalents. For more information, see the individual command descriptions in the next
section.
Table 5-2. Difference Between ROM-DOS and MS-DOS Commands
Command Features Exclusive
to ROM-DOS
ATTRIB -C: Clears all Þle attributes /S: Processes Þles in all
BUFFERS Allows designation of secondary
CHKDSK /C: Corrects errors without
user conÞrmation
COMMAND
Internal command help only
DIR /A X: Shows attributes /O:C and /O:-C: Sorts by
FCBS , [minimum number]
FIND /I: Not case-sensitive
Features Exclusive
to MS-DOS
subdirectories
buffer cache
BUFFERS n,m where m is
secondary buffer cache
/Y: Steps through batch Þle
speciÞed by /C or /K switch
HELP.HLP in MS-DOS includes
all commands (external and
internal), installable drivers, etc.
compression ratio
/C[H]: Displays compression
ratio of Þles compressed using
Drivespace or Doublespace
5-8
HELP Requires COMMAND.HLP MS-DOS requires external Þle,
HELP.COM, but provides more
help text
NEWFILE ALL Not available with MS-DOS
Page 61
Chapter 5: ROM DOS Commands
Table 5-2. Difference Between ROM-DOS and MS-DOS Commands (Continued)
Command Features Exclusive
to ROM-DOS
PRINT /F: Sets maximum number
of Þles
SHARE /U: Unloads SHARE.EXE /F:space: Allocates space to
SWITCHES /W
TREE /A: Indicates no graphics
VER /R: Shows full version and
release number
Allows revision of the
version number
XCOPY /Y /-Y: Turns conÞrmation
XDEL All Not available with MS-DOS
Features Exclusive
to MS-DOS
/D:LPTx (PDT 3200 has no
parallel port.)
/U
/M
/S
/Q
record
characters for tree symbols
prompts on or off
Similar to DELTREE
5-9
Page 62
PDT 3200 Technical Reference Guide
Command Descriptions
This section provides descriptions of the ROM-DOS commands listed in Table 5-2. Each
entry includes an explanation of the command's purpose, the command entry syntax, remarks, and examples.
Each command also has a label to designate whether it is an internal or external command. Internal commands are part of the command processor program, COMMAND.COM. These functions are available only while COMMAND.COM is running.
External commands are actually stand-alone utility programs. They are independent from
COMMAND.COM. Internal commands that are unique to CONFIG.SYS processing are
also identiÞed. These commands can be used only in a CONFIG.SYS Þle.
5-10
Page 63
Chapter 5: ROM DOS Commands
Command ?
Type Internal
Purpose
The question mark (?) command is placed on a command line in the CONFIG.SYS
Þle following the actual command. It directs ROM-DOS to pause and ask for
conÞrmation before processing the command.
Syntax
[
command
]? =
command_arguments
Remarks
The command can be any of the following standard CONFIG.SYS commands:
BREAK=
DEVICE=
DOS=
FILES=
STACKS=
BUFFERS=
FCBS=
INSTALL=
LASTDRIVE=
SWITCHES=
The command_argument can be any of the available options deÞned for the
command. Please refer to the individual command description for complete
instructions.
The question mark (?) should be placed just before the equals sign (=) in the
command line.
Examples
DEVICE?=VDISK.SYS 64 /E
The above example causes ROM-DOS to pause and ask for conÞrmation before
installing the VDISK. If Yes (y) is answered, the installation will continue. If No
(n) is answered, the device will not be loaded and processing will move on to
the external CONFIG.SYS command line.
5-11
Page 64
PDT 3200 Technical Reference Guide
DEVICE?=VDISK.SYS 64 /E
The above example causes ROM-DOS to pause and ask for conÞrmation before
installing the VDISK. If Yes (y) is answered, the installation will continue. If No
(n) is answered, the device will not be loaded and processing will move on to
the External CONFIG.SYS command line.
5-12
Page 65
Chapter 5: ROM DOS Commands
Command @
Type Internal
Purpose
The AT sign (@) is used to prevent a single command in a batch Þle from being
echoed to the screen as the batch Þle is being run. The @ sign is placed in front of
the command whose display is to be suppressed.
Syntax
@[
batch file command
]
Remarks
The batch file command argument can be any executable line in your batch Þle.
Examples
In the following example, the COPY instruction will be executed but the
instructions will not be echoed to the screen as the batch Þle runs.
@COPY FILE1.BAT FILE1.SAV
The ECHO OFF command differs from the @ sign in that it cause all commands
following it to not be displayed on the screen. To prevent the ECHO OFF command
from displaying itself, place the @ sign in front of the command.
@ECHO OFF
5-13
Page 66
PDT 3200 Technical Reference Guide
Command ;
Type Internal
Purpose
The semicolon (;) command has two purposes: to allow comments in a batch or
CONFIG.SYS Þle, and to temporarily disable a command without physically
deleting the command from the Þle. See also the REM command.
Syntax
;
any text here
Remarks
The ; command is used to functionally remove a command from the CONFIG.SYS
Þle without actually deleting it from the CONFIG.SYS Þle.
Examples
;C:\BIN\VDISK.SYS 64 /E
The above example causes the VDISK command to not be executed until the ;
command is removed.
5-14
Page 67
Chapter 5: ROM DOS Commands
Command ATTRIB
Type External
Purpose
The ATTRIB command either displays or modiÞes the attribute of a Þle.
Syntax
ATTRIB [+ ≠ -][
option][filespec
]
Remarks
The Þle attributes deÞne the characteristics of a Þle. They determine if a Þle may
be deleted or modiÞed, or if it is archived. The ATTRIB command is used to
manage these Þle attributes.
Wildcard characters may be used in the ATTRIB filespec.
The ATTRIB command will modify Þle attributes if modify commands are given
to ATTRIB. The modify commands are:
Option Description
+/- Add (+) or remove (-) attribute
A Archive attribute
C Clear all attributes
H Hidden File attribute
R Read Only attribute
S System File attribute
If no modify commands are found by ATTRIB, then the Þles are displayed along
with the Þle names and their current attributes.
Examples
ATTRIB will add the Read Only attribute to the Þle myfile.dat.
5-15
Page 68
PDT 3200 Technical Reference Guide
ATTRIB +r myfile.dat
ATTRIB will remove the Read Only attribute and the Archive attribute of all Þles
with the DAT extension.
ATTRIB -a -r *.dat
ATTRIB will display the attributes of all Þles with the DAT extension.
ATTRIB *.dat
5-16
Page 69
Chapter 5: ROM DOS Commands
Command BREAK
Type Internal
Purpose
Expands the list of operations that can be stopped by pressing <Ctrl><C> or
<Ctrl><Break>. Alternatively, returns to the default setting of a limited number of
Òbreak-ableÓ operations.
Syntax
BREAK [ON≠OFF]
Remarks
In the normal default condition, the BREAK switch is off. In the off mode, the
ÒstopÓ commands, <Ctrl><C> and <Ctrl><Break>, will affect activities that read
from or write to the keypad, the screen, or the printer. ROM-DOS will not look for
these stop commands during any other activities.
With the BREAK switch set to ON, ROM-DOS looks for <Ctrl><C> and
<Ctrl><Break> during other activities such as disk reads and writes.
Examples
BREAK ON
Expands the BREAK list.
BREAK OFF
Returns to limited BREAK list.
BREAK
Displays the current BREAK setting.
5-17
Page 70
PDT 3200 Technical Reference Guide
Command BUFFERS
Type CONFIG.SYS
Purpose
ROM-DOS has internal buffers to temporarily hold data read from the disk.
Increasing the number of internal buffers will speed system performance.
Syntax
BUFFERS =
number
Remarks
Each buffer used by ROM-DOS requires 512 bytes of RAM. The BUFFERS
command will increase or decrease the amount of RAM used by the operating
system.
The minimum number of buffers is 2 and the maximum number is 40. If a number
less than 2 is given then the number of BUFFERS is set to 2. If a number larger than
40 is given then BUFFERS is set to 40.
Example
The following example causes ROM-DOS to have 10 buffers. These 10 buffers will
use 5120 bytes of RAM.
5-18
BUFFERS = 10
Page 71
Chapter 5: ROM DOS Commands
Command CALL
Type
Internal Batch Subcommand
Purpose
CALL invokes execution of a secondary batch Þle without exiting the primary
batch Þle. When the secondary batch Þle is done executing, control is returned to
the primary batch Þle.
Syntax
CALL
batchfile [batchfile arguments
]
Remarks
Parameters for the secondary batch Þle may also be included, if appropriate.
Examples
CALL BATCH2
This command executes the batch Þle BATCH2.BAT.
CALL MYBATCH FILEX FILEZ
This command executes the batch Þle MYBATCH.BAT. The arguments passed to
MYBATCH.BAT are:
%1 = FILEX
%2 = FILEZ
5-19
Page 72
PDT 3200 Technical Reference Guide
Command CHDIR
(CHange DIRectory)
Type Internal
Purpose
Changes the default directory.
Syntax
CHDIR [d:][
path]subdir
CD [d:][
path]subdir
Remarks
Subdir is the name of the new default subdirectory. Note that CD may be used
instead of CHDIR.
The new directory which is to become the default must already exist. See MKDIR
for creation of subdirectories.
A series of two periods (..) can be used to indicate a move back to the parent
directory.
Specifying only the backslash (\) for the subdir argument will move you to the root
directory of the current default drive.
Examples
CHDIR \TOOLS
Entering of this command will move you into the subdirectory called TOOLS,
whose parent directory is the root of the current default drive.
CD A:
Entering of this command will display the current directory on drive A:. Any valid
drive letter can be substituted to get the current directory on that drive.
The following examples will all use this directory tree structure:
5-20
Page 73
Chapter 5: ROM DOS Commands
CD D:\TEST\NEW
This command will move you into the subdirectory called NEW, located on the D:
drive, under the parent directory TEST.
CHDIR ..
This command will move you back to the parent directory of the current
subdirectory. If you were in the directory D:\TEST\NEW (from the previous
example), this CHDIR command would move you from NEW back into the TEST
directory.
CD ..\WORDPROC
This command will move you back to the parent directory and then into a
subdirectory called WORDPROC. If we started in the TEST directory, we would
move back to the ROOT directory and then into the WORDPROC subdirectory.
CD \
This command will move you back to the root directory, from any starting point in
the directory tree.
5-21
Page 74
PDT 3200 Technical Reference Guide
Command CHKDSK
(CHecK DiSK)
Type External
Purpose
The CHKDSK command checks the disk directories and File Allocation Table
(FAT) and displays a disk and memory report.
Syntax
CHKDSK [d:][
path][filespec
][/C] [/F] [/V]
Remarks
CHKDSK examines a disk and determines if the disk has any errors in the File
Allocation Table (FAT) and will optionally Þx errors.
Options
The /F option causes CHKDSK to Þx errors on the disk if any were found. The
errors that can be found are directory or FAT errors. If the /F is not speciÞed then
CHKDSK acts as if it will Þx the disk, but the corrections will not be written out to
the disk.
If errors are detected, you will be prompted with a message similar to the
following:
15 lost allocation units found in 5 chains.
Convert lost chains to Þles?
If you answer Y for Yes, each lost chain will be written to a Þle in the root directory
of the current default drive. Each Þle will have the name FILEnnnn.CHK. nnnn will
be a sequential number. The Þrst chain will be in FILE000.CHK. These Þles can be
veriÞed to see if they contain valuable information, and then deleted if desired.
5-22
Page 75
Chapter 5: ROM DOS Commands
Answering N for No to the above prompt, CHKDSK will still make the corrections
however the lost chains will not be saved to the disk.
The /C option allows CHKDSK to correct errors without user conÞrmation. This
option must be used along with the /F option for corrections to be made.
The /V option causes CHKDSK to display each path and Þle as it is processed.
If a Þle speciÞcation is speciÞed, then CHKDSK displays all Þles matching the
speciÞcation that have non-contiguous data areas on the disk. Files that are stored
in non-contiguous areas, especially .EXE Þles, have slower disk access times. If
CHKDSK reports a large number of Þles with this problem, a utility program that
optimizes the Þles and free space on your disk should be used.
After checking the disk, CHKDSK displays any error messages followed by a
report on the state of the disk that was checked. An example of the report is shown
below.
Volume ROM-DOS created June 1,1990 1:00a
Volume Serial Number is 190E-4AA2
362496 bytes total disk space
0 bytes in 1 hidden files
6144 bytes in 2 user files
356352 bytes available on disk
655360 bytes total memory
595360 bytes free
CHKDSK does not wait for a disk to be inserted before the checking is initiated nor
does it repair any errors.
Examples
CHKDSK will check the integrity of drive A. The report will be printed to the
console.
CHKDSK a:
CHKDSK will check the integrity of RAM disk D. The report will be saved in a Þle
called DRIVE_D.RPT.
CHKDSK d: >drive_d.rpt
5-23
Page 76
PDT 3200 Technical Reference Guide
Command CLS
(CLear Screen)
Type Internal
Purpose
Clears the viewport to display a blank screen.
Syntax
CLS
Remarks
CLS clears the screen except for the ROM-DOS prompt and the cursor in the upper
left-hand corner. There are no additional options for CLS.
5-24
Page 77
Chapter 5: ROM DOS Commands
Command COMMAND
(Command Processor)
Type External
Purpose
Start a new Command Processor.
Syntax
COMMAND[
device
][/E:
number
][/K:
filename
][/P][/C
string
][/
MSG
]
Remarks
This command starts a new copy of the ROM-DOS Command Processor. The
Command Processor is the program that has all the internal DOS commands in it.
Starting a new Command Processor will also produce a new environment. The size
of the environment is 128 bytes by default, but can be changed using the /E switch.
Command and its arguments can also be used in a SHELL= statement in your
CONFIG.SYS Þle. See the full description of SHELL for more details.
Options
The device option speciÞes that COMMAND.COM should use a different device,
such as AUX, for input and output.
The /E:number switch sets the environment size. Number represents the size of the
environment in bytes. Number must be in the range from 160 to 32768. All other
values will be ignored and the default value of 256 will be used. ROM-DOS will
round the value entered up to the nearest multiple of 16.
The /K:filename option tells the command processor to run the speciÞed Þlename
and then display the ROM-DOS command prompt. It is not recommended that this
option be used in a CONFIG.SYS SHELL= statement.
The /P switch causes COMMAND not to exit, in other words, remain permanent.
The /P switch should only be used when command is used in a CONFIG.SYS
SHELL statement.
The /c string switch causes COMMAND to execute the command in string and
then terminate. The string command can be any internal or external command.
The /MSG option indicates that all error messages should be stored in memory.
This option is recommended only for diskette based systems. ROM-DOS keeps
5-25
Page 78
PDT 3200 Technical Reference Guide
many of its error messages in the resident part of COMMAND.COM rather than
using valuable memory to store them. If an error message is needed and you have
loaded ROM-DOS from a diskette, the message will only be available if the boot
disk is still in the drive. By using the /MSG option, the messages will be available
in memory at all times. The /P option must be used along with the /MSG option.
Examples
The following command will cause a new copy of COMMAND to be executed. It
will perform a DIR command on the C drive and then exit back to the previous
Command Processor.
COMMAND /C DIR C:
The following example shows loading of a permanent copy of command with an
environment size of 256 bytes.
SHELL=C:\COMMAND.COM /P /E:256
5-26
Page 79
Chapter 5: ROM DOS Commands
Command COPY
Type Internal
Purpose
Copies a Þle or set of Þles to a speciÞed destination which could be on another disk,
or on another subdirectory on the current disk, or on a completely different drive.
COPY may also be used to alter the Þlename within the current directory. In
addition, this command can be used to direct communication between Þles and
devices (e.g., Þle contents to a printer, keypad input to a Þle).
Syntax
This command has several possible formats. The essential structure of each
command is:
COPY
source target option
The source is the Òcopy fromÓ Þlespec or device, and the target is the Òcopy toÓ
Þlespec or device. Following are various conÞgurations of the COPY command
format.
COPY [d:][
[/
option
path]filename[/option
]
] [d:][
path]filename
Where the Þrst Þlespec indicates the source Þle(s) to be copied and the second
Þlespec indicates the target area on which to copy.
COPY [d:][
[
/option
path]filename[/option
] + ... [d:][
path]filename[/option
] + [d:][
path]filename
]
As shown, several source Þlespecs may be listed to be copied into the target
Þlespec which is listed last. The source Þles will be concatenated one after the other
into the target Þle.
COPY [d:][
path]filename[/option] device
The target device is a console or printer (PRN).
COPY
device [d:][path]filename[/option
]
The device is the source such as a keyboard or console, the output of which will be
directed to the target Þlespec.
5-27
Page 80
PDT 3200 Technical Reference Guide
Options
The /A and /B options stand for ASCII and binary, respectively. They act as
switches that allow each of these Þle types to be copied. When one of them is used,
it applies the preceding Þlename, and remains in effect for any Þlenames following
in the command line until superseded by another /A or /B.
Most of the time the /A and /B options are not necessary. They are only needed
when you are combining ASCII and binary Þles.
/A
Indicates that the Þle is to be treated as an ASCII Þle (text Þle). When used with
the source Þle, everything will be copied up to, but not including, the Þrst
<CTRL><Z> end-of-Þle marker. When /A is used on the target Þle, a
<Ctrl><Z> will be added as the last character in the Þle.
/B
Indicates that the Þle is to be treated as a binary Þle. When /B is used with the
source Þle, the entire Þle is copied regardless of any <Ctrl><Z> characters.
When /B is used with the target Þlespec, no <Ctrl><Z> end-of-Þle mark is
added.
5-28
/V
This is the Verify option. It tells COPY to compare what is written to the target
Þle with the contents of the source Þle. If discrepancies are discovered, an error
message is displayed. This option slows the execution of the COPY command.
Since errors in copying are quite rare, this option is recommended as a
safeguard only when copying critical data.
/Y
This option indicates that you want to copy the current Þle(s) over the existing
Þle(s) of the same name(s) without conÞrmation. Using this option overrides
the setting made by the COPYCMD environment variable.
Page 81
Chapter 5: ROM DOS Commands
/-Y
This option indicates that you want to conÞrm the copy of one Þle over the
existing Þle of the same name. Using this option will override the setting made
by the COPYCMD environment variable.
The COPYCMD environment variable can be set using the SET command. This
allows you to set conÞrmation on or off for the COPY command. If you always
want to be prompted for conÞrmation when a Þle will copy over an existing Þle,
set COPYCMD= /-Y. To automatically overwrite without conÞrmation during a
copy instruction, set COPYCMD= /Y. Refer to the SET command for proper usage.
Remarks
When no Þlename is speciÞed for the target, the new copy will be given the same
name as the source Þle name.
When no drive or path is speciÞed for the source, the current drive and directory
is assumed. When no drive or path is speciÞed for the target, the current drive and
directory are assumed.
If a drivename only is speciÞed without a path, the default directory for that drive
is assumed.
Both source and target Þlespecs may include wildcard characters (* and ?) to
specify a set of several Þles.
Examples
COPY LETTER.TXT A:
This command will copy the Þle LETTER.TXT (in your current default drive and
path) to the default directory on the disk in drive A.
COPY *.DOC A:
Copies all Þles in the default directory with an extension of .DOC to the default
directory of drive A.
COPY DATAORIG.DOC DATABACK.DOC/V
This example creates a backup copy, DATABACK.DOC, from the Þle
DATAORIG.DOC, then veriÞes that the Þle was correctly copied. The new Þle will
be located in the current default directory.
5-29
Page 82
PDT 3200 Technical Reference Guide
COPY JAN.DAT + FEB.DAT + MAR.DAT QTR1.DAT
Copies the Þles JAN.DAT, FEB.DAT, and MAR.DAT in sequence into the single Þle,
QTR1.DAT.
COPY CON NEWFILE.TXT
Sets up your console (keypad) to input directly to NEWFILE.TXT. <Ctrl><Z>
followed by <Enter> closes the Þle and returns to normal command line operation.
5-30
Page 83
Chapter 5: ROM DOS Commands
Command COUNTRY
Type CONFIG.SYS
Purpose
ROM-DOS supports multiple country formats for time, date, and currency, as well
as other basic country-speciÞc information. A country is identiÞed by a three-digit
international telephone country code.
Syntax
COUNTRY =
countrynumber [codepage
]
Remarks
The Þle COUNTRY.SYS must be present in the same directory as your
CONFIG.SYS Þle.
If you do not specify a code page, ROM-DOS will use the default code page for the
chosen country. If a code page is speciÞed, it must be either the default or alternate
code page for the chosen country.
The ROM-DOS DATE and TIME commands are affected by this command.
Applications that use DOS functions to determine the date, time, or currency
format, or request that DOS provide character sort order, or uppercase
information, will be affected as well.
5-31
Page 84
PDT 3200 Technical Reference Guide
The following table shows the currently supported countries:
Country Code Code Page
Australia 061 437 850
Belgium 032 850 437
Brazil 055 850 437
Canadian-French 002 863 850
Czech Republic 042 852 850
Denmark 045 850 437
Finland 358 850 437
France 033 850 437
Germany 049 850 437
Hungary 036 852 850
Italy 039 850 437
Japan 081 932 --Latin America 003 850 437
Netherlands 031 850 437
Norway 047 850 865
Poland 048 852 850
Portugal 351 850 860
Spain 034 850 437
Sweden 046 437 850
Switzerland 041 850 437
United Kingdom 044 437 850
United States 001 437 850
Yugoslavia 038 852 850
Alternative
Code Page
For more information on COUNTRY, see the section on ConÞguring ROM-DOS for
International Use. The default country code is 001, for the U.S.A.
5-32
Page 85
Chapter 5: ROM DOS Commands
Examples
COUNTRY= 049
COUNTRY = 049, 437
The next time you start ROM-DOS with either of these COUNTRY commands, the
date and time will be displayed as follows:
DATE
Current date is Wed 20.06.1990
Enter new date (dd.mm.yy):
TIME
Current time is 16:39:54,45
Enter new time:
The Þrst COUNTRY command above would use code page 850, by default, for
sorting and case conversion. The second COUNTRY command example would
use the speciÞed code page 437 instead.
5-33
Page 86
PDT 3200 Technical Reference Guide
Command CTTY
(Change TeleTYpe)
T ype
Internal
Purpose
Allows you to direct input and output to a device other than your computer's
standard keypad and viewport.
Syntax
CTTY
device
Remarks
This command would be used in any situation requiring interaction with an
alternate console.
Caution
The CTTY command only affects communication with ROMDOS and with programs that work through ROM-DOS for input
and output. For example, if you go into BASIC it will use standard keypad input regardless of previous CTTY command usage.
Examples
CTTY COM2
Sets the device on COM2 as the input/output device.
CTTY CON
Returns control to the standard keypad.
5-34
Page 87
Chapter 5: ROM DOS Commands
Command DATE
Type Internal
Purpose
Displays the current date (month, day, year) as known to ROM-DOS and also
allows you opportunity to change it.
Syntax
DATE [
mm-dd-yy
]
Remarks
The date set by this command is used, among other things, for Òdate stampingÓ
your Þle-revision dates. This information is displayed when you execute a
directory listing of your Þles.
You may want to include the DATE command in your AUTOEXEC.BAT Þle, to set
the date at boot-up. If your computer has an internal battery-operated clock, you
won't need to do so.
The format of the date command is also dependent on the Country speciÞed in
CONFIG.SYS. The date is displayed according to local standards for the speciÞed
country.
Also see the TIME command.
Examples
If the command is entered without the speciÞcation of mm-dd-yy, the current date
as known to ROM-DOS will be displayed and you will be prompted to enter a new
date. Like this:
Current date is Sat 6-10-1989
Enter new date (mm-dd-yy):
If you do not want to change the date, just press enter. Otherwise, key in the
current date and press enter.
Alternatively, you may skip the display and prompting by simply entering the
current date on the command line. To enter June 10, 1997, type the DATE command
as follows (the century number 19 is assumed):
5-35
Page 88
PDT 3200 Technical Reference Guide
DATE 6-10-97
Valid entries for months, days, and years are:
mm
= 1-12 dd = 1-31 yy = 80-99
(for years with 19 as the century).
ROM-DOS will Þgure out the day of the week; do not include it in your entry.
The earliest year that ROM-DOS can accept is 1980. ROM-DOS assumes that the
century is 19 unless something different is entered, such as 20, next to the year. For
example, February 18, 2014 would be:
DATE 02-18-2014
ROM-DOS will adopt your entry as the current date.
5-36
Page 89
Chapter 5: ROM DOS Commands
Command DEL
(DELete)
Type Internal
Purpose
Deletes a speciÞed Þle or set of Þles.
Syntax
DEL [d:][
path]filename
[/P]
Remarks
The DEL command and the ERASE command are functionally identical.
When no drive is speciÞed, the default is assumed. When no path is speciÞed, the
default path is assumed.
Global Þlename characters ? and * (wildcards) can be used in the Þlespec. This
should be done with caution as it is possible to delete multiple Þles unintentionally.
When the Þlespec *.* is used to delete all Þles in the speciÞed subdirectory, a
veriÞcation message will be displayed:
Are you sure (Y/N) ?
Type Y only if you want all Þles in the speciÞed subdirectory to be deleted.
Caution
There is no ROM-DOS command to ÒundeleteÓ a Þle. Although
utilities exist which can attempt an undelete, certain factors can
cause the deleted Þle to be partially or totally lost. The DEL command should be treated as a permanent delete.
DEL deletes Þles within a subdirectory, not the subdirectory itself. For
subdirectory removal, see the RMDIR command.
5-37
Page 90
Options
/P
The /P option causes DEL to pause and prompt the user before each Þle is
deleted. This option is most useful when deleting Þles with wildcards. A
sample prompt is shown below:
PDT 3200 Technical Reference Guide
Filename
, Delete (Y/N) ?
Examples
This example deletes all Þles on the A: drive with a .DOC extension. Before each
Þle is deleted the user is prompted to determine if that Þle should be deleted.
DEL A:*.DOC /P
Deletes the Þle MYLETTER.DOC from the current default subdirectory.
DEL MYLETTER.DOC
Deletes all Þles in the current subdirectory with a .DOC Þle extension.
DEL *.DOC
5-38
Page 91
Chapter 5: ROM DOS Commands
Command DEVICE
Type CONFIG.SYS
Purpose
A device driver may be installed into ROM-DOS via the DEVICE command.
Syntax
DEVICE =
device_driver arguments
Remarks
A device driver is used to allow ROM-DOS to access hardware that is not common
in all PCs.
The full drive path and Þle name of the device must be speciÞed. The arguments
are different depending on the device driver.
Examples
DEVICE=C\BIN\VDISK.SYS 120 /e
This example installs the ROM-DOS RAM disk driver, VDISK.SYS, via the
DEVICE command. There will be 120K bytes of extended memory dedicated to the
RAM disk in this example.
5-39
Page 92
PDT 3200 Technical Reference Guide
Command DEVICEHIGH
Type
CONFIG.SYS
Purpose
Loads an installable device driver into the upper memory area if available.
Syntax
DEVICEHIGH =
device_driver arguments
Remarks
A device driver is used to allow ROM-DOS to access hardware that is not common
in all PCs. A device can be loaded into the upper memory areas if they are available
and there is enough free upper memory to accommodate the drivers needs. To
make high memory available, the EMM386.EXE and HIMEM.SYS utilities must be
loaded. If these utilities are not loaded or there is not enough upper memory
available, the device will load into conventional memory.
The full drive path and Þle name of the device must be speciÞed. The arguments
are different depending on the device driver.
Example
The following example installs a driver called MYDEVICE with its command line
arguments as speciÞed. The device will load into upper memory if available.
DEVICEHIGH=C:\BIN\MYDEVICE.SYS /20 /M
5-40
Page 93
Chapter 5: ROM DOS Commands
Command DIR
(DIRectory)
Type Internal
Purpose
Displays a list of the Þles that are in a directory.
Syntax
DIR [d:][
path][filename
][/
option
]
Remarks
The DIR command can be used to list all the Þles in a directory, or to show the
directory entries of speciÞc Þles. The standard directory display format includes
columns for Þlenames, Þlename extensions, Þle sizes, and the dates and times the
Þles were created.
Options
/A attributes
The /A option causes the DIR command to display only the Þles that match the
speciÞed Þlespec and have the given attribute. The table below shows the legal
attribute descriptions.
Letter Description
A Archive
D Directories
H Hidden Files
R Read Only Files
S System Files
X Show Attributes
-
The dash (-) symbol can be used to negate listed attributes. For example, to
select all Þles that do not have the archive bit set, use the /A -A option.
5-41
Page 94
PDT 3200 Technical Reference Guide
/B
The /B, or bare, option causes the display to be displayed without volume
label, date, time, or size information.
/L
The /L option causes the Þlenames to be displayed in lowercase.
/P
The /P option selects page mode, which makes ROM-DOS pause the display
each time the screen is full. Press any key to go on to the next page of entries.
/O
The /O option causes the Þlenames to be displayed in sorted order. The sort
order can contain one or more of the following letters:
Letter Description
D By date and time, newest Þrst
E Alphabetic order by extension
G Directories grouped before Þles
N Alphabetic order by name
S Size, smallest Þrst
-
The dash (-) symbol can precede the sort option to reverse the sort order. For
example, to sort all Þles in the directory in reverse alphabetic order, use the /
O-N option.
/S
The /S option causes the display to include Þles in subdirectories also.
/W
Displays list in a wide format without date, time, or size.
The DIRCMD environment variable can be used to set the default preferences for
the DIR command. The SET command will assign the values to an environment
5-42
Page 95
Chapter 5: ROM DOS Commands
variable. Refer to the SET command section for proper usage. For example, if you
wanted to always have the /P option set for DIR, the statement SET DIRCMD=/P
could be used. The default settings in DIRCMD can be overridden by using the
minus sign (-) preceding the option. If you wanted to cancel the paging for a single
use of the DIR command, you would enter DIR /-P.
Examples
To see the directory entries of all Þles in the current drive and directory, type:
DIR
To see all Þles in the subdirectory MEMOS on drive B, type:
DIR B:\MEMOS
Display all Þles sorted by Þle name order.
DIR /ON
Display all hidden Þles.
DIR /AH
Display all Þles with a .DOC extension without Þle sizes, or volume labels.
DIR *.DOC /B
5-43
Page 96
PDT 3200 Technical Reference Guide
Command DOS
Type CONFIG.SYS
Purpose
ROM-DOS can be loaded in special memory, called the high-memory area, or
HMA, freeing more of the conventional (lower 640K) DOS memory for use by
applications.
Syntax
DOS=HIGH
Remarks
The DOS=HIGH command frees up more of the standard DOS memory for use by
applications.
This command will only work on 286, 386, and 486 CPUs with extended memory
and Datalight's HIMEM.SYS high-memory manager, or equivalent, installed. It
will not work on standard XT-class PCs. Setting DOS=HIGH is ignored when
ROM-DOS is in ROM.
The DOS=HIGH command will also work on Chips and Technology's PC/Chip, if
it has extended memory and Chips and Technology's HIDOS.SYS device driver, or
another memory driver, is loaded.
See the HIMEM.SYS device driver description in this manual. See also 386MAX by
Qualitas for more information.
Example
The following example loads the high-memory-area device driver and then loads
ROM-DOS into the HMA for increased conventional memory. The high memory
area device driver must be loaded Þrst, before DOS=HIGH.
DEVICE=HIMEM.SYS
DOS=HIGH
5-44
Page 97
Chapter 5: ROM DOS Commands
Command ECHO
Type
Internal Batch Subcommand
Purpose
Controls whether ROM-DOS commands and other messages are displayed during
batch Þle execution.
ECHO also allows you to create your own messages for display.
Syntax
ECHO [ON≠OFF]
message
ECHO
Remarks
The ON option is the default ECHO setting. It causes commands in a batch Þle to
be displayed as they are executed by ROM-DOS. Typing ECHO OFF turns off such
display, after which the ON option will switch it back on again.
The ECHO command alone, typed without the ON or OFF option, displays the
current ECHO setting.
The message option is a string of characters, such as a warning or a reminder, that
you want ROM-DOS to display. Although your message will be displayed whether
ECHO is on or off, the message display is useful only when ECHO is off.
To create a message, type ECHO followed by your message. If your message is
more than one line long, the ECHO command begins each line of the message.
The @ symbol can be used to suppress the echoing of a single command when
ECHO is off. Place the @ symbol Þrst on the command line.
Examples
A batch Þle message of more than one line could be the following:
ECHO This batch file moves files
5-45
Page 98
PDT 3200 Technical Reference Guide
ECHO to another directory.
To set ECHO to off , enter the following command:
ECHO OFF
5-46
Page 99
Chapter 5: ROM DOS Commands
Command ERASE
Type Internal
Purpose
Deletes a speciÞed Þle or set of Þles.
Syntax
ERASE [d:][
path]filename
[/P]
Remarks
The DEL command and the ERASE command are functionally identical.
When no drive is speciÞed, the default drive is assumed. When no path is
speciÞed, the default path is assumed.
Global characters (? and *) can be used in the Þlespec. This should be done with
caution as it is possible to delete multiple Þles unintentionally.
When the Þlespec *.* is used to delete all Þles in the speciÞed subdirectory, a
veriÞcation message will be displayed:
Are you sure (Y/N) ?
Type Y only if you want all Þles in the speciÞed subdirectory to be erased (deleted).
Caution
There is not any ROM-DOS command to ÒundeleteÓ a Þle. Although utilities exist which can attempt an undelete, certain factors can cause the deleted Þle to be partially or totally lost. The
ERASE command should be treated as a permanent delete.
ERASE deletes Þles within a subdirectory, not the subdirectory itself. For
subdirectory removal, see the RMDIR command.
Options
/P
5-47
Page 100
PDT 3200 Technical Reference Guide
The /P option causes ERASE to pause and prompt the user before each Þle is
deleted. This option is most useful when deleting Þles with wildcards. A
sample prompt is shown below:
Filename
, Erase (Y/N) ?
Examples
Erases the Þle MYLETTER.DOC from the current default subdirectory.
ERASE MYLETTER.DOC
Erases all Þles in the current subdirectory with a .DOC Þle extension.
ERASE *.DOC
This example erases all Þles on the A: drive with a .DOC extension. Before each Þle
is erased the user is prompted to determine if that Þle should be erased.
ERASE A:*.DOC /P
5-48
Loading...