KCLUG

kclug@kclug.org

3 participants
3240 discussions

Re: Cups - lpoptions - I Dunno?!?!
by RtX 22 Dec '06

22 Dec '06

Sometimes it seems that you have all the bases covered in your post but under stress you leave things out. Sorry. System here is Xubuntu 6.06 LTS (Debian). CUPS V-1.2.2. Okidata ML 320 Turbo. I found a post on the net where someone had the same issue. Upgrading from on old SCO box to Linux. They said this: <-- snip --> Since CUPS supports modern formats and languages, the sample drivers have to run your printers in graphics mode, which is significantly slower than the text mode used by the old SCO (System V) print spooler. The simplest fix is to use the interface scripts from your old server with CUPS: lpadmin -p printername -i scriptname.sh <-- snip --> I don't have access to the old system as it has sunk to "not working" yesterday. I gotta get this printer to print in text mode (high speed). Anything else you need, just ask. On 12/20/06, Kelsay, Brian - Kansas City, MO <brian.kelsay(a)kcc.usda.gov> wrote: > http://linuxmafia.com/faq/Essays/smart-questions.html > http://plone.org/documentation/how-to/ask-for-help > > You are doing pretty good, BUT you might like to tell us what distro of > Linux you installed, what version of CUPS, what config tools for CUPS, > if any, are installed. This is important for a few reasons, like what > updating tools might be used to install additional software, where apps > live (path to), etc. You did a really good job of describing the > problem, but you need to add those details so the solution can be > tailored to you. > > I might look at linuxprinting.org for config info on your printer. I > have not actually set up more than just an old laser printer under linux > and it may not have been using CUPS, but I got some good info there. > > > >-----Original Message----- > >From: On Behalf Of RtX > >Sent: Tuesday, December 19, 2006 5:10 PM > >To: KC Linux Users Group > >Subject: Cups - lpoptions - I Dunno?!?! > > > >So, I'm finishing up my conversion from SCO UNIX 3.2 / > >Keypoint to Linux. Got the data off the old server and onto > >the new server. Had the VAR setup Keypoint software and > >everything is working on that end. > >I still have a few hiccups that I'm working on and could use some help. > > > >1.) The Keypoint software requires WYSE 60 emulation to work properly. > >We are using SecureCRT for Windows workstation clients and all > >works well however, the ANSI characters are not the same as > >they were in the old serial terminals they were using. Dashes > >or hyphens that are used in the program for simple menus are > >now O's and the like. Is there a way (or setting) to get the > >proper characters back? > > > >2.) The biggest problem! They print from Keypoint using an > >Okidata ML320 9-pin printer which is connected to the server > >directly through lp0. The software prints everything fine but > >the printer prints in LQ mode instead of Draft mode. I need > >this printer to print in Draft mode for speed reasons. All > >settings on the front panel of the printer are overridden by > >cups (or lp?) at print time so simply selecting "Draft" > >from the printer's front panel does not work. > > > >On the old system, the printer would print everything in Draft > >mode and all was good. They have one certain page that they > >print that they would select a CPI of 17 (instead of 10) to > >get everything on the page. This no longer works. If I select > >a CPI of 17 on the front panel, then try to print this page, > >the CPI is changed back to 10 by the server. > > > >If I add "raw=true" in /etc/cups/lpoptions, the printer will > >print in Draft mode but does not handle page length properly. > >It feels like I need to add a "Draft" option to lpoptions but > >I have not found any reference to setting print quality in > >lpoptions on the net so I'm stuck. > > > >Comments? Please help and thanks a bunch! > > > >-- > >RtX... > > > >Ty Unes - Overland Park, Ks. > >riverty(a)gmail.com > -- RtX... Ty Unes - Overland Park, Ks. riverty(a)gmail.com

3 4

Re: [DISCUSS] 10 Good Unix command line habits
by Ed Allen 21 Dec '06

21 Dec '06

> ----- Forwarded message from Luke-Jr <luke(a)dashjr.org> ----- > Notes: > In "Quote variables with caution", it says to use square brackets, and then > goes on to give a correct example with curly braces. > "Stop piping cats" only refers to piping to grep, but in reality there's > almost never a good reason to pipe a single-file cat. The < operator provides > a file on standard input. So "cat foo | wc -l" can become "wc -l < foo" > An easy to see case where 'cat' is truly the easiest way... (cat /tmp/header; date; uptime;cat - /tmp/signature) | \ mail -s 'A case where cat is needed' kclug(a)kclug.org The ( ) pair spawns s sub-shell which allows multiple commands to share the same input, output, and error streams. In this case I used 'date' and 'uptime' along with a second 'cat'. The second 'cat' reads from stdin (standard in) till it sees EOF (End Of File <Control-D>) and then follows that with the /tmp/signature file. Stdout of all those commands is sent to stdin of the 'mail' command.

