This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Can't print because .lnk makes printer name invalid


 

> -----Original Message-----
> From: Igor Peshansky [mailto:pechtcha@cs.nyu.edu] 
> Sent: Friday, April 21, 2006 1:41 PM
> To: Rockefeller, Harry
> Cc: cygwin@cygwin.com
> Subject: RE: Can't print because .lnk makes printer name invalid
> 
> Ugh, top-posting...  Reformatted.
> 
> On Fri, 21 Apr 2006, Rockefeller, Harry wrote:
> 
> > > -----Original Message-----
> > > From: cygwin-owner@XXXXXX.XXX
> > > [mailto:cygwin-owner@XXXXXX.XXX] On Behalf Of Corinna Vinschen
> > > To: cygwin@XXXXXX.XXX
> 
> <http://cygwin.com/acronyms/#PCYMTNQREAIYR>.  Thanks.
> 
> > > Sent: Friday, April 21, 2006 12:17 PM
> > > Subject: Re: Can't print because .lnk makes printer name invalid
> > >
> > > On Apr 21 12:02, Rockefeller, Harry wrote:
> > > > I can open and view the security tab on the properties section
> > > > of the Windows share.
> > > >
> > > > I created a desktop shortcut to the printer and searched all
> > > > files for *servername.lnk but only the desktop link shows up.
> > > > I interpret this to mean that Cygwin itself is appending
> > > > '.lnk' to the printer share.
> > >
> > > No, the .lnk was appended by Windows.  The printer shortcut on the
> > > desktop is not the printer, it's just a shortcut.  To access the
> > > printer you need the real printer name, for instance 
> \\server\printer.
> > > You can't use the shortcut for this.
> >
> > I erased much of the previous email.
> > Here is the context:
> >
> > $ lpq -Sntserver1 -Psw-txt1
> >                          Windows 2000 LPD Server
> >                               Printer \\192.83.227.33\sw-txt1
> 
> I assume NTSERVER1 has the IP 192.83.227.33.  Also, since this is the
> Windows lpq, it might understand a shortcut in this context 
> (and so will
> /cygdrive/c/WINDOWS/system32/lpr, for that matter).

Thank you for the discussion.  Use of the 'which' command tells me alot.

> > harryr@harryr-pc ~/Desktop
> > $ echo $PRINTER
> > \\NTSERVER1\sw-txt1
> >
> > harryr@harryr-pc ~/Desktop
> > $ lpr junk
> > lpr: printer error: can't open '\\NTSERVER1\sw-txt1.lnk' 
> for writing:
> > The printer name is invalid.
> 
> Well, what does "ls -l //NTSERVER1/sw-txt1" show?  How about "ls -l
> //NTSERVER1/sw-txt1.lnk"?
> 	Igor

In each case: "No such file or directory"

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]