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 h
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/
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
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 inst
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
with awesome support.
Bill
Untitled Page
- Original Message -
*From:* antli...@youngman.org.uk
*To:* U2 Users List
*Date:* 1/28/2014 12:54 PM
*Subject:* Re: [U2] How do you verify windows printer is good befor
itled Page
- Original Message -
*From:* antli...@youngman.org.uk
*To:* U2 Users List
*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 bog
t: 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 probl
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
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
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 connecte
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
an 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
know
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
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 onl
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.
16 matches
Mail list logo