1 0

Cups - lpoptions - I Dunno?!?!
by RtX 20 Dec '06

20 Dec '06

So, I'm finishing up my conversion from SCO UNIX 3.2 / Keypoint to Linux. Got the data off the old server and onto the new server. Had the VAR setup Keypoint software and everything is working on that end. I still have a few hiccups that I'm working on and could use some help. 1.) The Keypoint software requires WYSE 60 emulation to work properly. We are using SecureCRT for Windows workstation clients and all works well however, the ANSI characters are not the same as they were in the old serial terminals they were using. Dashes or hyphens that are used in the program for simple menus are now O's and the like. Is there a way (or setting) to get the proper characters back? 2.) The biggest problem! They print from Keypoint using an Okidata ML320 9-pin printer which is connected to the server directly through lp0. The software prints everything fine but the printer prints in LQ mode instead of Draft mode. I need this printer to print in Draft mode for speed reasons. All settings on the front panel of the printer are overridden by cups (or lp?) at print time so simply selecting "Draft" from the printer's front panel does not work. On the old system, the printer would print everything in Draft mode and all was good. They have one certain page that they print that they would select a CPI of 17 (instead of 10) to get everything on the page. This no longer works. If I select a CPI of 17 on the front panel, then try to print this page, the CPI is changed back to 10 by the server. If I add "raw=true" in /etc/cups/lpoptions, the printer will print in Draft mode but does not handle page length properly. It feels like I need to add a "Draft" option to lpoptions but I have not found any reference to setting print quality in lpoptions on the net so I'm stuck. Comments? Please help and thanks a bunch! -- RtX... Ty Unes - Overland Park, Ks. riverty(a)gmail.com

2 1

Fwd: [DISCUSS] 10 Good Unix command line habits
by Don Ellis 18 Dec '06

18 Dec '06

KC Guys - I thought you might like to see this item. --Don Ellis ---------- Forwarded message ---------- From: Ed Howland <ed.howland(a)gmail.com> Date: Dec 16, 2006 2:09 PM Subject: [DISCUSS] 10 Good Unix command line habits To: discuss(a)sluug.org, Central West End Linux Users Group < cwe-lug(a)lists.firepipe.net> A good article from IBM developerWorks. http://tinyurl.com/vof3r Or the full thing: http://www-128.ibm.com/developerworks/aix/library/au-badunixhabits.html?ca=… Now some of the examples don't work (mkdir with parenthesized dirs) on Debian-like systems. But you might find a few gems there. I did. Ed -- Ed Howland http://greenprogrammer.blogspot.com ------- St. Louis Unix Users Group - http://www.sluug.org/ To unsubscribe from the SLUUG discussion mailing list, send a message to discuss-request(a)sluug.org with the word 'unsubscribe' as the body

3 3

Fwd: Fwd: Fwd: [DISCUSS] 10 Good Unix command line habits
by Don Ellis 18 Dec '06

18 Dec '06

