Re: [PCWorks] Converter/adapter from parallel printer port to USB port
- From: "Clint Hamilton-PCWorks Admin" <PCWorks@xxxxxxxxxxxxxxxxxxxxxxxx>
- To: <pcworks@xxxxxxxxxxxxx>
- Date: Sun, 14 Mar 2010 23:33:21 -0500
One way to know is to remove the adapter and try again. That should be
your first step. If it's not there, then obviously it's being caused by
the adapter (or its drivers/software).
-Clint
God Bless,
Clint Hamilton, Owner
www.OrpheusComputing.com
www.ComputersCustomBuilt.com
www.OrpheusComputing.com/cheap_reliable_web_hosting.html
www.OrpheusComputing.com/PCworks-computer-help-email-list.html
----- Original Message -----
From: "David Grossman"
I haven't used this printer in a while, so I don't recall whether it
happened after I hooked up the adapter. I assume that I would have
recalled
if it happened before.
Here's the text:
%-13355YAQKM!CCOMMEOU!IQ!MasesKeu!7MAQKM!SEU!QAGEQSOUECU=OGGAQKM!SEU!QAGEQSO
UEC
All on one line.
David Grossman
-----Original Message-----
Did this only start happening after you hooked up that adapter? If so,
then you got me. What exactly is the gibberish, can it be posted and
retain the character set?
-Clint
----- Original Message -----
From: "David Grossman"
I've been using my new cable for several days now. It works fine except
for
a minor nuisance that may occur the first time after turning on the
computer.
I can't explain it, but sometimes - not always - the first print job has
1-3
lines of gibberish on the top of the page, and nothing else. Remember
that
this happens when I turn on the printer, so there are no print jobs
waiting
(and if there had been print jobs waiting they would have printed out
right
away).
I then purge the printer of any (non-existing) remaining print jobs, and
confirm that the print queue is empty. Subsequent jobs in that computer
session print out fine.
Strange.
I've gotten used to printing out the first job on scrap paper, and then
following the process listed above for subsequent materials.
I don't know why, but I can't help but think that this strange behavior
has
to do with the cable's using a virtual machine to convert serial data to
parallel. It probably starts off with something like a stop bit (do
serial
data transfers have a "start" bit?) and then it doesn't get any further.
Maybe it kind of needs a reminder to "think parallel," after which there
are
no problems.
Each time I turn off the computer, that reminder goes into its
forgettery
(well, what word is the opposite of memory?) and then it has to be
reminded
again. In other words, it works well, but the cable's instruction set
is missing
something.
David Grossman
=========================
The list's FAQ's can be seen by sending an email to
PCWorks-request@xxxxxxxxxxxxx with FAQ in the subject line.
To unsubscribe, subscribe, set Digest or Vacation to on or off, go to
//www.freelists.org/list/pcworks . You can also send an email to
PCWorks-request@xxxxxxxxxxxxx with Unsubscribe in the subject line. Your
member list settings can be found at
//www.freelists.org/cgi-bin/lsg2.cgi/l=pcworks . Once logged in, you have
access to numerous other email options.
The list archives are located at //www.freelists.org/archives/pcworks/ .
All email posted to the list will be placed there in the event anyone needs to
look for previous posts.
-zxdjhu-
Other related posts:
