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

2006-04-24 Thread Rockefeller, Harry
Jay Abel wrote: >I would love to know how to get lpr to just print directly to the printer's >IP address, but the above isn't as bad as it seems, since it keeps windows >and cygwin print jobs in sequence, and visible in the queue. > >I'm sure there is a better way, but the above worked for me. W

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

2006-04-21 Thread Jay Abel
kefeller, Harry" <[EMAIL PROTECTED]> To: Sent: Friday, April 21, 2006 12:43 PM Subject: RE: Can't print because .lnk makes printer name invalid >I've looked at the trace. Nothing obvious comes to mind, but I did think of something else: on my machine, running "net u

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

2006-04-21 Thread Rockefeller, Harry
>I've looked at the trace. Nothing obvious comes to mind, but I did think >of something else: on my machine, running "net use" on the shared printer >helped enable it -- try "net use '\\NTSERVER1\sw-txt1'" and see if that >lets you print. Though the error I was getting before "net use" is >differ

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

2006-04-21 Thread Igor Peshansky
t; > > Cc: [EMAIL PROTECTED] > > Again, <http://cygwin.com/acronyms/#PCYMTNQREAIYR>. Thanks. > > > > Subject: RE: Can't print because .lnk makes printer name invalid > > > > > > Ugh, top-posting... Reformatted. > > > > > &

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

2006-04-21 Thread Igor Peshansky
TNQREAIYR>. Thanks. > > 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- > > > &g

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

2006-04-21 Thread Rockefeller, Harry
> -Original Message- > From: Igor Peshansky [mailto:[EMAIL PROTECTED] > 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... Ref

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

2006-04-21 Thread Igor Peshansky
REAIYR>. 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 > > >

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

2006-04-21 Thread Rockefeller, Harry
essage- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Corinna Vinschen > Sent: Friday, April 21, 2006 12:17 PM > To: cygwin@cygwin.com > Subject: Re: Can't print because .lnk makes printer name invalid > > On Apr 21 12:02, Rockefeller, Harry wrote:

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

2006-04-21 Thread Corinna Vinschen
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 Cygwi

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

2006-04-21 Thread Rockefeller, Harry
> -Original Message- > From: Igor Peshansky [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 20, 2006 2:22 PM > To: Rockefeller, Harry > Cc: cygwin@cygwin.com > Subject: Re: Can't print because .lnk makes printer name invalid > > On Thu, 20 Apr 2

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

2006-04-20 Thread Igor Peshansky
On Thu, 20 Apr 2006, Rockefeller, Harry wrote: > I had our UNIX administrator work on this for a couple of days. He > totally reinstalled Cygwin. The problem still exists. This has nothing to do with Cygwin -- the link is probably on the server share... Can you "ls" it and see what the permiss

Can't print because .lnk makes printer name invalid

2006-04-20 Thread Rockefeller, Harry
I had our UNIX administrator work on this for a couple of days. He totally reinstalled Cygwin. The problem still exists. However, I created a workaround which may be of benefit to others. With a postscript file or output from a2ps use this command cat $i.ps | $HOME/bin/print.pl and this perl