SECTION 3
Supporting Windows Applications
3-30 PEN*KEY
R
6200/6300 Hand-Held Computer Programmer’s Reference Guide
[NPCP Driver]
DeviceName=LPT1
CommAddress=0x03F8
CommVector=0x0C
FIFODepth=16
PowerManage=FALSE
ProcessQueryAbort=FALSE
FIFOTriggerLevel=0
IRQMultiplex=0
DeviceName=LPT1:
Names the device, to which Windows outputs, and be
directed out the IR port. This option must match the settings in WIN.INI.
CommAddress=0x03F8:
This option specifies the communications port address.
CommVector=0x0C:
This option specifies the communications port interrupt
request number.
FIFODepth=16:
This entry determines the FIFO usage on the UART. A value of
0 disables the FIFO.
PowerManage=FALSE:
This entry determines whether or not you are be able to
turn port power on and off. This function may not work with all thirdĆparty
APM services.
ProcessQueryAbort=FALSE:
This option disables/enables the QueryAbort
processing during printing. The default setting is FALSE, which disables the
ability to cancel the print job once it has started. Valid settings are TRUE or
FALSE.
FIFOTriggerLevel=0:
This option, which is valid only if the FIFODepth setting
is greater than 0, sets the Receive interrupt trigger level. The default value is 0;
valid settings are 0ć3. The Receive interrupt trigger is chipĆdependent. On a
550 UART, a value of 0 causes the chip to interrupt on every character. The
same value on an ST650 UART causes an interrupt on every eight characters (or
after four character times if at least one character is in the FIFO buffer. For
further details, see the UART documentation for setting the top two bits in the
FIFO control register.
IRQMultiplex=0:
Use this option to install/deinstall the ISR for every print job.
This can be useful if the IRQ is being multiplexed with some other device, such
as the scanner. The default setting of 0 indicates no multiplexing. Valid settings
are 0 and 1.
Usage
The NPCP printer driver uses COM1 communication hardware directly. The
COM1 hardware is initialized and the external RSĆ232 driver hardware is
powered on, allowing the driver a free and clean" data path to the printer. This
makes it necessary to be careful when sharing the COM1 hardware with any
other driver. Currently, there is no method of arbitrating COM1 access, so
drivers must be enabled and disabled only when they are needed. This means
that printing in the background and trying to use another driver that talks to
the COM1 hardware causes undetermined problems. The scanner driver is
currently the most likely source of port multiplexing problems. For information
relating to enabling and disabling the scanner driver at the appropriate times,
see the
6300 Integrated Scanner
topic, on page 3Ć25.
3. Windows
Applications
