SECTION 2
Supporting DOS Applications
2-20 PEN*KEY
R
6200/6300 Hand-Held Computer Programmer’s Reference Guide
DOS IrDA Printing: PRDRV.SYS, IRDAPDRV.EXE
The 6210 Computer supports IrDA printing under DOS. It consists of the device
driver, PRDRV.SYS, plus IRDAPDRV.EXE, the driver handler, link management
wrapper, and protocol stack. Together these form the IrDA printer solution,
providing a standard DOS character driver to support IrDA printers.
Installation and Configuration
Make sure the IRDAPDRV.EXE and PRDRV.SYS files are on the system. If the
system was delivered with an application requiring these files, they should
already be in flash. If not, look in the toolkit.
Required CONFIG.SYS Entry
The following entries are required in the CONFIG.SYS file:
device=d:\pathname\prdrv.sys
install=d:\pathname\irdapdrv.exe –txxxx
where
d:\pathname
is the specific path to the directory where your printer
drivers exist; and where
xxxx
is the technology" for the platform on which this
driver is used. In the case of the 6200 Computer,
xxxx
should be 6210. For the
6300 Computer,
xxxx
should be 6300.
Required AUTOEXEC.BAT Entry
There are no required entries in the AUTOEXEC.BAT file for IRDAPDRV.EXE.
Device Driver Entry Points
The IrDA printer driver supports the following DOS device driver entry points,
compatible with the standard input and output libraries provided by DOS
compilers, handling the request as indicated by the summarized processes
details (open, read, write, IOCTL, and close), as described:
open ć
Attempts discovery of an IrDA device, and if found, establishes an IrLMP
connection for a printer with the device.
"
NOTE:
Only one open connection is allowed.
read ć
Returns data sent by the system. A return count of zero implies that no
data is available.
write ć
The written character is stored in a local coalescence buffer (with the
IrLMP protocol header inserted) until the frame size is reached, when the
frame is transmitted to the printer. If the ćn switch is used, each user
write byte count is sent with the IrLMP protocol header inserted without
any attempt at local coalescence.
IOCTL ć This processing is specific to NORAND products and supports printing
applications. A printing program may hook the DOS INT 24 critical error
interrupt and then call the driver's IOCTL directly using the information
provided by INT 24. The driver responds by setting an extended error code
in the application's memory, using a pointer that was passed to it through
the IOCTL interface. The following IOCTL call switch is implemented.
2. DOS
Applications
