MACSCRPT Archives

March 2008

MACSCRPT@LISTSERV.DARTMOUTH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version:
1.0 (Apple Message framework v919.2)
Content-Type:
text/plain; charset=US-ASCII; format=flowed; delsp=yes
Date:
Sun, 2 Mar 2008 18:55:34 -0500
Reply-To:
Macintosh Scripting Systems <[log in to unmask]>
Subject:
From:
Bruce Carter <[log in to unmask]>
In-Reply-To:
<p06240844c3ef86bc0524@[172.21.197.244]>
Content-Transfer-Encoding:
7bit
Sender:
Macintosh Scripting Systems <[log in to unmask]>
Parts/Attachments:
text/plain (28 lines)
It's not EXACTLY accurate to say that Printer Setup Utility is no  
longer present in Leopard.  Take a look at /System/Library/ 
CoreServices/Printer Setup Utility.  Appears to launch faceless in the  
background.

On Mar 1, 2008, at 5:26 PM, Jan Hendrikx wrote:
> Thanks for your reply, it made me look again, and I think I found  
> out what was going on. First of all, you are completely right, even  
> though the "Printer Setup Utility" is no longer present in Leopard,  
> you can apparently still call it in a script. The reason why my  
> script was not working is that it seems that Tiger and Leopard use  
> different naming schemes for the assigned printers. I was trying to  
> set a shared printer on a colleague's computer to the current printer.
>
> In Tiger I could simply set the current printer to "ZTC LP2844- 
> Z-200dpi".
>
> However, in Leopard this printer shows up as "ZTC LP2844-Z-200dpi @  
> MyColleaguesComputer".
>
> So if the printer names are hard-coded, the script will fail. That's  
> what was going on. Thanks everybody for putting up with me!

-- 
Bruce Carter, Senior Systems Engineer              http://www.nd.edu/~bcarter/
Center for Creative Computing, University of Notre Dame, Notre Dame,  
IN  46556

ATOM RSS1 RSS2