Printing with BR 4.18 for Linux

Discussion about printing issues and techniques.

Moderators: Susan Smith, admin, Gabriel

Post Reply
Tom Lashley
Posts: 2
Joined: Wed Dec 02, 2009 2:20 pm
Location: Albany GA

Printing with BR 4.18 for Linux

Post by Tom Lashley »

Hello everyone. I am using BR 3.92 on Fedora 10 and the following code works correctly:

10 OPEN #255:"name=PRN:/10",display,output
20 PRINT #255: "abcd"
30 CLOSE #255:
90 STOP

On the same Fedora 10 system, with BR 4.18, when I try to run that code, I get the message : "lpr - The printer or class was not found"

Same substitute statements are in use in the ...config.sys files.

Can anyone clue me in to what is wrong ? Thanks.
1819 Green Valley Ln
Albany GA 31707-3115
229-435-4774
Susan Smith
Posts: 717
Joined: Sun Aug 10, 2008 4:24 am
Location: Southern California

Post by Susan Smith »

Hi Tom,

Welcome to the forum!

Can you post your BRCONFIG.SYS file here, or at least the printer substitution statements? That may give us a little more to go on. I'm not very well versed on Linux, but hopefully someone else will be able to spot the probably for you.

-- Susan
Tom Lashley
Posts: 2
Joined: Wed Dec 02, 2009 2:20 pm
Location: Albany GA

Post by Tom Lashley »

Hi Susan:

The wbconfig.sys and brconfig.sys files both have the following :

SUBSTITUTE PRN:/10,PRN:/Lexmark-E320
1819 Green Valley Ln
Albany GA 31707-3115
229-435-4774
Susan Smith
Posts: 717
Joined: Sun Aug 10, 2008 4:24 am
Location: Southern California

Post by Susan Smith »

Does this still happen if you use OPTION 31 in your BRCONFIG.SYS file?

The only other thing I can think of is whether or not your printer name in the O/S matches the name you are using BR. But if the only thing you changed was your BR version, then that's probably not it.

I wish I knew what the differences were between running BR with Linux and Windows, but I have no experience with Linux. Can somebody else jump in and offer a suggestion? Who is using Linux with BR?


-- Susan
gordon
Posts: 358
Joined: Fri Apr 24, 2009 6:02 pm

Post by gordon »

Based on the error message it is evident that BR is issuing an lpr command.

One way to see exactly what BR is doing is to put into your PATH (ahead of other references) a pointer to the following shell script:

Code: Select all

echo lpr $*
Once you do that you can remove the PATH setting and issue the command yourself to see what is happening.
Post Reply