|
Posted by John Pollard on September 1, 2008, 8:21 pm
Please log in for more thread options
Jerry Boyle wrote:
>> Jerry Boyle wrote:
>>>> Bob Wang wrote:
>>>>> Margaret and John:
>>>>>
>>>>> Just to add some info about HP network printing under
>>>>> Vista
>>>>> Ultimate 32-bit and 64-bit (both pre-SP1 and post-SP1)
>>>>> I have an HP LJ 1320nw wireless and HP CLJ 2840 wired
>>>>> printers on
>>>>> my network.
>>>>>
>>>>> The 2840 works without any glitches (except that HP
>>>>> Director
>>>>> doesn't work under Vista 64-bit)
>>>>>
>>>>> Every few weeks I need to remove and re-install the 1320nw
>>>>> drivers
>>>>> to be able to print.
>>>>
>>>> Is that to be able to print at all? Or just to be able to
>>>> print in
>>>> Quicken.
>>>>
>>>> The problem I was looking into when I asked the question of
>>>> Margret
>>>> was Quicken users reporting that they could print in Vista
>>>> with
>>>> every other application except Quicken.
>>>>
>>>> [I know that such statements are not proof that the
>>>> printing
>>>> problem is Quicken's - just that it might be. But I do
>>>> think that
>>>> if an application can't print using one printer driver, and
>>>> a
>>>> different driver is installed for that printer, and the
>>>> application can print ... I believe that is close to proof
>>>> that
>>>> the driver was the cause of the problem.] I'm interested in
>>>> concrete evidence that printer drivers are causing
>>>> problems for Quicken under Vista, that are not "apparent"
>>>> in other
>>>> applications.
>>>
>>> On my Dell Vista machine I just replaced an HP OfficeJet
>>> 7400xi
>>> with a Lexmark X5495.
>>>
>>> I had no problems printing from Quicken 2008 H&B on the
>>> OfficeJet
>>> using the generic Vista drivers. I like the HP printers, but
>>> not the
>>> bloated and outdated software that comes with them.
>>>
>>> When I uninstalled the HP and installed the Lexmark printing
>>> worked
>>> perfectly from all applications except Quicken, which was
>>> completely
>>> unable to communicate with the Lexmark. The problem
>>> apparently
>>> wasn't in the drivers but in the QuickenConfigwpr.dat
>>> file. When
>>> I renamed this file wpr.old everything worked fine. Wpr.dat
>>> is one
>>> of the Quicken files that is relocated from a system folder
>>> to the
>>> user's Documents area by Vista Virtualization, but I have no
>>> idea
>>> whether or not that fact is relevant.
>>
>> Interesting. I knew that wpr.dat could get "corrupted"
>> (which could
>> just be generic speak for inaccurate). I can't recall if any
>> of the
>> others having Quicken Vista printing problems ever mentioned
>> trying
>> to rename wpr.dat.
> Vista or no Vista, wpr.dat is a good file to know about for
> people
> who are having problems printing from Quicken but not from any
> other
> applications. Printer drivers are not application-specific but
> wpr.dat is used only by Quicken (and perhaps other Intuit
> products).
> Duh!
Si. I knew that. Good to have it recorded here.
> My problem may have been wpr.dat corruption or by more general
> corruption that affected only the way Quicken interfaces with
> a
> printer using information from wpr.dat.
> It may even be a Quicken
> program bug that failed to adjust wpr.dat for the fact that I
> switched from a network printer (the HP) to a USB printer (the
> Lexmark).
This is definitely an interesting possibility.
Though I thought that Margaret reported that using USP printers
"avoided" the printing problems.
I wish I knew more about how an application would have to change
its behavior in order to address different printer
configurations. Actually, I'd really like to know why any
application should have to change its PCL instructions to
correctly print to the same printer it printed to under an
earlier operating system. [Read that as my doubt that ANY
application should need to change its PCL priinter instructions
to accomodate a new operating system. I think this particular
aspect of the problem is the most interesting, and the most
likely to offer insights into the underlying problem.]
I'm reasonably certain that the same PCL (Printer Control
Language) instructions should produce the same result on every
PCL capable printer, no matter what the printer is (I assume
that all the printers involved in the discussions that have
triggered my interest, are PCL capable printers).
> Perhaps the problem is deeper in Vista when you switch
> between network and USB printers or have both types present on
> the
> same system.
> Jerry
--
John Pollard
First initial underscore Last name at mchsi dot com
Please reply to newsgroup
| 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML Sitemap