HP LaserJet 1320 printing black boxes instead of text
Solution 1
The issue here was complicated slightly by the fact that the printer is also used via Terminal Services. It seems that the LaserJet 1320 will not work via Terminal Services when using the x64 driver, but the P2015 will.
My sad recomendation - update your printer.
Solution 2
Does anybody know why this is happening?
No but you can also download from HP either the PCL6 64-bit Universal Driver or the Postscript 64-bit Universal Driver and try each of those. In my experience (I also have a 1320 and Win-7 64-bit), each of these drivers have different bugs.
The versions of Word etc can also make a difference. I have two identical Win-7 PCs bought at the same time, one PC with Word 2010 starter had fewer print problems than the other PC with Word 2007. The PCL6 64-bit Universal Driver seemed to work best.
It's worth noting that the HP1320 printer worked flawlessly with Windows XP 32-bit using many combinations of applications and many combinations of MS/HP × PCL5/PCL6/PS drivers. I don't think the faults lie in the printer itself.
Update: Printer configuration
Related videos on Youtube
daniel7558
Updated on September 18, 2022Comments
-
daniel7558 almost 2 years
For other software I need fftw-2.1.5 with
--enable-mpi --enable-type-prefix --enable-float
installed. It should be compiled withpgcc
PGCC, etc. are installed under the
/home
directory. For this post I have shortend it withpath-to
.I do:
./configure --prefix=/path-to/fftw --enable-mpi --enable-type-prefix --enable-float CC=path-to/pgcc CXX=path-to/pgc++ F77=path-to/pgf77 FC=path-to/pgfortran make`
./configure
finishes successful, duringmake
I get this error message:/usr/bin/ld: ../fftw/.libs/libsfftw.a(malloc.o): relocation R_X86_64_32 against .rodata' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: ../fftw/.libs/libsfftw.a(putils.o): relocation R_X86_64_32 against .rodata' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: ../fftw/.libs/libsfftw.a(twiddle.o): relocation R_X86_64_32 against .data' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Nonrepresentable section on output collect2: error: ld returned 1 exit status
I tried to recompile with the
-fPIC
flag:make clean make CFLAGS="-fPIC"
Then I get:
../fftw/.libs/libsfftw.a(twiddle.o): In function `fftw_compute_twiddle': /home/daniel/fftw-test/fftw-2.1.5/fftw/./twiddle.c:92: undefined reference to `__fd_sincos_1' /home/daniel/fftw-test/fftw-2.1.5/fftw/./twiddle.c:126: undefined reference to `__fd_sincos_1' ../fftw/.libs/libsfftw.a(twiddle.o): In function `fftw_compute_rader_twiddle': /home/daniel/fftw-test/fftw-2.1.5/fftw/./twiddle.c:65: undefined reference to `__fd_sincos_1' collect2: error: ld returned 1 exit status
I've now tried to find a solution to why this happens for hours but I cannot figure it out.
When I configure it to use the gcc compiler (system default) everything works perfectly:
./configure --prefix=/fftw --enable-mpi --enable-type-prefix --enable-float make make install
EDIT, more information:
The program for which I need fftw, needs pgcc. I though it would be best if I compile everything with it as it was recommended on some forum sites.
In twiddle.c there is not a single mention of
__fd_sincos_1
. For example line 92 is simplyfor (i = 0; i < n; ++i) {
When I drop the
--enable-type-prefix
nothing changes. Still the same error.
-
David Gard over 11 yearsThe printer was previously used on Windows 2000 and it worked just fine, so it is definatly related to Win 7 64-bit. As far as I can tell through the HP website though, the Universal PCL6 and Postscript drivers are not available for the 1320. I know the definition of 'Universal' means they should be, but I also know what should be true often isn't in IT!!
-
user5249203 over 11 years@David: I've installed all three drivers concurrently on Windows-7 64-bit and used them for a HP Laserjet 1320dtn.
-
David Gard over 11 yearsI've now added the PCL6 x64 drivers, but when ever Windows automatically installs the printer it still goes for the PCL5 drivers. I've tried installing the printer manually using the PLC6 drivers (and Postscript), but they do not work at all - when I try to print a test page, it doesn't even make it to the queue. Any other tips at all?
-
user5249203 over 11 yearsI've updated my answer with screenshots of my printer settings. My 1320 is network attached (built-in JetDirect functionality), if yours is directly attached via USB then obviously settings will be different. I used manual configuration and typed in the IP-address manually (if I remember correctly)
-
David Gard over 11 yearsMany thanks. It is indeed attached via USB, but I'm certain the screen shots will help. Will have a look just as soon as I can.
-
David Gard over 11 yearsWell I've had time to try this out, and switching to the PCL6 drivers has worked for the local machine, but for a couple of applications we use Terminal Services, and now the TS won't print at all (PCL XL error - Subsysstem: KERNEL - Error: UnsupportedProtocol). The drivers are installed on the Terminal Server (Server 2003, 32-bit).
-
user5249203 over 11 yearsIn a corporate context, I think I'd be considering two courses of action. a) get support from HP if possible (perhaps via printer vendor/distributor) or b) cease internal IT support for 1320s and replace with a fully tested alternative. It's a shame as the device itself is fine - it just seems to be a problem with HP drivers.
-
David Gard over 11 yearsI'd love to cease support for the 1320's - we mainly have M401's, and they work a treat, but sadly all the boss sees is pound signs! I'll keep trying, and if I do find a work around, I'll post as an answer. Thanks for all your help.
-
David Gard over 11 yearsJust FYI, I replaced the 1320 with a spare 2015 (well, I stole it when someone wasn't looking, but that counts...), and it had exactly the same problem with the PCL5 drivers, but worked fine with the PCL6.