blazer still doesn't work

[Igor Gueths]

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 at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>