[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::windows-nt

Title:	Windows NT
Notice:	See note 15.0 for HCL location
Moderator:	TARKIN::LIN.com::FOLEY

Created:	Thu Oct 31 1991
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	6086
Total number of notes:	31449

6065.0. "printing multiple copies of odd number of pages in duplex" by 16.201.32.75::HERTA (For something fulfilled this hour, loved, or endured) Mon Jun 02 1997 08:54

If a file contains an odd number of pages, and you request multiple copies of
that file be printed in duplex, the even numbered copies start at the back
of the last page of the odd numbered copies.  E.g. if you request two duplexed
printouts of a three page document, the first sheet of paper will have page 1
on the front, and page 2 on the rear.  The second sheet of paper will have page
3 of the first copy on the front, and page 1 of the second copy on the rear.

I got this behaviour on both Windows NT V4.0 (SP 2) and Windows 95.  Does anyone
now a workaround?

For completeness sake, the print queue needs to serve as a remote queue for
systems located on other parts of the WAN.  We prefer defining the number of
copies on the NT queue to prevent the print jobs from being copied over the WAN
multiple times.

Herta

T.R	Title	User	Personal Name	Date	Lines
6065.1	Print driver issue?	RDVAX::akocstdhcp104-25.ako.dec.com::levy	Run Like an Antelope	`Tue Jun 03 1997 06:11`	17
	I'd assume this is the responsibility of the print driver to handle correctly. If this is a Digital printer and printer driver, you might want to take up the issue in HUMANE::POSTCRIPT_PRINTING. If this is another vendor's printer and print driver, you might want to contact them. I just tried this on an LPS32 that is served from Windows NT 4.0 using the Digital drivers and it behaves correctly. That is: page 1 is on sheet 1 front side page 2 is on sheet 1 back side page 3 is on sheet 2 front side sheet 2 back side is blank page 1 is on sheet 3 front side etc. dave
6065.2	anyone with HP LJ experience?	16.201.32.75::HERTA	For something fulfilled this hour, loved, or endured	`Tue Jun 03 1997 07:46`	12
	Re .1: Dave > I'd assume this is the responsibility of the print driver to handle > correctly. If this is a Digital printer and printer driver, you might > want to take up the issue in HUMANE::POSTSCRIPT_PRINTING. If this is Thanks for the suggestion. I'll ask there. The client I'm working for is going to buy HP LaserJets 4 and 5. Does anyone know whether these work correctly? Feedback highly appreciated. Herta
6065.3	Sell Digital	RDVAX::akocstdhcp104-25.ako.dec.com::levy	Run Like an Antelope	`Tue Jun 03 1997 08:52`	5
	If they don't work correctly, here is a nice opportunity to push the capabilities of Digital's printers, eh? dave
6065.4		16.201.32.75::HERTA	For something fulfilled this hour, loved, or endured	`Tue Jun 03 1997 09:40`	10
	Re. .3 Provided we can get ours to work properly ... I'm afraid the customer has already decided on its desktop strategy. The LPS printers are only supported in the new environment because they already have them. Any new printers will be HPs. (We sold them 4 ASE clusters of 2 AlphaServer 4100 systems each, and they don't want to become too dependent on us ;-) ) Herta
6065.5	application problem	16.201.32.75::HERTA	For something fulfilled this hour, loved, or endured	`Tue Jun 03 1997 10:06`	6
	In the HUMANE::POSTSCRIPT_PRINTING conference, Tima Lasko pointed out it might just as well be an application problem. He was right. When I print from Notepad, it works fine. I guess it's time to visit ORION::WINWORD... Herta
6065.6	Word 97 is ok	RDVAX::akocstdhcp104-25.ako.dec.com::levy	Run Like an Antelope	`Tue Jun 03 1997 10:26`	3
	My test was with Word 97...and it worked correctly. dave
6065.7	utterly and totally confused	16.201.32.75::HERTA	For something fulfilled this hour, loved, or endured	`Tue Jun 03 1997 10:41`	15
	OK. I managed to get completely confused. I currently don't have access to my NT V4.0 system where I initially encountered the problem using Word 95, so I cannot run further tests. The system I'm using now runs Windows 95. I can reproduce the problem printing from Word 97, but not from Notepad. Based on some info I found in the ORION::WINWORD conference, I checked the technet CD (March 97 - couldn't find a more recent one so quickly), and there MS claims this feature is not a bug but intentional design. (I'd love to hear their arguments in support of that design.) If that is indeed the case, the question is: "why does it work?", rather than "why doesn't it work?" Herta