Carl I just assumed (naively possibly) that the Win7-installed printer driver would have been 64-bit on the 64-bit version of Win7. I'll check it out, thanks.
Paul On 12/4/12 9:13 AM, Carl Lindner wrote: > Paul, > > I use print2pdf (postscript/ghostscript) to generate pdfs in XP/32 and > W7/32. It fails in W7/64. I still have not resolved it. When I > investigated, there were discussions about the need for a 64 bit ps driver. > I found > > TITLE: HP Universal PostScript Printer Driver (64-bit) VERSION ... > ftp://ftp.hp.com/pub/softpaq/sp39001-39500/sp39327.html > > Have you investigated this option? > > Carl Lindner > > -----Original Message----- > From: ProFox [mailto:[email protected]] On Behalf Of Paul McNett > Sent: Tuesday, December 04, 2012 11:55 AM > To: [email protected] > Subject: Re: SET PRINTER TO NAME (psPrinter) in VFP 8 / Windows 7 64 > > On 12/4/12 6:39 AM, Ted Roche wrote: >> On Tue, Dec 4, 2012 at 8:55 AM, Paul McNett <[email protected]> wrote: >> >>>> I can't explain why, but setting the printer properties for the PS >>>> printer to "print directly to the printer" appears to have fixed >>>> the issue for this user. >>>> I've never >>>> had to do that before. >>>> >>>> >> That's a great clue we ought to file away. I suspect there's a change >> in the API/behavior of the print queue in Win7/64 that prevents VFP's >> redirection "to file" from working properly. Might be a Win7 thing, or >> a 32/64-bit thing, but that's a good trick to try. > > I take back my solution to print directly to the printer. The user just > emailed to inform me that the print jobs are still PCL. Actually, the fax > server (hylafax) thinks they are PCL but in fact I've looked at the file and > it is PS although it is prepended with some non-PS junk like: > > @PJL SET STRINGCODESET=UTF8 > > There are 8 of those such lines before we get to: > > %!PS-Adobe-3.0 > > I also note that the file size jumped from about 60K to about 600K between > Windows XP and Windows7 using the same printer driver (HP LaserJet 2800 PS). > I need to wait until tonight to try to work around this but I'll try at > least: > > 1) experiment with different PS drivers (non-HP) > 2) experiment with lowering the DPI (this one indicates in the comments that > it is > 600 dpi which is way higher than needed) > > Thanks and sorry for the misinformation on the fix. > > Paul > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
