--------------167EB0E72781E494446B9B3D
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
I suspect that the problem is in whatever driver/low level routines
omniprn uses to manage the the PC serial port. I have the same problems
you do (except I haven't built your excellent AC adaptor yet :-).
If I connect the cable directly to an HP LJ3 serial port, it works
fine no matter what the state of the batteries.
I've written software for serial ports - it can be very tricky; there
are usually lots of undocumented things you have to do and all kinds
of communication parameters (e.g. RTS/CTS or XON/XOFF) you have to
track.
It occurs to me that there also might be interference between the
W's and R's that omniprn writes on the screen and communication with the
serial port.
All in all, I think omniprn is an excellent program that just needs a
little tuning.
David
--
_____________________________________________________________________
David M. Elins voice: (617) 229-7160
Xionics Document Technologies, Inc. fax: (617) 229-4171
70 Blanchard Rd. Burlington, MA 01803 eMail: delins@xionics.com
yde@world.std.com
_____________________________________________________________________
--------------167EB0E72781E494446B9B3D
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Return-Path: <owner-ogo@lifelike.com>
Received: from europe.std.com by services.xionics.com
id <11882-0@services.xionics.com>; Wed, 24 Jul 1996 14:55:37 -0400
Received: from world.std.com by europe.std.com (8.7.5/BZS-8-1.0) id OAA11260;
Wed, 24 Jul 1996 14:55:35 -0400 (EDT)
Received: from mail.crl.com by world.std.com (5.65c/Spike-2.0) id AA11021;
Wed, 24 Jul 1996 14:52:05 -0400
Received: from lifelike.com by mail.crl.com with SMTP id AA14976 (5.65c/IDA-1.5
for <yde@world.std.com>); Wed, 24 Jul 1996 11:42:04 -0700
Received: by lifelike.com (4.1/SMI-4.1) id AA29181; Wed, 24 Jul 96 10:55:47 PDT
Received: from atc.boeing.com by lifelike.com (4.1/SMI-4.1) id AA29174;
Wed, 24 Jul 96 10:55:28 PDT
Received: by atc.boeing.com (5.65/splinter.boeing.com) id AA24541;
Wed, 24 Jul 1996 10:53:51 -0700
Received: from edcca4.bgl.ca.boeing.com by splinter.boeing.com
with SMTP (1.37.109.16/16.2) id AA016640827;
Wed, 24 Jul 1996 10:53:47 -0700
Received: by edcca4.bgl.ca.boeing.com (AIX 4.1/UCB 5.64/4.03.B4) id AA20654;
Wed, 24 Jul 1996 10:53:54 -0700
Date: Wed, 24 Jul 1996 10:53:54 -0700
From: ust941@edcca4.bgl.ca.boeing.com (Jeff Hinman)
Message-Id: <9607241753.AA20654@edcca4.bgl.ca.boeing.com>
To: ogo@lifelike.com
Subject: Printing
Cc: yngv@gnn.com
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Md5: 23ZyYIK3nx3sM2rR19KsqA==
Sender: owner-ogo@lifelike.com
Precedence: bulk
X-Mozilla-Status: 0001
I asked a question concerning printing over a week ago and didn't get a
response, so I'll ask again to see if maybe it wasn't received.
I use the omniprn program that allows Omnigo printing via a PC to a laserjet. I
noticed that when my batteries were low, especially on the higher baud rate of
19200, there was a lot of noise and incorrect printing. If I used fresh high
quality alkalines, the printing improves, but is still not perfect. If I use an
AC adaptor, the printing is great even at the high transfer rate of 19200 bps.
It seems like the serial data quality is linked to the power level in the
batteries. How can this be since both sender and target are digital? Does this
occur with other applications that use the serial cable such as Installer and
the Connectivity Pack?
Any clues? Thanks.
Jeff Hinman
ust941@edcca4.bgl.ca.boeing.com
--------------167EB0E72781E494446B9B3D--