Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer.
Wols Lists <[email protected]>
| Newsgroups | gmane.comp.db.u2.general |
|---|---|
| Message-ID | <[email protected]> |
On 28/01/14 17:10, Jeff Schasny wrote: > I was assuming, based on the fact that he is using SETPTR to address > which printer he is directing the data to, that he was looking at queues > available to the machine since that is what SETPTR does. Correct. Except he was *also* using the URI syntax, ie \\COMPUTER\QUEUE. So if I am working on \\ASHDOWN (the name of my computer) I can use SETPTR to point at \\TIGGER\HP - a printer logically connected to a different computer that I've never told UV anything about. Setptr is quite happy to be given a windows remote computer reference and it works fine. That was how all our printers worked - they usually had network cards in them, so when a new printer turned up, I would assign it a name in DNS, and for anybody who was supposed to use it I would just edit their login script to add eg SETPTR ...,AT \\ACCOUNTS-HP\RAW And it just worked. No UV printer setting up whatsoever. Okay, my setup was a little bit cleverer than that, but everything, and I mean EVERYTHING, was done in my programs. Nothing at the UV level whatsoever. Cheers, Wol > > Wols Lists wrote: >> On 28/01/14 15:07, Jeff Schasny wrote: >> >>> SPOOL -LIST will show you all the print queue names >>> >> >> Is that all the printer names known to U2, or all the printer names >> known to the network? >> >> In Chuck's example, this particular printer will never have been >> declared to U2 - I did this all the time. The only printer UV was told >> about was DEFAULT, which didn't exist ... >> >> In fact, I suspect this syntax will list all the printers known to the >> server on which U2 is running, which could easily NOT include a valid >> printer the user is trying to print to ... >> >> Cheers, >> Wol >> >>> Charles Stevenson wrote: >>> >>>> SETPTR 0,80,60,3,3,1,AT \\BAD\NAME >>>> seems to execute w/o throwing an error. >>>> but an actual PRINT statement yields a fatal error: >>>> >>>> Program "PRT": Line 2, Printer name \\BAD\PRINTERNAME is not >>>> recognized by the system. >>>> >>>> I'd like to verify we're printing to a good printer *before* >>>> attempting to do so. >>>> Execute some DOS command, maybe? >>>> >>>> _______________________________________________ >>>> U2-Users mailing list >>>> [email protected] >>>> http://listserver.u2ug.org/mailman/listinfo/u2-users >>>> . >>>> >>>> >> >> _______________________________________________ >> U2-Users mailing list >> [email protected] >> http://listserver.u2ug.org/mailman/listinfo/u2-users >> >> > _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users