From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: Re: blazer still doesn't work
Date: Thu, 3 Apr 2003 17:44:09 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0304031743020.2419-100000@igueths> (raw)
In-Reply-To: <Pine.LNX.4.53.0304031613100.2336@homerun.midsouth.rr.com>
Its just the laptop that has win on it. And when I try catting the file on
Linux, I return to a prompt and the blazer just sits there as if nothing
had happened. And that is what I have in my kernel i.e., parport and
printer support. The ink printer appears to be working, but I don't know
why the blazer is not? Greg, didn't you say you had a blazer? Have you had
any luck?
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 Thu, 3 Apr 2003, Adam Myrow wrote:
> When you try to cat a file to /dev/lp0, does the prompt return, or does it
> sit there until you hit control-C? Why the Blazer works in DOS/Windows
> and not Linux is a complete mystery. As for the kernel, I would think
> that parallel port support and printing support would be all that is
> required. I usually add EEE1284 status support, but I don't think that's
> strictly necessary. Is the computer you have the Blazer on dual boot? Or
> does it just have Linux? From what you've posted, I get the idea that
> it's just the laptop that has Windows on it.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths
` Adam Myrow
` Igor Gueths [this message]
` 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.0304031743020.2419-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).