1. ov378parw2k.zip Driver
2. README.TXT File Contents

README.TXT Driver File Contents (ov378parw2k.zip)

FILE: readme.txt             Copyright (c), Symmetric Research, 2003-2004

Diag checks the PARxCH for proper installation and operation.

Run diag with the /? option to get a usage message showing a list of
what diagnostic tests are available.  Some sample command lines are:

> diag /?
> diag std
> diag SrParXch378 PAR8CH ecp/bpp led empty acquire

Most users should start with "std" which includes a series of four
tests.  The first automatically tries various driver names and
parallel port modes, checking for an attached PARxCH and generating a
report.  Using the first successful reported driver and mode, the
second test checks which Xch model is connected.  The third test
identifies the default Xch model that is used in the application
programs when no Xch model is given by the user.  For the final test
of the std series, diag enters a mode where you can twiddle the yellow
PARxCH led until pressing q+ENTER to quit and return to the command
prompt.

The driver name, xch model, and parallel port modes identified as
successful by the diag std tests should be used when running the
application programs like meter, simp, scope, and etc.

NOTE: As all PAR1CH boards are currently programmed with PAR4CH
firmware, diag can not distinguish between these two Xch models.

In determining whether a PARxCH is attached to a particular port,
diag reads and writes to that port.  If you have a printer or other
device attached, you may find characters have been written to it.
Check any parallel port devices you have connected to your computer
after running diag to see if they have some data in their buffers.


* GET RID OF CONFLICTING PARALLEL PORT DRIVERS

When using the PARxCH many users will disconnect their printer from
the parallel port and connect the PARxCH.  If you do so, be sure to
also disable any parallel port drivers that are servicing the printer
on that port.  For most OS's, this step will have already been done as
part of installing the PARxCH driver.

Under older multiuser systems like Win95, printer drivers may
ascynchronously access the parallel port while the PARxCH software is
executing.  This will cause a conflict and prevent proper operation.
Disabling or removing the printer driver removes the problem.

HP printer drivers are a known problem in this regard ... do not
leave them installed on the PARxCH parallel port.