3.02 to 3.03 with an unavailable printer Options

[Derek Wright]

I have been happily running PMView 3.02 (registered)
I downloaded 3.03 from my special BMT account

Prior to installing 3.03, the last time that I had been using 3.02 I had had it printing to a printer connected to another PC on my Peer to Peer network (File and Print sharing)
The printer being used was not the default printer.

Several days later I installed 3.03 (however the other machine was not connected)

I could start 3.03 but when I requested a print operation, PMVIEW crashed

I have now reinstalled 3.02 - I guess that to get 3.03 working I will have to ensure that the prior to 3.03 being installed I will have to have 3.02 printing to the default printer on the primary machine.

I have in the past never considered the need to have the PMView do a final print to the default home printer after printing via a remote printer.

Any comments etc - is this an expected outcome.

Thanks

[Peter]

v3.03 unfortunately has a new bug in the printing code that probably creates more problems than the enhanced code in v3.03 solves. The bug in v3.03 makes PMView crash if the IBMNULL printer is installed.

Suggested workarounds for the problem:
-Downgrade to v3.02 (recommended)
-Delete the IBMNULL printer object (this may or may not solve the problem)

Thanks,



Edited By Peter on 1072027844