public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: Re: blazer still doesn't work
Date: Wed, 2 Apr 2003 19:14:39 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0304021913240.27155-100000@igueths> (raw)
In-Reply-To: <Pine.LNX.4.53.0304021714450.1092@homerun.midsouth.rr.com>

Hi Adam. Apparently your test worked, I just hadn't thought of trying
that. And now the question is why does it not work on Linux? I checked
syslog like I said I was going to in a previous post, however there were
no relevant entries. I wonder if the blazer rqeuires a cr/lf before it can
print anything?

May you code in the power of the source,
may the kernel, libraries, and utilities be with you,
throughout all distributions until the end of the epoch.

On Wed, 2 Apr 2003, Adam Myrow wrote:

> You might also want to use lpq to list the jobs and lprm to clean them
> out.  When you invoke lpr, it will usually hold a job in its queue forever
> until either a printer is ready for it or you remove it.  If you suddenly
> get the Blazer working and don't clean up the queue, you will likely have
> tons of jobs go through at once.  Here's another test to try.  Connect the
> Blazer to a Windows machine and go into a DOS prompt (or command prompt
> depending on the version of Windows.)  Then do something like "type
> file.brl > lpt1" and see if anything happens.  This is the DOS/Windows
> equivalent of "cat file.brl >/dev/lp0."  You would, of course, replace
> "file.brl" with a filename of an actual file you wanted to send to the
> embosser.  If this test fails, then it is likely that Duxbery is sending
> some magic sequence to wake up the embosser, and you would need to find
> out what that magic sequence is or somehow find a way around that.  I wish
> I could be of more help, but I am at a loss for other ideas.  I just
> realized that if you are using Windows NT, 2000, or XP, you might need
> administrative rights for the above test.  Of course, a true DOS machine
> would work, but they are getting kind of rare.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>



  reply	other threads:[~ UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 igueths
 ` Adam Myrow
   ` Igor Gueths [this message]
     ` Adam Myrow
  -- strict thread matches above, loose matches on Subject: below --
 Igor Gueths
 ` Adam Myrow
   ` Igor Gueths
     ` Chuck Hallenbeck
       ` Igor Gueths
         ` Ann Parsons
     ` Ann Parsons
 igueths
 Igor Gueths
 ` Gregory Nowak
   ` Ann Parsons
     ` Igor Gueths
 ` Luke Davis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.44.0304021913240.27155-100000@igueths \
    --to=igueths@attbi.com \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).