NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
use Perl Log In
Beatnik (493)
Beatnik
(email not shown publicly)
http://www.ldl48.org/
A 29 year old belgian who likes Mountain Dew, Girl Scout Cookies, Tim Hortons French Vanilla Flavoured Cappucinno, Belgian beer, Belgian chocolate, Belgian women, Magners Cider, chocolate chipped cookies and Perl. Likes snowboarding, snorkling, sailing and silence. Bach can really cheer him up! He still misses his dog.
Project Daddy of Spine [sf.net], a mod_perl based CMS.
In his superhero time (8.30 AM to 5.30 PM), he works on world peace.
(email not shown publicly)
http://www.ldl48.org/
A 29 year old belgian who likes Mountain Dew, Girl Scout Cookies, Tim Hortons French Vanilla Flavoured Cappucinno, Belgian beer, Belgian chocolate, Belgian women, Magners Cider, chocolate chipped cookies and Perl. Likes snowboarding, snorkling, sailing and silence. Bach can really cheer him up! He still misses his dog.
Project Daddy of Spine [sf.net], a mod_perl based CMS.
In his superhero time (8.30 AM to 5.30 PM), he works on world peace.
Tuesday March 02, 2004
06:36 PM
Printer woes
One of our customers has a Nashuatec D422 printer hooked onto a Windows 2000 machine. It's apparently a Lexmark printer (only doing PCL). I need to access the printer remotly and so far without luck. I tried through SMB shares but it seems the jobs are sent out properly but not queued properly. All of this is done remotly and I continuesly have to call my contact to verify settings on the windows box. The Nashuatec site has some linux installation and filter scripts. I'll check lprngtool configuration tomorrow...
Printer woes
More |
Login
| Reply
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
I pour myself a cup of strong coffee. :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
I would... (Score:1)
That will basically turn Windows into a dumb network print box and make it keep its hands to itself. You will have to make sure your client has the proper drivers for the printer, but Windows will basically had the print jobs directly to the printer without interference. And, more importantly, without "helping".
I have found that when printing from a non-Win client... this works much better.
YMMV
Re:I would... (Score:1)