UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Ubuntu Linux 16.04, Debian 10, LineageOS 14.1
Posts: 1,572
Rep:
My first suggestion is what I wrote in post #43. If that fails, my second suggestion is to try the same command but replace the ppd file with the generic Epson 24-pin Dot-Matrix ppd, which apparently is a part of cups.
PS, might be an idea too to install foomatic-db for the second suggestion. To do that:
Code:
sudo apt-get install foomatic-db
Last random thoughts:
If you still find it won't set up on the the parallel port, then try modprobe parport, modprobe parport_pc, and modprobe lp. If that still fails, then try installing wine and using the Windows exe-file that you've got. If that fails, just buy a new printer.
Last edited by mark_alfred; 02-22-2015 at 04:30 PM.
Mark, I will give it a try and see what happens. I can't exactly say when but soon as I can. If I get feeling better later I will try then. I will post if anything goes right or maybe even wrong if it isn't to long a deal. Thank you, Jim
Mark, this is what is happening with the parallel command, Jim
james@james-System-Product-Name:~$ sudo /usr/lpadmin -p Epson570 -E -v parallel:/dev/lp1 -m Epson-LQ-570plus-epson.ppd
[sudo] password for james:
sudo: /usr/lpadmin: command not found
james@james-System-Product-Name:~$
Distribution: Ubuntu Linux 16.04, Debian 10, LineageOS 14.1
Posts: 1,572
Rep:
Yes, you're typing it wrong. It is "sudo /usr/sbin/lpadmin" NOT "sudo /usr/lpadmin" as you typed. Might I suggest again that you copy and paste the commands?
widget, CPM and the very early days of the Dos both used commands to do most anything on a computer. Right off hand i can't remember all that much about it (CPM) but it was a sysyem that would run on most any machine. Even the Commodore C-128's would run CPM that allowed the C-128 to run certain Dos based programs. I would have to do a lot of digging to try to locate my stuff on that now days but you have to remember that computer drives were all floppy drives and the business machines used both tapes as well as drives in the neighborhood of about 8" floppy disks. When Commodore's were the hot machine,, I paid $850.00 for a L.T. Kernal 20 Meg hard drive which was supposed to work with the C-128 but basically ended up being a paper wait as few programs would run on it. Possibly you might still find the Group that had been called "F.O.G" as they were very big concerning the very old operating systems way back. I would give you more but my memory is not all that great. Plus today it doesn't matter very much. Thanks, Jim
Mark, I couldn't get the command straight on your #43 post. I had tried to write it down as it is clippend short in the box without scrolling. I also did not know I could copy and paste it into the Terminal either. I just learned that now. I also "just learned" that the tools menu at the top of the page has a printer friendly deal which makes it possible to see the command line as you posted it! So, I am learning a few of the ropes as I go along. I also have to learn more about pointing from one directory to another so I can copy files from one to the other as well. As I said to you before I am not the brightest bulb in the string and Linux is different than what I have been doing for years now. So, it is confusing for me and I have to get the hang of it. I have to be "doing things" to learn as reading and trying are not so easy for me to grasp. Also doing it the way that I have to also is mistake riddled as well. I will get there though by hook or crook. Thank you, Jim
While I am being guilty of an off topic hijack of this thread I may as well ask this: What the devil is this CPM you mentioned?
CP/M, to use its proper spelling, was the absolute original operating system for microprocessors, written by Gary Kildall when he was a consultant for Intel. Its full name was 'Control Program/Microprocessor' and it ran on an 8-bit system, with the 8080 CPU. In the 1970/80 period, it became the standard for all microprocessor systems.
When the 16-bit CPU known as the 8086 appeared, a small company named Seattle Computer Products created a board to run it, and an SCP employee created a quite deliberate clone of CP/M to control it. The reason for cloning CP/M was to simplify conversion of existing software over to the new system. One William Gates, needing a 16-bit system in a hurry to show to IBM in 1981, bought a copy and later negoatiated rights to it, renaming it MS-DOS 1.1.
I've used both CP/M and ZDOS 1.25 (Heath-Zenith's name for their version of the SCP system; Gates bought SCP's version 1.24) back in the 90s. Today's systems are much more complex, but you can find traces of CP/M way down under their bells and whistles!
The two files I had placed which were Windows NT4.0 will not install via LocalHost as it says they are Windows files.
A very important point that perhaps nobody has yet mentioned to you (since we all tend to take it for granted) is that unlike Windows or CP/M, Linux is totally case-sensitive. If you're re-typing the suggested commands, you have to be extremely careful about this. When we suggest you go to http://localhost:631 to get into the CUPS control pages, adding the capitalization to make it LocalHost is an absolute guarantee you'll get an error message!
FYI, "localhost" is a convention that always translates to an IP address of the machine in use, which is normally 127.0.0.1 (the "loopback" address, used by many system packages for internal communication).
Earlier, you asked about "$HOME" so I'll try to explain it also. In a Windows batch file, this would have been %home, to return the content of a local variable named "home" and similarly in Linux, the $ prefix to a variable name causes return of the variable's content. It's a convention to put names of global variables in all-uppercase, with those of local variables in lowercase or "TitleCase" form. You can see all current variables, both global and local, with the command "env" at a command-line prompt. The globals are all created when you log in, and persist until you log out. The locals are created for only the duration of a script and vanish at its end.
Hope this helps! And FWIW, I too am a cardiac patient -- CHF, but it's been in remission for more than a decade now. Good luck overcoming the problems!
Mark, I couldn't get the command straight on your #43 post. I had tried to write it down as it is clippend short in the box without scrolling.
Highlight any word in the "code" box, then triple-left-click and you'll get the entire line highlighted for copying. Then right-click, and you can copy without moving the pointer.
I just verified this, after discovering that using Ctrl-A as I normally would doesn't work properly in these forums! The triple-click, though, will be quite useful.
Yes, that's what I like about Linux. There are plenty of opportunities to learn, and most people in the forums are quite helpful.
Well Mike, I can say that holds very true both on this forum as well as the Ubuntu forum and, others as well. You certainly have been a great help to me as have others. And, I deeply Appreciate it!! I am a very slow learner at best and I dislike being in that position. However it has been a problem that has dogged me all my life no matter how I approach things. I do not know how to express all of this in better words but, also, my hope is that through the things I have been going through as well as all the help you and other folks have given here would also help some other folks glean something from it as well.
Thank you, Jim
A very important point that perhaps nobody has yet mentioned to you (since we all tend to take it for granted) is that unlike Windows or CP/M, Linux is totally case-sensitive.
Quote:
If you're re-typing the suggested commands, you have to be extremely careful about this. When we suggest you go to http://localhost:631 to get into the CUPS control pages, adding the capitalization to make it LocalHost is an absolute guarantee you'll get an error message!
FYI, "localhost" is a convention that always translates to an IP address of the machine in use, which is normally 127.0.0.1 (the "loopback" address, used by many system packages for internal communication).
Earlier, you asked about "$HOME" so I'll try to explain it also. In a Windows batch file, this would have been %home, to return the content of a local variable named "home" and similarly in Linux, the $ prefix to a variable name causes return of the variable's content. It's a convention to put names of global variables in all-uppercase, with those of local variables in lowercase or "TitleCase" form. You can see all current variables, both global and local, with the command "env" at a command-line prompt. The globals are all created when you log in, and persist until you log out. The locals are created for only the duration of a script and vanish at its end.
Hope this helps! And FWIW, I too am a cardiac patient -- CHF, but it's been in remission for more than a decade now. Good luck overcoming the problems!
JimKyle, You are on target concerning the upper and lower case thing. What has been a real struggle for me personally is actually trying to figure out certain letter forms that seem to be common on the forums. Letters like the i,j, and l for me have to be carefully looked at to be able to actually figure out what letter they actually are in the first place. It has been only the last few days now, I know what I am looking at concerning what letter they in fact really are. It has taken me awhile studdying them out to be able to discern them. My eye sight is about as good or worse than my spelling!
I also couldn't remember that CP/M was written down like this as it has been "years" ago that I fiddled with that as well as DOS. I still have my old Commodore 128 and it is still set up but haven't fired it up in over ten years or better now.
Also glad to hear that you are doing well with the heart situation. I on the other hand, I am stuck with being married to my doctors. They tell me that I am fortunate to still be complaining and kicking. I also am thankfull to be still around but, I have a fair number of side effects which I am seemingly stuck with as well and have made life a larger challange. Even so, I keep "trying" to do everything I possibly can manage too do. I am a mechanic by trade and still work at that as well as other things too within limits.
Thank you for sharing your in put, Jim
widget, It's a good thing JimKyle buzzed in with more info as I had forgotten many of the terms. Fact is that now days I wouldn't be any further a long if I were to have to use those systems now than I am at the moment with Linux. Jim
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.