A response from a St. Louis colleague: ---------- Forwarded message ---------- From: Robert Citek <robert.citek(a)gmail.com> Date: Dec 17, 2006 7:42 PM Subject: Re: Fwd: Fwd: [DISCUSS] 10 Good Unix command line habits To: discuss(a)sluug.org Also, in "Use escape sequences to manage long input", there's no need to put a backslash after a pipe (|), logical or (||), or logical and (&&). So, this: ~ $ cd tmp/a/b/c || \ > mkdir -p tmp/a/b/c && \ > tar xvf -C tmp/a/b/c ~/archive.tar can be re-written as this: ~ $ cd tmp/a/b/c || > mkdir -p tmp/a/b/c && > tar xvf -C tmp/a/b/c ~/archive.tar Happy Holidays to all. Regards, - Robert Don Ellis wrote: > Ed and Group, > > Here's a note from one of our KC colleagues (to whom I forwarded this) > pointing out an error on the page (which I noticed but didn't share). > > --Don Ellis > > > ---------- Forwarded message ---------- > From: *Luke-Jr* <luke(a)dashjr.org <mailto:luke@dashjr.org>> > Date: Dec 17, 2006 12:54 AM > Subject: Re: Fwd: [DISCUSS] 10 Good Unix command line habits > To: kclug(a)kclug.org <mailto:kclug@kclug.org> > > Notes: > In "Quote variables with caution", it says to use square brackets, and then > goes on to give a correct example with curly braces. > "Stop piping cats" only refers to piping to grep, but in reality there's > almost never a good reason to pipe a single-file cat. The < operator > provides > a file on standard input. So "cat foo | wc -l" can become "wc -l < foo" ------- St. Louis Unix Users Group - http://www.sluug.org/ To unsubscribe from the SLUUG discussion mailing list, send a message to discuss-request(a)sluug.org with the word 'unsubscribe' as the body

1 0

minix 3 released under BSD-like license
by David Nicol 17 Dec '06

17 Dec '06

http://www.minix3.org/ maybe this development will spur an open device driver standard, or adoption of wrappers for the unified BSD driver standard into other frameworks -- He thought he could organize freedom how naive and controlling of him

4 3

Dan's Guardian
by Dale Beams 15 Dec '06

15 Dec '06

Does anybody know an alternative to Dan's Guaurdian? His license details are muddy. _________________________________________________________________ Stay up-to-date with your friends through the Windows Live Spaces friends list. http://clk.atdmt.com/MSN/go/msnnkwsp0070000001msn/direct/01/?href=http://sp…

4 6

TiVoToGo On Your Mac
by Jonathan Hutchins 13 Dec '06

13 Dec '06

Decrypting .tivo files: http://www.zatznotfunny.com/2006-12/tivotogo-on-your-mac/

1 0

Linux / Sco Stuff.
by RtX 13 Dec '06

13 Dec '06

I have a client that has a very old 486 server running SCO UNIX 3.2. My job is to get the data off of this machine and get it on to a Linux machine. The problem here is that the 486 is ISA bus only. It does not have an IDE bus, main system HDD is SCSI (328MB). No network option, tape backup drive does not work either. I want to add a second SCSI disk to the system formatted in DOS FAT16, copy the data over to this drive, and then copy the data back on to the new Linux server. I am having no joy getting this SCO 3.2 system to mount the drive. I don't know how. I mean I know how to mount drives in Linux and AIX but I fail to get this done in SCO. Could anyone please advise me on the steps needed to get this drive mounted in SCO? -- RtX... Ty Unes - Overland Park, Ks. riverty(a)gmail.com

5 4

RE: Linux / Sco Stuff.
by Kelsay, Brian - Kansas City, MO 11 Dec '06

11 Dec '06

Well good luck in the fight to remove old hardware and more specifically SCO. Yet more reason that SCO blows goats and why you can't get too far behind the times w/ a proprietary OS. I bet if you contacted SCO, they'd sell you some pkg to give full DOS support, a tool to format a drive to work in SCO, or even network support. The key is they'd sell you something to get your data back off their incompatible old piece of crap OS. Good luck with Debian and may your nightmares be few. Many server apps I'm seeing lately have support for at least RedHat, so there is hope. >-----Original Message----- >From: On Behalf Of RtX >Sent: Sunday, December 10, 2006 11:43 AM > >Job is done. Success! Yes, SCO UNIX has not kicked my ass yet, >even on an old 486! > >Before I tell how I want to thank everyone for their help and support. >You all are great! > >I located a working 50-pin SCSI 1.2 GB tape drive with tape, >and simply made a tar backup with this drive, added the drive >and SCSI card to the new server and untarred from backup. >Works like buttuh! I did not have this drive before and didn't >know I would have it when I started the thread. I was hoping >to get the same thing done >(basically) by using a SCSI HDD. Still no joy on that front. I >found out that SCO 3.2 does not have full DOS file system >support (only for >floppies) and this is why I had so much trouble with the HDD. > >BTW - The software in question here is "Keypoint" software. >It's mainly for the trucking industry but maybe more. They are >still pushing SCO UNIX for their products. I asked about a >Linux port for my clients as I wanted to get them off of SCO >and on to something a little more flexible. They have made it >work on Linux before. >Specifically RedHat Enterprise Server. I'm doing it in Debian. >Wish me luck... > >RtX... > >Ty Unes - Overland Park, Ks.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

KCLUG