🚀 go-pugleaf

Victor Bien <nospam.vbien@attglobal.net> wrote in message news:<alfa3f$j1c$1@merki.connect.com.au>...
> K. B. wrote:
> [auto-citation of previous cut]
> 
> > I remember to have had a similar problem long time ago. It was not 
> > sufficient to merely remove the printer objects. I had to delete all 
> > printer drivers (see settings page, click on the printer driver icon).
> > I can no more remember how to remove the last one because you have to 
> > select a different driver for the actual printer object to unlock the 
> > driver...
> >  
> > 
> > Freundliche Gr��e
> > 
> > Klaus
> > 
> 
>    After making the changes previously described I ran into the problem 
> of not being able to print across the network from my Windoze machine. 
> My need to print from there was suddenly blocked!  Aigh??
> 
>    I map the DOS (IBMNull) shared printer to LPT3 on the Windows machine 
> and connect a Lexmark printer object to that port.  Now the shared 
> printer still appears in Network Neighbourhood but Windows thinks it is 
> "off-line".  Further strangeness is that while this situation prevailed, 
> I could still print something from a DOS window, redirecting say a type 
> <filename.txt> command to LPT3!
> 
>    This took hours of intense investigation to resolve!  The story is as 
> follows:
> 
>    I had to delete all the printer objects again!  I could not simply 
> recreate a DOS printer using IBMNull.  On sharing this the same problem 
> as the above reappeared.  I first had to create the DOS printer using 
> say the Lexmark PCL5 driver.  Then sharing would give the right result. 
>   After this I could go back into Properties and change the driver to 
> the desired IBMNull.  The share would stay alive!
> 
>    Following this I recreated my Lexmark printer.  At this point PMView 
> gave the message "There are no printers defined" again!  However, on 
> recreating the Fax printer object PMView printing came back to life! 
> Now both FxPrint and the Lexmark appeared.  On recreating the Postscript 
> printer object it also appeared in PMView's printer dialogue box.
> 
>    Weird eh?  Is this due to the extraordinary complexity of the WPS and 
> sometimes it just gets internally tangled?  I ran Cleanini which did get 
> rid of a lot of junk but it made no difference to the strange printer 
> behaviour.

This is interesting. I had a look at what situation would cause PMView
do display no printers defined. I found out that PMView really is a
bit too picky about the printer information, because if there is no
DEFAULT printer defined, PMView would give this message. This is of
course NOT correct behavior in PMView and will be fixed in the next
version of PMView.

Best regards,
Peter Nielsen
[Author of PMView]