Mike Chaney's Tech Corner
March 29, 2024, 09:02:58 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Qimage registration expired? New lifetime licenses are only $59.99!
 
   Home   Help Search Login Register  

Professional Photo Printing Software for Windows
Print with
Qimage and see what you've been missing!
Pages: 1 [2]
  Print  
Author Topic: Page Background set as black but prints faded gray  (Read 8025 times)
admin
Administrator
Forum Superhero
*****
Posts: 4109



View Profile Email
« Reply #15 on: April 19, 2019, 12:36:04 PM »

Thank you very much for your explanation Mike.

You guess that it is my printerdriver causing the problem.
If that is the case then please explain why it has worked perfectly for 7 years.
Its the same printer, the same driver (there is no other driver) that previously worked just fine.

This is the reason why it is so hard for me to accept that its the driver/printer.


You stole MY question.  Wink  The code that prints the page background hasn't changed in years and the changing variable here is the rebuilt PC.  We know QU is sending 0,0,0 to the driver because your print-to-tiff gave you true black.  When QU prints to file, it runs the exact same code as that which sends the data to the printer: it just reroutes the data to a file.  It's more likely that the driver isn't "happy" with something regarding your new PC build.

Mike
Logged
Gurrung
Newbie
*
Posts: 10


View Profile Email
« Reply #16 on: April 22, 2019, 09:47:39 AM »

I create 8 new templates the way Mike suggests.
Its printing slower than before, but it works.
I created the templates in version 2019.117p.
I saw the upgrade to 118, and installed it.
 The result was a 'division by zero' error when opening my new template.
I uninstalled completely and removed all remains of previous installation, and installed again.
 Same error.
Then I noticed and installed 119, and received the same error.

I am now back on 117, and everything works fine again.

What was happening here?

Logged
admin
Administrator
Forum Superhero
*****
Posts: 4109



View Profile Email
« Reply #17 on: April 22, 2019, 01:11:59 PM »

The code in 117, 118, and 119 is identical for you since you are running a Xerox printer and the code changes in 117, 118, and 119 only get executed if you are running a Canon or Epson printer.

Because the same code is running in 117 and 119 but you are getting different results and the only difference is the memory address at which that code runs, I think we are down to two possibilities:

(1) The printer driver is loading at a slightly different address and not working properly.  Try using the PCL driver for your Xerox printer instead of the PS driver.  Windows uses PCL and at some point that PS data is going to have to be converted to PCL anyway.  I've seen some strange results when printing to Postscript drivers in Windows from other drivers so using the non-PS (PCL) driver instead may correct the problems you are seeing.  Postscript is an Adobe creation meant mostly for PDF's and vector graphics and sometimes doesn't mesh well with Windows and the raster graphics needed for photo printing.

(2) Your anti-virus software may be inferfering with normal operation.  Try temporarily disabling it to see if it fixes the problem.

Regards,
Mike
Logged
Gurrung
Newbie
*
Posts: 10


View Profile Email
« Reply #18 on: April 24, 2019, 09:49:04 AM »

WOW, what a journey.
I removed my printer driver and QU.
Cleaned the registry from everything I could find on both.
Then installed QU 2019.119.
It worked, even with my new templates, although when printing to file it created a black file and a second file with a black vertical strip.
But...it did not crash.
Then i searched for the latest driver at xerox support site.
I found out I already had the latest (I did not trust).
After a long search I found out that Xerox merged with Fuji, so I searched on their site.
I found an older, Generic 64 bit PS driver, and thought what the heck it cannot get any worse.
Installed it with my fingers crossed.

Everything is working perfect now. (it cost me this entire afternoon, but it was worth it)

Thank you for sticking with this stubborn fellow.
I appreciate the time and effort you spent on me. Much kudos.
Logged
Pages: 1 [2]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!
Security updates 2022 by ddisoftware, Inc.