S
SunDisplay
Guest
We are getting this error intermittently for a custom print driver. The customer upgraded from windows 7 to 10. The issue is intermittent with some documents and workstations. Driver is installed on windows 2012 R2 server and the driver is shared among workstations. Could it be a usergroup policy issue. IT says that its only for production workstations. They made a clone of this workstation and printing has no problem!. I don't know the difference between a workstation and a clone of the workstation. This is a Type 3 print driver
We have an application written by a developer more than 7years back. The application has a print driver, print port, broker, print publisher, client. I am able to compile all the parts of the application and connect each one to talk to another except print driver. This print driver is written in c++. I don't know how to compile and troubleshoot this legacy black box driver code. I am afraid because of the legacy nature of the driver, it might have to be debugged and rebuilt. But any suggestions on where to start to rebuild/debug/troubleshoot this print driver. These are the files available in the print driver folder in source control. The output of this print driver is PCL. Please suggest. I have never done windows driver development. My experience with c++ is minimal.
1) How I do build this to be able to generate a print driver, .ini file. This is legacy code and still being used. Its upto me now to figure out how to actually make this code generate an output.
2) All I know is the output of this black box code is a PCl which is then later on in the application converted to a TIFF. This TiFF is written to the drive
3) We have a customer who TIFF is not being written. I intercepted the input to the applicatoin and tried to see if the PCL is being received. It looks like the PCL file only the header is generated and there is no other data. Now I am leaning towards PCL not being generated by the print driver because of some font issues or registry
4) Happens on some documents after a windows 7 to 10 upgrade. How do I troubleshoot this print driver. Please suggest. What am I looking for in a process monitor log.
5) Could this be the problem see the good procmon and bad
Good
Bad: SetAllocationInformationFile is missing in the bad file proc mon
I appreciate reading this post
sunDisplay
Continue reading...
We have an application written by a developer more than 7years back. The application has a print driver, print port, broker, print publisher, client. I am able to compile all the parts of the application and connect each one to talk to another except print driver. This print driver is written in c++. I don't know how to compile and troubleshoot this legacy black box driver code. I am afraid because of the legacy nature of the driver, it might have to be debugged and rebuilt. But any suggestions on where to start to rebuild/debug/troubleshoot this print driver. These are the files available in the print driver folder in source control. The output of this print driver is PCL. Please suggest. I have never done windows driver development. My experience with c++ is minimal.
1) How I do build this to be able to generate a print driver, .ini file. This is legacy code and still being used. Its upto me now to figure out how to actually make this code generate an output.
2) All I know is the output of this black box code is a PCl which is then later on in the application converted to a TIFF. This TiFF is written to the drive
3) We have a customer who TIFF is not being written. I intercepted the input to the applicatoin and tried to see if the PCL is being received. It looks like the PCL file only the header is generated and there is no other data. Now I am leaning towards PCL not being generated by the print driver because of some font issues or registry
4) Happens on some documents after a windows 7 to 10 upgrade. How do I troubleshoot this print driver. Please suggest. What am I looking for in a process monitor log.
5) Could this be the problem see the good procmon and bad
Good
Bad: SetAllocationInformationFile is missing in the bad file proc mon
I appreciate reading this post
sunDisplay
Continue reading...