Mike FABIAN wrote:
ghugh Song
さんは書きました: [...]
Unfortunately, on my old personal printer HP6mp, I got an error printout like the following:
======================================== The PostScript interpreter in your printer is 2014.108 This printout requres at least version 2015 or greater.
[ ...] =========================================
Isn't it normal? Do I have to throw out my old HP6mp?
I wanted to say "Is it normal?"
It appears that I have to update the firmware of the HP6mp. Of course, I have no idea how to flash the firmware of this printer.
Just setup your HP6mp printer as a non-PostScript printer with YaST2 as already explained in my last mail. Then the Ghostscript will be used as the PostScript interpreter, the old PostScript interpreter in your HP6mp will not be used.
With the newer RPM packages of ghostscript, when the printer is set up as a PCL printer HP6 series PCL from yast2 and CUPSlibrary, HP6MP gave me an endless output of empty blank sheets. Also, I reported already to you that my another printer HP LJ2200 configured by Ghostscript driver `stp': driver `stp' showed a similar symptom after generating a beautiful Hangul web page only once. I think that there is still some misconfigured setup in my ghostscript rpm setting even after SuSEconfig. When I choose Ghostscript from the choice of yast2 printer setup by choosing Postscript Distillery 'sDEVICE=pswrite', which is again different from using ghostscript by choosing a PCL printer, then the printer becomes unresponsive. No blinking at all. This last trouble seems to come from the use of CUPS. I say so because when I used lprng, 'pswrite' seemed to be working.
Mike, As you can imagine, I sorta think that mozilla-1.3b is essential in getting the corrent hangul page from the above experience.
Not true.
You may have all sorts of nice new features with mozilla-1.3b, but just printing the correct hangul already works for a long, long time.
All this experience tells me something. Printer setup appears to be the most basic thing in whatever OSes. Yet, I have had all sorts of trouble. That was the prime reason I switched to SuSE from RedHat about four years ago around the SuSE verseion 6.3. Now when I upgraded to SuSE-8.1 coming with CUPS by default, I almost thought of going back to RedHat. I sorted out all those trouble with CUPS by using those rpms in /pub/projects/. I would not understand SuSE if those rpms are still sitting only in /pub/projects rather than in /suse/update/8.1. Best regards, G. Hugh Song