Inconsistent values in JOB_INFO_2.TotalPages when collating copies

[Christoph Lindemann]

When printing a 13 page job in 2 copies, the TotalPages value is
inconsistent, depending on ?.

normally:
JOB_INFO_2.TotalPages = 26
JOB_INFO_2.pDevMode.dmCopies = 2
here TotalPages is the TOTAL number of pages

but sometimes:
JOB_INFO_2.TotalPages = 13
JOB_INFO_2.pDevMode.dmCopies = 2
Here TotalPages is only the number of pages pr. job. So the TOTAL would be
(TotalPages*dmCopies)

Until now I thought this is depending on the JOB_INFO_2.pDevMode.dmCollate
field:
if JOB_INFO_2.pDevMode.dmCollate == DMCOLLATE_TRUE then
TOTAL = JOB_INFO_2.TotalPages
else
TOTAL = JOB_INFO_2.TotalPages * JOB_INFO_2.pDevMode.dmCopies

But I have seen cases where JOB_INFO_2.pDevMode.dmCollate != DMCOLLATE_TRUE
but TOTAL = JOB_INFO_2.TotalPages

So the question is, can some one at Microsoft (or anyone else) shed some
light on how these fields depend on each other.
Might be this behaviour depends on something total different, like the used
driver, print processor, if the sun is shining ;)

[Jeffrey Tan[MSFT]]

Hi clindemann2,

Thanks for your post!

Based on my understanding, you got 2 different behaviors from
JOB_INFO_2.TotalPages field when printing. Do you get the 2 different
behaviors on the same machine from different applications, or from 2
different test machines? I suspect you are the latter case.

I have never seen these 2 different behaviors. In the situation you
described, I have the thought as you, different printer driver behavior
should result in different data reported by JOB_INFO_2 structure. I have
some suggestion currently.

1. Have you checked JOB_INFO_2.PagesPrinted field? Is this field always
equal to JOB_INFO_2.TotalPages?
2. Based on dmCollate field description of DEVMODE structure, it is a
really potential useful information to determine the state. In your code,
have you checked DEVMODE.dmFields field first. Based on MSDN,
DEVMODE.dmCollate member only takes effect when the printer driver
indicates support for collation by setting the dmFields member to
DM_COLLATE.

Thanks

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[Christoph Lindemann]

As it looks, the 2 different behavior can exist on the same computer, but on
different printers. But on other computers, it works ok, even with the
driver that gives "wrong" (JOB_INFO_2.pDevMode.dmCollate != DMCOLLATE_TRUE
but TOTAL = JOB_INFO_2.TotalPages) results on other computers.

The "wrong" behaviour has been reported with HP Desk/DesignJet and IBM
ProPrinter drivers. I have testet the later, with no problems.

Post by Jeffrey Tan[MSFT]
1. Have you checked JOB_INFO_2.PagesPrinted field? Is this field always
equal to JOB_INFO_2.TotalPages?

In general they are different, in the way that one always is 0. So in the
case that PagesPrinted <= 0 I do use TotalPages.

Post by Jeffrey Tan[MSFT]
2. Based on dmCollate field description of DEVMODE structure, it is a
really potential useful information to determine the state. In your code,
have you checked DEVMODE.dmFields field first.

Yes I take into account the flags. Also the "wrong" behaviour seems to be
consistent on the computer-driver-application combinations, where it occurs.

So what triggers this behaviour? If would know, then I could build an
workaround.
But as I am not know all the internal workings of the spooler, I do not even
know which components use and modify these fields.


Kind regards,
Christoph

[Jeffrey Tan[MSFT]]

Hi Christoph,

Thanks for your feedback.

Post by Christoph Lindemann
The "wrong" behaviour has been reported with HP Desk/DesignJet and IBM
ProPrinter drivers. I have testet the later, with no problems.

I am not sure I understand this statement well. What does "later" mean in
your scenario? Does it mean IBM ProPrinter drivers?

I will try to perform some research on this issue to see if there is any
known issue regarding it, I will update you ASAP. Thanks

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[Christoph Lindemann]

Hi Jeffrey,

Thank you for the support!

Post by Jeffrey Tan[MSFT]

Post by Christoph Lindemann
The "wrong" behaviour has been reported with HP Desk/DesignJet and IBM
ProPrinter drivers. I have testet the later, with no problems.

I am not sure I understand this statement well. What does "later" mean in
your scenario? Does it mean IBM ProPrinter drivers?

Yes, the problem has shown consistent at the customer with then IBM
Infoprint 1145 PS3 driver (Version 7.4.1.0). I have testet the same driver,
on different configurations, without problems.
So I guess the driver has nothing to do with the problem, but then on the
other hand...
The server where the problem occurs, looks like a plain vanilla windows
installation.
I was just wondering if the client os vs. server os relationship (including
drivers) might have any influence.

Post by Jeffrey Tan[MSFT]
I will try to perform some research on this issue to see if there is any
known issue regarding it, I will update you ASAP. Thanks

No thank you. :)

Kind regards,
Christoph Lindemann

[Jeffrey Tan[MSFT]]

Hi Christoph,

Yes, it seems that the problem is that machine specific. Based on the
currently information available, I still can not find any useful
information to resolve it. Because you said "No" in your reply, do you
still need any help in the newsgroup? Have you tried to re-install your
machine?

Thanks

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[Christoph Lindemann]

Post by Jeffrey Tan[MSFT]
Yes, it seems that the problem is that machine specific. Based on the
currently information available, I still can not find any useful
information to resolve it. Because you said "No" in your reply, do you
still need any help in the newsgroup?

Well, yes, as I have not solved this problem.

Would be nice, I someone in the printing department could sheed some light
on, how/where the spooler updates these values internally. Which modules
(driver, print handler, print processor, print monitor) have an influence,
and how.

This would help finding the "faulty" part.

Post by Jeffrey Tan[MSFT]
Have you tried to re-install your
machine?

Well, as this happens on a customers mashine, I can not just ask him to
re-install his mashine.
And that wouldn't help in the future, to prevent this problem from happening
again.
I realy need to find the cause of this.

[Jeffrey Tan[MSFT]]

Hi Christoph,

Thanks for your feedback!

Yes, I see your concern. However, without reproducing the problem it is
hard to give it a definite troubleshooting.

Currently, I am not sure if the problem lies in printer side or Windows
printer modules side. Because other non-problem machines use the same
Windows OS as the problematic machine, it is hard for us to know where does
the problem exist in the printer module.

Do you install the same printer driver in the problematic machine as other
working machines? Do they have the same printer&driver settings?
Based on the symptom, such problem is more likely to be on driver/hardware
side than OS printer module side. I recommend you to contact the
problematic printer manufacture for some information, maybe this is a known
issue of their product in cooperating with certain Windows OS.

At last, if you want to find out the root cause, looking at the nature of
this issue, it would require intensive troubleshooting which would be done
quickly and effectively with direct assistance from a Microsoft Support
Professional through Microsoft Product Support Services. You can contact
Microsoft Product Support by contacting us at 1-[phone] or by
choosing one of the options listed at
http://www.microsoft.com/services/microsoftservices/srv_support.mspx.

Thanks for your understanding.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.