Symbol is a registered trademark of Symbol Technologies, In c.
Windows 95 and Microsoft are r egistered trademarks
of the Microsoft Corporation.
All other product or trade references appearing in this manual are registered
trademarks of their respective owners.
The information in this manual is subjectto change without notice.
Symbol Technologies shall not be liable for technical or editorial omissions or
mistakes in this manual. Nor shall it be liable for in cidental or consequential
damages resulting from the use of the information contained in this manual.
This manual is copyrighted. No part of this manual may be photocopied or
reproduced in any form without the prior written consent of Symbol.
This manual was written by the Symbol Technical
Publications Group. This group is tasked with
providing technical documentation for the Symbol
PTC-2134 product line that uses the Microsoft®
Windows CE® Operating System. Ev ery effort has
been made to provide accurate and concise information
to you, our customer.
The PTC-2134 DOS Software Guide provides
information that allows the use r to set up and use the
PTC-2134. This manual is meant to provide
information on the various components of this
product, including
•General regulations,
•Overview of the PTC-2134,
•Maintenance and trouble shooting,
•Available accessories.
This manual, h owever, does not provide instructions
on how to perform t he tasks specific to your job within
your organization. For job-specific information, refer to
the instructions provided b y your organization.
PTC-2134 DOS Software Guidei
Chapter 3 Configuring TN-3270/5250
Contacting Symbol’s Support Center
Symbol’s Support Center may be contacted to obtain
help in resolving any PTC-21 34 system problem that
you may experience.
If you have a problem running your unit or using your
equipment, contact your facility’s technical or system
support. If there is a problem with the equipment, the
system support will contact the Symbol Support
Center at 1-800-653-5350.
For additional information on Symbol’s products and
services, please visit our website at
The PTC-2134 is a rugged AMD™SC400
processor-powered, pen-based Portable
Tele-transaction Computer (PTC). It couples standard
PC technology with Symbol’s expertise in data
collection and radio technology to provide a f lexible,
high-performance portable system.
This section of the manual provides a basic overview
of the PTC-2134’s software environment, including
brief discussions of
•thesystemBIOS,
•the operating system and applications,
•thesoftwarekernel,
•the PenRight! operating environment,
•power management, and
•software development kits (SDKs).
PTC-2134 DOS Software Guide1
Chapter 3 Configuring TN-3270/5250
Functional Overview
The PTC-2134 uses a PC-type software architecture
consisting of three major software layers:
•BIOS(Basic Input/Output System)
•OperatingSystem
•Application
BIOS
Application
Operating S ystem
BIOS
Hardware
The BIOS is the lowest software layer and typically
exists i n ROM memory.It pr ovides basic input/output
services for the system and an insulating interface
between the upper software layers and the hardware
layer.
The PTC-2134 uses a customized version of the
Phoenix™ BIOS to support PTC-2134 hardware
features. To achieve this level of supp ort while
maintaining PC compatibility, a system extension
called the Symbol BIOS, or TBIOS, is used.
TBIOS is a method for expanding the BIOS functions
without reserving a function number thatcould be
used by another application. This is accomplished by
forcing the TBIOS code to r eside with standard BIOS
code, but providing a different entry point to the
TBIOS. The entrypoint is defined by the contents of a
static lo cation in the BIOS Compatibility Area
(COMPAS).
2PTC-2134 DOS Software Guide
Other Software Components
Operating System
The operating system provides additional higher-level
services to the Application Layer and uses the BIOS
interface for performing hardware functions. By using
standardized BIOS interfaces, the PC architecture
supports standard operating syste ms. The PTC-2134
supports the MS-DOS 6.22 operating system.
Application
The application is the highest software layer and
provides c ontrolling software programs for the unit.
Other Software Components
Software Kernel
The softwarekernel is a simple program loader that is
used to reprogram the PTC-2134 Flash PROM
memory areas.
PenRight! Operating Environment
PenRight! is a graphical application development tool
used to create forms containing objects such as
buttons, l ist boxes, and writing fields for pen-based
computers. These objects are activated with a stylus
pen, which can be used to select options, highlight
items, enter strings of characters, or enter a signature
on a digitized screen.
PenRight! applications are DOS progra ms that are
driven by events. Each depression or release of the
stylus on the digitized screen triggers a particular
type of programmed action.
PTC-2134 DOS Software Guide3
Chapter 3 Configuring TN-3270/5250
Power Management
Power management is a necessityfor battery-operated
devices such as the PTC-2134. The unit is designed to
incorporate battery-saving p ower management
functionsdirectlyintothe unit hardwareand s oftware
architecture. The platform hardware incorporates
features t hat allow most internal elements to be
slowed down or deactivated. Together, the hardware
and software constantly monitor system activity and
implementpower management activity states that are
used for power management functions.
Software Development Kits
Symbol provides application development tools in the
form of Software Development Kits (SDKs) to help
developers design application programs for the SC400
product family. The SDK is a collection of run-time
libraries and TSRs that assist in the development of C
application programs on PC-compatible computers.
Once an application program is developed, it can be
copied to a PCMCIA card and in serted into th e
PTC-2134 to load or run the app lication.
Note:If converting applicationsfrom a PTC-1134, any
portion of the applicationsoftware that directly
manipulates the SLC (P TC-1134) hardware will
have to be re-written before it will work on the
PTC-2134. The internal architecture of the
PTC-2134 is not compatible with SLC. Any
software (BIOS, drivers, or applications) that
manipulates hardware must be written
specifically for the PTC-2134.
4PTC-2134 DOS Software Guide
PTC-2134 Unit Configurations
The PTC-2134 DOS unit is available in a wide variety
of configurations.
This section will cover the configuration options for
the following devices:
•Radio
•RAM
•ROM
•Storage
•PCMCIA Slots
•Displays
•IrDA
•Ethernet
•DCDDevices
PTC-2134 DOS Software Guide5
Chapter 3 Configuring TN-3270/5250
Radio Options
Batch
A batch unit does not have an antenna c able
integrated in the unit. It is still possible to install a
radio in the unit by way of the user accessible
PCMCIA slots. However, an antenna must be
installed on the radio. Either of the PCMCIA slots
may be used for a radio c ard.
LAN Radio Ready
The radio ready unit has an RSMA antenna cable
integratedintotheunit.Theendofthecableroutes
through the unit to the externally accessible PCMCIA
slot door. A radio can be installed into PCMCIA slot 0
(slot farthest from the unit’sdisplay).
LAN Radio Factory Installed
The radio factory installed unit utilizes the internally
installed PCM CIA slot (slot 2). An RSM antenna cable
integratedintotheunitroutestotheradiointhis
internalslot.Thisprovidestheunitwiththree
PCMCIA card slots and frees up both external
PCMCIA SLOTS for other uses . The radio is installed
in the internal slot (slot 2).
WAN Radio Factory Installed
When ordered with a WAN radio such as a DataTac or
Mobitex network radio, the radio mo dule is installed
internally in the unit. Because these radio types are
not PCMCIA form factor, they require additional
space in the unit. The unit therefore has a deeper
backshell than non W AN radio equipped units.
6PTC-2134 DOS Software Guide
Memory
Memory
RAM
The PTC-2134 has RAM configurations of 4, 20, 36, or
64 MB on the CPU board. When the 16- and 32-MB
memory modules are added, the 4 MB is included. The
64-MBconfigurationactually contains68 MB of RAM,
but the SC400 is able to address only 64 MB and the
4 MB on the CPU board is disabled.
ROM
The PTC-2134 comes with 512 KB of ROM, w hic h
contains the BIOS for DOS.
Storage Options
ATA
The PTC -2134 supports ATA drives, both solid state
and rotating. ATA Type II cards can be applied to
either of the user accessible PCMCIA slots. Symbol
offers factory installed c ard s in a variety of sizes.
The 520-MB rotating ATA disks (any Type III) are
installed in PCMCIA slot 0.
SRAM
The PTC-2134 also supports SRAM (static RAM)
cards. Generally, these cards are used for special
purposes like reloadin g the ROM images (Genesis
procedure) or booting the unit, r ather than data
storage because the capacities are rather low (e.g.,
4 MB). However, these cards may also be used by the
application for data storage.
PTC-2134 DOS Software Guide7
Chapter 3 Configuring TN-3270/5250
Compact Flash
The PTC-2134 has an internal Compact Flash ad ap ter
which is a standard 50 pin port that supports a
variety of Compact Flash module sizes.
PCMCIA Slots
The PTC-2134 has three PCMCIA slots, two that are
user-accessible and onethatis internal(whentheunit
is ordered with a factory installe d radio). T he two
external slotsare controlled by an Intel PCMCIA
controller. The internal slot is controlled by a Vadem
PCMCIA controller and is register-compatible with
the Intel 82365SL.
External Slots
Slot 0
This is the card slot farthest away from th e display.
Slot 1
This is the card slot closest to the display.
Internal Slot
Slot 2
This slot is located inside the unit and is only usab le
when the unit is ordered with a factory installed LAN
radio. O ther unit configurations will n ot be e quipped
with the PCMCIA card slot case to use this slot.
8PTC-2134 DOS Software Guide
Display Types
Display Types
The PTC-2134 has a 640 x 480 VGA monochrome
liquid crystal display (LCD) screen, w hich can show
up to 64 shades of gray. The display also has a
resistive touch panel digitizer. The digitizer enables
the unit to recognize data entered w ith a passive
stylus. It also has a palm reject feature, which
prevents accidental activation of the unit by casual
hand or finger contact.
The display can be of either Transmissive or
Transflective type.
Transmissive Displays
Transmissive displays generally produce brighter
images than transflective displays but consume more
battery power.A transmissive display does not reflect
ambient light and is intended for indoor use on ly. It
requires the backlight to be on at all times.
Transflective Displays
Transflective displays use reflected ambient light to
produce viewable display images. It is ide al for use in
outdoor applications. For indoor use, the unit’s
backlight must be used to optimize the display
visibility. The backlight is defaulted to the ON setting
and can be turned off to conserve power.
IrDA
The PTC-2134 supports infrared communications via
anIrDAcompliantportatthebaseendoftheunit.
Refer to the section titled “
guide f or more details.
PTC-2134 DOS Software Guide9
IrDA” on page 55 of this
Chapter 3 Configuring TN-3270/5250
Ethernet
The PTC-2134 has an internal Ethernet interface and
is implemented by a CS8920 Crystal ISA Ethernet
controller. When the unit is docked into a cradle,
Ethernet signals pass through the contacts on the
cradle and unit, and then pass through the cra dl e’s
RJ-45 jack.
Refer to the section titled “
Management” on page 52 of this Guide for more
details.
Ethernet Power
DCD Devices
The PTC-2124 supports Symbol’s Data Collection
Device (DCD) architecture. This architecture allows
applications to obtain data from a variety of data
input devices without requiring that device-specific
code be written. Devices with DCD-compliant drivers
are sometimes referred to as DCD Devices.
Scanners
The PTC-2134 supports contact and non-contact
barcode sc anners. The appropriate module attaches to
the front underside of the unit. For non-contact
scanners, there are four activation buttons; two on the
top along the sides of the display, and two in the
scanning module itse lf, und erneath the unit. The
buttons o n the scan module are more access ible than
the buttons on the top of the unit and may be the
preferred activation buttons.
10PTC-2134 DOS Software Guide
PTC-2134 Assignments
This section provides information on the following
PTC-2134 com p o ne nts:
•Resource Map,
•Hardware Interrupts,
•COM Port Assignments.
PTC-2134 DOS Software Guide11
Chapter 3 Configuring TN-3270/5250
Resource Map
PTC-2134 c omponents are assignedvarious address
ranges within system memory.
Memory Allocation Table
PTC-2134 m emory is allocated as follows:
AddressSizeResourceComments
000000-09FFFFh640KBBaseBase Memory
0A0000-0BFFFFh128KBVideoVideo Display Frame Buffer
0C0000-0C7FFFh32KBVideoVGA BIOS ROM
0C8000-0C9FFFh8KBASICSharedRAM area for ASIC
0CA000-0CBFFF8KB--Unused
0CC000-0CCFFFh8KBPCMCIA/UMBPCMCIAWindoworUpperMemory
Knowledge of hardware interrupt assignments will be
useful for making system configuration decisions.
Interrupt Table
PTC-2134 hardware is assigned to the following
interrupts (IRQs):
H/W InterruptPC/AT UsagePTC-2134 UsageNotes
IRQ0Timer0Timer0
IRQ 1KeyboardKeyboard
IRQ 2IRQ(15:9) CascadeIRQ(15:9) Cascade
IRQ 3COM 2COM 2/4COM 2 = User Port
COM4=WANRadioSerial
Port
IRQ 4COM 1COM 1IrDA Port I/F
IRQ 5LPT 2
IRQ 6Floppy Disk
IRQ 7LPT 1LPT 1
IRQ 8RTCRTC Alarm
IRQ 9PCMCIAOpen for PCMCIA devices
IRQ 10Ethernet
IRQ 11PCMCIAOpen for PCMCIA devices
IRQ 12MouseDigitizer
IRQ 13MathExceptionASIC
IRQ14HardDiskIDEATASSHardDisk
IRQ 15PCMCIAOpen for PCMCIA devices
PTC-2134 DOS Software Guide13
Chapter 3 Configuring TN-3270/5250
COM Port Assignments
ThefollowingarethedefaultCOMPortsettingsfor
the PTC-2134:
•COM 1: Ir DA,
•COM 2: 15 pin serial or cr adle serial ports,
•COM 3: S canner,
•COM 4: WAN radio.
14PTC-2134 DOS Software Guide
Boot Options
The PTC-2134 uses a customized version of the
Phoenix BIO S (Basic Input/OutputSystem) that
supports PTC-2134 features. Because the BIOS
interfaces with the hardware, it must be aware of the
physical devices present in the system. This section
provides information on the following:
•The behavior of the BIOSat boot-up,
•Changing BIOS settings,
•Changing the boot source,
•Drive letter mapping,
•Reflashing the BIOS,
•Resetting/Re booting the PTC-2134.
PTC-2134 DOS Software Guide15
Chapter 3 Configuring TN-3270/5250
POST
In PC-base d systems, afte r a boot, the BIOS is
responsible for testing and initializing all hardware
components and boot-loading the operating system
into memory. This process is known as the Power-On
Self Test, or POST.
What Happens During POST
During the POST process, messages must be
generated for the system. The POST, initializations,
and messages are customized for the PTC-2134.
Once the POST operations are complete, the BIOS
loads the operating system. Once a bootable disk is
found, the boot loader is loaded into memory and
executed. If no bootable disk i s found, the system
displays a message: “No Boot Device Available.”
16PTC-2134 DOS Software Guide
Changing BIOS Settings
Changing BIOS Settings
There are many settings in the BIOS of the PTC-2134,
settings that you would expect to see in a desktop
computer system. Once set, the BIOS settings
generallydo not have to be returned.However, access
will need to be gained to the BIOS configuration.
To access the BIOS settings, attach a physical
keyboard to the PTC-2134. During the memory test
portion of the POST process,press F2. Upon
completion of t he memory test, access w ill be granted
to the BIOS setup menu.
Power ManagementThere are several time out settings for high-speed
time out, Standby, Suspend, etc.
Boot Location and SequenceThis determines which drive is booted.
CPU SpeedThere are three possible settings: 33, 66, and 100
MHz. The default is 100MHz.
Note:The system’s contrast and brightness
controls become disabled while in the
BIOS setup mode.
PTC-2134 DOS Software Guide17
Chapter 3 Configuring TN-3270/5250
Boot Sources and Drive Letter Mapping
Normal Boot
Under normal conditions, t he u nit boots from the
internal Compact Flash card and loads Card and
Socket Services to support SRAM and ATA cards.
Drive Letter Assignments When Booting from Compact Flash
Installation SlotDrive Letter
Compact FlashC
0D
1E
Note:If Card and Socket Services are not
loaded, the unit will not have access
to SRAM or ATA card types.
18PTC-2134 DOS Software Guide
Boot Sources and Drive Letter Mapping
Booting From an ATA Card
To prepare an ATA Card for booting purposes,
perform the following steps:
1. TheATACardmustfirstbeformatted.The
HDFMT utility located in the /DOS directory on
the unit can be used for this. This command is
identical to the MS-DOS FORMAT.COM utility.
For more information, refer to the "Formatting an
ATA Card" section later in this guide.
2. Copy the MS-DOS operatingsystem files onto the
unit. This can be done by run ning the MS-DOS
SYS.COM utility.
To boot from an ATA Card, perform the following
steps:
1. Removethe CompactFlash card from the CF slot
inside the unit.
2. Install the ATA card into PCMCIA slot 0 (farthest
from display).
3. Restart the unit.
4. Press F2 during POST to enter CMOS Setup.
5. Access the EmbeddedFeaturesscreen.
6. Ensure that the PCMCIA ATA option is enabled.
7. Reboot th e system.
Note:Do not attempt to load Card and
Socket Services when booting from
ATA.
PTC-2134 DOS Software Guide19
Chapter 3 Configuring TN-3270/5250
Drive Letter Assignments When Booting From ATA
Installation SlotDrive Letter
Compact Flash
Not Installed
1
0C
1
1
CF Car d must be removed.
2
Card and Socket Services cannot be loaded.
Doing so will cause the unit to lock up
Not supported
2
.
Booting From An SRAM Card
The PTC-2134 can be co nfigu red to boot from an
SRAM card instead of it’s internal C ompact Flash
Card. This is similar to booting a PC from a floppy
disk.
Note:When an SRAM Card is used as the
boot source, it must remain in the
PCMCIA slot. Do not attempt to
remove it.
In order for an SRAM Card to be recognized properly
by the unit, it should hav e No-Attribute Memory.
SRAM Cards with Attribute Memory may not be
properly recognized by the unit at boot up.
Note:Do not attempt to load Card and
Socket Services when booting from
SRAM.
20PTC-2134 DOS Software Guide
Boot Sources and Drive Letter Mapping
To prepare an SRAM Card for booting purposes,
perform the following steps:
1. The SRAM Card must first be properly formatted.
To do this, the PCFORMAT utility in the PCM
directory can be used. Referto the "Formatting an
SRAM Card" section later in this guide for h elp on
using PCFORMAT.
2. Copy the MS-DOS operatingsystem files onto the
unit. This can be done by running the MS-DOSSYS.COM utility.
To boot from an SRAM Card, perform the following
steps:
1. Insert the SRAM Card into Sl ot 0 (farthest from
the display).
2. Press F2 during POST to enter CMOS Setup.
3. Ensure that the boot Sequence is A: then C:.
4. Access the EmbeddedFeaturesscreen.
5. Ensure that [ROM/RAM Disk 0] op tio n is set to
[PCMCIA].
6. Reboot th e system.
PTC-2134 DOS Software Guide21
Chapter 3 Configuring TN-3270/5250
Drive Letter Assignments When Booting From SRAM
Installation SlotDrive Letter
Compact FlashC
0AorB
1
1
Card and Socket Services cannot be loaded.
Doing so will cause the unit to lock up
Not Supported
1
.
Note: There is a possibility of a boot error if all video
modes are not calibrated. As the PTC-2134 bo ots up,
tapping on the screen as the config.sys,
autoexec.bat, user_boot.bat, or application is
loading may produce one of the following errors:
•Run-time error R6002 — integer divide by 0
•Divide overflow — memory allocation error
•Divide overflow
Should one of these errors occur, it can be corrected by
applying the following steps:
1. Delete tmouse.ini in themouse directory
2. Reboot unit and allow it to go into calibration
mode
3. Calibrate all video modes
4. Save and Exit
5. Reboot the unit
22PTC-2134 DOS Software Guide
Reflashing the BIOS
Reflashing the BIOS
TFLASH Utility
The TFlash utility is a DOS command line program
that will reflash a system BIOS image into the unit.
To use this program:
StepAction
Copy the binary ROM image of the BIOS to
1
be flashed to the directory w here the
TFlash.exe resides.
Boot the unit into D OS protected mode
(perform a “clean” boot w ith NO MEMORYMANAGERLOADED).Thiscanbedoneby
2
using a keyboard and pressing F5 or by
renaming the config.sys and autoexec.bat
files (i.e., config.old, autoexec.old,etc.).
Type TFlash < name>
3
(<name>=new BIOS ROM Image name).
4Press ENTER.
No “crisis mode” is associated with
this utility. If a failure occurs during
the flash process, the process must
be repeated in its entirety.
PTC-2134 DOS Software Guide23
When the flash process is complete, restart the unit. If
the unit displays a blank screen without restarting, or
if the user does not receive the restart message, the
unit should be reset by pressing the reset button and
then the Resume button. The unit is now operable
with the new BI OS image.
The TFLASH utility can also read the BIOS image
from ROM and write it to disk. The command line
option for this is:
Tflash romimage.bin –r8000
-r8000 is the memory location for the bios. The resulting file size
should be 256KB.
-r Reads <length> bytes, default=512k,fromROM into a file.
-e Erases <length> bytes, default=512k, ROM area to all FFs.
Automatic Genesis Flash
When the need arises to re-flash the BIOS of the
PTC-2134, th e following proced ure can be used. N o te
thatthis procedurecan also be usedto force the
PTC-2134 to boot from a system bootable SRAM card
on slot 0 of the user accessible PCMCIA slots.
To perform an Automatic Genesis Flash, follow these
steps:
StepAction
1Insert the Genesis formatted SRAM card
into Slot 0.
2Turn on the PTC - 2134.
3Press and hold the Backlight button.
4Press and hold the Resume button.
5Release the Backlight button.
6Press and release the Backlight button.
7Release the Resume button.
8The Status light should start t o flash and
the backlight should turn on. The unit will
then beep about 15–20 times to indicate that
the BIOS is being r eloaded.
9After the unit stops beeping, remove the
SRAM card from Slot 0.
10Perform a Warm Boot on the unit.
24PTC-2134 DOS Software Guide
Resetting/Rebooting the PTC-2134
Resetting/Rebooting the PTC-2134
There are several ways to reset the PTC-2134. The
following section describes the suggested procedures.
Note:Always suspend the unit before
removingthe batterypack. The bridge
battery may not be capable of
supporting some features by itself.
Cold Reboot
The blue push button switch located inside the
PCMCIA door performs a cold reboot. It powers off
and puts the PTC-2134 in ship mode. Turning on the
unit at this point (pressing the "Resume" button) will
reinitialize the PTC-2134.
Console Reboot
The following Console Reboot procedure stops the
PTC, resets it, then restarts (boots) it. This procedure
erases all programs and data stored in RAM. When
the PTC starts ag ain, it returns to the operating
system.
StepAction
1Turn on the PTC-2134.
2Press and hold the "Contrast" button.
3Press and hold the "Resume"button.
4Release the "Contrast" button.
5Press and release the "Contrast" button.
6Release the "Resume" button.
PTC-2134 DOS Software Guide25
Chapter 3 Configuring TN-3270/5250
APM
As b attery conservation measures are dependent upon
user operations and preferences, the PTC-2134 al lows
the user application program to direct and control
Power Management operations via the industry
standard Advanced Power Management (APM)
software interface. This interface is defined by the
APM Interface Specification which is currently at
revision level 1.2. The platform software uses the
APM functions and states to p lace the PTC-2134 into
the appropriate platform Power Management Activity
State.
To support the APM interface in the PTC-2134,
Symbol enhanced the APM BIOS functions supported
in the Phoenix BIOS from APM revision 1.0 to 1.2.
The APM BIOS functions manage power in the
background, based on d ev ice activity, and are specific
for the PTC-2134 hardware platform. The APM BIOS
is the software interface to the P TC-2134 platfo rm
and its power manage d devices and components. This
interface allows software applications to take an
active part in managing the power consumed by the
PTC-2134 unit .
Power Management
26PTC-2134 DOS Software Guide
Monitoring
Monitoring
When full power management is enabled, system
activity is monitored at two different levels. The APM
Driver software monitors the frequency of certain
interrupts, and the APM BIOS monitors the hardware
activity directly. Both w ork together to inform
APM-aware applications, Device Drivers, and TSRs
about power management events and conditions. The
PTC-2134 a llows all elements to work together to
conserve power.
APM Driver
POWER.EXE
For MS-DOS environments, Symbol provides a n APM
Driver module, power.exe, whic h connects to the
APM BIOS and controls power management policy via
function calls to the APM software interface. This
DOS drive r was modified by Symb ol to provide a
specific inte rface to the PTC-2134 Pen Based
computer. power.exe is a terminate and stay
resident (TSR) driver that must be loaded into
config.sys.
Command Line Parameters
The following is a description of the power.exe
command line parameters. The curren t settings are
always displayed when invok ing power.exe from the
command line.
Command Line:power [/option]
Options:
PTC-2134 DOS Software Guide27
/SUSPEND XXXX
This parameter sets the amount of time that the unit
will be in Standby state before entering Suspe nd .
There are only 8 valid settings for this parameter.
They are 0 (disable), 64, 128, 256, 512, 1024, 2048,
and 4096 seconds. Any value of 1– 4096 entered will
be rounded off to the nearest valid value. A parameter
value of 4097 or higher will cause an “Invalid
Parameter” error. The default s etting for this
parameter i s 16 minut es.
Chapter 3 Configuring TN-3270/5250
/STANDBY XXXX
This parameter sets the amount of time that the unit
will be in High Speed state before entering Standby.
There are only 8 valid settings for this parameter.
They are 0 (disable), 8, 16, 32, 64, 256, 512, and 1024.
Any value of 1–1024 will be rounded off to the nearest
valid value. A parameter value of 1025 or higher will
cause an “Invalid Parameter” error. When Standby is
disabled, the Suspend timer never starts. Therefore,
disabling Standby effectively disable s Suspend. The
default setting for this parameter is 32 seconds.
/ADV:[MIN:MAX:REG]
This parameter means that power.exe has enabled
and connected to the APM BIO S. It monitors
hardware and applications, then reduces power
consumption where possible. The MIN, MAX, and
REG parameters are optional. MIN conserves the
least power, MAX conserves the most power, and REG
gives average power conservation. The default setting
for this parameter is REG.
/STD
This parameter means that power.exe will enab le
the APM BIOS but it will disconnect. Therefore,
power.exe will not poll for APM ev ents.
/OFF
This parameter means that power.exe disables the
APM power managem ent.
Note:Ahelpmessagecanbecalledby
entering “POWER /?”
28PTC-2134 DOS Software Guide
Power Management States
Power Management States
There are four operational states for the PTC-2134:
Ship, Full Run, Standby, and Suspend.
StateDescription
ShipThe u nit is completely powered off. The resume
key must be pressed to power-up the unit.
PressingtheBlueButtoninsidethePCMCIA
door puts the unit into this mode.
Full RunThe system C PU and devices are fully awake
and functional — also referred to as fully operational.
StandbyA state generated by software-controlled timers
and lack of activity on monitored buses. While
in the Standby state, the unit’s power usage is
reduced by up to 50%, and the unit is able to
process many functions at a reduced rate
(8 MHz).
SuspendAstatewherethesystemfurtherreducesthe
power consumption fr om Standby mode. There
are several suspend options that are controlled
by the BIOS or device drivers. Most of the state
changes that occur to get into Suspendare due
to lack of activity of devices. While in the
Suspend state, the unit’spowerusageis
reducedbyupto90%;however,theunitis
functionally deactivated until it is reawakened.
The PTC -2134 allows the user to directly help
conserve power via the Suspend/Resume feature. This
feature allows the user to place the unit into Suspend
state by depressing the Resume switch o n the unit's
top cabinet. This deactivates the unit and most
internal hardware elements. The user can reactivate
the unit by pressing the Re sume switch again.
PTC-2134 DOS Software Guide29
Chapter 3 Configuring TN-3270/5250
Additionally, the PTC-2134 p rovides a Standby T imer,
which specifies the inactive time before automatically
entering the Standby state and deactivating most
internal elements. T he s ystem default setting for this
timer is approximately 32 s econds. During this period,
the unit can be reactivated via the Digitizer or the
RESUME switch.Once the unit enters Suspend state,
the Digitizer will no longer wake the unit.
Magic Packet Mode
Another feature of the PT C-2134’s power
management is the ability to enable the Magic Packet
Wake-Upmode(MagicPacketisanE-Wakeutility
developed by AMD) when the unit is docked in a
cradle and in the Suspend state. Magic Packet mod e
provides the ability to remotely wake up t he u nit by
using the Ethernet connection established through
thecradle.Thisallowstheunittobeaccessed
remotely and managed even if the Suspend state has
been entered. The Magic Packet feature does not
require that a software network driver be loaded in
the unit.
When the unit is manually put into the Suspend state
(while docked in a cradle), the Ethernet controller will
automatically enable Magic Packet mode. While in
Magic Packet mode, the unit will monitor all incoming
frames to determine if any of them is a Magic Packet
frame. A Magic Packet frame is a unit of data that is
sent by a network manager, via Ethernet connection,
from a remote site with the intent to wake up the
unit. When a Magic Packet frame is received and
detected,the Ethernet controller will wake up the
unit and disable Magic Packet mode. The unit then
returns to Full R un state, regaining full functionality,
including network accessibility.
30PTC-2134 DOS Software Guide
Power Management States
Features of Power Management in the Standby State
While in Standby, the PTC-2134 has the following
features:
•Reduced p ower usage (up to 50% savings).
•Processor speed drops to 8 M Hz.
•Display is turned off, all other devicesare stillon.
The following conditions will prevent the unit from
entering St andby mode:
•IrDA drivers loaded.
•Cradle Ethernet link with CradTSR loaded
For more information, see the section titled
CradTSR” on page 44.
“
•Scrnblnk utility loa ded
For more information, see the section titled
SCRNBLNK” on page 48.
“
The follo wing table illustrates wake sources used to
bring the PTC-2134 out of Standby mode:
Wake SourceComment
Touch/Digitizer Unit wakes when the digitizer registers a
touch.
RTC AlarmUnit wakes when a Real Time Comparator
Alarm is initiated.
Dock/UndockUnit wakes when it is connectedto or
disconnected from a cradle.
KeyboardUnit wakes with inp ut from a keyboard that
is attached to a cradle.
Resume button Unit wakes when the Res ume button is
pressed.
PTC-2134 DOS Software Guide31
Chapter 3 Configuring TN-3270/5250
Features of Power Management in the Suspend State
While in Suspend, the PTC-2134 has the following
features:
•Reduced p ower usage (up to 90% savings).
•Processor speed drops to 32 KH z.
•All devices are turned off, except for non-PCMCIA
•Ethernet is in Low Power.
The following conditions will prevent the unit from
entering Suspend mode:
•IrDA drivers loaded.
•LAN radio and drivers loaded.
•Cradle Ethernet link with CradTSR loaded.
•Scrnblnk utility loa ded.
The follo wing table illustrates wake sources used to
bring the PTC-2134 out of Suspend mode:
based WAN radios.
For more information, see the section titled
“
CradTSR” on page 44.
For more information, see the section titled
SCRNBLNK” on page 48.
“
Wake S ou rc eComment
User
Serial Port
Cradle
Serial Port
WANUnit wakes in response to a Ring In dicator.
EthernetUnitwakes in response to E-Wake.
Dock/
Undock
Resume
Button
32PTC-2134 DOS Software Guide
Unit wakes in response to a Ring Indicator.
Unit wakes in response to a Ring Indicator.
Unit wakes when it is connected to or
disconnected from a cradle.
Unit wakes when the Resume Button is
pressed.
SC 400 Power Control
Unit Is Running
SC 400 Power Control
Yes
Yes
No
Any Activity Within
StandbyTime-out
Parameter?
No
Is
CradTSR Loaded and
Unit Docked/On An
Ethernet Link?
No
System Standby
Request Is
Processed
Does Unit Go Into
Standby Mode?
Suspend Button Is
Suspend Request
No
Pressed
System/User
Is Processed
UnitGoes Into
Suspend Mode
No
Is Wake
Source
Initiated?
Yes
Yes
PTC-2134 DOS Software Guide33
WakeUpWithin
Suspend Time-out
Parameter?
Yes
Unit Resumes
Running
Chapter 3 Configuring TN-3270/5250
The PTC-2134 provides support for Symbol d rivers.
Common Symbol drivers are described in the
following sections.
Driver Support
34PTC-2134 DOS Software Guide
Cradle Overview
Cradle Information
Cradle Overview
The Symbol PTC- 2 134 Desktop/Vehicle Cradle is a
specialized docking station designed for the PTC. The
cradle provides the following services:
•Battery recharging connection,
•External keyboard connection,
•Three external serial port connection(s),
•2DB-9ports
•1DB-15port
•External Ethernet connection.
The Desktop and Vehicle cradles are identical units.
The PTC identifies the type of cradle type in which it
is installed based on the cradle’s power source. The
cradle has two power jacks: a connector identical to the
one on the bottom of t he PTC and a second DIN type
connector. W hen powe r is applied to the cradle’s PTCtype power connector, the cradle is identified as a
desktop cradle. When power is applied to the cradle’s
DIN connector, the cradle is identified as a Vehicle
cradle.
Symbol’s cradle driver allows users to take advantage
of cradle services in two ways: (1) it detects cradle
docking and undocking and automatically enables
interfaces to the cradle connectors. (2) it allows
application developers to write cradle-aware
applications which canmake more sophisticated use of
cradle services.
PTC-2134 DOS Software Guide35
Chapter 3 Configuring TN-3270/5250
PTC-2134 Cradle Interaction
The PTC-2134 only has one COM port available f or
use by peripherals. The PTC-2134 use s an electrically
controlled serial switch-box with a 9-wire interfa ce to
provide additional s erial ports for this single CO M
port.
The PTC-2134 provides IrDA on COM1 and wired
serial on COM2. An infrared sensor on the PTC-2134
provides the IrDA outlet. A DB-15 connector on the
PTC-2134 pr ovides the serialoutlet.
The following table summarizes the po ssibilities for a
PTC-2134. Whe n out of the cradle, COM1 is available
as IrDA and COM2 is availableat the DB-15. When
docked, COM1 is available as IrDA and COM2 is
re-routed to one of the DB-9 serial connectors or the
DB-25 serial connector on the c radle.
CradleCOM1 OutletCOM2 Outlet
Undocked
Docked
IrDA on
PTC-2134
IrDA on
PTC-2134
DB-15on
PTC-2134
DB-9or DB-25
on cradle
PTC-2134 Plugged Into A Cradle
Power
IrDA
2134 Crad le
Transceivers
20-Pin
Connector
Transceivers
RS232DB-9
RS232
RS232
Transceivers
(Port 1)
DB-25
(Port 2)
DB-9
(Port 3)
PTC-2134
DB-15
(COM 2)
(COM 1)
36PTC-2134 DOS Software Guide
PTC-2134 Cradle Interaction
Cradle Serial Interface
Thecradleserialinterfaceisimplementedusinga
communication chip and cradle electronics to create
four multiplexed RS232 serial ports, one internal port
and three external ports. Since the serial ports are
multiplexed , only one port can be active at a time.
Serial Port 1DB9 Connector (Male P ins)
Serial Port 2DB25 Connector (Male Pins)
Serial Port 3DB9 Connector (Male P ins)
Control PortNo Connector, Internal to unit
The Vehicle/Desktop-2134 Cradle supports the
communication chip interface to the PTC-2134 unit via
the Cradle Contacts. The Communica tion Interface
uses COM 2 (2F8 Hex) on the PTC-2134 unit. This
interface is specifically designed f or use with th e
Symbol cradles and is provided by the communication
chip. The Vehicle/Desktop-2134 Cradle uses a wired
implementation of the interface.
ThesameCOM2Portisusedforboththe
Vehicle/Desktop-2134 Cradle’s Serial Connectors and
the serial port in the PTC-2134unit’sDB-15connector.
Hence, only one COM interface can be used. When the
PTC-2134 is placed in a cradle, the cradle’s serial ports
can be used if the unit’s application program uses t he
cradle serial routines from the PTC -2134 SDK. (Refer
to the PTC-2134 SDK for software de tails.)
PTC-2134 DOS Software Guide37
Chapter 3 Configuring TN-3270/5250
The Optical Serial Signals use the cradle contacts on
the PTC-2134 unit as shown below:
In the Optical Serial Interface, two lines are used for
Receive and Transmit data and two lines are used for
status lines. The two status lines (OTXS#, ORXS#)
provide communication status information via
Time-Divis ion-Multiplexing. In this technique, the
status information is embedded in the status dat a of
each line.
The Status Word, like a normal Data Word, begins
with a Start Bit and ends with a Stop bit. However, the
StatusWorduses three Stop bits to provide an easy
identification of the en d of the word.
PinSignalsDescription
1OTXDOptical Transmit Data
2ORXDOptical Receive Data
3OTXS#Optical Transmit Status
4ORXS#Optical Receive S tatus
The Status Lines operate at a 38.4 KBP S data rate,
where as the Data Lines operate at the rate
programmed for the internal communication chip
UART controlling the Ser ial Port. The Serial
communication chip UART can be programmed to
support the following standard communications
functions:
•Data Rate 75 to
115.2 Kbps.
•Parity Even, Odd,
None.
38PTC-2134 DOS Software Guide
•DataWidth5,6,7,or8
bits.
•Stop Bits 1 o r 2.
PTC-2134 Cradle Interaction
Internal Control Port
The internal Control Port is used to interface with
application software within the PTC-2134 unit. Using
the Control Port signals, the application program can
determine the cradle configuration being used.
The external pow er s ource is used by the cradle
electronicsto determine the c radle environment as
described b elow:
•Desktop Cradle - external power is connected to
the Power Jack Connector
•Vehicle Cradle - external power is connected to the
3-Pin Power Connector
Thecradleloopsbackthefollowingsignals:
Pin #FromPin #To
7RTS8 CTS
7RTS1 CD
3TX2 RX
4DTR6 DSR
4DTR9 RI
See the next page for an ex planation of the loopback
signals.
PTC-2134 DOS Software Guide39
Chapter 3 Configuring TN-3270/5250
Explanation of Loopback Signals :
SignalExplanation
RTSReady To Send
CTSClear To Send
CDClear Detect
TXTransmit
RXReceived
DTRData Terminal Ready
DSRData Se t Ready
RIRing Indicate
Note:User-In and User-Out signals are not
connected and are reserved for possible
future implementation.
DTR and RTS Latching
The Vehicle/Desktop-2134 Cradle provides DTR and
RTS latching on inactive Serial Port 3 to prevent the
connected device from dropping the communication
link with the PTC-2134. Prior to switching to another
Serial Port, the cradle will latch the DTR and RTS
lines at their current levels. For example, if the sig nal
iscurrentlyhigh,thelinewillbelatchedhigh,orifthe
signal is currently low, the line will be latched low.
This feature is particularly us eful when connecting to
devicessuchasWANradios.
Ring Indicator
In order to allow the Ring Indicator (RI) signal to
reach the PTC-2134 unit from any serial port (active
or not),the RI signalsfrom all SerialPorts are
logically Ored together. The RI signal can b e used to
wake the PTC-2134 unit from Standby or Susp end
Modes.
40PTC-2134 DOS Software Guide
PTC-2134 Cradle Interaction
DB-9 Serial Connector Pinout
Thepin-outoftheRS232portDB-9(malepins)
connectors are as shown in the tables below:
Pin SignalPin Signal
1CD6DSR
2RXD7RTS
3TXD8CTS
4DTR9RI
5GND
DB-25 Serial Connector Pinout
Thepin-outoftheRS232portDB-25(malepins)
connector is shown in the tables below:
The 10 Mbps Ethernet Port is available via an RJ-45
connector. The Ethernet Port is located on the right
side of the cradle and interfaces to the Cradle
Contacts. The cradle RJ-45 port will be wired as DCE
accepting a standard male LAN cable. The Ethernet
RJ-45 connector pin-out is as follows:
PIN SIGNALPIN SIGNAL
1TXD+5 NC
2TXD-6 RXD3RXD+7 NC
4NC8 NC
Note:The Ethernet Port is locatedon both the
Desktop and Vehicle configurations;
however, the port will typically be used
only in a Desktop configuration.
42PTC-2134 DOS Software Guide
PTC-2134 Cradle Interaction
Keyboard Port
The Vehicle/Desktop-2134 Cradle supports an external
PS/2 Keyboard Port which is located on the right side
of the unit. The PS/2 K eyboard Port supports the
following connector pinout:
PinSIGNALDESCRIPTION
1KB_DATAKeyboard Data
2N/CNot Connected
3GNDGround
45VSWKeyboar d Power (+ 5 VDC)
5KB_CLOCKKeyboard Clock
6N/CNot Connected
Note:Permanent Keyboard damage may
occuriftheuserconnectsordisconnects
the keyboardfrom the cradle's keyboard
connector while the unit is docked,
unless the unit is suspended first.
PTC-2134 DOS Software Guide43
Chapter 3 Configuring TN-3270/5250
Crad TSR Overview
CradTSR is a Terminate and Stay Resident (TSR)
program which controls how the PTC-2134 operates
while in a cradle.
Specifically, CradTSR does th e following:
•Interacts with the unit’s on-board Ethernet
•Rejects APM system Standby and Suspend
•Re-routes COM2 from the DB-15 on the bottom of
CradTSR
controller to enable the controller when the unit is
in the cradle and disables the controller when the
unit is out of the cradle.
requests if Ethernet link activity is detected.
the unit to one of the three serialports on the
cradle.
•Configures the bau d rate, parity, and stop bits on
the three serial ports on the cradle.
•Provides cradle status information to user
applications via API calls.
This section discusses in general what happens when
CradTSR is invoked, both for the first time and at
subsequent times.
For more information on Ethernet functions within
CradTSR, refer to the chapter on Ethernet.
44PTC-2134 DOS Software Guide
Invoking CradTSR
Invoking CradTSR
When CradTSR is invoked for the first ti me after a
reboot, it queries the Symbol BIOS extensions to
determinethe modelof PTC on which it is running. If
it finds any model other than the one it is des i gned for,
it exits.
Specifying Interrupt Vector
There is no need to specify the software interrupt
vector used for communicating with the TSR.
CradTSR h as been assigned vector 0 x 63 and by
default uses that. Optionally, one can override this
value using the /V option. Additionally, one can specify
the /S option, which will cause CradTSR to
automatically locate a free vector by scanning the IDT
between 0 x 060 and 0 x 06F.
Binary Interface of CradTSR
When Crad TSR has already been lo aded and is
resident and CradTSR is invoked again, the command
line options ma y be used as a binary interface to the
TSR. Many of the CradTSR SDK functions are exposed
via the binary interface, including options for changing
COM2 configuration options, querying current status,
etc.
When CradTSR is invoked for the N
N ≠ 1, it searches the software interr upt vector range
looking for a pre-loaded version of CradTSR. When it
findsone, it uses the CradTSRSDK interface to query
its major and minor version numbers and reports
them to the user.
The arguments, /C2P, /C2C1, etc., may be used to alter
the cu rrent settings of COM1 or COM2. If specified
when the PTC-2134 is outside of the cradle, the change
takes place immediately. If the PTC-2134 is in the
cradle, the COM1 parameters are not immediate ly
altered.
PTC-2134 DOS Software Guide45
th
time where
Chapter 3 Configuring TN-3270/5250
Besides the Device parameters, the /M argument may
be used to monitor the in-cradle state, and the /Q
argument will dump all of the Device settings and
other state variables.
Command Line Arguments
This section describes specific command-line
arguments available when invoking CradTSR.
When the CradTSR is invoked, the syntax is:
Cradtsr [ options ]
There are more options available for the N
invocation (N ≠ 1 ) than for the 1st. In the table on the
next page, options available only for later invocations
are marked with the phrase “if pre-loaded” (meaning
valid only if CradTSR is already loaded).
In this table, BR stands for a decimal baud rate
between 300 and 115200. D stands for the number of
data bits (5-8), and S s tands for the number of s top
bits (1 or 2). P stands for a parity c ode: E (even),
O (odd), and N (none) are supported.
The ‘-u’ option for /C2P, /C2C1, etc., tells CradTSR to
stop altering the syste m state to support the given
configuration.
th
46PTC-2134 DOS Software Guide
Command Line Arguments
The table below provides a description of each option
and specifies when each option is available.
OptionAvailable:Description
/V:hexVecIf not l oadedLoad the TSR at hex vector hexVec if
available.
/?AlwaysPrint summary of command-line options.
/C2C1:BR,D-P-SAlwaysSetup of COM2 on Cradle DB1
(whenincradle).
/C2C2:BR,D-P-SAlwaysSetup of COM2 on Cradle DB2
(whenincradle).
/C2C3:BR,D-P-SAlwaysSetup of COM2 on Cradle DB3
/QIf pre-loadedQuery current configuration.
/UIf pr e-loadedUnload the TSR (if possible).
/C2C1: -uIf pre-loadedDisable COM2 on Cradle DB1.
/C2C2: -uIf pre-loadedDisable COM2 on Cradle DB2.
/C2C3: -uIf pre-loadedDisable COM2 on Cradle DB3.
/C2C1: +uIf pre-loadedEnable CO M2 on Cradle DB1.
/C2C2: +uIf pre-loadedEnable CO M2 on Cradle DB2.
/C2C3: +uIf pre-loadedEnable CO M2 on Cradle DB3.
1
Cradle port must first be enabled with one of the
[/C2Cx: + u] enable options.
PTC-2134 DOS Software Guide47
Chapter 3 Configuring TN-3270/5250
Purpose
ThepurposeoftheTSRistopromotelongerdevicelife
by turning off the video driver and backlight after a
determined period ofidle time has elapsed. Idle time is
based on monitored events.
SCRNBLNK is useful in situations where the unit is
notallowedtogointosystemStandby/Requeststates
(such as when there is an active Ethernet link on the
cradle, or when a radio is installed in the unit).
The goals of the TSR are as follows:
•Prolong the useful battery time.
SCRNBLNK
•Automatically resume processing upon events.
•Allow the user to easily select the time-out period.
User Interface Functions
The user interface is a standard DOS command line
with options to reject S TANDBY messages, specify the
time-out period in seconds, unload the TSR, and use a
selected vector:
scrnblnk /r /t[seconds] /u /v[vector]
Reject STANDBY (/r option)
The user may choose to reject STANDBY messages.
This will prevent the unit from moving to SUSPEND
from a power t imer.
5PTC-2134 DOS Software Guide
TSR Internal Functions
Time-out (/t option)
The user may change the time-out period by
reentering the command line with a different time.
The time-out period may be s et to a value within the
range of 1– 3600 (seconds).
The use r may effectively disable the TSR by entering
"/t0" seconds for a time-out period.
Unload (/u option)
The user may unload the TSR and recover the memory
if no vectors have been changed since the TSR was
installed.
Vector (/v option)
The user may choose a vector in the range 60 through
6f for the TSR to use; if the vector is already in u se, an
error message will be displayed.
The use r may access a usage screen by entering the
argument “/?”.
TSR Internal Functions
The TSR has the form of a Finite State Machine
(FSM). The events and states relationships are
described b elow.
Events
The events that the TSR sensesare
•Keypad— through INT 75h chain.
•Mouse — throughINT74hchain.
•Timer — throughINT1chchain.
PTC-2134 DOS Software Guide6
Chapter 3 Configuring TN-3270/5250
INIT State
When the user presses Enter to conclude the command
entry, the TSR enters the INIT state. If the TSR is not
in memory, it is loaded and the state is changed to
SBL_ON; if it is already in memory, a new time-out
value may be entered, and the resident sta te remains
SBL_ON.
SBL_ON State
The TSR monitors the 55 msec clock to calculate its
elapsed t ime; when the t ime-out period has elapsed
and no event has occurred, the current state of the
backlight is saved; the backlight and video are turned
off; and the state is changed to SBL_OFF.Ifanevent
occurs, th e timer is reset to its initial value and the
time-out countdown is restarted.
SBL_OFF State
The backlight cannot be turned on w hen the TSR is in
the SBL_OFF state; the state must be changed to
SBL_ON to turn on the backlight.
When either a mouse or keypad event occurs, the
backlight is restored to its saved state; the video is
turned on; the timer is set to its initial value and the
time-out countdown is restarted; and the state is
changed to SBL_ON.
INACTIVE State
When a delay of 0 seconds is entered, the TSR is
effectively disabled but remains in memory, and the
state is changed to INACTIVE.When a non-0delay is
entered, the timer is set to the new delay value and
the state is changed to SBL_ON.
7PTC-2134 DOS Software Guide
Standby/Suspend/Resume
The Standby/Suspend/Resume messages are a special
set of circumstances. Their activity is sensed from a
broadcast message through INT 2fh.
Standby messages may be rejected when the TSR
state is either SBL_OFF or SBL_ON.
Resume messages are always recognized. The timer is
set to its initial value; if a scrnblnk time-outhas
occurred, the backlight is restored to its saved state,
the video is turned on, and the TSR state is changed to
SBL_ON.
If the cradle driver (CRADTSR) is loaded, the
Ethernet driver (TEP) can optimize its power
management significantly.
It does this in two ways:
1. When the u nit is undocked, the Ethernet interface
2. When the unit is docked in a cradle with an
Ethernet Power Management
is put into a low-power mo de called “hardware
suspend mode.” This mode extends the battery
lifetime by reducing power consumption.
attached Ethernet, it will not automatically go into
standby mode or suspend mode. This keeps the
unit from turning itself off while the u ser is
downloading large files.
If CRADTSR is not l oaded, TEP will continue to
function as a normal packet driver. However, this
mode of operation is not recommended.
9PTC-2134 DOS Software Guide
Ethernet Drivers/Utilities
Ethernet Drivers/Utilities
Installing Ethernet Drivers
To install Ethernet drivers, perform t he following
steps:
1. Edit the autoexec.bat file and uncommentthe
lines which call ethernet.bat and cradle.bat.
2. If the FTP TCP/IP stack is to be loaded, copy the
necessary files to Ethernet/Pkt (these are not
included on the unit). E dit ethernet.bat and
uncomment the two FTP linesat the b ottom.
3. Uncomment the SCRNBLNK line if screen
blanking is needed to conserve power.
ETHERCTL.EXE
etherctl.exe is a power control utility that turns the
power to the ethernet chip on and off. This utility is
part of the eth ernet.bat file.
Command Line:etherctl.exe [-f] { suspend | wake }
Option:-f = ignore packet driver link status
TEP.COM
tep.com is the ether net packet driver and is loaded
when ethernet.bat is run.
Options:-i = Force drive r to report itself as IEEE 802.3
instead of Ethernet.
-d = Delayed initialization. Used for d iskless booting.
-n = NetWare c onversion. Converts 802.3 packets
into 8137 packet.
PTC-2134 DOS Software Guide10
Chapter 3 Configuring TN-3270/5250
ETHERNET.BAT
Ethernet.bat is a batch file that turns on the power
to the ethernet chip, loads the ethernet driver, and
then loads the TCP stack.
-w = Windows hack, obsoleted by winpkt.
-p = Promiscuous mode disable.
-u =Uninstall.
-s = Scan I/O space even if a plug and play card
found.
-f = Fake hardware. U se d for debugging.
Note:The TCP/IP stack drivers are not included
on the base image and must be installedby
the user. Once installed, ethernet.bat must
be edited to load the stack.
11PTC-2134 DOS Software Guide
IrDA Power Management
IrDA Power Management
IrDA power is controlled by two simple utilities.
Neither of these utilities requires parameters.
JIRDAON.EXE
Jirdaon.exe is the IR power on utility for the
PTC-2134.
JIRDAOFF.EXE
Jirdaoff.exe is the IR power off utility for the
PTC- 2134.
IrDA
LP20.EXE
LP20.exe is the executable file that loads the
LitePlus drivers.
LitePlus 2.0 IrDA Print Driver
Even though the LitePlus 1.10 D OS driver provides
the ability to print to IrDA compliant printers with
APM support, it can only send data in one d irection
(to printers). I t is also not strictly IrDA-compliant in
that it lacks the ability to act as a secondary station.
The LitePlus 2.0 DOS driver is designed to provide
bidirectional d ata transfer capability along with many
other enhancements. These new features include a
user-configurable buf fer size and the ability to
enable/disable IrDA stack, change IrDA COM ports
on-the-fly, supportthe application callback function,
and provide a high-efficiency data exchange between
the driver and the application.
PTC-2134 DOS Software Guide12
Chapter 3 Configuring TN-3270/5250
LitePlus 2.0 IrDA DOS Driver Architecture
The LitePlus 2.0 IrDA DOS driver is based on a
completely different architecture than that of LitePlus
1.10, even though its functions are natural extensions
of that program.
LitePlus 2.0 still uses the format of DOS TSR
program and supports only single point-to-point data
exchange. However, the IrDA state m achine will be
driven by the timer interrupt rather than BIOS
interrupts. The whole implementation will be purely
interrupt-driven. T his will ensure that there is no
waiting under most circumstances inside the IrDA
driver, therefore providing maximum efficiency and
consuming minimum system resources.
LitePlus 2.0 still controls INT 17H to support
traditional DOS printing functions such as Ctrl-P,
Print-Screen, and re-direction t o an LPT driver.
LitePlus 2.0 also controls INT 14H, adding new
extension APIs to support two-way data transfer
effectively. Direct re-direction to COMx por ts is no
longer supported. The new APIs provide applications
with direct access to IrDA stack information an d allow
high efficiency data exchange between the application
and LitePlus 2.0.
IrDA Related Specification
LitePlus 2.0 is an IrDA primary station that can act
as a secondary station. Whether it plays the primary
or secondary role depends on which IrDA device
initiates the connection procedure.
13PTC-2134 DOS Software Guide
IrDA Power Management
Physical Layer
LitePlus 2.0 supports the standard IrDA SIR Physical
Layer Specification 1.0 (except for 2400 bps-only
devices). Implementing 2400 bps support increases
the complexity and code size without benefit; all IrDA
devices st a rt with 9600 bps discovery and connection
sequence. A 2400 bps-only station star ts its discovery
with the initial command frames beginning with a
minimum of five SOP delimiters (0 x C0) at 2400 bps.
A station that suppo rts 2400 bps hears the SOPs sent
from the 2400 bps as a sequence of characters ‘0x77,
0x77,0xFF’. After recognizing this signature
sequence, it shifts over to 2400 bp s and starts from
there.
LitePlus 2.0 s upports two types of hardwareIR
implementations:
•internal transceivers, and
•external dongles.
Dongles can be attached to serial ports directly or
indirectly(through a cradle). The internal transceiver
design usually requires the IrDA infrared transceiver
baud rate to b e controlled by the baud rate registers of
the COM port it occupies. Internal implementations
that require additional register control can be
supported by treating them as external dongles. The
only external dongle currentlyused supports SIR
speeds of 9600, 19200, 57600, an d 115200 bps only.
To make an IrDA connection to an ex ternal dongle,
follow these steps:
1. Install infrared drivers onto a Win 95 PC. Connect
IrDAdongleto a free COM Port.
2. Start hyperterminal, pointing the opening of the
port to the a ssigned IrDA COM Port (i.e., COM 4).
3. Fromthe DOS prompt,run type config.sys >lpt1.
The hyperterminal screen should display the
contents of config.sys.
PTC-2134 DOS Software Guide14
Chapter 3 Configuring TN-3270/5250
Link Access Control Layer (IrLAP)
LitePlus 2.0 supports Link Access protocol IrDA
specifications 1.0 and 1.1, with the followin g
limitations:
•Connectionless Data Services are not supported.
•Sniff services are not supported. Since LitePlus
•A window size of only one fr ame is supported. For
•SinceLitePlus2.0residesinmainmemoryasa
Also, LitePlus 2.0 does not expose such services t o
the application.
2.0 supports only single Service Access Points
(SAP), such services ar e redundant and are not
available to the application.
the single SAP TSR design, supporting window
sizes of more than one significantly increases the
amount of memory required for buffers and the
complexity of state machine implementation.
TSR, a trade-off between communication
efficiency and memory resources is required.
Large buffers (more memory) means less overhead
when transferring large amountsof data.
However, it also means less mem ory is available
to run applications.All IrLAP APIs are not
directly available to a pplications.
15PTC-2134 DOS Software Guide
IrDA Power Management
The IrLAP summary for LitePlus 2.0 parameter
negotiation is provided in the following table:
Negotiation
category
Baud rate9600, 19200,
Maximum turn
around time
Data sizeUp to 2048 bytesAny
Window size1 frame window1 frame
Number of
BOFs
Minimum turn
around time
Link Disc onnect40,30,25,2 0,16,1
LitePlus XID
response
38400, 57600,
115200
500 ms500 ms
2 @ 115,200 bpsAny
10 msAny
2,8,3 seconds
Preferred
receipt value
Anything
but 2400,
38400
window
Any
PTC-2134 DOS Software Guide16
Chapter 3 Configuring TN-3270/5250
Link Management Layer (IrLMP)
LitePlus 2.0 supports IrLMP 1.0 and 1.1 with the
following ex ceptions:
•Only one Service Access Point is supported. With
•LitePlus 2.0 does not include the architectural
•Exclusive Mode is not supported. The Multiplexed
•Connectionless data is not supported.
•Sniffing primitive is not supported. LitePlus
a single SAP, LitePlus 2.0 can support two-way
data exchange.
component described in the Link Management
Protocol Document section 2.2.3 – Transport
Protocol. LitePlus 2.0 does not support multiple
IrLMP connections simultaneously.
mode supports only simultaneous connections of
IAS (Information Access Service) and dat a
transfer channel.
provides only normal discovery services.
•Thehintbyteissetto0x04,whichidentifiesthe
IrDA driver as a Computer. The printer bit is not
seteventhoughDOSprintingdatacanbe
redirected to the driver. This byte can also be used
by another computer to decide/display how the
unit containing the IrDA driver is used.
•Device nickname — thedevicenicknameis
exchanged during discovery sequence. LitePlus
2.0 allows nicknames to be changed through a
command line option.
•The DISCOVER a nd RESOLVE ADDRESS states
described in section 3.5.2 and 3.5.2.3.1 of Link
Management Protocol D ocument are not
implemented internally in IrLMP b ut rather in
the IrLAP layer.
•Only the CONNECT, DISCONNECTED and
TRANSFER READY states are supported in the
diagram in section 6.3.1 of Link Management
Protocol Document. Other states are not used by
LitePlus 2.0.
17PTC-2134 DOS Software Guide
IrDA Power Management
•The only supported IAS primitive is
LM_GetValueByClass. Other primitives,
including LM_GetinfoBaseDetails,
LM_GetObjects,LM_GetValue,
LM_GetObjectInfo, and LM_GetAttributeNames
should not be used. The IrLMP API is not exposed
to the application, and all IAS services are
handled by LitePlus automatically.
All IrLMP APIs, including those for IAS, are not
directly available to applications. The applications
will use extended INT14H functions to access the
IrDA stack directly.
Classes and Attributes
LitePlus 2.0 will support the following three IAS
classes and attributes:
ClassAttributeVa l u e
DeviceDeviceName{0,1,0,0,3,0,22,
“IrDADriverby
ACTiSYS”}
IrLMPSupport{0,1,0,0,2,0,3,1,
0,0}
IrCOMM*Parameters{0,1,0,1,2,0,6,0,
1,1,1,1}
LSAPSel0,1,0,1,1,0,0,0,2}
IrLPT**Parameters{0x81,0}
LSAPSel{0,1,0,4,1,0,0, 0, 2
}
PTC-2134 DOS Software Guide18
Chapter 3 Configuring TN-3270/5250
Only a three-wire-raw portion is supportedfor
IrCOMM. Three-wire-raw is sufficient for LitePlus
2.0. More complicated protocols, such as
nine-wire-cooked, target different usage models and
require additional protocol support on top of IrLAP
and IrLMP. TinyTP is such a protocol and is not a
part of LitePlus 2.0 design.
** Supported for backward c omp atibility. Even
IrDA Compatibility
LitePlus 2.0 is based on the ACT1 IrDA stack, which
has passed Ir D A compatibility tests conducted by
ACTiSYS. Those tests include both test suites from
Genoa for IrDA compatibility and interoperability
tests, including many third-party implementations.
DOS BIOS INT17H Function Extension
printing will use three-wire-raw in the IrCOMM
object instead of the IrLPT object.
OneofthekeyfeaturesofLitePlus1.10issupportfor
data printing through the IrDA driver under a DOS
prompt. T his feat ure is achieved by replacing the
INT17H interrupt routine.
When L ite Plus is enabled, all calls to INT17H are
redirected to the IrDA stack only when DX is zero.
This implies that LitePlus 2.0 distinguishes between
different LPTx ports, and only LPT1 i s mapped to the
IrDA port. The reason LPT1 is always used is because
all DOS printing functions, such as PRINT SCREEN,
are always redirected to LPT1. When LitePlus is
disabled or DX is not zero, all calls are direc ted to the
original INT17H routine. Following are the details for
the new INT 17H.
19PTC-2134 DOS Software Guide
Print Character
The print character function sends the byte in AL to
LitePlus 2.0’s internal bufferif a connection has
already been configured.If a connectionhas not been
established,LitePlus 2.0 waits for a full discovery
cycle before it returns.
Called with:AH =0
AL =character to print
DX =0Only LPT1 is mapped to IrDA port.
Returns:AH =0 x 90 If successful.
0 x 31 If failed.
Initialize Printer
This function initializes the IrDA driver by
initializing discovery/connection.
Called with:AH =1
DX =0Only LPT1 is mapped to IrDA port.
IrDA Power Management
Returns:AH =0 x 90 If successful.
0 x A8 If failed.
Get Printer Status
This function always returns successfully.
Called with:AH =2
DX =0Only LPT1 is mapped to IrDA port.
Returns:AH =0 x 90
Tests to support the following DOS printing functions
will be conducted and demonstrated before release:
•Re-direction of TYPE, DIR or COPY command.
•Print-screen Sys Rq.
•Ctrl-P.
PTC-2134 DOS Software Guide20
Chapter 3 Configuring TN-3270/5250
DOS BIOS INT14H Function Extension
Although LitePlus 1.10 supports printing through
re-direction to COMx (where x is the number of IrDA
COM ports), LitePlus 2.0 no longer supports such
usage. All printing data should be redirected to the
LPT port instead. One of the major features of
LitePlus 2.0 is support for two-way, h igh-efficiency
data transfers.
Due to well-known latency of DOS serial BIOS calls,
most DOS programmers bypass the BIOS call and
directly access the registers. Unfortunately , DOS does
not hav e the capability to catch direct access to
registers and make legacy programs work
transparently. To use the new IrDA capability, use
the extended APIs that LitePlus supports.
Instead of supporting DOS redirection to COMx
similar to LPT1 ports, LitePlus 2.0 actually ex tends
INT14H to support two-way, high-efficiency data
transfer. Applications can directly access IrDA stack
buffers and status through these extensions. This
method also provides application software a way to
disable/enable the entire IrDA stack.
Upon installation, LitePlus 2.0 installs its own
INT14H routine. All calls without the correct COMx
port specified, or with a function number small er than
0 x 80, are passed over to the old INT14H. T he
following are details of the new INT14H functions.
Buffer Control Block (BCB)
To increase the efficiency of da ta transfer, structures
called Buffer Control Blocks (BCBs) are exchanged
between IrDA stacks and application software. Th e
definition of a BCB is as follows:
typedef struct BufferControlBlock {
intStatus;/* Internal buffer usage indicator
*/
struct BufCntlBlck* pNext; /*Pointer to next BCB structure*/
21PTC-2134 DOS Software Guide
IrDA Power Management
unsigned int BufferSize;/* Size of the buffer pointe d by
unsigned int DataLength;/* Length of total frame data */
unsigned int DataOffset;/* Offset to the start o f useful
unsigned char pPacket;/* Pointer to the start of the
pPacket */
data */
buffer */ } BCB;
Two BCB queues are maintained independent ly by
the LitePlus 2.0 driver: the send queue and the
receive queue. For receiving data, the application can
either poll the LitePlus 2.0 driver to get a BCB that
LitePlus 2.0 received successfully or directly use the
pointer returned by the callback function.
After the data in the BCB is consumed, the
application returns the BCB to LitePlus 2.0’s receive
queue. For sending data, t he application first requests
a free BCB from LitePlus 2.0. If succ essful, it fills up
the BCB and passes it back to LitePlus via an
INT14H call.
StatusThis field is used internally by LitePlus 2.0 for buffer
management. The application software sets it to zero
before returning it to the IrDA driver to send.
pNextThis field is also used internally by LitePlus 2.0 for
buffer manage ment. The application software should
ensure not to change this field for both incoming and
outgoing bu ffers.
BufferSizeThis number is the size of the buffer pointed by
pPacket and is the maximum num b er of bytes of d ata
this BCB can carry. The application should always
check this field to ensure it does not write too much
data into a BCB. For future consideration,
applications should assume that all BCBs could have
different BufferSize values. For L itePlus 2.0, this
value is set for all BCBs during the dr iver load.
PTC-2134 DOS Software Guide22
Chapter 3 Configuring TN-3270/5250
DataLengthFor incoming buffers, this field indicates the length of
the data bytes in the IrDA I frame received. The
number of ‘real’ data bytes is this number minus four.
For outgoing buffers, this field indicates how many
bytes are to be sent and should be set correctly by the
application. The numbe r of “real” data bytes is this
number plus four.
DataOffsetThis field indicates the starting index of real data in
the Data array pointed by pPacket. For all BCBs, this
field is four and h as been included for future
compatibility with more complicated protocols such as
TinyTP.
For outgoing BCBs, th is field has no effect.
pPacketThis is the pointer to wh ere real data is stored. For
incoming BCBs, the effective data starts with
pPacket[DataOffset]withlengthofDataLength.
23PTC-2134 DOS Software Guide
Initialize IrDA Stack
Called with:AH= 0 x 80
AL= 0Disable IrDA stack. Discards all data
= 1Enable IrDA stack with callback
EX:BXAddre ss of a callback function.
(AL = 1)The callback fu nction contains the
IrDA Power Management
buffers that have not yet been sent.
All data buffers received but not yet
consumed will also be lost. This is
necessary to maintain the integrity of
buffer, as there could be a buffer
occupied b y printing data from
INT17H. Once disabled, the only way
to enable the stack again is to call INT
14H with AH = 0 x 80 and AL = 1.
function. Discards all data buffers that
have not yet been sent. All data
buffers received but not consumed will
be lost.
void Ca llBack (ch ar far * fpData, int
iDataLength) prototype. If EX:BX was
setto0:0,nocallbackoccurs.The
received data buffer is available
through other calls.
CX= 0Internal transceiver used on the COM
port
= 1ACT220L dongle is used.
0xFFFFDefaultdongle.Thisiseitherthe
default transceiver (internal) or th e
one specified on the command line.
DX=Serial port 0 to 3. This parameter
allows usersto change the IrDA serial
port “on the fly.” A value of FFFFh
indicates that the defaultport (or the
one specified on the command line)
should be used.
PTC-2134 DOS Software Guide24
Chapter 3 Configuring TN-3270/5250
Returns:AH =0 x 90 Successful. This value is always
ES:BXPointer to a data structure that
returned.
contains all the IrDA-related
information. The definition of the data
structure is listed below. After the
first initialization call, the application
software s hould be able t o get most of
the useful information directly from
this structure.
Although the main purpose of this call is to
disable/enable the LitePlus 2.0 driver, the returned
pointer points to a data structure that allows the
application to retrieve many of the counters and
statistics of the underlying LitePlus 2. 0 driver while
the IrDA connection is active.
The LitePlus 2.0 driver is enabled by default after
installation.
BaudRateThe current Baud rate used by the IrDA transceiver.
LAP_StatusThis fie l d indicates the current status of the LiteP lus
2.0 driver. T he following are the possible values for
this field:
0Disconnected. The driver has not yet
set up a connection with a nother IrDA
device. LitePlus 2.0 can either be idle
or in the middle of a discovery/
connection procedure.
1Connected. The driver is al ready
connected with another IrDA device.
Data transfer occurs only when
LitePlus 2.0 is in this state.
2Disabled. The driver will reject any
data transfer request. This implies
that if a BCB is requested, a NULL
pointer will be returned.
EngineTypeThis field indicates what role the LitePlus 2.0 driver
is currently playing. Following are the possible
values:
0Secondary station role. In this role,
LitePlus 2.0 responds passively.
1Primary station role. In this role,
LitePlus 2.0 actively attempts to
connect wi th another device.
2Undecided. The LitePlus 2.0 is idle in
disconnected mode. Which role it will
play depends on whether another
IrDAdevicetriestoinitiatea
connection first.
IAS_SelectionThis field indicates how IAS responds to inquiries.
Therearetwopossiblevalues:
0LitePlus2.0supportsIrLPTonly
(UsedonlybyLitePlus1.x.
1IrCOMM, Th ree-wire-raw (Used by
LitePlus 2. 0).
PTC-2134 DOS Software Guide26
Chapter 3 Configuring TN-3270/5250
DeviceAddressThis long word is the MAC address used by the IrDA
LAP of LitePlus 2.0 (source address).
dDeviceAddressThis long word is the MAC address used by the IrDA
LAP of the IrDA device that communicates with
LitePlus 2.0 (destination address).
LocalDiscoveryInfoThis string contains the nickname of the local
station/IrDA stack. LitePlus 2.0 always sets it to
“LitePlus.”
RemoteDiscoveryInfoThis string contains the nickname of the remote
station/IrDA stack.
ReceivedPacketsThis long word counter contains the total packets
receivedby LitePlus 2.0. This counter is reset each
time the stack ma kes a transition f rom connected to
disconnected mode.
ReceivedBytesThis long word counter contains the total bytes
received by LitePlus 2.0. Please note that this coun ter
is NOT the total number of bytes of effective data
carried over the infrared link. It includes all the bytes
in all packets and is a good indication of infrared
channel quality.
SendPacketsThis long word counter contains the total packets sent
by LitePlus 2.0. This counter is reset each time the
stack makes a transition from connected to
disconnected mode.
SentBytesThis long word counter contains the total bytes sent
by LitePlus 2.0. Please note that this counter is the
NOT the total number of bytes of effective data
carried over the infrared link. It includes all the bytes
in all packets.
27PTC-2134 DOS Software Guide
IrDA Power Management
DataInSendQueueThis long word counter contains the total number of
bytes already in the L itePlus 2.0 send data queue but
not sent over the infrared link. Packets that have
already b een sent but not yet acknowledged are also
included.
DataInReceiveQueueThis long word counter contains the total number of
bytes already received by LitePlus 2.0 but not yet
consumed by the application.
BadPacketsThis long word counter co ntains the t otal bad packets
received by LitePlus 2.0. Bad packets are those
complete packets with bad CRC or partial packets.
This counter will be reset each time the stack makes a
transition from connected to disconnected mode.
TotalResendThis long word counter contains the total number of
times a packet has been r esent. A resent condition
could occur for several reasons: (1) The other station
does not receive the packet; (2) The other station
received the packet but the received packet does not
have a valid CRC; (3) The response from the other
station is not received by this statio n; (4) The
response is not valid. This counter is reset each time
the LitePlus 2.0 makes a transition from connected to
disconnected mode.
Send/Return BCB
Called with:AH= 0 x 81
AL=0TheBCBhasvaliddataandistobe
sent.
= 1The data in this BCB has been
consumed. The application is
returning the BCB to LitePlus 2.0.
Returns:AH =0 x 90 Success. This value is returned as long
as LiteP lus 2.0 is enabled.
0 x A0 Fail. LitePlus 2.0 is currently in a
disabled mode.
PTC-2134 DOS Software Guide28
Chapter 3 Configuring TN-3270/5250
This function has two different uses: the application
can use this function to request L itePlus 2.0 to send a
BCB that has be en filled wit h data, or it can return a
BCB with received data already used by the
application.
Receive/Get Free BCB
Called with:AH =0 x 82
AL =0Ask LitePlus 2.0 for possible incoming
Returns:AH =0 x 90 Success. This value is returned as long
EX:BXPointer to the BCB. It could be a BCB
BCB
1Ask LitePlus 2.0 for possible free BCB
as LiteP lus 2.0 is enabled.
0 x A0 Fail. LitePlus 2.0 is now in disabled
mode.
that contains the data LitePlus 2.0
successfully received over the infrared
link or a fr ee BCB for application to
place send data. A NULL po inter can
be returned in both cases. A NULL
pointer means no data has been
received if the application is asking for
incoming BCB. It also mean s no free
BCB is available if the application is
requesting free BCB.
Get Status
Called with:AH =0 x 83
AL =0Discovery status
1Connectionstatus
29PTC-2134 DOS Software Guide
Returns:AX =Corresponding status
If the application asks for discovery status, the
possible return values are:
0Never discovered
1Already discovered, but LitePlus 2.0 is
idle
2In the middle of a discovery procedure
4Already discovered, probably
connected
If the application requests connection status, the
possible return values are:
0Disconnected. LitePlus 2.0 is in NDM
state.
1Connecting. LitePlus 2.0 is in the
middleof a connection procedure.
2Connected. LitePlus 2.0 is already
connected with another station.
IrDA Power Management
4Disabled.
Please note that this status information i s used by the
application to display the status of the underlying
LitePlus 2.0 driver.
Unload LitePlus Driver
Called with:AH =0 x 84
Returns:BX =0Unable to unload the LitePlus driver.
Before unloading the LitePlus driver,
it checks to ensure that APM interrupt
support is installed. If yes, it verifies
that the current interrupt vector is the
same as in the LitePlus driver. If not,
it means another routine replaced the
APM driver after LitePlus was loaded.
It is not possible to unload the driver.
PTC-2134 DOS Software Guide30
Chapter 3 Configuring TN-3270/5250
BX =otherwise LitePlus has recovered all the
Miscellaneous
Command Line Options
All command line options start with ‘/’. The following
command line options are availa ble for LitePlus 2.0.
The synopsis for LitePlus 2.0 is as follows:
Please note that all options are case insensitive.
/COM:xThis option allows the user to choose
interruptvectors.BX now contains
the _psp variable of the LitePlus
driver. The caller can then use this
variable to unload the driver.
[/SUSPENDOK] [/NAME:ssss] [/HELP] [/UNLOAD]
the UART port to wh ich the IrDA
hardware is connected. The ‘x’ can be
any value between 1 and 4. LitePlus
2.0 uses DOS def ault register
addresses, and the default COM port
is COM3. LitePlus 2.0 also assigns an
IRQ number accordingly. The default
values for DOS are
Please note that 38400 bps is listed here, even though
ACT IR220L does not suppo rt 38400 bps, because the
default d ongle is assumed to be an internal dongle.
/EXT:xThis option tells LitePlus 2.0 what
external dongle is attached to the
serial port. Following values are
currently supported.
0Noexternaldongle(Default)
1ACT IR220L
/BUFFER:xThis option tells LitePlus 2.0 the
maximum size for a single buffer.
Following values are supported:
064 bytes (default)
1128 byt es
2256 byt es
3512 byt es
41024 bytes
52048 bytes
PTC-2134 DOS Software Guide32
Chapter 3 Configuring TN-3270/5250
This is the only control over memory a llocation for
buffers. Send queue and receive queue each contain
two BCBs. Ea ch BCB contains a data buffer of the
size d efined here.
/NOAPMLitePlus2.0 supports the Symbol APM
/SUSPENDOK By default, LitePlus 2.0 rejects a
(Advanced P ower Management)
driver. B y default, LitePlus 2.0
attempts to detect APM driver and
install APM supp ort accordingly.
However, if the APM driver is not
detected or the user chooses to in stall
with the /NOAPM option, LitePlus 2.0
will not install APM support. By
supporting APM, LitePlus 2.0 is able
to recover from a suspend/resume
cycle.
request to suspend if it is in the
middle of a communication section.
However, if the driver is installed with
this option, LitePlus 2.0always honors
the request.
/NAME:ssssThis option allows the nam e of the
IrDAstack to be changed. This name
is displayed when the device is
discoveredby Windows 95. The default
value is “PTC-2134.” Please note t hat
Windows95displaysonlythefirst18
characters of the string whe n
disconnected and can display at least
28 characters when con nected. The
longest name that LitePlus 2.0 can
handle is 28 characters. LitePlus 2.0
truncates the string if it is longer than
28.
/HELPIf this option is used, LitePlus will
simply display the following message
and quit without further action.
Name:Any string. Only the first 28 characters are used.
Default is PTC-2134.
Note:In the preceding parameters, “*” indicates a default
setting value.
/UNLOADLitePlus attempts to recover all the
interrupt vectors it changed and
unloads itself. If successful, the
message “LitePlus uninstalled” is
displayed. If unsuccessful, the
message “APM interrupt prevent
unloading LitePlus” is displayed, and
the driver stays unchanged. Notice
that when the /UNLOAD option is
used, all other options are ignored.
PTC-2134 DOS Software Guide34
Chapter 3 Configuring TN-3270/5250
Initial Detection
Before installing the LitePlus 2.0 TSR driver, the
software per forms the following detections:
•Whether the required COM port has been
•Whether the LitePlus 2.0 TSR has already been
If either of the detections fail, LitePlus 2.0 aborts the
installation procedure with an appropriate error
message.
Discussions
•Callback functions can easily di srupt or disable
detectedbyDOS.Thisisachievedbycheckingthe
BIOS data area at 0 x 40:0. The associated error
message is “Serial port not found. Driver not
installed.”
installed. This is ac hieved by checking the
‘LitePlus’ identification s tring. The associated
error mes sage is “Driver alread y loaded.”
the system if the application terminates without
first disabling the IrDA driver.
•Since callback functions are actually called from
inside the interrupt ro utine, the application
should return as soon as possible. Long delays in
the callback routine co uld cause the behavior of
the driver to be unpredictable.
35PTC-2134 DOS Software Guide
NTMOUSE
This section describes NTMOUSE, Symbol’s digitizer
driver for the Nissha touchscreen controller.
What is NTMOUSE?
NTMOUSE is the Symbol digitizer driver for the
Nissha™ touchscreen controller. This section
describes the relationship between di gitizers, the
NTMOUSE digitizer driver, and the PENCAL pen
calibration utility.
The Nissha digitizer (or touchscreen controller)
generates interrupts when the screen is touched with
astylus.Thedataprovidedbythedigitizerisina
very raw format, consisting of X and Y coordinates in
“digitizer units.” These digitizer units do not
correspond to pixels; the digitizer simply c onverts
analog X and Y voltages from the touchscreen into a
digital v alue and generates an interrupt to the
digitizer driver.
The NTMOUSE digitizerdriver (sometimes called the
“pen driver” or “mouse driver”) reads the stylus
position in digitizer units and makes it available to
applications as “mouse” input. The ma in roles of
NTMOUSE are to (a) emulate the DOS interrupt 74h
mouse programming interface, and (b) convert
digitizer unit coordinates to mouse coordinates.
The co nversion from digitizer units to mouse units is
simple once NTMOUSE is properly calibrated.
NTMOUSE monitors the current video mode of the
PTC, giving it the range of valid X and Y coordinates
in mouse units. For example, Video Mode 18 is 640 by
480 pixels in X and Y dimensions and has 16 colors.
The dig itizer simply has to convert digitizer units into
a 640 x 480 range for each digitizer interrupt.
PTC-2134 DOS Software Guide36
Chapter 3 Configuring TN-3270/5250
Pencal
PENCAL is the tool that configures NTMOUSE with
the minimum and maximum X and Y digitizer unit
coordinates for each video mode.It does this by
displaying a configuration screen with four c rosshairs
and asking the user to tap each one in sequence.
For each pen tap, PENCAL obtains the digitizer
coordinates of the crosshair. Because it knows the
pixel coordinates of the crosshair, PENCAL can
calculate the for mula needed to convert between the
two. It saves this information in a configuration file
(generally tmouse.ini)thatisreadbyNTMOUSE
when it loads.
Using NTMOUSE
To run NTMOUSE, invoke it at the DOS command
prompt using command-line arguments appropriate to
the PTC display type. NTMOUSE contains the
following command-line:
ntmouse [/Q] [/B] [/?]
These arguments are optional:
•/Q indicates the display is a 320x240 1/4-VGA.
•/B dis ables the beep on APM resume
(available in version 3.02.02 and later).
•/? displays the usage line.
By default, NTMOUSE assumes a 64 0 x 480
“full” VGA display and expects to read calibration
information from TMOUSE.INI.
37PTC-2134 DOS Software Guide
ThepathtoNTMOUSE’s calibration file can be
configured using environment variables. When it
loads, the file looks for an environment variable
named TMOUSE. This variable should contain a
pointer to the configuration file (for example,
TMOUSE = c:\mouse\tmouse.ini). If this variable
does not exist, NTMOUSE reads its program segment
prefix to determine its installation directory. It then
tries to open tmo use.ini in its installation directory.
If this fails, NTMOUSE will still l oad but will use
default calibration values that may be incorrect.
NTMOUSE Interaction with APM
The NTMOUSE driver is APM aware. This means
that it gets a notification when the PTC on which it is
running is suspended or resumed. During resume,
NTMOUSE reinitializesthe touchscreen hardware
and generates a beep. The beep is NTMOUSE’ssignal
to the user that the touchscreen is active again and is
ready for input.
Units with the mouse, Ethernet, and cradle driver
loaded that are left in a cradle with an active
Ethernet link will emit a beep at regular intervals,
whenever the unit attempts to go into APM s tandby
mode and the E t hernet driver rejects the attempt. The
reason for this is that a rejectedAPM standbyrequest
results in an APM resume notification to alldrivers,
and this causes NTMOUSE to generate a beep. This
can be disabled with the /B command mentioned in
the "Using NTMOUSE" section.
PTC-2134 DOS Software Guide38
Chapter 3 Configuring TN-3270/5250
The Pen’s Sample Rate
With the pen sample rate set too high, the system
reads and interprets noise as pen data and its output
appears nonlinear (jagged) when drawing lines using
the pen. On some Symbol devices, the defau lt
sampling rate is set to the highest sampling rate
possible.
TheDOS/PenRight!imageshouldbemodifiedsothat
the NISSHA_RATE environment variable is set to 30
(decimal) in the 2134 stanza of \util\WHICH.BAT
prior to loading NTMOUSE.
Therearetwowaystoadjustthesamplingrate.At
load time, the driver searches fo r an envi ronment
variable called NISSH A_RAT E. The value of this
variable is a decimal integer w hich will be
programmed directly into the touchscreen controller’s
rate configuration register. So for example, this
variable in the WHICH.BAT file for the PTC-2134
could be set as follows:
set NISSHA_RATE=30
This variable has to be set before the driver is loaded
for it to take effect. The driver ignores the setting if it
is (a) zero, (b) not a decimal integer value, or (c)
greater than 255. Note that choosing an appropriate
value for the rate requires knowledge of how the
Nissha touchscreen controller translates rate register
values into interrupts per second. In general, the
larger the rate value the fewer interrupts per second.
39PTC-2134 DOS Software Guide
At run time, the mouse driver exports the standard
interrupt 74h API to applications. One of the
supported entry points is function 1Ch, “Set Mouse
Interrupt Rate”.Here’sthedefinitionoftheAPI:
; mouse_fn_1CH-INT 74H AX = 1CH Set Mouse Interrupt Rate
;
; Sets the number of mouse interrupts generated while the pen
is down.
;Faster rates provide better resolution in graphics mode but
;can degrade the performance of application programs.
;
;Callwith:
;AX= 001CH
;BX= interrupt rate flags
;Bit(s)Significance (if set)
;0lowest possible rate
;130 interrupts/second
;250 interrupts/second
;3100 interrupts/second
;4200 interrupts/second
;5-15reserved (0)
;
;Returns:
;Nothing
Note that adjusting the sampling rate affects the
pen’s sensitivity to quick taps and movements.
Special Notes for Programmers
NTMOUSE does not support INT 74h functions 7 and
8 (Set Horizontal Limits f or Pointer and Set Vertical
Limits for Pointer, r espectively).
Some applications (such as the PenRight! runtime)
routinely use these calls to set the horizontal limits to
0 through 640 and the vertical limits to 0 through
480. Intern ally, NTMOUSE uses the pointer limits to
scale digitizer coordinates to mouse coordinates, so
these calls interfere with its ability to provide
accurate information to applications. NTMOUSE will
silently ignore attempts to set the pointer limit s using
these two functions.
PTC-2134 DOS Software Guide40
Chapter 3 Configuring TN-3270/5250
2124POP is a popup keyboard utility. 2124POP allows
users to utilize the pen-based screen to touch the keys
in the pop-up keyboard with a stylus to key in text on
the comm a nd line or in other applications. 2124POP
also has a "gas gauge" function to show battery life.
This function will display a meter that displays the
amount of life remainin g in the battery as a
percentage of the originallife.
Command Line:The command str ing for the 2124POP is as follows:
2124pop [/option]
Options:Individual parameters within the string influence
different features or operations as follows:
/Denables the Direct Video I/O Mode.
2124POP
/Ndisables the Drag feature.
/Benables the budget Keyboard o peration.
/Eenables the Keyboard when popup is
invoked.
/K:nn=0– 9999, sets the standard keyboard
delay (default = 25).
/F:path specifies a file containing "action" k ey
definitions.
/S:nn=0– 9999, sets the secondary keyboard
delay f or "action" ke ys.
/M:path specifies a Macro Definition File.
/R:nn=0– 60, sets the time-out value for the
Resume Time-out macro.
41PTC-2134 DOS Software Guide
/G[:n]enables the Battery Gas Gauge. n = 0 – 8
default=2,setgasgaugealarmlevel
(optional).
/T:nn=1– 5, sets the triple-tap activation time
threshold (default = 2).
/A:nn=1– 5, sets the triple-tap activation area
threshold (default = 2).
/X:nSets the numberof videocolumns.
/Y:nSets the numberof videorows.
PTC-2134 DOS Software Guide42
Chapter 3 Configuring TN-3270/5250
This section describes PENCAL, Symbol’spen
calibration utility. PENCAL is used in conjunction
with Symbol’s DOS-based digitizer drivers, such as
NTMOUSE.
What is PENCAL?
To understand PENCAL, it is necessary to
understand Symbol’s digitizer drivers. This section
gives a brief overview of how the digitizer, the
digitizer driver, and PENCAL work together.
The digitizer (or touchscreen) generates interrupts
when the screen is touched using a stylus. The data
provided by the digitizer is in a very raw format,
consisting of X and Y coordinates in “digitizer units.”
These digitizer units do not correspond to pixels in
anyway;thedigitizersimplyconvertsanalogXandY
voltages f rom the touchscreen into a digital value and
generates an interrupt to the digitizer driver.
PENCAL
The digitizer driver is sometimes
called the pen driver or mouse
driver.
43PTC-2134 DOS Software Guide
The digitizer driver reads the stylus position in
digitizer units and makes it available to applications
as “mouse” input. The main roles of the digitizer
driver are to
•emulate the DOS interrupt 74h mouse
programming interface, and
•convert digitizer unit coordinates to mouse
coordinates.
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.