public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
* blazer still doesn't work
@  Igor Gueths
   ` Gregory Nowak
   ` Luke Davis
  0 siblings, 2 replies; 17+ messages in thread
From: Igor Gueths @  UTC (permalink / raw)
  To: speakup

Hi all. I recently upgraded to 2.4.20, and have since tested printing
functionality. As usual, the ink printer works. Note that I do not receive
the "lp0: compatibility mode" message. However the embosser still doesn't
work. I have made sure more than once that the port configs are set
properly in the blazer's options, and that lpd is started. I have actually
had to emboss something here for a while but couldn't because I can't send
jobs to the blazer from this machine. Does anyone perhaps know anyone else
who has this working on a Linux system? I have really run out of ideas on
what to do, considering that I have a winblows laptop that can emboss to
it successfully just fine using duxbury. But I hate Winblows and want to
avoid using it! Thanks for any help on this, and sorry for the repeated
posts. I have honestly run out of ideas on this one.

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.



^ permalink raw reply	[flat|nested] 17+ messages in thread
* Re: blazer still doesn't work
@  igueths
   ` Adam Myrow
  0 siblings, 1 reply; 17+ messages in thread
From: igueths @  UTC (permalink / raw)
  To: speakup

Hi Greg. If you could do that that would be great! Well in terms of messing up 
the settings for the ink printer, that really isn't possible, since you are not 
modifying any of the print queue settings in /etc/printcap. Throughout all my 
testing I have not modified printcap in any way. And in terms of how I print to 
the ink printer, I use lpr -Pqueue1 filename. Queue1 is the name of my print 
queue. I have an hp400 printer and am using magicfilter as its filter. Note the 
above procedure works just fine. However, when I try lpr filename to the 
embosser, I get put back into a shell prompt. No messages to stdout, absolutely 
nothing. I have made sure everything is owrking hardware wise by even switching 
the cables around on my parallel switch, just to make sure none of the ports on 
that are bad. And it appears that all the parports on the switch appear to be 
working. One thing I did not do is check syslog for any messages related to the 
lpr command issued to the embosser. Perhaps I should check on that? 
> When I get some time, I might try to see if my blazer works with my linux box.
> 
> I am however somewhat reluctant to try that out, since I have my print printer 
> working just fine, and I don't want to go messing things up.
> 
> If I can be assured that my ink printer settings won't get messed up, I'll try 
> the blazer out when I get a chance.
> 
> Greg
> 
> 
> On Tue, Apr 01, 2003 at 09:22:18PM -0500, Igor Gueths wrote:
> > Hi all. I recently upgraded to 2.4.20, and have since tested printing
> > functionality. As usual, the ink printer works. Note that I do not receive
> > the "lp0: compatibility mode" message. However the embosser still doesn't
> > work. I have made sure more than once that the port configs are set
> > properly in the blazer's options, and that lpd is started. I have actually
> > had to emboss something here for a while but couldn't because I can't send
> > jobs to the blazer from this machine. Does anyone perhaps know anyone else
> > who has this working on a Linux system? I have really run out of ideas on
> > what to do, considering that I have a winblows laptop that can emboss to
> > it successfully just fine using duxbury. But I hate Winblows and want to
> > avoid using it! Thanks for any help on this, and sorry for the repeated
> > posts. I have honestly run out of ideas on this one.
> > 
> > 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.
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup


^ permalink raw reply	[flat|nested] 17+ messages in thread
* Re: blazer still doesn't work
@  igueths
  0 siblings, 0 replies; 17+ messages in thread
From: igueths @  UTC (permalink / raw)
  To: speakup

Hi Adam. I did try that when I was using an earlier kernel and that didn't 
work. Meaning I connected the blazer directly to the lp0. I tried 2 different 
cables, and both the cables appeared to be working as they should. I also 
reversed the ink printer, meaning I put it on the port that is used by the 
embosser to make sure the switch wasn't bad, and the ink printer still worked. 
However, I will still try your sugggestion as it may very well work on the 
later kernel. Hmm. I wonder if the blazer expects a crlf pair and that is why 
it prints fine when data is sent to lpt1 in Dos? Because there is actually an 
auto-linefeed option that I may turn on. I believe this might give the Blazer 
the crlf it expects in order to start printing. 
> On Wed, 2 Apr 2003, Igor Gueths wrote:
> 
> > 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?
> 
> Well, how about trying the exact same file sent to /dev/lp0 under Linux
> with the Blazer directly connected to the computer instead of through the
> switch?  As you probably know, Linux/Unix uses just a linefeed for a new
> line whereas DOS/Windows use the CR/LF pair to indicate new lines.  By
> trying the same file, you would be assured that it contains CR/LF pairs
> for new lines.  Here's another thing to keep in mind.  If you don't
> specify a printer with the lpr command, it defaults to whatever the first
> printer is usually.  I'm guessing that you would want some sort of "raw"
> option to create a printcap for an embosser.  That is, you want to tell
> the software to pass the data straight through with no attempt at
> translation or formatting.  In Slackware I use APSfilter.  It lets you
> create an entry like this which I have used on a Samba server so that
> Windows could talk to the printer directly and it works quite well for
> that.  Until you actually get it working with "cat file >/dev/lp0," don't
> even think about lpr.  It's best to start simple and work up from there.
> If it turns out that the file will print if it has CR/LF pairs, look in
> the Blazer's setup menu for an option to turn on auto-linefeeds or
> similar.  Good luck.
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup


^ permalink raw reply	[flat|nested] 17+ messages in thread
* blazer still doesn't work
@  Igor Gueths
   ` Adam Myrow
  0 siblings, 1 reply; 17+ messages in thread
From: Igor Gueths @  UTC (permalink / raw)
  To: speakup

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.



^ permalink raw reply	[flat|nested] 17+ messages in thread

end of thread, other threads:[~ UTC | newest]

Thread overview: 17+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
 blazer still doesn't work Igor Gueths
 ` Gregory Nowak
   ` Ann Parsons
     ` Igor Gueths
 ` Luke Davis
 igueths
 ` Adam Myrow
   ` Igor Gueths
     ` Adam Myrow
 igueths
 Igor Gueths
 ` Adam Myrow
   ` Igor Gueths
     ` Chuck Hallenbeck
       ` Igor Gueths
         ` Ann Parsons
     ` Ann Parsons

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).