From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: blazer still doesn't work
Date: Thu, 3 Apr 2003 14:38:37 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0304031432370.1135-100000@igueths> (raw)
Hi all. Well I have the blazer connected directly to lp0, and when I do
cat filename.brf >/dev/lp0 it still doesn't work. I turned on the linefeed
option, and there was no effect. I wonder if I am missing something in my
kernel which I should have? If only I knew what the winblows machine was
sending that thing with the type command that is not being sent here, I
could work from there. Can anyone think of anything else I should try to
get this working? Thanks!
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.
next reply other threads:[~ UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths [this message]
` Adam Myrow
` Igor Gueths
` Chuck Hallenbeck
` Igor Gueths
` Ann Parsons
` Ann Parsons
-- strict thread matches above, loose matches on Subject: below --
igueths
igueths
` Adam Myrow
` Igor Gueths
` Adam Myrow
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.0304031432370.1135-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).