In a message dated 4/15/2004 09:35:51 Eastern Daylight Time, [EMAIL PROTECTED] writes:
This sounds like the old problem on Novell using the capture command and not
specifying a timeout setting.
Sami,
If you are using a Novell, there are a couple of "gotcha's" in there. First, if it's Netware 5.1 or lower, DON'T print directly to the printer, no matter WHAT the documentation says!!!!!!!! That waits FOREVER to print, and I have actually had documents that have printed the next DAY! I can't speak to 6.0 or above, because I'm still on 5.1.
Set up a print queue, and print to the queue. I have better luck setting the queue on a specific server, and just send it to that server and queue, i.e. \\FS3\PrinterQueueName. Then from Netadmin, set the printer to service the queue, and it's done. I always use the configuration as follows:
Queue Name : \\FS3\PrinterName-Q (Lets you know it's a print Queue)
Define the queue as a printer in Win Printer Setup
Prnsetup \\FS3\PrinterName-Q
output printer
print reportname where..........
output screen
If you set it up as an NDPS queue, it seems to get a little flakey, and then RBase chokes on the Prnsetup i.e.
\\SSW1\PrinterName-Q.Stalder
RBase dies on the "." in NDPS, so the Server Queues work without aggravation. And most system admins don't have a problem adding a print queue. It can be serviced by any NDPS printer.
Hope it helps :)
Damon
Damon D. Kaufman
President
Stalder Spring Works, Inc
ISO-9002 / QS-9000 Certified
2345 S. Yellow Springs St.
Springfield, Ohio 45506
Voice 937-322-6120
Fax 937-322-2126
email: [EMAIL PROTECTED]
- [RBASE-L] - RE: RBDOS - Windows XP - the saga continues DKauf22024
