Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer.
Not quite so easy - Remember that under Windows a printer is a combination of a driver and a device. If you link to a remote printer, it needs to install the driver locally on your server so as to access the printer correctly .. that means either it has to be a model that has previously been installed (say, if you have two equivalent HP Lasers on different machines) or the client needs to have the right drivers to publish back to you - which can give problems if they are running different versions of Windows and e.g. 64 bit vs 32 bit and you haven't loaded them all. Also, BTW, being able to access the driver doesn't mean the printer is working. Most drivers only check when they actually start printing. So any 'is this printer online or offline' messages only relate to the last thing the driver knew about and not necessarily the current state. That said, you can try the DOS NET commands. NET USE will show you what you have visible already: C:\Users\briannet use New connections will be remembered. Status Local RemoteNetwork --- Unavailable LPT1: \\tiny\text1 Microsoft Windows Network The command completed successfully. Now this is NOT showing what is actually available. C:\Users\brianNET USE \\tiny\HP Color LaserJet CP2020 Series PCL6 The command completed successfully. Now it is there: Status Local RemoteNetwork --- Unavailable LPT1: \\tiny\text1 Microsoft Windows Network OK \\tiny\HP Color LaserJet CP2020 Series PCL6 Microsoft Windows Network The command completed successfully. Brian ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer.
Thanks, Brian. I was heading that general direction with net view \\[printserver] Then searching for the printer I'm looking for. You're right about the drivers, but I don't think I'll get a fatal error just because the printing is garbled or printer is offline, will I? We've been getting a rash of errors in something that's been pretty stable for years, resulting in incomplete updates because the PRINT statements aborted were in the middle of the writes. On 1/30/2014 4:23 PM, Brian Leach wrote: Not quite so easy - Remember that under Windows a printer is a combination of a driver and a device. If you link to a remote printer, it needs to install the driver locally on your server so as to access the printer correctly .. that means either it has to be a model that has previously been installed (say, if you have two equivalent HP Lasers on different machines) or the client needs to have the right drivers to publish back to you - which can give problems if they are running different versions of Windows and e.g. 64 bit vs 32 bit and you haven't loaded them all. Also, BTW, being able to access the driver doesn't mean the printer is working. Most drivers only check when they actually start printing. So any 'is this printer online or offline' messages only relate to the last thing the driver knew about and not necessarily the current state. That said, you can try the DOS NET commands. NET USE will show you what you have visible already: C:\Users\briannet use New connections will be remembered. Status Local RemoteNetwork --- Unavailable LPT1: \\tiny\text1 Microsoft Windows Network The command completed successfully. Now this is NOT showing what is actually available. C:\Users\brianNET USE \\tiny\HP Color LaserJet CP2020 Series PCL6 The command completed successfully. Now it is there: Status Local RemoteNetwork --- Unavailable LPT1: \\tiny\text1 Microsoft Windows Network OK \\tiny\HP Color LaserJet CP2020 Series PCL6 Microsoft Windows Network The command completed successfully. Brian ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer.
Thanks Anthony. Yeah, it you can find the code w/o too much trouble, I'd be interested. BTW, it's impressive how little printing this company actually does. Remember that promise of a paperless society? Maybe we're getting there. Good. I hate printers. Always have. Chuck On 1/29/2014 10:43 PM, Anthonys Lists wrote: On 28/01/2014 20:59, Charles Stevenson wrote: Anthony pretty much nailed how we're doing it. But my original question is still unanswered. I want to make sure it's a valid printer before I start printing to it. I think I problably need to do something like EXECUTE DOS /C [some-command] \\MY_PRINT_SERVER\PrinterName CAPTURING DOSMSG IF DOSMSG = [something bad] THEN . . . I was hoping someone in this august body had crossed that bridge before. We never had that problem. I had a PRINTER subroutine or suchlike that accessed a printers file with all the parameters. Any programatic (or user command line) attempt to access a printer was via my stuff, that checked this file, and set things up accordingly. So as far as eg accounts was concerned, they had the ACCOUNTS printer. Whenever anything changed, I simply changed the ACCOUNTS entry in the parameter file. Very useful, because on the odd occasion when a printer went down I just made a temporary change to the file and everything got diverted :-) If tyou're interested, let me know and I'll see if I can find the code - I know I had it but it's a long time ago ... Cheers, Wol ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer.
On 30/01/2014 22:15, Charles Stevenson wrote: Thanks Anthony. Yeah, it you can find the code w/o too much trouble, I'd be interested. BTW, it's impressive how little printing this company actually does. Remember that promise of a paperless society? Maybe we're getting there. Good. I hate printers. Always have. I'll see if I can find them for you. But it'll have to wait as it's long past bed-time here :-) The company I learnt all about printers at ... when I started there they had a full-blown printing press in the basement! But by the time I left all the info was going out on CDs or over the web. Cheers, Wol ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer.
On 28/01/2014 20:59, Charles Stevenson wrote: Anthony pretty much nailed how we're doing it. But my original question is still unanswered. I want to make sure it's a valid printer before I start printing to it. I think I problably need to do something like EXECUTE DOS /C [some-command] \\MY_PRINT_SERVER\PrinterName CAPTURING DOSMSG IF DOSMSG = [something bad] THEN . . . I was hoping someone in this august body had crossed that bridge before. We never had that problem. I had a PRINTER subroutine or suchlike that accessed a printers file with all the parameters. Any programatic (or user command line) attempt to access a printer was via my stuff, that checked this file, and set things up accordingly. So as far as eg accounts was concerned, they had the ACCOUNTS printer. Whenever anything changed, I simply changed the ACCOUNTS entry in the parameter file. Very useful, because on the odd occasion when a printer went down I just made a temporary change to the file and everything got diverted :-) If tyou're interested, let me know and I'll see if I can find the code - I know I had it but it's a long time ago ... Cheers, Wol ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
[U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer.
SETPTR 0,80,60,3,3,1,AT \\Bad\PrinterName 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 U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
[U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer.
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 U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer.
SPOOL -LIST will show you all the print queue names 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 U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users . -- Jeff Schasny - Denver, Co, USA jschasny at gmail dot com ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer.
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 U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users . ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer.
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. 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 U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users . ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users -- Jeff Schasny - Denver, Co, USA jschasny at gmail dot com ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer.
The Spool -List only lists universe print queues It doesn't like printers on the network. When we create a new printer on our network, we have to go into Universe and add the queue and link the two to each other. -Original Message- From: Wols Lists antli...@youngman.org.uk To: u2-users u2-users@listserver.u2ug.org Sent: Tue, Jan 28, 2014 8:19 am Subject: Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer. 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 U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users . ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer.
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 U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users . ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer.
I've been using Universe since it was in beta and I had no idea you could use a URI in SETPTR. Its a good day, I've learned something new. Thanks! Wols Lists wrote: 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 Correct. Except he was *also* using the URI syntax, ie \\COMPUTER\QUEUE. 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 U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users . ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users -- Jeff Schasny - Denver, Co, USA jschasny at gmail dot com ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer.
On 28/01/14 20:31, Jeff Schasny wrote: I've been using Universe since it was in beta and I had no idea you could use a URI in SETPTR. Its a good day, I've learned something new. Thanks! Just watch out. In today's modern world of GDI printers, sending a raw text dump from UV is often not a good idea. In the old days of dot-matrix, or even PCL that just expected a text stream, it worked fine. It's nowhere near that simple any more :-( Cheers, Wol Wols Lists wrote: 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 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer.
Anthony pretty much nailed how we're doing it. But my original question is still unanswered. I want to make sure it's a valid printer before I start printing to it. I think I problably need to do something like EXECUTE DOS /C [some-command] \\MY_PRINT_SERVER\PrinterName CAPTURING DOSMSG IF DOSMSG = [something bad] THEN . . . I was hoping someone in this august body had crossed that bridge before. cds On 1/28/2014 11:31 PM, Jeff Schasny wrote: I've been using Universe since it was in beta and I had no idea you could use a URI in SETPTR. Its a good day, I've learned something new. Thanks! Wols Lists wrote: 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 Correct. Except he was *also* using the URI syntax, ie \\COMPUTER\QUEUE. 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 U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer.
Do a SETPTR, followed by a PRINT and capture that output It's the only way to *guarantee* that the process won't work in exactly the same way as it's not working now. -Original Message- From: Charles Stevenson stevenson.c...@gmail.com To: U2 Users List u2-users@listserver.u2ug.org Sent: Tue, Jan 28, 2014 1:00 pm Subject: Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer. Anthony pretty much nailed how we're doing it. But my original question is still unanswered. I want to make sure it's a valid printer before I start printing to it. I think I problably need to do something like EXECUTE DOS /C [some-command] \\MY_PRINT_SERVER\PrinterName CAPTURING DOSMSG IF DOSMSG = [something bad] THEN . . . I was hoping someone in this august body had crossed that bridge before. cds On 1/28/2014 11:31 PM, Jeff Schasny wrote: I've been using Universe since it was in beta and I had no idea you could use a URI in SETPTR. Its a good day, I've learned something new. Thanks! Wols Lists wrote: 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 Correct. Except he was *also* using the URI syntax, ie \\COMPUTER\QUEUE. 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 U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer.
You know, I was able to integrate all printers into U2 by writing a few simple programs and using Print Wizard to convert our PCL5 output into a .pdf file. This way, I never work with printers at the UD level any more. And PW is an awesome product with awesome support. Bill Untitled Page - Original Message - *From:* antli...@youngman.org.uk *To:* U2 Users List u2-users@listserver.u2ug.org *Date:* 1/28/2014 12:54 PM *Subject:* Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer. On 28/01/14 20:31, Jeff Schasny wrote: I've been using Universe since it was in beta and I had no idea you could use a URI in SETPTR. Its a good day, I've learned something new. Thanks! Just watch out. In today's modern world of GDI printers, sending a raw text dump from UV is often not a good idea. In the old days of dot-matrix, or even PCL that just expected a text stream, it worked fine. It's nowhere near that simple any more :-( Cheers, Wol Wols Lists wrote: 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 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer.
I second the motion. I recently installed Print Wizard on a client's machine and was impressed at how easy it was to use. Robert Norman ROBERT NORMAN AND ASSOCIATES 23441 Golden Springs Dr., #289, Diamond Bar, CA 91765 (951) 541-1668 i...@keyway.net mailto:i...@keyway.net http://users.keyway.net/~ice/ http://users.keyway.net/%7Eice/ Affordable computer consulting services and computer programming for UNIVERSE, UNIDATA, U2, PICK/BASIC, DATA/BASIC, UniVerseBasic, UniBasic, R/BASIC, jBC. Ask about our $50 discounted rate for telecommuting projects. On 1/28/2014 2:37 PM, Bill Haskett wrote: You know, I was able to integrate all printers into U2 by writing a few simple programs and using Print Wizard to convert our PCL5 output into a .pdf file. This way, I never work with printers at the UD level any more. And PW is an awesome product with awesome support. Bill Untitled Page - Original Message - *From:* antli...@youngman.org.uk *To:* U2 Users List u2-users@listserver.u2ug.org *Date:* 1/28/2014 12:54 PM *Subject:* Re: [U2] How do you verify windows printer is good before fatal error by PRINTing to a bogus printer. On 28/01/14 20:31, Jeff Schasny wrote: I've been using Universe since it was in beta and I had no idea you could use a URI in SETPTR. Its a good day, I've learned something new. Thanks! Just watch out. In today's modern world of GDI printers, sending a raw text dump from UV is often not a good idea. In the old days of dot-matrix, or even PCL that just expected a text stream, it worked fine. It's nowhere near that simple any more :-( Cheers, Wol Wols Lists wrote: 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 ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
