Permissions problem

[Matt Falvey]

Hi I have just bought a second hand iMac and when I try to save files from 
Safari on it to another iMac I get a message “The document “x.pdf” could 
not be exported as ".pdf" as You don’t  have Permission. To view or 
change permissions select the item in the Finer and choose File > Get Info

But if I try to save the file without exporting it, it saves without a problem.

Any ideas as to why the two are not talking? 

Sharing is on and Screen, File and Printer Sharing are all ticked.

Thanks

Matt.
-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>

Re: Photoshop CS5 - Permissions issue

[Ronni Brown]

> On 27 Jan 2016, at 1:10 PM, Matt Falvey  wrote:
> 
> Hi, I am using Photoshop CS5 on OS X 10.10 on an iMac and OS X 10.9.5 on a 
> MPB.
> 
> Since upgrading from 10.9.5 to 10.10 on the iMac, whenever I try to save a 
> file from the iMac to the MBP or vice versa I keep getting various messages, 
> 
> “The document “x.jpg” could not be exported as “x.jpg”. You don’t 
> have permission.   To view or change permissions, select the item in the 
> Finder and choose File > Get Info. If I try to download on from Facebook on 
> the MBP and save it on the iMac.
> 
> “Could not save as “x.jpg” because the file is locked or you do not have 
> the necessary access privileges. Use the “Get Info” command in the Finder to 
> unlock the file to change permissions on the file or enclosing folders”. 
> After downloading from Facebook to the MBP and trying to save it on the iMac.
> 
> “Could not save as “x.jpg” because write access was not granted”. When 
> trying to transfer a file from the iMac to the MBP.
> 
> Now I have gone into File>Get Info and changed the privileges on: Me, Staff 
> and everyone to “Read & Write” (on the file downloaded from FB instead of 
> Staff there was a new title “Fetching” which I also changed to “Read & Write”.
> 
> So the files are wide open, I just don’t know why they are behaving like 
> this, any ideas as to how to remedy it?

Hi Matt,

You have some ‘weird’ and incorrect permissions - privilege settings… and 
changing all to “Read & Write” is  NOT a good decision its a very bad decision!

I would suspect you have User Account - Home Folder Permissions ACL problems on 
the iMac OS X 10.10.x  (& perhaps on the MBP if you are experiencing permission 
errors)

Reset Home Folder Permissions in Terminal

Disk Utility only checks a limited subset of files, and it won’t repair 
anything within your Home folder. There is a slightly more convoluted way to 
fix permissions issues there.
Why might you want to do this, you ask? The most common scenario is that 
something’s gone wonky with files or folders in your Home folder; you try to 
save something to your Desktop, say, and your Mac tells you that you don’t have 
permission to do so.

Reset ‘Home Folder Permissions’ in Mountain Lion & Mavericks & Yosemite

You can reset your Home Folder Permissions from the Recovery HD using the Reset 
Password application.
This utility was primarily designed to reset user passwords; nonetheless, this 
tool also has the ability to Reset a User’s home folder permissions and ACL’s. 
Keep in mind that this process resets ALL home folder permissions, including 
intentionally changed permissions that may have benefited the user.

Again, the Reset Password application is ONLY available from an OS X Recovery 
system.

NOTE: You do NOT enter a New Password
——
1. Shut Down your computer
2. Boot to the Recovery HD: Start the computer and after the chime press and 
hold down the COMMAND and R keys until the menu screen appears. Alternatively, 
start the computer and after the chime press and hold down the OPTION key until 
the boot manager screen appears. 
Select the Recovery HD and click on the downward pointing arrow button.

3. OpenTerminal application (via the Utilities menu).
4. type resetpassword and press return
5. Once Reset Password opens
Select your Hard Disk volume
Select your user account (the account you want to Reset)
6. Click the Reset button at the bottom of the window in the Reset home folder 
permissions and ACLs section.
NOTE: DO NOT enter a New user password - leave all that blank
The reset process takes just a couple of minutes. 
7. Quit the Password Utility and go back to the main recovery screen.
8. On your keyboard, press Cmd + Q and Restart your computer (Select Apple logo 
> Restart from the menu bar). 

It's very important that you don't hold down the power button to exit the 
recovery session, or the ACL reset won't be performed.

Cheers,
Ronni

13-inch MacBook Air (April 2014)
1.7GHz Dual-Core Intel Core i7, Turbo Boost to 3.3GHz
8GB 1600MHz LPDDR3 SDRAM
512GB PCIe-based Flash Storage

OS X El Capitan 10.11.1


> Thanks.
> 
> Matt.  

-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>

Photoshop CS5 - Permissions issue

[Matt Falvey]

Hi, I am using Photoshop CS5 on OS X 10.10 on an iMac and OS X 10.9.5 on a MPB.

Since upgrading from 10.9.5 to 10.10 on the iMac, whenever I try to save a file 
from the iMac to the MBP or vice versa I keep getting various messages, 

“The document “x.jpg” could not be exported as “x.jpg”. You don’t have 
permission.   To view or change permissions, select the item in the Finder and 
choose File > Get Info. If I try to download on from Facebook on the MBP and 
save it on the iMac.

“Could not save as “x.jpg” because the file is locked or you do not have 
the necessary access privileges. Use the “Get Info” command in the Finder to 
unlock the file to change permissions on the file or enclosing folders”. After 
downloading from Facebook to the MBP and trying to save it on the iMac.

“Could not save as “x.jpg” because write access was not granted”. When 
trying to transfer a file from the iMac to the MBP.

Now I have gone into File>Get Info and changed the privileges on: Me, Staff and 
everyone to “Read & Write” (on the file downloaded from FB instead of Staff 
there was a new title “Fetching” which I also changed to “Read & Write”.

So the files are wide open, I just don’t know why they are behaving like this, 
any ideas as to how to remedy it?

Thanks.

Matt.  

 
-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>

Re: Repair Permissions in Disk Utility prior to OS X 10.11 El Capitan - Reset Home Folder Permissions in Terminal

[Michael Hawkins]

Thanks Ronni for your very clear explanation.  Cheers,
Michael

Sent from my iPhone

> On 4 Oct 2015, at 11:15 AM, Ronni Brown  wrote:
> 
> Hi Michael and any member interested in this subject,
> 
> Michael’s previous questions to the list under the Subject: Re: the spinning 
> beach ball has changed!
> 
>> "Going by how often running "repair permissions" seemed to work for me, does 
>> this mean (a) I was deluded (b) Apple has sorted something out that had 
>> lingered for a long time or (c) software updates are going to be released 
>> every three weeks or so 😇?"
> 
> 
> To answer your question, I’ll need to explain to you what “Repair 
> Permissions” using Disk Utility in OS X prior to El Capitan repaired. 
> Hopefully below will help answer your previous questions.
> 
> Repair Permissions in Disk Utility - Reset Home Folder Permissions in 
> Terminal  
> 
> Part A of my Reply:
> Repair Permissions in Disk Utility in OS X prior to El Capitan 
> 
> In OS X, each file contains information specifying which users (or parts of 
> the system) can read it, modify it, or execute it. 
> This information is collectively known as permissions. If a file has 
> incorrect permissions, it can cause apps to misbehave in various ways, such 
> as crashing or failing to launch.
> 
> Ordinarily, installers set the correct permissions for the files they 
> install, and the permissions stay that way permanently. However, a poorly 
> written installer can mess up permissions — even for files it did not install 
> — and if you use Unix commands such as chown and chmod, you can accidentally 
> set files’ permissions incorrectly. 
> These sorts of problems occur infrequently, but they do occur.
> 
> The Repair Permissions feature looks for certain software installed using 
> Apple’s installer, which saves files called receipts that list the locations 
> and initial permissions of all the files in a given package. Repair 
> Permissions compares the current permissions to those in the receipts and, if 
> it finds any differences, changes the files back. 
> The command ignores software installed in other ways (using a different 
> installer or drag-and-drop installation, for instance) and knows nothing 
> about permission changes you may have made deliberately.
> 
> Permissions don’t go out of whack all by themselves; you (or software you 
> install) must do something to change them. 
> 
> Are all files affected by Repair Disk Permissions?
> 
> No. As you may have inferred from the above description, only those files 
> installed using OS X’s Installer utility and whose installation packages 
> leave behind a proper receipt in /Library/Receipts are affected by the Repair 
> Disk Permissions function. 
> 
> This means that most of the files affected by the Repair Disk Permissions 
> function are system-level files, application files, or system add-ons—not 
> applications installed by drag-and-drop, and not your documents or other 
> user-level files.
> Repairing permissions is mainly a tool for fixing 'permissions-related' 
> problems with OS-level Apple software .
> But beyond that, only certain receipts are referenced, all of them associated 
> with OS-X-related software.
> 
> Although some might argue that restricting the Repair Disk Permissions 
> function to Apple-installed software is a limitation, it’s also good 
> security. If third-party receipts were used as references when repairing 
> permissions, a piece of malware could leave behind a receipt designed to 
> maliciously change permissions on system-level files—for example, to assign 
> more-accessible permissions on normally secure files and directories. This 
> could be a major security risk.
> 
> But starting in OS X 10.11 El Capitan, the Repair Permissions feature is gone 
> from Disk Utility entirely.
> Beginning with OS X El Capitan, system file permissions are automatically 
> protected. 
> It's no longer necessary to verify or repair permissions with Disk Utility.
>  Instead, permissions are repaired automatically when you install software 
> using Apple’s installer.
> —
> Part B of my Reply:
> Does repairing permissions affect third-party application files?
> 
> Apple’s description of the Repair Disk Permissions function seems to imply 
> that any software, including third-party software, installed using Installer 
> and accompanied by a receipt in /Library/Receipts is affected by repairing 
> permissions. 
> However, we know from my previous reply above that this isn’t the case. The 
> only third-party software affected by repairing permissions is software 
> included with Mac OS X and installed by the Mac OS X Installer.
> 
> Reset Home Fol

Repair Permissions in Disk Utility prior to OS X 10.11 El Capitan - Reset Home Folder Permissions in Terminal

[Ronni Brown]

Hi Michael and any member interested in this subject,

Michael’s previous questions to the list under the Subject: Re: the spinning 
beach ball has changed!

> "Going by how often running "repair permissions" seemed to work for me, does 
> this mean (a) I was deluded (b) Apple has sorted something out that had 
> lingered for a long time or (c) software updates are going to be released 
> every three weeks or so 😇?"


To answer your question, I’ll need to explain to you what “Repair Permissions” 
using Disk Utility in OS X prior to El Capitan repaired. 
Hopefully below will help answer your previous questions.

Repair Permissions in Disk Utility - Reset Home Folder Permissions in Terminal  

Part A of my Reply:
Repair Permissions in Disk Utility in OS X prior to El Capitan 

In OS X, each file contains information specifying which users (or parts of the 
system) can read it, modify it, or execute it. 
This information is collectively known as permissions. If a file has incorrect 
permissions, it can cause apps to misbehave in various ways, such as crashing 
or failing to launch.

Ordinarily, installers set the correct permissions for the files they install, 
and the permissions stay that way permanently. However, a poorly written 
installer can mess up permissions — even for files it did not install — and if 
you use Unix commands such as chown and chmod, you can accidentally set files’ 
permissions incorrectly. 
These sorts of problems occur infrequently, but they do occur.

The Repair Permissions feature looks for certain software installed using 
Apple’s installer, which saves files called receipts that list the locations 
and initial permissions of all the files in a given package. Repair Permissions 
compares the current permissions to those in the receipts and, if it finds any 
differences, changes the files back. 
The command ignores software installed in other ways (using a different 
installer or drag-and-drop installation, for instance) and knows nothing about 
permission changes you may have made deliberately.

Permissions don’t go out of whack all by themselves; you (or software you 
install) must do something to change them. 

Are all files affected by Repair Disk Permissions?

No. As you may have inferred from the above description, only those files 
installed using OS X’s Installer utility and whose installation packages leave 
behind a proper receipt in /Library/Receipts are affected by the Repair Disk 
Permissions function. 

This means that most of the files affected by the Repair Disk Permissions 
function are system-level files, application files, or system add-ons—not 
applications installed by drag-and-drop, and not your documents or other 
user-level files.
Repairing permissions is mainly a tool for fixing 'permissions-related' 
problems with OS-level Apple software .
But beyond that, only certain receipts are referenced, all of them associated 
with OS-X-related software.

Although some might argue that restricting the Repair Disk Permissions function 
to Apple-installed software is a limitation, it’s also good security. If 
third-party receipts were used as references when repairing permissions, a 
piece of malware could leave behind a receipt designed to maliciously change 
permissions on system-level files—for example, to assign more-accessible 
permissions on normally secure files and directories. This could be a major 
security risk.

But starting in OS X 10.11 El Capitan, the Repair Permissions feature is gone 
from Disk Utility entirely.
Beginning with OS X El Capitan, system file permissions are automatically 
protected. 
It's no longer necessary to verify or repair permissions with Disk Utility.
 Instead, permissions are repaired automatically when you install software 
using Apple’s installer.
—
Part B of my Reply:
Does repairing permissions affect third-party application files?

Apple’s description of the Repair Disk Permissions function seems to imply that 
any software, including third-party software, installed using Installer and 
accompanied by a receipt in /Library/Receipts is affected by repairing 
permissions. 
However, we know from my previous reply above that this isn’t the case. The 
only third-party software affected by repairing permissions is software 
included with Mac OS X and installed by the Mac OS X Installer.

Reset Home Folder Permissions in Terminal

Disk Utility only checks a limited subset of files, and it won’t repair 
anything within your Home folder. There is a slightly more convoluted way to 
fix permissions issues there.
Why might you want to do this, you ask? The most common scenario is that 
something’s gone wonky with files or folders in your Home folder; you try to 
save something to your Desktop, say, and your Mac tells you that you don’t have 
permission to do so.

Reset ‘Home Folder Permissions’ in Mountain Lion & Mavericks & Yosemite

You can reset your Home Folder Permissions fro

Re: Changing Get Info permissions

[Ronda Brown]

Hi Pat,

I'm pleased the Terminal command worked for you.
Did you download and install Java 8 64-bit Java Runtime 
You don't want it running in 32-bit mode in Mavericks

http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html

 Mac OS X x64   56.61 MB jre-8u5-macosx-x64.dmg

Automator is great, I created an App using Automator awhile back for someone on 
WAMUG who needed to combine multiply PDFs to be viewed as a single document 
(PDF).
I did a document explaining & showing how to "Combine Multiply PDF Documents 
Using Automator". You can do a lot of useful workflows with Automator.

Cheers,
Ronni
Sent from Ronni's iPad4


> On 4 Jun 2014, at 10:55 am, Pat  wrote:
> 
> Thanks very much, Ronni and Neil! It’s working.
> 
> Ronni, your Terminal suggestion opened it.
> 
> Neil, your Automator recipe didn’t work as it was, but I managed to alter it 
> so it did (beginner’s luck, I think, because I haven’t used Automator before).
> 
> So, the final recipe was: Get Specified Finder Items
>   wildfire-launcher.jar
> 
>   Run Shell Script
>   cd /Applications/j-wildfire-1.62
>   sh start_mac.command
> 
>   Get Specified Finder Items
>   j-wildfire.jar
> 
> And the application opens and runs. The application seems a little buggy for 
> Mac, because it often shows a grey working area, but clicking around may get 
> it going again. Or it might be because I use a stylus: some applications just 
> don’t work very well with a stylus.
> 
> I will try Parallels soon, just to compare the two different operating 
> systems.
> 
> Anyway, thank you both for spending the time and effort to help me with this. 
> I’m very grateful.
> 
> Cheers,
> Pat
> 
> 
>> On 3 Jun 2014, at 10:46 pm, Ronda Brown  wrote:
>> 
>> Hi Pat,
>> 
>> Check if the files are in place ( /Applications/JWildfire/lib/j-wildfire.jar 
>> ) 
>> If so then try in Terminal:
>> 
>> cd /Applications/JWildfire
>> sh start_mac.command
>> 
>> Cheers,
>> Ronni
>> Sent from Ronni's iPad4
>> 
>> 
>>> On 3 Jun 2014, at 6:22 pm, Pat  wrote:
>>> 
>>> Hi, Ronni,
>>> 
>>> Yes. Or rather, it is one of two.
>>> 
>>> Pat
>>> 
>>> 
>>>> On 3 Jun 2014, at 4:34 pm, Ronda Brown  wrote:
>>>> 
>>>> Hi Pat,
>>>> 
>>>> You are in your Administrator Account?
>>>> 
>>>> Cheers,
>>>> Ronni
>>>> Sent from Ronni's iPad4
>>>> 
>>>> 
>>>>> On 3 Jun 2014, at 3:47 pm, Pat  wrote:
>>>>> 
>>>>>> On 2 Jun 2014, at 7:08 pm, Neil Houghton  wrote:
>>>>>> 
>>>>>> Hi Pat,
>>>>>> 
>>>>>> As Ronni says, I take no responsibility for what you do running terminal 
>>>>>> commands – typos can do real damage!
>>>>>> 
>>>>>> According to this page 
>>>>>> <http://apple.stackexchange.com/questions/24262/what-is-the-difference-between-command-tool-and-sh-file-extensions>
>>>>>> .command - (Terminal shell script) Specifically associates a shell 
>>>>>> script with Terminal. Sometimes referred to as a "Terminal File."
>>>>>> So:
>>>>>> Have you checked in the “get info” for the file that it is set to “open 
>>>>>> with” terminal
>>>>>> Have you checked that you successfully changed the permissions to give 
>>>>>> yourself execute permission (use the “ls –l” command to check the actual 
>>>>>> permissions of the .command file – tell us what it says.
>>>>> Hi, Neil,
>>>>> 
>>>>> Here is the output from Terminal:
>>>>> 
>>>>> Last login: Tue Jun  3 14:40:33 on ttys001
>>>>> SpeedyGonzalez:~ pat$ cd /Applications/j-wildfire-1.62 
>>>>> SpeedyGonzalez:j-wildfire-1.62 pat$ ls -l
>>>>> total 18328
>>>>> -rw-r--r--@ 1 pat  staff67104 26 May 23:28 CHANGES.txt
>>>>> -rw-r--r--@ 1 pat  staff   391680 26 May 23:28 JWildfire.exe
>>>>> drwxr-xr-x@ 4 pat  staff  136  2 Jun 13:05 META-INF
>>>>> -rw-r--r--@ 1 pat  staff  232 26 May 23:28 README!!!.txt
>>>>> -rw-r

Re: Changing Get Info permissions

[Neil Houghton]

Hi Pat,

Glad you finally got it working. Obviously my automator app was different to
yours because I opted to open j-wildfire-launcher.jar directly, not by
invoking the start_mac.command. So, for me, my automator opened the launcher
window ­ the problem was that then pressing ³start² gave the errors as
logged.

After looking at your recipe, it occurred to me ³what happens if you just
open j-wildfire.jar ?²  and I found that just double-clicking that did,
indeed, open the wildfire application ­ which seemed to be working just fine
­ the problem is the launcher readme says:
> PLEASE DO NOT START THE j-wildfire.jar DIRECTLY!
> 
> If you start the j-wildfire.jar directly then JWildfire is started with
> default Java otions.
> 
> In the most cases you cannot render large images with those settings because
> not enough memory is reserved at startup. So even if you have plenty of memory
> it can not be used for rendering this way. Additionally, the wrong settings
> may cause slower rendering.
> 

However, it also says:
> HOW THE LAUNCHER WORKS
> --
> -
> It analyzes certain system settings to locate java runtimes on your system and
> automatically selects the most recent one. You can override the automatically
> selected version by selecting another entry in the listbox.
> 
> If the scanner did not find a java runtime (probably on Macs as I have no way
> to test this) you can manually add it. You must do this only once, of course.
> 
> The memory setting lets you specify the maximum amount of memory in megabytes
> to use. 
> This memory amount is only allocated if required. But there is no way to
> allocate more memory than here specified if JWildfire is already running.
> I. e., you must choose this value wisely.
> Example: 6000 MB should work fine to render images in high-end quality for
> print.

When I ran the launcher, it obviously found the Java runtime and I did set
the memory to 6000MB ­ it was just that hitting start didn¹t then launch
wildfire. However, the fact that wildfire runs means it can find the Java
runtime OK and the fact that if I open the launcher again, after changing
the memory allocation, it shows the allocation that was set at the last
opening presumably means that this setting is ³sticking² - however, since
the ³start² process fails, I¹m not sure if this setting has been passed to
the main wildfire app if I open it directly.

Anyway, I think my launcher problem might be down to my outdated OSX/Java.
Out of interest, I followed Ronni¹s terminal instructions to change the
permissions on start_mac.command and then run it ­ and it did, indeed run
and opened the launcher but, as before, hitting ³start² just caused it to
quit.

The following was reported in terminal (on running the command and before
hitting start):
> NRH-iMac27:j-wildfire-1.62 neil$ sh start_mac.command
> java.lang.NoSuchMethodException:
> java.util.prefs.MacOSXPreferences.WindowsRegOpenKey(int, [B, int)
> at java.lang.Class.getDeclaredMethod(Class.java:1973)
> at org.jwildfire.launcher.JDKScanner.(Unknown Source)
> at org.jwildfire.launcher.Launcher.scanForJDKs(Unknown Source)
> at org.jwildfire.launcher.Launcher.(Unknown Source)
> at org.jwildfire.launcher.Launcher$1.run(Unknown Source)
> at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
> at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:715)
> at java.awt.EventQueue.access$400(EventQueue.java:82)
> at java.awt.EventQueue$2.run(EventQueue.java:676)
> at java.awt.EventQueue$2.run(EventQueue.java:674)
> at java.security.AccessController.doPrivileged(Native Method)
> at 
> java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCont
> ext.java:86)
> at java.awt.EventQueue.dispatchEvent(EventQueue.java:685)
> at 
> java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:2
> 96)
> at 
> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:211)
> at 
> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:2
> 01)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:196)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:188)
> at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
> NRH-iMac27:j-wildfire-1.62 neil$
If debug is checked when ³start² is hit, the debug messages are also
reported in terminal:
> java.lang.Exception: Return code was 1 - see below for details:
> at org.jwildfire.launcher.Launcher.launchApp(Unknown Source)
> at org.jwildfire.launcher.Launcher.launchAction(Unknown Source)
> at org.jwildfire.launcher.Launcher.access$100(Unknown Source)
> at org

Re: Changing Get Info permissions

[Pat]

Thanks very much, Ronni and Neil! It’s working.

Ronni, your Terminal suggestion opened it.

Neil, your Automator recipe didn’t work as it was, but I managed to alter it so 
it did (beginner’s luck, I think, because I haven’t used Automator before).

So, the final recipe was: Get Specified Finder Items
wildfire-launcher.jar

Run Shell Script
cd /Applications/j-wildfire-1.62
sh start_mac.command

Get Specified Finder Items
j-wildfire.jar

And the application opens and runs. The application seems a little buggy for 
Mac, because it often shows a grey working area, but clicking around may get it 
going again. Or it might be because I use a stylus: some applications just 
don’t work very well with a stylus.

I will try Parallels soon, just to compare the two different operating systems.

Anyway, thank you both for spending the time and effort to help me with this. 
I’m very grateful.

Cheers,
Pat


On 3 Jun 2014, at 10:46 pm, Ronda Brown  wrote:

> Hi Pat,
> 
> Check if the files are in place ( /Applications/JWildfire/lib/j-wildfire.jar 
> ) 
> If so then try in Terminal:
> 
> cd /Applications/JWildfire
> sh start_mac.command
> 
> Cheers,
> Ronni
> Sent from Ronni's iPad4
> 
> 
> On 3 Jun 2014, at 6:22 pm, Pat  wrote:
> 
>> Hi, Ronni,
>> 
>> Yes. Or rather, it is one of two.
>> 
>> Pat
>> 
>> 
>> On 3 Jun 2014, at 4:34 pm, Ronda Brown  wrote:
>> 
>>> Hi Pat,
>>> 
>>> You are in your Administrator Account?
>>> 
>>> Cheers,
>>> Ronni
>>> Sent from Ronni's iPad4
>>> 
>>> 
>>> On 3 Jun 2014, at 3:47 pm, Pat  wrote:
>>> 
>>>> On 2 Jun 2014, at 7:08 pm, Neil Houghton  wrote:
>>>> 
>>>>> Hi Pat,
>>>>> 
>>>>> As Ronni says, I take no responsibility for what you do running terminal 
>>>>> commands – typos can do real damage!
>>>>> 
>>>>> According to this page 
>>>>> <http://apple.stackexchange.com/questions/24262/what-is-the-difference-between-command-tool-and-sh-file-extensions>
>>>>> .command - (Terminal shell script) Specifically associates a shell script 
>>>>> with Terminal. Sometimes referred to as a "Terminal File."
>>>>> So:
>>>>> Have you checked in the “get info” for the file that it is set to “open 
>>>>> with” terminal 
>>>>> Have you checked that you successfully changed the permissions to give 
>>>>> yourself execute permission (use the “ls –l” command to check the actual 
>>>>> permissions of the .command file – tell us what it says.
>>>> Hi, Neil,
>>>> 
>>>> Here is the output from Terminal:
>>>> 
>>>> Last login: Tue Jun  3 14:40:33 on ttys001
>>>> SpeedyGonzalez:~ pat$ cd /Applications/j-wildfire-1.62 
>>>> SpeedyGonzalez:j-wildfire-1.62 pat$ ls -l
>>>> total 18328
>>>> -rw-r--r--@ 1 pat  staff67104 26 May 23:28 CHANGES.txt
>>>> -rw-r--r--@ 1 pat  staff   391680 26 May 23:28 JWildfire.exe
>>>> drwxr-xr-x@ 4 pat  staff  136  2 Jun 13:05 META-INF
>>>> -rw-r--r--@ 1 pat  staff  232 26 May 23:28 README!!!.txt
>>>> -rw-r--r--+ 1 pat  staff  710 26 May 23:28 README_APPLET.txt
>>>> -rw-r--r--+ 1 pat  staff 2554 26 May 23:28 README_LAUNCH.txt
>>>> -rw-r--r--@ 1 pat  staff  625 26 May 23:28 README_SUPPORT.txt
>>>> -rw-r--r--@ 1 pat  staff  2619817 26 May 23:28 j-wildfire-applet.jar
>>>> -rw-r--r--@ 1 pat  staff  6266569 26 May 23:28 j-wildfire-launcher.jar
>>>> drwxr-xr-x@ 4 pat  staff  136  2 Jun 13:05 lib
>>>> -rw-r--r--@ 1 pat  staff   33 26 May 23:28 start_linux.sh
>>>> -rwxr--r--@ 1 pat  staff   33  2 Jun 16:24 start_mac.command
>>>> -rw-r--r--@ 1 pat  staff   40 26 May 23:28 start_windows.bat
>>>> SpeedyGonzalez:j-wildfire-1.62 pat$ 
>>>> 
>>>> The start_mac.command is executable  and is supposed to start the  
>>>> j-wildfire-launcher.jar  which is not executable which is in the directory 
>>>> lib, which is executable. I tried the same Terminal method on it, but here 
>>>> is what Terminal says about that:
>>>> 
>>>> Last login: Tue Jun  3 14:41:03 on ttys000
>>>> SpeedyGonz

Re: Changing Get Info permissions

[Ronda Brown]

Hi Pat,

Check if the files are in place ( /Applications/JWildfire/lib/j-wildfire.jar ) 
If so then try in Terminal:

cd /Applications/JWildfire
sh start_mac.command

Cheers,
Ronni
Sent from Ronni's iPad4


> On 3 Jun 2014, at 6:22 pm, Pat  wrote:
> 
> Hi, Ronni,
> 
> Yes. Or rather, it is one of two.
> 
> Pat
> 
> 
>> On 3 Jun 2014, at 4:34 pm, Ronda Brown  wrote:
>> 
>> Hi Pat,
>> 
>> You are in your Administrator Account?
>> 
>> Cheers,
>> Ronni
>> Sent from Ronni's iPad4
>> 
>> 
>>> On 3 Jun 2014, at 3:47 pm, Pat  wrote:
>>> 
>>>> On 2 Jun 2014, at 7:08 pm, Neil Houghton  wrote:
>>>> 
>>>> Hi Pat,
>>>> 
>>>> As Ronni says, I take no responsibility for what you do running terminal 
>>>> commands – typos can do real damage!
>>>> 
>>>> According to this page 
>>>> <http://apple.stackexchange.com/questions/24262/what-is-the-difference-between-command-tool-and-sh-file-extensions>
>>>> .command - (Terminal shell script) Specifically associates a shell script 
>>>> with Terminal. Sometimes referred to as a "Terminal File."
>>>> So:
>>>> Have you checked in the “get info” for the file that it is set to “open 
>>>> with” terminal
>>>> Have you checked that you successfully changed the permissions to give 
>>>> yourself execute permission (use the “ls –l” command to check the actual 
>>>> permissions of the .command file – tell us what it says.
>>> Hi, Neil,
>>> 
>>> Here is the output from Terminal:
>>> 
>>> Last login: Tue Jun  3 14:40:33 on ttys001
>>> SpeedyGonzalez:~ pat$ cd /Applications/j-wildfire-1.62 
>>> SpeedyGonzalez:j-wildfire-1.62 pat$ ls -l
>>> total 18328
>>> -rw-r--r--@ 1 pat  staff67104 26 May 23:28 CHANGES.txt
>>> -rw-r--r--@ 1 pat  staff   391680 26 May 23:28 JWildfire.exe
>>> drwxr-xr-x@ 4 pat  staff  136  2 Jun 13:05 META-INF
>>> -rw-r--r--@ 1 pat  staff  232 26 May 23:28 README!!!.txt
>>> -rw-r--r--+ 1 pat  staff  710 26 May 23:28 README_APPLET.txt
>>> -rw-r--r--+ 1 pat  staff 2554 26 May 23:28 README_LAUNCH.txt
>>> -rw-r--r--@ 1 pat  staff  625 26 May 23:28 README_SUPPORT.txt
>>> -rw-r--r--@ 1 pat  staff  2619817 26 May 23:28 j-wildfire-applet.jar
>>> -rw-r--r--@ 1 pat  staff  6266569 26 May 23:28 j-wildfire-launcher.jar
>>> drwxr-xr-x@ 4 pat  staff  136  2 Jun 13:05 lib
>>> -rw-r--r--@ 1 pat  staff   33 26 May 23:28 start_linux.sh
>>> -rwxr--r--@ 1 pat  staff   33  2 Jun 16:24 start_mac.command
>>> -rw-r--r--@ 1 pat  staff   40 26 May 23:28 start_windows.bat
>>> SpeedyGonzalez:j-wildfire-1.62 pat$ 
>>> 
>>> The start_mac.command is executable  and is supposed to start the  
>>> j-wildfire-launcher.jar  which is not executable which is in the directory 
>>> lib, which is executable. I tried the same Terminal method on it, but here 
>>> is what Terminal says about that:
>>> 
>>> Last login: Tue Jun  3 14:41:03 on ttys000
>>> SpeedyGonzalez:~ pat$ /Applications/j-wildfire-1.62/start_mac.command ; 
>>> exit;
>>> Unable to access jarfile j-wildfire-launcher.jar
>>> logout
>>> 
>>> [Process completed]
>>>> When you say “Terminal didn’t fix the permission problems” did you get 
>>>> some error message in terminal when running the chmod command?
>>> There were no error messages, it’s just that there were no visible changes 
>>> in Get Info, and I couldn’t start the program.
>>> 
>>>> Alternatively, unless you really want to learn a lot more about terminal, 
>>>> permissions etc, then it may well be easier/safer to just try the Windows 
>>>> program in Parallels ;o)
>>> 
>>> I haven’t yet tried Parallels yet, but will do so.
>>> 
>>>> Out of interest, what is this program?
>>> 
>>> It can create very intricate and beautiful images. If you look at images of 
>>> ‘Flame Fractals’ on Google, you will see what I mean.
>>> 
>>> Thank you very much for your assistance! It is much appreciated.
>>> 
>>> Pat
>>> 
>>> 
>>>> Cheers
>>>> 
>>>> 
>>>> 
>>>> Neil
>>>> -- 
>>>> Neil R. Houghton
>>>> Albany, Western Australia
>>>> Tel: +61 8 9841 6063
>>>> Email: n...@possumology.com
>>&

Re: Changing Get Info permissions

[Neil Houghton]

And if you get it working, why not make it a Mac app using automator ­ it¹s
pretty easy (took me a couple of minutes):

1. Open automator 
2. From the choose template dialogue choose ³application²
3. Drag the j-wildfire-launcher.jar file onto the workflow window
4. You will see that a ³get specified finder items² action has been added
with the path to the launcher
5. From the ³Actions² library, select ³open finder items² and drag it onto
the workflow window (below the get items action)
6. In the menubar choose File/save as and save the application into your
³applications² folder (or anywhere else you want it) with a suitable name
(eg Wildfire). 
7. Quit automator

That¹s it ­ go to your applications and double click ³Wildfire² and it
should open the launcher. Then why not give it a better icon ­ copy a
suitable image ­ plenty here 
then do ³get info² on your new Wildfire app and select the icon and paste
the image you just copied ­ now your new app has an appropriate icon ;o)

Well, I find it fun ;o)


Cheers



Neil
-- 
Neil R. Houghton
Albany, Western Australia
Tel: +61 8 9841 6063
Email: n...@possumology.com


on 3/6/14 19:25, Neil Houghton at n...@possumology.com wrote:

> Hi Pat,
> 
> This may or may not help you ;o)
> 
> 



-- The WA Macintosh User Group Mailing List --
Archives - 
Guidelines - 
Settings & Unsubscribe - 

Re: Changing Get Info permissions

[Neil Houghton]

.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:2
> 96)
> at 
> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:211)
> at 
> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:2
> 01)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:196)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:188)
> at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
> 
> 
> Attempting to launch JWildfire using the command:
> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin/java
> -Xms256m -Xmx6000m -cp "/Applications/User
> Utilities/j-wildfire-1.62/lib/j-wildfire.jar" org.jwildfire.swing.Desktop


Now I really should get back to more pressing matters, so I can¹t let myself
get distracted by looking at this log ­ and I presume you are running a more
up-to-date OSX and Java, so you may find you have different messages - or it
may even be that my old system IS the problem and it works OK for you ;o)
- either way, it would be worth you launching the j-wildfire-launcher.jar
directly as it should get you further down the track and at least give you a
message log to post to the forums.

Interestingly, I tried launching the cut-down applet - j-wildfire-applet.jar
­ and it runs just fine although, as the readme says:
> The JWildfireApplet introduced with version 1.04 is just for playing around
> and has only two functions:
> *  create random fractals and display them on the screen using a progressive
> display 
> *  export the parameters of the currently displayed fractal (if you like it)
> to the clipboard for further processing in the full application
So there is not much to do with it ­ but the create next and to clipboard
buttons both work!



Anyway, something to try ­ HTH


Cheers




Neil
-- 
Neil R. Houghton
Albany, Western Australia
Tel: +61 8 9841 6063
Email: n...@possumology.com






on 3/6/14 15:47, Pat at clamsh...@iinet.net.au wrote:

> On 2 Jun 2014, at 7:08 pm, Neil Houghton  wrote:
> 
>> Re: Changing Get Info permissions
>> Hi Pat,
>> 
>> As Ronni says, I take no responsibility for what you do running terminal
>> commands ­ typos can do real damage!
>> 
>> According to this page
>> <http://apple.stackexchange.com/questions/24262/what-is-the-difference-betwee
>> n-command-tool-and-sh-file-extensions>
>> * .command - (Terminal shell script) Specifically associates a shell script
>> with Terminal. Sometimes referred to as a "Terminal File."
>> So:
>> * Have you checked in the ³get info² for the file that it is set to ³open
>> with² terminal 
>> * Have you checked that you successfully changed the permissions to give
>> yourself execute permission (use the ³ls ­l² command to check the actual
>> permissions of the .command file ­ tell us what it says.
> Hi, Neil,
> 
> Here is the output from Terminal:
> 
> Last login: Tue Jun  3 14:40:33 on ttys001
> SpeedyGonzalez:~ pat$ cd /Applications/j-wildfire-1.62
> SpeedyGonzalez:j-wildfire-1.62 pat$ ls -l
> total 18328
> -rw-r--r--@ 1 pat  staff67104 26 May 23:28 CHANGES.txt
> -rw-r--r--@ 1 pat  staff   391680 26 May 23:28 JWildfire.exe
> drwxr-xr-x@ 4 pat  staff  136  2 Jun 13:05 META-INF
> -rw-r--r--@ 1 pat  staff  232 26 May 23:28 README!!!.txt
> -rw-r--r--+ 1 pat  staff  710 26 May 23:28 README_APPLET.txt
> -rw-r--r--+ 1 pat  staff 2554 26 May 23:28 README_LAUNCH.txt
> -rw-r--r--@ 1 pat  staff  625 26 May 23:28 README_SUPPORT.txt
> -rw-r--r--@ 1 pat  staff  2619817 26 May 23:28 j-wildfire-applet.jar
> -rw-r--r--@ 1 pat  staff  6266569 26 May 23:28 j-wildfire-launcher.jar
> drwxr-xr-x@ 4 pat  staff  136  2 Jun 13:05 lib
> -rw-r--r--@ 1 pat  staff   33 26 May 23:28 start_linux.sh
> -rwxr--r--@ 1 pat  staff   33  2 Jun 16:24 start_mac.command
> -rw-r--r--@ 1 pat  staff   40 26 May 23:28 start_windows.bat
> SpeedyGonzalez:j-wildfire-1.62 pat$
> 
> The start_mac.command is executable  and is supposed to start the
> j-wildfire-launcher.jar  which is not executable which is in the directory
> lib, which is executable. I tried the same Terminal method on it, but here is
> what Terminal says about that:
> 
> Last login: Tue Jun  3 14:41:03 on ttys000
> SpeedyGonzalez:~ pat$ /Applications/j-wildfire-1.62/start_mac.command ; exit;
> Unable to access jarfile j-wildfire-launcher.jar
> logout
> 
> [Process completed]
>> * When you say ³Terminal didn¹t fix the permission problems² did you get some
>> error message in terminal when running the chmod command?
> There were no error messages, it¹s just that there were no visible changes in
> Get Info, and I couldn¹t start the progr

Re: Changing Get Info permissions

[Pat]

Hi, Ronni,

Yes. Or rather, it is one of two.

Pat


On 3 Jun 2014, at 4:34 pm, Ronda Brown  wrote:

> Hi Pat,
> 
> You are in your Administrator Account?
> 
> Cheers,
> Ronni
> Sent from Ronni's iPad4
> 
> 
> On 3 Jun 2014, at 3:47 pm, Pat  wrote:
> 
>> On 2 Jun 2014, at 7:08 pm, Neil Houghton  wrote:
>> 
>>> Hi Pat,
>>> 
>>> As Ronni says, I take no responsibility for what you do running terminal 
>>> commands – typos can do real damage!
>>> 
>>> According to this page 
>>> <http://apple.stackexchange.com/questions/24262/what-is-the-difference-between-command-tool-and-sh-file-extensions>
>>> .command - (Terminal shell script) Specifically associates a shell script 
>>> with Terminal. Sometimes referred to as a "Terminal File."
>>> So:
>>> Have you checked in the “get info” for the file that it is set to “open 
>>> with” terminal
>>> Have you checked that you successfully changed the permissions to give 
>>> yourself execute permission (use the “ls –l” command to check the actual 
>>> permissions of the .command file – tell us what it says.
>> Hi, Neil,
>> 
>> Here is the output from Terminal:
>> 
>> Last login: Tue Jun  3 14:40:33 on ttys001
>> SpeedyGonzalez:~ pat$ cd /Applications/j-wildfire-1.62 
>> SpeedyGonzalez:j-wildfire-1.62 pat$ ls -l
>> total 18328
>> -rw-r--r--@ 1 pat  staff67104 26 May 23:28 CHANGES.txt
>> -rw-r--r--@ 1 pat  staff   391680 26 May 23:28 JWildfire.exe
>> drwxr-xr-x@ 4 pat  staff  136  2 Jun 13:05 META-INF
>> -rw-r--r--@ 1 pat  staff  232 26 May 23:28 README!!!.txt
>> -rw-r--r--+ 1 pat  staff  710 26 May 23:28 README_APPLET.txt
>> -rw-r--r--+ 1 pat  staff 2554 26 May 23:28 README_LAUNCH.txt
>> -rw-r--r--@ 1 pat  staff  625 26 May 23:28 README_SUPPORT.txt
>> -rw-r--r--@ 1 pat  staff  2619817 26 May 23:28 j-wildfire-applet.jar
>> -rw-r--r--@ 1 pat  staff  6266569 26 May 23:28 j-wildfire-launcher.jar
>> drwxr-xr-x@ 4 pat  staff  136  2 Jun 13:05 lib
>> -rw-r--r--@ 1 pat  staff   33 26 May 23:28 start_linux.sh
>> -rwxr--r--@ 1 pat  staff   33  2 Jun 16:24 start_mac.command
>> -rw-r--r--@ 1 pat  staff   40 26 May 23:28 start_windows.bat
>> SpeedyGonzalez:j-wildfire-1.62 pat$ 
>> 
>> The start_mac.command is executable  and is supposed to start the  
>> j-wildfire-launcher.jar  which is not executable which is in the directory 
>> lib, which is executable. I tried the same Terminal method on it, but here 
>> is what Terminal says about that:
>> 
>> Last login: Tue Jun  3 14:41:03 on ttys000
>> SpeedyGonzalez:~ pat$ /Applications/j-wildfire-1.62/start_mac.command ; exit;
>> Unable to access jarfile j-wildfire-launcher.jar
>> logout
>> 
>> [Process completed]
>>> When you say “Terminal didn’t fix the permission problems” did you get some 
>>> error message in terminal when running the chmod command?
>> There were no error messages, it’s just that there were no visible changes 
>> in Get Info, and I couldn’t start the program.
>> 
>>> Alternatively, unless you really want to learn a lot more about terminal, 
>>> permissions etc, then it may well be easier/safer to just try the Windows 
>>> program in Parallels ;o)
>> 
>> I haven’t yet tried Parallels yet, but will do so.
>> 
>>> Out of interest, what is this program?
>> 
>> It can create very intricate and beautiful images. If you look at images of 
>> ‘Flame Fractals’ on Google, you will see what I mean.
>> 
>> Thank you very much for your assistance! It is much appreciated.
>> 
>> Pat
>> 
>> 
>>> Cheers
>>> 
>>> 
>>> 
>>> Neil
>>> -- 
>>> Neil R. Houghton
>>> Albany, Western Australia
>>> Tel: +61 8 9841 6063
>>> Email: n...@possumology.com
>>> 
>>> 
>>> 
>>> 
>>> 
>>> on 2/6/14 16:32, Pat at clamsh...@iinet.net.au wrote:
>>> 
>>>> Hi, Ronni and Neil,
>>>> 
>>>> Thank you for the information and the cautions. Yes, I am cautious, but I 
>>>> trust the developer. It is another case of interesting software written 
>>>> for Windows and later, as an afterthought, ported to Mac. The forum shows 
>>>> a lot of other disappointed Mac users also have trouble.
>>>> 
>>>> Unfortunately, Terminal didn’t fix the permission problems. I tried both 
>>>> methods of typing the path and dragging the files.
>>>

Re: Changing Get Info permissions

[Ronda Brown]

Hi Pat,

You are in your Administrator Account?

Cheers,
Ronni
Sent from Ronni's iPad4


> On 3 Jun 2014, at 3:47 pm, Pat  wrote:
> 
>> On 2 Jun 2014, at 7:08 pm, Neil Houghton  wrote:
>> 
>> Hi Pat,
>> 
>> As Ronni says, I take no responsibility for what you do running terminal 
>> commands – typos can do real damage!
>> 
>> According to this page 
>> <http://apple.stackexchange.com/questions/24262/what-is-the-difference-between-command-tool-and-sh-file-extensions>
>> .command - (Terminal shell script) Specifically associates a shell script 
>> with Terminal. Sometimes referred to as a "Terminal File."
>> So:
>> Have you checked in the “get info” for the file that it is set to “open 
>> with” terminal
>> Have you checked that you successfully changed the permissions to give 
>> yourself execute permission (use the “ls –l” command to check the actual 
>> permissions of the .command file – tell us what it says.
> Hi, Neil,
> 
> Here is the output from Terminal:
> 
> Last login: Tue Jun  3 14:40:33 on ttys001
> SpeedyGonzalez:~ pat$ cd /Applications/j-wildfire-1.62 
> SpeedyGonzalez:j-wildfire-1.62 pat$ ls -l
> total 18328
> -rw-r--r--@ 1 pat  staff67104 26 May 23:28 CHANGES.txt
> -rw-r--r--@ 1 pat  staff   391680 26 May 23:28 JWildfire.exe
> drwxr-xr-x@ 4 pat  staff  136  2 Jun 13:05 META-INF
> -rw-r--r--@ 1 pat  staff  232 26 May 23:28 README!!!.txt
> -rw-r--r--+ 1 pat  staff  710 26 May 23:28 README_APPLET.txt
> -rw-r--r--+ 1 pat  staff 2554 26 May 23:28 README_LAUNCH.txt
> -rw-r--r--@ 1 pat  staff  625 26 May 23:28 README_SUPPORT.txt
> -rw-r--r--@ 1 pat  staff  2619817 26 May 23:28 j-wildfire-applet.jar
> -rw-r--r--@ 1 pat  staff  6266569 26 May 23:28 j-wildfire-launcher.jar
> drwxr-xr-x@ 4 pat  staff  136  2 Jun 13:05 lib
> -rw-r--r--@ 1 pat  staff   33 26 May 23:28 start_linux.sh
> -rwxr--r--@ 1 pat  staff   33  2 Jun 16:24 start_mac.command
> -rw-r--r--@ 1 pat  staff   40 26 May 23:28 start_windows.bat
> SpeedyGonzalez:j-wildfire-1.62 pat$ 
> 
> The start_mac.command is executable  and is supposed to start the  
> j-wildfire-launcher.jar  which is not executable which is in the directory 
> lib, which is executable. I tried the same Terminal method on it, but here is 
> what Terminal says about that:
> 
> Last login: Tue Jun  3 14:41:03 on ttys000
> SpeedyGonzalez:~ pat$ /Applications/j-wildfire-1.62/start_mac.command ; exit;
> Unable to access jarfile j-wildfire-launcher.jar
> logout
> 
> [Process completed]
>> When you say “Terminal didn’t fix the permission problems” did you get some 
>> error message in terminal when running the chmod command?
> There were no error messages, it’s just that there were no visible changes in 
> Get Info, and I couldn’t start the program.
> 
>> Alternatively, unless you really want to learn a lot more about terminal, 
>> permissions etc, then it may well be easier/safer to just try the Windows 
>> program in Parallels ;o)
> 
> I haven’t yet tried Parallels yet, but will do so.
> 
>> Out of interest, what is this program?
> 
> It can create very intricate and beautiful images. If you look at images of 
> ‘Flame Fractals’ on Google, you will see what I mean.
> 
> Thank you very much for your assistance! It is much appreciated.
> 
> Pat
> 
> 
>> Cheers
>> 
>> 
>> 
>> Neil
>> -- 
>> Neil R. Houghton
>> Albany, Western Australia
>> Tel: +61 8 9841 6063
>> Email: n...@possumology.com
>> 
>> 
>> 
>> 
>> 
>> on 2/6/14 16:32, Pat at clamsh...@iinet.net.au wrote:
>> 
>>> Hi, Ronni and Neil,
>>> 
>>> Thank you for the information and the cautions. Yes, I am cautious, but I 
>>> trust the developer. It is another case of interesting software written for 
>>> Windows and later, as an afterthought, ported to Mac. The forum shows a lot 
>>> of other disappointed Mac users also have trouble.
>>> 
>>> Unfortunately, Terminal didn’t fix the permission problems. I tried both 
>>> methods of typing the path and dragging the files.
>>> 
>>> Maybe I will have to fire up Parallels again, sigh.
>>> 
>>> Thanks!
>>> Pat
>>> 
>>> 
>>> On 2 Jun 2014, at 2:00 pm, Ronda Brown  wrote:
>>> 
>>>> Hi Pat,
>>>> 
>>>> As Neil has mentioned be very careful that you know what this 
>>>> Program/Script is and how safe it is. Not knowing what the program is or 
>>>> why you have to run this script, I hesitate to recommend anything.
>>

Re: Changing Get Info permissions

[Pat]

On 2 Jun 2014, at 7:08 pm, Neil Houghton  wrote:

> Hi Pat,
> 
> As Ronni says, I take no responsibility for what you do running terminal 
> commands – typos can do real damage!
> 
> According to this page 
> <http://apple.stackexchange.com/questions/24262/what-is-the-difference-between-command-tool-and-sh-file-extensions>
> .command - (Terminal shell script) Specifically associates a shell script 
> with Terminal. Sometimes referred to as a "Terminal File."
> So:
> Have you checked in the “get info” for the file that it is set to “open with” 
> terminal
> Have you checked that you successfully changed the permissions to give 
> yourself execute permission (use the “ls –l” command to check the actual 
> permissions of the .command file – tell us what it says.
Hi, Neil,

Here is the output from Terminal:

Last login: Tue Jun  3 14:40:33 on ttys001
SpeedyGonzalez:~ pat$ cd /Applications/j-wildfire-1.62 
SpeedyGonzalez:j-wildfire-1.62 pat$ ls -l
total 18328
-rw-r--r--@ 1 pat  staff67104 26 May 23:28 CHANGES.txt
-rw-r--r--@ 1 pat  staff   391680 26 May 23:28 JWildfire.exe
drwxr-xr-x@ 4 pat  staff  136  2 Jun 13:05 META-INF
-rw-r--r--@ 1 pat  staff  232 26 May 23:28 README!!!.txt
-rw-r--r--+ 1 pat  staff  710 26 May 23:28 README_APPLET.txt
-rw-r--r--+ 1 pat  staff 2554 26 May 23:28 README_LAUNCH.txt
-rw-r--r--@ 1 pat  staff  625 26 May 23:28 README_SUPPORT.txt
-rw-r--r--@ 1 pat  staff  2619817 26 May 23:28 j-wildfire-applet.jar
-rw-r--r--@ 1 pat  staff  6266569 26 May 23:28 j-wildfire-launcher.jar
drwxr-xr-x@ 4 pat  staff  136  2 Jun 13:05 lib
-rw-r--r--@ 1 pat  staff   33 26 May 23:28 start_linux.sh
-rwxr--r--@ 1 pat  staff   33  2 Jun 16:24 start_mac.command
-rw-r--r--@ 1 pat  staff   40 26 May 23:28 start_windows.bat
SpeedyGonzalez:j-wildfire-1.62 pat$ 

The start_mac.command is executable  and is supposed to start the  
j-wildfire-launcher.jar  which is not executable which is in the directory lib, 
which is executable. I tried the same Terminal method on it, but here is what 
Terminal says about that:

Last login: Tue Jun  3 14:41:03 on ttys000
SpeedyGonzalez:~ pat$ /Applications/j-wildfire-1.62/start_mac.command ; exit;
Unable to access jarfile j-wildfire-launcher.jar
logout

[Process completed]
> When you say “Terminal didn’t fix the permission problems” did you get some 
> error message in terminal when running the chmod command?
There were no error messages, it’s just that there were no visible changes in 
Get Info, and I couldn’t start the program.

> Alternatively, unless you really want to learn a lot more about terminal, 
> permissions etc, then it may well be easier/safer to just try the Windows 
> program in Parallels ;o)

I haven’t yet tried Parallels yet, but will do so.

> Out of interest, what is this program?

It can create very intricate and beautiful images. If you look at images of 
‘Flame Fractals’ on Google, you will see what I mean.

Thank you very much for your assistance! It is much appreciated.

Pat


> Cheers
> 
> 
> 
> Neil
> -- 
> Neil R. Houghton
> Albany, Western Australia
> Tel: +61 8 9841 6063
> Email: n...@possumology.com
> 
> 
> 
> 
> 
> on 2/6/14 16:32, Pat at clamsh...@iinet.net.au wrote:
> 
>> Hi, Ronni and Neil,
>> 
>> Thank you for the information and the cautions. Yes, I am cautious, but I 
>> trust the developer. It is another case of interesting software written for 
>> Windows and later, as an afterthought, ported to Mac. The forum shows a lot 
>> of other disappointed Mac users also have trouble.
>> 
>> Unfortunately, Terminal didn’t fix the permission problems. I tried both 
>> methods of typing the path and dragging the files.
>> 
>> Maybe I will have to fire up Parallels again, sigh.
>> 
>> Thanks!
>> Pat
>> 
>> 
>> On 2 Jun 2014, at 2:00 pm, Ronda Brown  wrote:
>> 
>>> Hi Pat,
>>> 
>>> As Neil has mentioned be very careful that you know what this 
>>> Program/Script is and how safe it is. Not knowing what the program is or 
>>> why you have to run this script, I hesitate to recommend anything.
>>> 
>>> By the sound of what you have said, you would need to use Terminal to 
>>> change the permissions on such a script.
>>> You need to set 'execute' on the file for it to allow you to run it.
>>> Something like this:
>>> - Open Terminal in the Applications/Utilities folder and type this:
>>> 
>>> chmod u+x /path/to/file.command
>>> u is the owner of the file, +x adds 'execute', so u+x gives the owner of 
>>> the file the ability to execute it
>>> --
>>> Or Something like this perhaps:
>>> - Open Terminal in

Re: Changing Get Info permissions

[Neil Houghton]

Hi Pat,

As Ronni says, I take no responsibility for what you do running terminal
commands ­ typos can do real damage!

According to this page
<http://apple.stackexchange.com/questions/24262/what-is-the-difference-betwe
en-command-tool-and-sh-file-extensions>
* .command - (Terminal shell script) Specifically associates a shell script
with Terminal. Sometimes referred to as a "Terminal File."

So:
* Have you checked in the ³get info² for the file that it is set to ³open
with² terminal 
* Have you checked that you successfully changed the permissions to give
yourself execute permission (use the ³ls ­l² command to check the actual
permissions of the .command file ­ tell us what it says.
* When you say ³Terminal didn¹t fix the permission problems² did you get
some error message in terminal when running the chmod command?

Alternatively, unless you really want to learn a lot more about terminal,
permissions etc, then it may well be easier/safer to just try the Windows
program in Parallels ;o)


Out of interest, what is this program?



Cheers



Neil
-- 
Neil R. Houghton
Albany, Western Australia
Tel: +61 8 9841 6063
Email: n...@possumology.com





on 2/6/14 16:32, Pat at clamsh...@iinet.net.au wrote:

> Hi, Ronni and Neil,
> 
> Thank you for the information and the cautions. Yes, I am cautious, but I
> trust the developer. It is another case of interesting software written for
> Windows and later, as an afterthought, ported to Mac. The forum shows a lot of
> other disappointed Mac users also have trouble.
> 
> Unfortunately, Terminal didn¹t fix the permission problems. I tried both
> methods of typing the path and dragging the files.
> 
> Maybe I will have to fire up Parallels again, sigh.
> 
> Thanks!
> Pat
> 
> 
> On 2 Jun 2014, at 2:00 pm, Ronda Brown  wrote:
> 
>> Hi Pat,
>> 
>> As Neil has mentioned be very careful that you know what this Program/Script
>> is and how safe it is. Not knowing what the program is or why you have to run
>> this script, I hesitate to recommend anything.
>> 
>> By the sound of what you have said, you would need to use Terminal to change
>> the permissions on such a script.
>> You need to set 'execute' on the file for it to allow you to run it.
>> Something like this:
>> - Open Terminal in the Applications/Utilities folder and type this:
>> 
>> chmod u+x /path/to/file.command
>> u is the owner of the file, +x adds 'execute', so u+x gives the owner of the
>> file the ability to execute it
>> --
>> Or Something like this perhaps:
>> - Open Terminal in the /Applications/Utilities/ folder and type in:
>>  
>> chmod u+x
>>  
>> followed by a space. Drag the file into the open Terminal window and press
>> Enter.
>>  
>> Controlling permissions to this extent is normally only needed by people who
>> work under the hood and is therefore not an option in the Finder.
>> 
>> I take absolutely NO responsibility at all if you decide to try either of the
>> above Terminal Commands and something goes wrong. I would strongly suggest
>> you get in touch with the developer who built the special script to find out
>> how to run it.
>> 
>> Cheers,
>> Ronni  
>> Sent from Ronni's iPad4
>> 
>> 
>> On 2 Jun 2014, at 1:35 pm, Neil Houghton  wrote:
>> 
>>> Re: Changing Get Info permissions Hi Pat,
>>> 
>>> There are three specific permissions on Unix-like systems that apply to each
>>> class: 
>>> * Read 
>>> * Write 
>>> * Execute
>>> See more here: <http://en.wikipedia.org/wiki/File_system_permissions>
>>> 
>>> So to run the file, read/write is not sufficient.
>>> 
>>> However, I guess my questions would be:
>>> 1. Do you really want to be running a program on your Mac from someone who
>>> can¹t be bothered writing a proper Mac program?
>>> 2. What do you know about this program/script ­ can it be trusted?
>>> 
>>> 
>>> Just my 2c worth.
>>> 
>>> 
>>> Cheers
>>> 
>>> 
>>> Neil



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>

Re: Changing Get Info permissions

[Pat]

Yes. I have set it to ‘ask’.

Pat


On 2 Jun 2014, at 5:09 pm, Ronda Brown  wrote:

> Hi Pat,
> 
> Does the Forum mention that you need Java installed for this application 
> script to run?
> 
> Sent from Ronni's iPad4






> 
> On 2 Jun 2014, at 4:32 pm, Pat  wrote:
> 
>> Hi, Ronni and Neil,
>> 
>> Thank you for the information and the cautions. Yes, I am cautious, but I 
>> trust the developer. It is another case of interesting software written for 
>> Windows and later, as an afterthought, ported to Mac. The forum shows a lot 
>> of other disappointed Mac users also have trouble.
>> 
>> Unfortunately, Terminal didn’t fix the permission problems. I tried both 
>> methods of typing the path and dragging the files.
>> 
>> Maybe I will have to fire up Parallels again, sigh.
>> 
>> Thanks!
>> Pat
>> 
>> 
>> On 2 Jun 2014, at 2:00 pm, Ronda Brown  wrote:
>> 
>>> Hi Pat,
>>> 
>>> As Neil has mentioned be very careful that you know what this 
>>> Program/Script is and how safe it is. Not knowing what the program is or 
>>> why you have to run this script, I hesitate to recommend anything.
>>> 
>>> By the sound of what you have said, you would need to use Terminal to 
>>> change the permissions on such a script.
>>> You need to set 'execute' on the file for it to allow you to run it.
>>> Something like this:
>>> - Open Terminal in the Applications/Utilities folder and type this:
>>> 
>>> chmod u+x /path/to/file.command
>>> u is the owner of the file, +x adds 'execute', so u+x gives the owner of 
>>> the file the ability to execute it
>>> --
>>> Or Something like this perhaps:
>>> - Open Terminal in the /Applications/Utilities/ folder and type in:
>>>  
>>> chmod u+x
>>>  
>>> followed by a space. Drag the file into the open Terminal window and press 
>>> Enter.
>>>  
>>> Controlling permissions to this extent is normally only needed by people 
>>> who work under the hood and is therefore not an option in the Finder.
>>> 
>>> I take absolutely NO responsibility at all if you decide to try either of 
>>> the above Terminal Commands and something goes wrong. I would strongly 
>>> suggest you get in touch with the developer who built the special script to 
>>> find out how to run it.
>>> 
>>> Cheers,
>>> Ronni  
>>> Sent from Ronni's iPad4
>>> 
>>> 
>>> On 2 Jun 2014, at 1:35 pm, Neil Houghton  wrote:
>>> 
>>>> Hi Pat,
>>>> 
>>>> There are three specific permissions on Unix-like systems that apply to 
>>>> each class: 
>>>> Read
>>>> Write
>>>> Execute
>>>> See more here: <http://en.wikipedia.org/wiki/File_system_permissions>
>>>> 
>>>> So to run the file, read/write is not sufficient.
>>>> 
>>>> However, I guess my questions would be:
>>>> Do you really want to be running a program on your Mac from someone who 
>>>> can’t be bothered writing a proper Mac program?
>>>> What do you know about this program/script – can it be trusted?
>>>> 
>>>> 
>>>> Just my 2c worth.
>>>> 
>>>> 
>>>> Cheers
>>>> 
>>>> 
>>>> Neil
>>>> -- 
>>>> Neil R. Houghton
>>>> Albany, Western Australia
>>>> Tel: +61 8 9841 6063
>>>> Email: n...@possumology.com
>>>> 
>>>> 
>>>> 
>>>> on 2/6/14 13:16, Pat at clamsh...@iinet.net.au wrote:
>>>> 
>>>> > Hi, I downloaded a small graphics program which contains a special 
>>>> > script for 
>>>> > starting the program on the Mac. However, these messages appear when I 
>>>> > click 
>>>> > it:
>>>> > 
>>>> > "The file “start_mac.command” could not be executed because you do not 
>>>> > have 
>>>> > appropriate access privileges.
>>>> > 
>>>> > "To view or change access privileges, select the file in the Finder and 
>>>> > choose 
>>>> > File > Get Info."
>>>> > 
>>>> > The Get Info panel says that I do have read and write privileges. I 
>>>> > tried 
>>>> > restarting the computer, and searched WAMUG f

Re: Changing Get Info permissions

[Ronda Brown]

Hi Pat,

Does the Forum mention that you need Java installed for this application script 
to run?

Sent from Ronni's iPad4


> On 2 Jun 2014, at 4:32 pm, Pat  wrote:
> 
> Hi, Ronni and Neil,
> 
> Thank you for the information and the cautions. Yes, I am cautious, but I 
> trust the developer. It is another case of interesting software written for 
> Windows and later, as an afterthought, ported to Mac. The forum shows a lot 
> of other disappointed Mac users also have trouble.
> 
> Unfortunately, Terminal didn’t fix the permission problems. I tried both 
> methods of typing the path and dragging the files.
> 
> Maybe I will have to fire up Parallels again, sigh.
> 
> Thanks!
> Pat
> 
> 
>> On 2 Jun 2014, at 2:00 pm, Ronda Brown  wrote:
>> 
>> Hi Pat,
>> 
>> As Neil has mentioned be very careful that you know what this Program/Script 
>> is and how safe it is. Not knowing what the program is or why you have to 
>> run this script, I hesitate to recommend anything.
>> 
>> By the sound of what you have said, you would need to use Terminal to change 
>> the permissions on such a script.
>> You need to set 'execute' on the file for it to allow you to run it.
>> Something like this:
>> - Open Terminal in the Applications/Utilities folder and type this:
>> 
>> chmod u+x /path/to/file.command
>> u is the owner of the file, +x adds 'execute', so u+x gives the owner of the 
>> file the ability to execute it
>> --
>> Or Something like this perhaps:
>> - Open Terminal in the /Applications/Utilities/ folder and type in:
>>  
>> chmod u+x
>>  
>> followed by a space. Drag the file into the open Terminal window and press 
>> Enter.
>>  
>> Controlling permissions to this extent is normally only needed by people who 
>> work under the hood and is therefore not an option in the Finder.
>> 
>> I take absolutely NO responsibility at all if you decide to try either of 
>> the above Terminal Commands and something goes wrong. I would strongly 
>> suggest you get in touch with the developer who built the special script to 
>> find out how to run it.
>> 
>> Cheers,
>> Ronni  
>> Sent from Ronni's iPad4
>> 
>> 
>>> On 2 Jun 2014, at 1:35 pm, Neil Houghton  wrote:
>>> 
>>> Hi Pat,
>>> 
>>> There are three specific permissions on Unix-like systems that apply to 
>>> each class: 
>>> Read
>>> Write
>>> Execute
>>> See more here: <http://en.wikipedia.org/wiki/File_system_permissions>
>>> 
>>> So to run the file, read/write is not sufficient.
>>> 
>>> However, I guess my questions would be:
>>> Do you really want to be running a program on your Mac from someone who 
>>> can’t be bothered writing a proper Mac program?
>>> What do you know about this program/script – can it be trusted?
>>> 
>>> 
>>> Just my 2c worth.
>>> 
>>> 
>>> Cheers
>>> 
>>> 
>>> Neil
>>> -- 
>>> Neil R. Houghton
>>> Albany, Western Australia
>>> Tel: +61 8 9841 6063
>>> Email: n...@possumology.com
>>> 
>>> 
>>> 
>>> on 2/6/14 13:16, Pat at clamsh...@iinet.net.au wrote:
>>> 
>>> > Hi, I downloaded a small graphics program which contains a special script 
>>> > for 
>>> > starting the program on the Mac. However, these messages appear when I 
>>> > click 
>>> > it:
>>> > 
>>> > "The file “start_mac.command” could not be executed because you do not 
>>> > have 
>>> > appropriate access privileges.
>>> > 
>>> > "To view or change access privileges, select the file in the Finder and 
>>> > choose 
>>> > File > Get Info."
>>> > 
>>> > The Get Info panel says that I do have read and write privileges. I tried 
>>> > restarting the computer, and searched WAMUG files using ‘Permissions’, 
>>> > ‘changing Permissions’ and ‘Get Info’ but found nothing appropriate.
>>> > 
>>> > Get Info suggested that Terminal could be used to fix the problem, but I 
>>> > don’t 
>>> > know enough Unix to do that.
>>> > 
>>> > Advice will be much appreciated.
>>> > Pat
>>> > -- The WA Macintosh User Group Mailing List --
>>> > Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
>>> > Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
>>> > Settings & Unsubscribe - 
>>> > <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>
>> -- The WA Macintosh User Group Mailing List --
>> Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
>> Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
>> Settings & Unsubscribe - 
>> <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>
> 
> -- The WA Macintosh User Group Mailing List --
> Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
> Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
> Settings & Unsubscribe - 
> <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>
-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>

Re: Changing Get Info permissions

[Pat]

Hi, Ronni and Neil,

Thank you for the information and the cautions. Yes, I am cautious, but I trust 
the developer. It is another case of interesting software written for Windows 
and later, as an afterthought, ported to Mac. The forum shows a lot of other 
disappointed Mac users also have trouble.

Unfortunately, Terminal didn’t fix the permission problems. I tried both 
methods of typing the path and dragging the files.

Maybe I will have to fire up Parallels again, sigh.

Thanks!
Pat


On 2 Jun 2014, at 2:00 pm, Ronda Brown  wrote:

> Hi Pat,
> 
> As Neil has mentioned be very careful that you know what this Program/Script 
> is and how safe it is. Not knowing what the program is or why you have to run 
> this script, I hesitate to recommend anything.
> 
> By the sound of what you have said, you would need to use Terminal to change 
> the permissions on such a script.
> You need to set 'execute' on the file for it to allow you to run it.
> Something like this:
> - Open Terminal in the Applications/Utilities folder and type this:
> 
> chmod u+x /path/to/file.command
> u is the owner of the file, +x adds 'execute', so u+x gives the owner of the 
> file the ability to execute it
> --
> Or Something like this perhaps:
> - Open Terminal in the /Applications/Utilities/ folder and type in:
>  
> chmod u+x
>  
> followed by a space. Drag the file into the open Terminal window and press 
> Enter.
>  
> Controlling permissions to this extent is normally only needed by people who 
> work under the hood and is therefore not an option in the Finder.
> 
> I take absolutely NO responsibility at all if you decide to try either of the 
> above Terminal Commands and something goes wrong. I would strongly suggest 
> you get in touch with the developer who built the special script to find out 
> how to run it.
> 
> Cheers,
> Ronni  
> Sent from Ronni's iPad4
> 
> 
> On 2 Jun 2014, at 1:35 pm, Neil Houghton  wrote:
> 
>> Hi Pat,
>> 
>> There are three specific permissions on Unix-like systems that apply to each 
>> class: 
>> Read
>> Write
>> Execute
>> See more here: <http://en.wikipedia.org/wiki/File_system_permissions>
>> 
>> So to run the file, read/write is not sufficient.
>> 
>> However, I guess my questions would be:
>> Do you really want to be running a program on your Mac from someone who 
>> can’t be bothered writing a proper Mac program?
>> What do you know about this program/script – can it be trusted?
>> 
>> 
>> Just my 2c worth.
>> 
>> 
>> Cheers
>> 
>> 
>> Neil
>> -- 
>> Neil R. Houghton
>> Albany, Western Australia
>> Tel: +61 8 9841 6063
>> Email: n...@possumology.com
>> 
>> 
>> 
>> on 2/6/14 13:16, Pat at clamsh...@iinet.net.au wrote:
>> 
>> > Hi, I downloaded a small graphics program which contains a special script 
>> > for 
>> > starting the program on the Mac. However, these messages appear when I 
>> > click 
>> > it:
>> > 
>> > "The file “start_mac.command” could not be executed because you do not 
>> > have 
>> > appropriate access privileges.
>> > 
>> > "To view or change access privileges, select the file in the Finder and 
>> > choose 
>> > File > Get Info."
>> > 
>> > The Get Info panel says that I do have read and write privileges. I tried 
>> > restarting the computer, and searched WAMUG files using ‘Permissions’, 
>> > ‘changing Permissions’ and ‘Get Info’ but found nothing appropriate.
>> > 
>> > Get Info suggested that Terminal could be used to fix the problem, but I 
>> > don’t 
>> > know enough Unix to do that.
>> > 
>> > Advice will be much appreciated.
>> > Pat
>> > -- The WA Macintosh User Group Mailing List --
>> > Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
>> > Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
>> > Settings & Unsubscribe - 
>> > <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>
> -- The WA Macintosh User Group Mailing List --
> Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
> Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
> Settings & Unsubscribe - 
> <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>

-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>

Re: Changing Get Info permissions

[Ronda Brown]

Hi Pat,

As Neil has mentioned be very careful that you know what this Program/Script is 
and how safe it is. Not knowing what the program is or why you have to run this 
script, I hesitate to recommend anything.

By the sound of what you have said, you would need to use Terminal to change 
the permissions on such a script.
You need to set 'execute' on the file for it to allow you to run it.
Something like this:
- Open Terminal in the Applications/Utilities folder and type this:

chmod u+x /path/to/file.command
u is the owner of the file, +x adds 'execute', so u+x gives the owner of the 
file the ability to execute it
--
Or Something like this perhaps:
- Open Terminal in the /Applications/Utilities/ folder and type in:
 
chmod u+x
 
followed by a space. Drag the file into the open Terminal window and press 
Enter.
 
Controlling permissions to this extent is normally only needed by people who 
work under the hood and is therefore not an option in the Finder.

I take absolutely NO responsibility at all if you decide to try either of the 
above Terminal Commands and something goes wrong. I would strongly suggest you 
get in touch with the developer who built the special script to find out how to 
run it.

Cheers,
Ronni  
Sent from Ronni's iPad4


> On 2 Jun 2014, at 1:35 pm, Neil Houghton  wrote:
> 
> Hi Pat,
> 
> There are three specific permissions on Unix-like systems that apply to each 
> class: 
> Read
> Write
> Execute
> See more here: <http://en.wikipedia.org/wiki/File_system_permissions>
> 
> So to run the file, read/write is not sufficient.
> 
> However, I guess my questions would be:
> Do you really want to be running a program on your Mac from someone who can’t 
> be bothered writing a proper Mac program?
> What do you know about this program/script – can it be trusted?
> 
> 
> Just my 2c worth.
> 
> 
> Cheers
> 
> 
> Neil
> -- 
> Neil R. Houghton
> Albany, Western Australia
> Tel: +61 8 9841 6063
> Email: n...@possumology.com
> 
> 
> 
> on 2/6/14 13:16, Pat at clamsh...@iinet.net.au wrote:
> 
> > Hi, I downloaded a small graphics program which contains a special script 
> > for 
> > starting the program on the Mac. However, these messages appear when I 
> > click 
> > it:
> > 
> > "The file “start_mac.command” could not be executed because you do not have 
> > appropriate access privileges.
> > 
> > "To view or change access privileges, select the file in the Finder and 
> > choose 
> > File > Get Info."
> > 
> > The Get Info panel says that I do have read and write privileges. I tried 
> > restarting the computer, and searched WAMUG files using ‘Permissions’, 
> > ‘changing Permissions’ and ‘Get Info’ but found nothing appropriate.
> > 
> > Get Info suggested that Terminal could be used to fix the problem, but I 
> > don’t 
> > know enough Unix to do that.
> > 
> > Advice will be much appreciated.
> > Pat
> > -- The WA Macintosh User Group Mailing List --
> > Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
> > Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
> > Settings & Unsubscribe - 
> > <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>
-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>

Re: Changing Get Info permissions

[Neil Houghton]

Hi Pat,

There are three specific permissions on Unix-like systems that apply to each
class: 
* Read 
* Write 
* Execute
See more here: <http://en.wikipedia.org/wiki/File_system_permissions>

So to run the file, read/write is not sufficient.

However, I guess my questions would be:
1. Do you really want to be running a program on your Mac from someone who
can¹t be bothered writing a proper Mac program?
2. What do you know about this program/script ­ can it be trusted?


Just my 2c worth.


Cheers


Neil
-- 
Neil R. Houghton
Albany, Western Australia
Tel: +61 8 9841 6063
Email: n...@possumology.com



on 2/6/14 13:16, Pat at clamsh...@iinet.net.au wrote:

> Hi, I downloaded a small graphics program which contains a special script for
> starting the program on the Mac. However, these messages appear when I click
> it:
> 
> "The file ³start_mac.command² could not be executed because you do not have
> appropriate access privileges.
> 
> "To view or change access privileges, select the file in the Finder and choose
> File > Get Info."
> 
> The Get Info panel says that I do have read and write privileges. I tried
> restarting the computer, and searched WAMUG files using ŒPermissions¹,
> Œchanging Permissions¹ and ŒGet Info¹ but found nothing appropriate.
> 
> Get Info suggested that Terminal could be used to fix the problem, but I don¹t
> know enough Unix to do that.
> 
> Advice will be much appreciated.
> Pat
> -- The WA Macintosh User Group Mailing List --
> Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
> Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
> Settings & Unsubscribe -
> <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>


-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>

Changing Get Info permissions

[Pat]

Hi, I downloaded a small graphics program which contains a special script for 
starting the program on the Mac. However, these messages appear when I click it:

"The file “start_mac.command” could not be executed because you do not have 
appropriate access privileges.

"To view or change access privileges, select the file in the Finder and choose 
File > Get Info."

The Get Info panel says that I do have read and write privileges. I tried 
restarting the computer, and searched WAMUG files using ‘Permissions’, 
‘changing Permissions’ and ‘Get Info’ but found nothing appropriate.

Get Info suggested that Terminal could be used to fix the problem, but I don’t 
know enough Unix to do that.

Advice will be much appreciated.
Pat
-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>

Re: Repair Permissions

[Ronda Brown]

Hi Laura,

Nothing to worry about there. The "Warning: SUID file etc etc has been modified 
a nod will not be repaired" can be ignored.

The Group Differs on &  permissions differs on have been repaired... 
So nothing to worry about ;-)

http://support.apple.com/kb/ts1448

Ps. The WAMUG Mailing list moderator will be on your case for sending an 
attachment. There has been a few attachments 'slipping through' lately

Cheers,
Ronni

Sent from Ronni's iPad4


> On 24 Feb 2014, at 1:50 pm, Laura Webb  wrote:
> 
> 
> After doing a Repair Permissions on my MacMini (OS X 10.9.1), I have the 
> following message. I would appreciate advice as to whether this is something 
> I should be concerned about i.e. the Warning statement referring to the SUID 
> file.
> 
> Many thanks.
> Regards
> Laura
> 
> 
-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>

Repair Permissions

[Laura Webb]

After doing a Repair Permissions on my MacMini (OS X 10.9.1), I have the following message. I would appreciate advice as to whether this is something I should be concerned about i.e. the Warning statement referring to the SUID file.Many thanks.RegardsLaura-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>

Re: Permissions repair on my iMac

[Ronda Brown]

Hi Marcus,

Keep checking Software Update and install any updates & Security Updates.
When you first install Mavericks Repair Permissions (as you have noticed) made 
a heap of changes.

After a security update the other day, I then only had a very few items in Disk 
Utility > Repair Permissions.

Cheers,
Ronni

Sent from Ronni's iPad4

> On 17 Nov 2013, at 5:42 pm, Marcus F Harris  wrote:
> 
> Just a note of interest. After installing the latest Maverick updates to 
> Apple's apps, Pages , Numbers etcetera, sequentially,, the repairs ran to 21 
> printed pages!!
> Everything seems to be working well, it's just that normally PR is maybe ten 
> items max!
> iMac 27" late 2009 Maverick
> Marcus
> 
> Message sent from my iPhone 4S 
> -- The WA Macintosh User Group Mailing List --
> Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
> Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
> Settings & Unsubscribe - 
> <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>
-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>

Permissions repair on my iMac

[Marcus F Harris]

Just a note of interest. After installing the latest Maverick updates to 
Apple's apps, Pages , Numbers etcetera, sequentially,, the repairs ran to 21 
printed pages!!
Everything seems to be working well, it's just that normally PR is maybe ten 
items max!
iMac 27" late 2009 Maverick
Marcus

Message sent from my iPhone 4S 
-- The WA Macintosh User Group Mailing List --
Archives - 
Guidelines - 
Settings & Unsubscribe - 

Re: iMac 10.8.5 Permissions Repair

[Rick Armstrong]

Thanks Ronni,
I must have not done permissions since the update to ITunes 11.1 update.
Regards, Rick.
 
On 22/09/2013, at 2:13 PM, Ronda Brown  wrote:

> Hi again Rick,
> 
> I just noticed that you thought the Permissions differ were due to: 
>>> Since downloading iOS7 software for the iPhone 4
> Just to clear your understanding... No they have nothing to do with iOS 7.
> They are appearing since the  iTunes 11.1 update.
> 
> Apple changed the way they create ".nib" files, and Disk Utility hasn't been 
> updated yet to recognise the change. I would imagine Apple will correct this 
> in due time.
> The 'problem'... which is actually not a problem' :-) is in Disk Utility, not 
> in iTunes.
> 
> Hope that clarifies things for you.
> 
> Cheers,
> Ronni
> Sent from Ronni's iPad4
> 
> On 22 Sep 2013, at 1:20 pm, Ronni Brown  wrote:
> 
>> 
>> On 22/09/2013, at 12:46 PM, Rick Armstrong  wrote:
>> 
>>> 10.8.5
>>> Since downloading iOS7 software for the iPhone 4
>>> The iMac (10.8.5) says 
>>> Permissions differ on 
>>> “Applications/iTunes.app/Contents/Resources/Dutch.lproj/AACEncoderConfig.nib”;
>>>  should be drwxr-xr-x ; they are -rwxr-xr-x .
>>> Repaired 
>>> “Applications/iTunes.app/Contents/Resources/Dutch.lproj/AACEncoderConfig.nib”
>>> This list  just goes on and on and on with various subtext
>>> Permissions repair complete
>>> and same comes up again with next Permissions Repair
>>> (previously was a clean report with Permissions Repair).
>>> Thanks, Rick.
>> 
>> Hi Rick,
>> 
>> Same here. But you should consider them as not important...
>>  
>> Permissions differ on 
>> “Applications/iTunes.app/Contents/Resources/Dutch.lproj/AACEncoderConfig.nib”;
>>  should be drwxr-xr-x ; they are -rwxr-xr-x .
>>  
>> What this means in Unix language is that permissions check is expecting that 
>> "AACEncoderConfig.nib" to be a directory and it's not. You can tell because 
>> of "drwxr-xr-x" the d letter at the beginning of the string means 
>> "directory" and when compared with the actual value "-rwxr-xr-x", the 
>> absence of d means that it refers to a file.
>>  
>> Now you might ask why is the system expecting a directory?
>> Here is a link that describes why: 
>> <http://support.apple.com/kb/HT1452?viewlocale=en_US&locale=en_US>
>>  
>> OK...but what is this kind of files .nib?
>> This files are normally GUI files...and in the past...not so far away...it 
>> was based on a directory structure...but iTunes 11.1 is the first released 
>> Apple app that is using their new nib file spec. And this is somehow 
>> apparent...I mean the error messages we are all seeing when we run the 
>> permissions check suggest it.
>> 
>> Cheers,
>> Ronni
> -- The WA Macintosh User Group Mailing List --
> Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
> Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
> Settings & Unsubscribe - 
> <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>

-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>

Re: iMac 10.8.5 Permissions Repair

[Ronda Brown]

Hi again Rick,

I just noticed that you thought the Permissions differ were due to: 
>> Since downloading iOS7 software for the iPhone 4
Just to clear your understanding... No they have nothing to do with iOS 7.
They are appearing since the  iTunes 11.1 update.

Apple changed the way they create ".nib" files, and Disk Utility hasn't been 
updated yet to recognise the change. I would imagine Apple will correct this in 
due time.
The 'problem'... which is actually not a problem' :-) is in Disk Utility, not 
in iTunes.

Hope that clarifies things for you.

Cheers,
Ronni
Sent from Ronni's iPad4

> On 22 Sep 2013, at 1:20 pm, Ronni Brown  wrote:
> 
> 
>> On 22/09/2013, at 12:46 PM, Rick Armstrong  wrote:
>> 
>> 10.8.5
>> Since downloading iOS7 software for the iPhone 4
>> The iMac (10.8.5) says 
>> Permissions differ on 
>> “Applications/iTunes.app/Contents/Resources/Dutch.lproj/AACEncoderConfig.nib”;
>>  should be drwxr-xr-x ; they are -rwxr-xr-x .
>> Repaired 
>> “Applications/iTunes.app/Contents/Resources/Dutch.lproj/AACEncoderConfig.nib”
>> This list  just goes on and on and on with various subtext
>> Permissions repair complete
>> and same comes up again with next Permissions Repair
>> (previously was a clean report with Permissions Repair).
>> Thanks, Rick.
> 
> Hi Rick,
> 
> Same here. But you should consider them as not important...
>  
> Permissions differ on 
> “Applications/iTunes.app/Contents/Resources/Dutch.lproj/AACEncoderConfig.nib”;
>  should be drwxr-xr-x ; they are -rwxr-xr-x .
>  
> What this means in Unix language is that permissions check is expecting that 
> "AACEncoderConfig.nib" to be a directory and it's not. You can tell because 
> of "drwxr-xr-x" the d letter at the beginning of the string means "directory" 
> and when compared with the actual value "-rwxr-xr-x", the absence of d means 
> that it refers to a file.
>  
> Now you might ask why is the system expecting a directory?
> Here is a link that describes why: 
> <http://support.apple.com/kb/HT1452?viewlocale=en_US&locale=en_US>
>  
> OK...but what is this kind of files .nib?
> This files are normally GUI files...and in the past...not so far away...it 
> was based on a directory structure...but iTunes 11.1 is the first released 
> Apple app that is using their new nib file spec. And this is somehow 
> apparent...I mean the error messages we are all seeing when we run the 
> permissions check suggest it.
> 
> Cheers,
> Ronni
-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>

Re: iMac 10.8.5 Permissions Repair

[Ronni Brown]

On 22/09/2013, at 12:46 PM, Rick Armstrong  wrote:

> 10.8.5
> Since downloading iOS7 software for the iPhone 4
> The iMac (10.8.5) says 
> Permissions differ on 
> “Applications/iTunes.app/Contents/Resources/Dutch.lproj/AACEncoderConfig.nib”;
>  should be drwxr-xr-x ; they are -rwxr-xr-x .
> Repaired 
> “Applications/iTunes.app/Contents/Resources/Dutch.lproj/AACEncoderConfig.nib”
> This list  just goes on and on and on with various subtext
> Permissions repair complete
> and same comes up again with next Permissions Repair
> (previously was a clean report with Permissions Repair).
> Thanks, Rick.

Hi Rick,

Same here. But you should consider them as not important...
 
Permissions differ on 
“Applications/iTunes.app/Contents/Resources/Dutch.lproj/AACEncoderConfig.nib”; 
should be drwxr-xr-x ; they are -rwxr-xr-x .
 
What this means in Unix language is that permissions check is expecting that 
"AACEncoderConfig.nib" to be a directory and it's not. You can tell because of 
"drwxr-xr-x" the d letter at the beginning of the string means "directory" and 
when compared with the actual value "-rwxr-xr-x", the absence of d means that 
it refers to a file.
 
Now you might ask why is the system expecting a directory?
Here is a link that describes why: 
<http://support.apple.com/kb/HT1452?viewlocale=en_US&locale=en_US>
 
OK...but what is this kind of files .nib?
This files are normally GUI files...and in the past...not so far away...it was 
based on a directory structure...but iTunes 11.1 is the first released Apple 
app that is using their new nib file spec. And this is somehow apparent...I 
mean the error messages we are all seeing when we run the permissions check 
suggest it.

Cheers,
Ronni

-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>

iMac 10.8.5 Permissions Repair

[Rick Armstrong]

10.8.5
Since downloading iOS7 software for the iPhone 4
The iMac (10.8.5) says 
Permissions differ on 
“Applications/iTunes.app/Contents/Resources/Dutch.lproj/AACEncoderConfig.nib”; 
should be drwxr-xr-x ; they are -rwxr-xr-x .
Repaired 
“Applications/iTunes.app/Contents/Resources/Dutch.lproj/AACEncoderConfig.nib”
This list  just goes on and on and on with various subtext
Permissions repair complete
and same comes up again with next Permissions Repair
(previously was a clean report with Permissions Repair).
Thanks, Rick.




-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>

Performance boost - Repair User Permissions

[Steven Knowles]

I've been experiencing sluggish performance for ages on my MBP running Lion, 
particularly when it came to using Spotlight, or the search facility within 
Mail.

Then I came across the Repair User Permissions process detailed at:

http://osxdaily.com/2011/11/15/repair-user-permissions-in-mac-os-x-lion

After following this process, I'm ecstatic with the difference in performance. 
Chalk & cheese. I mention it here in case anybody else has a sluggish Mac for 
no particularly good reason.

Steven
-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>

Re: Repaired permissions again and again

[Lloyd White]

Thanks Tim and Ronni,

I read the article and am now happier. At least it is not my particular
iMac!

Lloyd 



> This article might be helpful Lloyd.  http://support.apple.com/kb/ts1448
> 
> It seems that to expect NIL Errors is  just not going to happen.
> 
> Given this list at http://support.apple.com/kb/ts1448 is quite long, plus they
> are safe to ignore, it would seem a pity that Apple hasn't tagged or flagged
> these, so that non expert  users, ie most of us,  would know the task is done
> when there are no permissions errors.
> 
> Tim
> 
> 
> 
> On 11/09/2011, at 7:33 PM, Lloyd White wrote:
> 
>> Hi everyone. I hope you were all out there in the sunshine today and not
>> glued to a  computer!
>> 
>> I decided to Repair Permissions, so I restarted into Recovery and repaired
>> permissions ­ a lot of them. So I did it again, and again there were just as
>> many, so did it again, and again! Four times, and each time there were a
>> bundle of permissions to repair. So I gave up and went to the beach.
>> 
>> Should this happen? How many times is reasonable? Or should I have restarted
>> in Recovery and tried again?
>> 
>> Lloyd 
>> 
>> 
>> 





-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Repaired permissions again and again

[Ronda Brown]

Boot from the recovery partition (command-R at startup) and repair permissions.

You don't mention what errors you are receiving Lloyd.
You'll always get error messages from it -- normally ok to ignore them as long 
as you see "Repair Permissions Complete".

Sent from Ronni's iPad

On 11/09/2011, at 8:06 PM, Tim Law  wrote:

> This article might be helpful Lloyd.  http://support.apple.com/kb/ts1448
> 
> It seems that to expect NIL Errors is  just not going to happen. 
> 
> Given this list at http://support.apple.com/kb/ts1448 is quite long, plus 
> they are safe to ignore, it would seem a pity that Apple hasn't tagged or 
> flagged these, so that non expert  users, ie most of us,  would know the task 
> is done when there are no permissions errors. 
> 
> Tim
> 
> 
> 
> On 11/09/2011, at 7:33 PM, Lloyd White wrote:
> 
>> Hi everyone. I hope you were all out there in the sunshine today and not 
>> glued to a  computer!.
>> I decided to Repair Permissions, so I restarted into Recovery and repaired 
>> permissions – a lot of them. So I did it again, and again there were just as 
>> many, so did it again, and again! Four times, and each time there were a 
>> bundle of permissions to repair. So I gave up and went to the beach.
>> 
>> Should this happen? How many times is reasonable? Or should I have restarted 
>> in Recovery and tried again?
>> 
>> Lloyd 
> 



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Repaired permissions again and again

[Tim Law]

This article might be helpful Lloyd.  http://support.apple.com/kb/ts1448

It seems that to expect NIL Errors is  just not going to happen. 

Given this list at http://support.apple.com/kb/ts1448 is quite long, plus they 
are safe to ignore, it would seem a pity that Apple hasn't tagged or flagged 
these, so that non expert  users, ie most of us,  would know the task is done 
when there are no permissions errors. 

Tim



On 11/09/2011, at 7:33 PM, Lloyd White wrote:

> Hi everyone. I hope you were all out there in the sunshine today and not 
> glued to a  computer!
> 
> I decided to Repair Permissions, so I restarted into Recovery and repaired 
> permissions – a lot of them. So I did it again, and again there were just as 
> many, so did it again, and again! Four times, and each time there were a 
> bundle of permissions to repair. So I gave up and went to the beach.
> 
> Should this happen? How many times is reasonable? Or should I have restarted 
> in Recovery and tried again?
> 
> Lloyd 
> 
> 
> 
> 
> -- The WA Macintosh User Group Mailing List --
> Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
> Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
> Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>




-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Repaired permissions again and again

[Lloyd White]

Hi everyone. I hope you were all out there in the sunshine today and not
glued to a  computer!

I decided to Repair Permissions, so I restarted into Recovery and repaired
permissions ­ a lot of them. So I did it again, and again there were just as
many, so did it again, and again! Four times, and each time there were a
bundle of permissions to repair. So I gave up and went to the beach.

Should this happen? How many times is reasonable? Or should I have restarted
in Recovery and tried again?

Lloyd 






-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: iTunes folder permissions problem (was: I can't register my new iPad)

[Ronda Brown]

Hi David,

Your news is great!  I’m pleased I was able to help you & Alan solve the 
problem.
I’m only sorry I missed your original post re this problem. I just scrolled 
back to find when it was posted as I didn’t see it.
I was under personal pressure at that time as my only ‘Big Sis’ (we are known 
as "The Glue Sisters”),  was in ICU in Hospital in Melbourne and it was  
uncertain if she was going to make it.
She has got through the emergency operation and the prognosis is looking much 
better than a few days ago.

Ah, Beethoven … I love Beethoven, I love Mozart … I love classical music!

Cheers,
Ronni

On 26/07/2011, at 5:49 PM, David Nicholas wrote:

> Ronni
> 
> Yes, alan is correct - I am under some time pressure - BUT
> 
> You are right.  The problem did arise after a migration from my older Mac to 
> the new one.
> 
> And your solution worked.  I deleted the SC Info file, restarted, went to the 
> Apple Store, spent US$1.69 on some Beethoven (the A$ is getting more valuable 
> right now) and it has come down and I am playing it.
> 
> Thanks you very much.
> 
> David
> 
> 
> On 26/07/2011, at 5:17 PM, Ronda Brown wrote:
> 
>> Hi again Alan & David,
>> 
>> I’ve studied your email more thoroughly. Did this problem arise after a 
>> migration from an older Mac to a new Mac?
>> Especially this message David received first.
>> 
>>>>>  iTunes couldn't download your purchase.   You don't have access for your 
>>>>> iTunes Media folder or a folder within it. Change permissions (in the 
>>>>> Finder) and then choose Store > Check for Available Downloads.
>> 
>> Try doing removing the /Users/Shared/SC Info directory and restart.
>> 
>> 1. In the top finder bar, go to GO > Go to Folder (Shift+Cmd+G)
>> 2. Type in “/Users/Shared/SC Info”
>> 3. Click ‘Go’
>> 4. Switch to Column View if you’re not in it already
>> 5. Delete the “SC Info” folder
>> 6. Restart
>> 
>> Or, if you’re OK in the terminal, type this in from the command line:
>> rm /Users/Shared/SC\ Info
>> 
>> And then restart.
>> 
>> Let me know how you get on please.
>> 
>> Cheers,
>> Ronni
>> 
>> On 26/07/2011, at 4:34 PM, Ronda Brown wrote:
>> 
>>> Hi Alan,
>>> 
>>> You mentioned you have changed permissions on the Home > Music > iTunes 
>>> Music Folder & ALL enclosed folders.
>>> 
>>> You need to check and see that you have both Read AND Write permission on 
>>> the iTunes Music folder AND on all folders within it. 
>>> Log in to the account where the library resides and navigate to the Music 
>>> folder through Finder. 
>>> The File > Get Info and check your permissions.
>>> Unlock the little lock at the bottom of this window 
>>> To change them, you need to input the Admin password. 
>>> 
>>> The click the 'little cog’ and “Apply to enclosed items”.
>>> As its very important, to make sure that Read and Write permission is 
>>> applied to ALL enclosed folders. 
>>> 
>>> Failing this, does David have a backup of his iTunes Folder when it was all 
>>> working correctly?
>>> 
>>> Cheers,
>>> Ronni
>>> 
>>> On 26/07/2011, at 2:35 PM, Alan Smith wrote:
>>> 
>>>> 
>>>> On 23/07/2011, at 12:19 PM, David Nicholas   
>>>> submitted I can't register my new iPad
>>>> 
>>>> I have been assisting David by phone to analyse his problem with "I can't 
>>>> register my new iPad", and now look for more experienced WAMUG help.   I 
>>>> changed the thread subject line because there were no responses to the 
>>>> original posting and I thought the most significant problem lay with the 
>>>> second item David raised.   All problems are still there!
>>>> 
>>>> PART A:    iTunes alert message stated by David after purchasing the iPad 
>>>> iBooks app:
>>>> 
>>>>>  iTunes couldn't download your purchase.   You don't have access for your 
>>>>> iTunes Media folder or a folder within it. Change permissions (in the 
>>>>> Finder) and then choose Store > Check for Available Downloads.
>>>> 
>>>> 
>>>> Action taken: 
>>>> (1)  Books and Apps were included in the iTunes Preferences to show in the 
>>>> Library.
>>>> (2)  Repair Disk Permissions run  on the Macintosh HD via Disk Utility.  
>>>> (No problems indicated).
>>&

Re: iTunes folder permissions problem (was: I can't register my new iPad)

[David Nicholas]

Ronni

Yes, alan is correct - I am under some time pressure - BUT

You are right.  The problem did arise after a migration from my older Mac to 
the new one.

And your solution worked.  I deleted the SC Info file, restarted, went to the 
Apple Store, spent US$1.69 on some Beethoven (the A$ is getting more valuable 
right now) and it has come down and I am playing it.

Thanks you very much.

David


On 26/07/2011, at 5:17 PM, Ronda Brown wrote:

> Hi again Alan & David,
> 
> I’ve studied your email more thoroughly. Did this problem arise after a 
> migration from an older Mac to a new Mac?
> Especially this message David received first.
> 
>>>>  iTunes couldn't download your purchase.   You don't have access for your 
>>>> iTunes Media folder or a folder within it. Change permissions (in the 
>>>> Finder) and then choose Store > Check for Available Downloads.
> 
> Try doing removing the /Users/Shared/SC Info directory and restart.
> 
> 1. In the top finder bar, go to GO > Go to Folder (Shift+Cmd+G)
> 2. Type in “/Users/Shared/SC Info”
> 3. Click ‘Go’
> 4. Switch to Column View if you’re not in it already
> 5. Delete the “SC Info” folder
> 6. Restart
> 
> Or, if you’re OK in the terminal, type this in from the command line:
> rm /Users/Shared/SC\ Info
> 
> And then restart.
> 
> Let me know how you get on please.
> 
> Cheers,
> Ronni
> 
> On 26/07/2011, at 4:34 PM, Ronda Brown wrote:
> 
>> Hi Alan,
>> 
>> You mentioned you have changed permissions on the Home > Music > iTunes 
>> Music Folder & ALL enclosed folders.
>> 
>> You need to check and see that you have both Read AND Write permission on 
>> the iTunes Music folder AND on all folders within it. 
>> Log in to the account where the library resides and navigate to the Music 
>> folder through Finder. 
>> The File > Get Info and check your permissions.
>> Unlock the little lock at the bottom of this window 
>> To change them, you need to input the Admin password. 
>> 
>> The click the 'little cog’ and “Apply to enclosed items”.
>> As its very important, to make sure that Read and Write permission is 
>> applied to ALL enclosed folders. 
>> 
>> Failing this, does David have a backup of his iTunes Folder when it was all 
>> working correctly?
>> 
>> Cheers,
>> Ronni
>> 
>> On 26/07/2011, at 2:35 PM, Alan Smith wrote:
>> 
>>> 
>>> On 23/07/2011, at 12:19 PM, David Nicholas   
>>> submitted I can't register my new iPad
>>> 
>>> I have been assisting David by phone to analyse his problem with "I can't 
>>> register my new iPad", and now look for more experienced WAMUG help.   I 
>>> changed the thread subject line because there were no responses to the 
>>> original posting and I thought the most significant problem lay with the 
>>> second item David raised.   All problems are still there!
>>> 
>>> PART A:iTunes alert message stated by David after purchasing the iPad 
>>> iBooks app:
>>> 
>>>>  iTunes couldn't download your purchase.   You don't have access for your 
>>>> iTunes Media folder or a folder within it. Change permissions (in the 
>>>> Finder) and then choose Store > Check for Available Downloads.
>>> 
>>> 
>>> Action taken: 
>>> (1)  Books and Apps were included in the iTunes Preferences to show in the 
>>> Library.
>>> (2)  Repair Disk Permissions run  on the Macintosh HD via Disk Utility.  
>>> (No problems indicated).
>>> (3) The iTunes Media folder (located under User/Music/iTunes/iTunes Media) 
>>> and all enclosed items were given full R/W permissions & privileges, even 
>>> though all individual visible folders were already set OK.  Noted that a 
>>> folder called Downloads (empty) exists under iTunes Media.
>>> 
>>> iMac restarted and iTunes reloaded etc: still get same Alert message when 
>>> checking for available downloads.  
>>> 
>>>  PART B:  David had also attempted to purchase an iTunes music item and got 
>>> a different Alert warning:
>>> 
>>> We could not complete your iTunes Store request. You do not have enough 
>>> access privileges for this operation. There was an error in the iTunes 
>>> Store.  Please try again later.
>>> 
>>> This alert message appears immediately iTunes is loaded.   So it may refer 
>>> to the act of loading the software, or to the unfinished sale of the 
>>> unsuccessful music purchase

Re: iTunes folder permissions problem (was: I can't register my new iPad)

[Alan Smith]

Hi Ronni

David was rushing to go out so he may not have seen this message.  Will do the 
suggested action tomorrow.

Yes, David used Migration Assistant to transfer data from an older machine.

Apple Support suggested checking permissions on the Shared folder, which David 
did (via File>Get Info, as Terminal is a bit of a challenge!) but David never 
mentioned the existence of a CS Info folder.I don't have one on my iMac (or 
it is hidden), so I didn't prompt David to inspect his folder.

BTW, David doesn't think his Time Machine has a reliable backup of his iTunes 
library.   Perhaps his iTunes problems have been around for along time - since 
Migration?

Cheers
Alan

On 26/07/2011, at 5:17 PM, Ronda Brown wrote:

Hi again Alan & David,

I’ve studied your email more thoroughly. Did this problem arise after a 
migration from an older Mac to a new Mac?
Especially this message David received first.

>>>  iTunes couldn't download your purchase.   You don't have access for your 
>>> iTunes Media folder or a folder within it. Change permissions (in the 
>>> Finder) and then choose Store > Check for Available Downloads.

Try doing removing the /Users/Shared/SC Info directory and restart.

1. In the top finder bar, go to GO > Go to Folder (Shift+Cmd+G)
2. Type in “/Users/Shared/SC Info”
3. Click ‘Go’
4. Switch to Column View if you’re not in it already
5. Delete the “SC Info” folder
6. Restart

Or, if you’re OK in the terminal, type this in from the command line:
rm /Users/Shared/SC\ Info

And then restart.

Let me know how you get on please.

Cheers,
Ronni

On 26/07/2011, at 4:34 PM, Ronda Brown wrote:

> Hi Alan,
> 
> You mentioned you have changed permissions on the Home > Music > iTunes Music 
> Folder & ALL enclosed folders.
> 
> You need to check and see that you have both Read AND Write permission on the 
> iTunes Music folder AND on all folders within it. 
> Log in to the account where the library resides and navigate to the Music 
> folder through Finder. 
> The File > Get Info and check your permissions.
> Unlock the little lock at the bottom of this window 
> To change them, you need to input the Admin password. 
> 
> The click the 'little cog’ and “Apply to enclosed items”.
> As its very important, to make sure that Read and Write permission is applied 
> to ALL enclosed folders. 
> 
> Failing this, does David have a backup of his iTunes Folder when it was all 
> working correctly?
> 
> Cheers,
> Ronni
> 
> On 26/07/2011, at 2:35 PM, Alan Smith wrote:
> 
>> 
>> On 23/07/2011, at 12:19 PM, David Nicholas   
>> submitted I can't register my new iPad
>> 
>> I have been assisting David by phone to analyse his problem with "I can't 
>> register my new iPad", and now look for more experienced WAMUG help.   I 
>> changed the thread subject line because there were no responses to the 
>> original posting and I thought the most significant problem lay with the 
>> second item David raised.   All problems are still there!
>> 
>> PART A:iTunes alert message stated by David after purchasing the iPad 
>> iBooks app:
>> 
>>>  iTunes couldn't download your purchase.   You don't have access for your 
>>> iTunes Media folder or a folder within it. Change permissions (in the 
>>> Finder) and then choose Store > Check for Available Downloads.
>> 
>> 
>> Action taken: 
>> (1)  Books and Apps were included in the iTunes Preferences to show in the 
>> Library.
>> (2)  Repair Disk Permissions run  on the Macintosh HD via Disk Utility.  (No 
>> problems indicated).
>> (3) The iTunes Media folder (located under User/Music/iTunes/iTunes Media) 
>> and all enclosed items were given full R/W permissions & privileges, even 
>> though all individual visible folders were already set OK.  Noted that a 
>> folder called Downloads (empty) exists under iTunes Media.
>> 
>> iMac restarted and iTunes reloaded etc: still get same Alert message when 
>> checking for available downloads.  
>> 
>>  PART B:  David had also attempted to purchase an iTunes music item and got 
>> a different Alert warning:
>> 
>> We could not complete your iTunes Store request. You do not have enough 
>> access privileges for this operation. There was an error in the iTunes 
>> Store.  Please try again later.
>> 
>> This alert message appears immediately iTunes is loaded.   So it may refer 
>> to the act of loading the software, or to the unfinished sale of the 
>> unsuccessful music purchase.   The iStore can be accessed and browsed 
>> without problems.   It shows David as logged in and he can see his

Re: iTunes folder permissions problem (was: I can't register my new iPad)

[Ronda Brown]

Hi again Alan & David,

I’ve studied your email more thoroughly. Did this problem arise after a 
migration from an older Mac to a new Mac?
Especially this message David received first.

>>>  iTunes couldn't download your purchase.   You don't have access for your 
>>> iTunes Media folder or a folder within it. Change permissions (in the 
>>> Finder) and then choose Store > Check for Available Downloads.

Try doing removing the /Users/Shared/SC Info directory and restart.

1. In the top finder bar, go to GO > Go to Folder (Shift+Cmd+G)
2. Type in “/Users/Shared/SC Info”
3. Click ‘Go’
4. Switch to Column View if you’re not in it already
5. Delete the “SC Info” folder
6. Restart

Or, if you’re OK in the terminal, type this in from the command line:
rm /Users/Shared/SC\ Info

And then restart.

Let me know how you get on please.

Cheers,
Ronni

On 26/07/2011, at 4:34 PM, Ronda Brown wrote:

> Hi Alan,
> 
> You mentioned you have changed permissions on the Home > Music > iTunes Music 
> Folder & ALL enclosed folders.
> 
> You need to check and see that you have both Read AND Write permission on the 
> iTunes Music folder AND on all folders within it. 
> Log in to the account where the library resides and navigate to the Music 
> folder through Finder. 
> The File > Get Info and check your permissions.
> Unlock the little lock at the bottom of this window 
> To change them, you need to input the Admin password. 
> 
> The click the 'little cog’ and “Apply to enclosed items”.
> As its very important, to make sure that Read and Write permission is applied 
> to ALL enclosed folders. 
> 
> Failing this, does David have a backup of his iTunes Folder when it was all 
> working correctly?
> 
> Cheers,
> Ronni
> 
> On 26/07/2011, at 2:35 PM, Alan Smith wrote:
> 
>> 
>> On 23/07/2011, at 12:19 PM, David Nicholas   
>> submitted I can't register my new iPad
>> 
>> I have been assisting David by phone to analyse his problem with "I can't 
>> register my new iPad", and now look for more experienced WAMUG help.   I 
>> changed the thread subject line because there were no responses to the 
>> original posting and I thought the most significant problem lay with the 
>> second item David raised.   All problems are still there!
>> 
>> PART A:iTunes alert message stated by David after purchasing the iPad 
>> iBooks app:
>> 
>>>  iTunes couldn't download your purchase.   You don't have access for your 
>>> iTunes Media folder or a folder within it. Change permissions (in the 
>>> Finder) and then choose Store > Check for Available Downloads.
>> 
>> 
>> Action taken: 
>> (1)  Books and Apps were included in the iTunes Preferences to show in the 
>> Library.
>> (2)  Repair Disk Permissions run  on the Macintosh HD via Disk Utility.  (No 
>> problems indicated).
>> (3) The iTunes Media folder (located under User/Music/iTunes/iTunes Media) 
>> and all enclosed items were given full R/W permissions & privileges, even 
>> though all individual visible folders were already set OK.  Noted that a 
>> folder called Downloads (empty) exists under iTunes Media.
>> 
>> iMac restarted and iTunes reloaded etc: still get same Alert message when 
>> checking for available downloads.  
>> 
>>  PART B:  David had also attempted to purchase an iTunes music item and got 
>> a different Alert warning:
>> 
>> We could not complete your iTunes Store request. You do not have enough 
>> access privileges for this operation. There was an error in the iTunes 
>> Store.  Please try again later.
>> 
>> This alert message appears immediately iTunes is loaded.   So it may refer 
>> to the act of loading the software, or to the unfinished sale of the 
>> unsuccessful music purchase.   The iStore can be accessed and browsed 
>> without problems.   It shows David as logged in and he can see his account 
>> status etc.
>> 
>> Action taken:
>> (1)  Tried later and next day - no change.
>> (2)  Confirmed folder permissions for Macintosh HD / Library / Preferences 
>> were OK for David as admin.
>> (3)  Confirmed folder permissions for User / Library / Preferences were OK 
>> for David as admin.
>> (4)  Confirmed user security Firewall is "off".
>> 
>> I searched the Apple Support HT and TS files for permission issues but the 
>> specific Alerts received have no diagnostic advice.   So, a lot of time 
>> invested for no clear result.  Is it time for a .plist trashing?  Or to 
>> re-install iTunes 10.4?  (I can't give any advice about th

Re: iTunes folder permissions problem (was: I can't register my new iPad)

[David Nicholas]

Ronni

Thanks for your response.

With frequent consultations with Alan I have done the things you mention.  I 
have a Shared Folder. Apple Support suggested I check permissions of the Shared 
Folder, but they are all OK.  We decided to Deauthorise the Computer and then 
Reauthorise it, but it wouldnt  let me.  It gave a message "There was an error 
storing your authorization information on this computer.  The required file was 
not found or has a permissions error.  Correct this permissions problem and try 
again, or deathorize this computer if the permissions cannot be changed."

That seemed to have circular advice in it, and didn't give me a clear path.

Can you suggest anything further Ronni?

David

iMac OSX  10.6.8
iTues 10.4





On 26/07/2011, at 4:34 PM, Ronda Brown wrote:

> Hi Alan,
> 
> You mentioned you have changed permissions on the Home > Music > iTunes Music 
> Folder & ALL enclosed folders.
> 
> You need to check and see that you have both Read AND Write permission on the 
> iTunes Music folder AND on all folders within it. 
> Log in to the account where the library resides and navigate to the Music 
> folder through Finder. 
> The File > Get Info and check your permissions.
> Unlock the little lock at the bottom of this window 
> To change them, you need to input the Admin password. 
> 
> The click the 'little cog’ and “Apply to enclosed items”.
> As its very important, to make sure that Read and Write permission is applied 
> to ALL enclosed folders. 
> 
> Failing this, does David have a backup of his iTunes Folder when it was all 
> working correctly?
> 
> Cheers,
> Ronni
> 
> On 26/07/2011, at 2:35 PM, Alan Smith wrote:
> 
>> 
>> On 23/07/2011, at 12:19 PM, David Nicholas   
>> submitted I can't register my new iPad
>> 
>> I have been assisting David by phone to analyse his problem with "I can't 
>> register my new iPad", and now look for more experienced WAMUG help.   I 
>> changed the thread subject line because there were no responses to the 
>> original posting and I thought the most significant problem lay with the 
>> second item David raised.   All problems are still there!
>> 
>> PART A:iTunes alert message stated by David after purchasing the iPad 
>> iBooks app:
>> 
>>>  iTunes couldn't download your purchase.   You don't have access for your 
>>> iTunes Media folder or a folder within it. Change permissions (in the 
>>> Finder) and then choose Store > Check for Available Downloads.
>> 
>> 
>> Action taken: 
>> (1)  Books and Apps were included in the iTunes Preferences to show in the 
>> Library.
>> (2)  Repair Disk Permissions run  on the Macintosh HD via Disk Utility.  (No 
>> problems indicated).
>> (3) The iTunes Media folder (located under User/Music/iTunes/iTunes Media) 
>> and all enclosed items were given full R/W permissions & privileges, even 
>> though all individual visible folders were already set OK.  Noted that a 
>> folder called Downloads (empty) exists under iTunes Media.
>> 
>> iMac restarted and iTunes reloaded etc: still get same Alert message when 
>> checking for available downloads.  
>> 
>>  PART B:  David had also attempted to purchase an iTunes music item and got 
>> a different Alert warning:
>> 
>> We could not complete your iTunes Store request. You do not have enough 
>> access privileges for this operation. There was an error in the iTunes 
>> Store.  Please try again later.
>> 
>> This alert message appears immediately iTunes is loaded.   So it may refer 
>> to the act of loading the software, or to the unfinished sale of the 
>> unsuccessful music purchase.   The iStore can be accessed and browsed 
>> without problems.   It shows David as logged in and he can see his account 
>> status etc.
>> 
>> Action taken:
>> (1)  Tried later and next day - no change.
>> (2)  Confirmed folder permissions for Macintosh HD / Library / Preferences 
>> were OK for David as admin.
>> (3)  Confirmed folder permissions for User / Library / Preferences were OK 
>> for David as admin.
>> (4)  Confirmed user security Firewall is "off".
>> 
>> I searched the Apple Support HT and TS files for permission issues but the 
>> specific Alerts received have no diagnostic advice.   So, a lot of time 
>> invested for no clear result.  Is it time for a .plist trashing?  Or to 
>> re-install iTunes 10.4?  (I can't give any advice about these!)   
>> 
>> By the way, David has an older iMac (OSX 10.5.8) on the same home network 
>> that has no problem

Re: iTunes folder permissions problem (was: I can't register my new iPad)

[Ronda Brown]

Hi Alan,

You mentioned you have changed permissions on the Home > Music > iTunes Music 
Folder & ALL enclosed folders.

You need to check and see that you have both Read AND Write permission on the 
iTunes Music folder AND on all folders within it. 
Log in to the account where the library resides and navigate to the Music 
folder through Finder. 
The File > Get Info and check your permissions.
Unlock the little lock at the bottom of this window 
To change them, you need to input the Admin password. 

The click the 'little cog’ and “Apply to enclosed items”.
As its very important, to make sure that Read and Write permission is applied 
to ALL enclosed folders. 

Failing this, does David have a backup of his iTunes Folder when it was all 
working correctly?

Cheers,
Ronni

On 26/07/2011, at 2:35 PM, Alan Smith wrote:

> 
> On 23/07/2011, at 12:19 PM, David Nicholas   submitted 
> I can't register my new iPad
> 
> I have been assisting David by phone to analyse his problem with "I can't 
> register my new iPad", and now look for more experienced WAMUG help.   I 
> changed the thread subject line because there were no responses to the 
> original posting and I thought the most significant problem lay with the 
> second item David raised.   All problems are still there!
> 
> PART A:iTunes alert message stated by David after purchasing the iPad 
> iBooks app:
> 
>>  iTunes couldn't download your purchase.   You don't have access for your 
>> iTunes Media folder or a folder within it. Change permissions (in the 
>> Finder) and then choose Store > Check for Available Downloads.
> 
> 
> Action taken: 
> (1)  Books and Apps were included in the iTunes Preferences to show in the 
> Library.
> (2)  Repair Disk Permissions run  on the Macintosh HD via Disk Utility.  (No 
> problems indicated).
> (3) The iTunes Media folder (located under User/Music/iTunes/iTunes Media) 
> and all enclosed items were given full R/W permissions & privileges, even 
> though all individual visible folders were already set OK.  Noted that a 
> folder called Downloads (empty) exists under iTunes Media.
> 
> iMac restarted and iTunes reloaded etc: still get same Alert message when 
> checking for available downloads.  
> 
>  PART B:  David had also attempted to purchase an iTunes music item and got a 
> different Alert warning:
> 
> We could not complete your iTunes Store request. You do not have enough 
> access privileges for this operation. There was an error in the iTunes Store. 
>  Please try again later.
> 
> This alert message appears immediately iTunes is loaded.   So it may refer to 
> the act of loading the software, or to the unfinished sale of the 
> unsuccessful music purchase.   The iStore can be accessed and browsed without 
> problems.   It shows David as logged in and he can see his account status etc.
> 
> Action taken:
> (1)  Tried later and next day - no change.
> (2)  Confirmed folder permissions for Macintosh HD / Library / Preferences 
> were OK for David as admin.
> (3)  Confirmed folder permissions for User / Library / Preferences were OK 
> for David as admin.
> (4)  Confirmed user security Firewall is "off".
> 
> I searched the Apple Support HT and TS files for permission issues but the 
> specific Alerts received have no diagnostic advice.   So, a lot of time 
> invested for no clear result.  Is it time for a .plist trashing?  Or to 
> re-install iTunes 10.4?  (I can't give any advice about these!)   
> 
> By the way, David has an older iMac (OSX 10.5.8) on the same home network 
> that has no problems with iTunes, purchases, etc.   The new iPad can access 
> iTunes Store (and download items) via WiFi with no problems.  Therefore Apple 
> ID, network and internet assumed to be OK.   But the iMac-iTune problem is 
> making the iPad sync process hairy.
> 
> 
> Regards, Alan
> 
> Alan Smith
>   iMac 21.5" Intel Core 2 Duo 3.06GHz 4M - OSX 10.6.8
>   iPad2;  ATV2   
> 
> 
> 
> 
> On 23/07/2011, at 12:19 PM, David Nicholas   wrote:
>> 
>> For the past 12 hours I have been trying to register my new iPad.
>> 
>> When I select Register Now it tells me the following
>> 
>> Could not complete the iTunes Store request.  The store may be busy.
>> Check your Internet connection or try again later.
>> 
>> I suppose it is possible the iTunes store is busy with people downloading 
>> Lion - but really - I have been trying this repeatedly over a long time.  I 
>> have checked the Apple discussion forum and other people have the same 
>> problem with no suggested solutions offered.
>> 
>> I have a second problem related to the iTunes App store f

iTunes folder permissions problem (was: I can't register my new iPad)

[Alan Smith]

On 23/07/2011, at 12:19 PM, David Nicholas   submitted I 
can't register my new iPad

I have been assisting David by phone to analyse his problem with "I can't 
register my new iPad", and now look for more experienced WAMUG help.   I 
changed the thread subject line because there were no responses to the original 
posting and I thought the most significant problem lay with the second item 
David raised.   All problems are still there!

PART A:iTunes alert message stated by David after purchasing the iPad 
iBooks app:

>  iTunes couldn't download your purchase.   You don't have access for your 
> iTunes Media folder or a folder within it. Change permissions (in the Finder) 
> and then choose Store > Check for Available Downloads.


Action taken: 
(1)  Books and Apps were included in the iTunes Preferences to show in the 
Library.
(2)  Repair Disk Permissions run  on the Macintosh HD via Disk Utility.  (No 
problems indicated).
(3) The iTunes Media folder (located under User/Music/iTunes/iTunes Media) and 
all enclosed items were given full R/W permissions & privileges, even though 
all individual visible folders were already set OK.  Noted that a folder called 
Downloads (empty) exists under iTunes Media.

iMac restarted and iTunes reloaded etc: still get same Alert message when 
checking for available downloads.  

 PART B:  David had also attempted to purchase an iTunes music item and got a 
different Alert warning:

We could not complete your iTunes Store request. You do not have enough access 
privileges for this operation. There was an error in the iTunes Store.  Please 
try again later.

This alert message appears immediately iTunes is loaded.   So it may refer to 
the act of loading the software, or to the unfinished sale of the unsuccessful 
music purchase.   The iStore can be accessed and browsed without problems.   It 
shows David as logged in and he can see his account status etc.

Action taken:
(1)  Tried later and next day - no change.
(2)  Confirmed folder permissions for Macintosh HD / Library / Preferences were 
OK for David as admin.
(3)  Confirmed folder permissions for User / Library / Preferences were OK for 
David as admin.
(4)  Confirmed user security Firewall is "off".

I searched the Apple Support HT and TS files for permission issues but the 
specific Alerts received have no diagnostic advice.   So, a lot of time 
invested for no clear result.  Is it time for a .plist trashing?  Or to 
re-install iTunes 10.4?  (I can't give any advice about these!)   

By the way, David has an older iMac (OSX 10.5.8) on the same home network that 
has no problems with iTunes, purchases, etc.   The new iPad can access iTunes 
Store (and download items) via WiFi with no problems.  Therefore Apple ID, 
network and internet assumed to be OK.   But the iMac-iTune problem is making 
the iPad sync process hairy.


Regards, Alan

Alan Smith
  iMac 21.5" Intel Core 2 Duo 3.06GHz 4M - OSX 10.6.8
  iPad2;  ATV2   




On 23/07/2011, at 12:19 PM, David Nicholas   wrote:
> 
> For the past 12 hours I have been trying to register my new iPad.
> 
> When I select Register Now it tells me the following
> 
> Could not complete the iTunes Store request.  The store may be busy.
> Check your Internet connection or try again later.
> 
> I suppose it is possible the iTunes store is busy with people downloading 
> Lion - but really - I have been trying this repeatedly over a long time.  I 
> have checked the Apple discussion forum and other people have the same 
> problem with no suggested solutions offered.
> 
> I have a second problem related to the iTunes App store from my iMac.
> 
> I tried to download iBooks as an iPad App and got the following
> 
> iTunes couldn't download your purchase
> You don't have access for your iTunes Media folder or a folder within it. 
> Change permissions (in the Finder) and then choose Store > Check for 
> Available Downloads.
> 
> However when I check my Media folder I can't find any permissions which are 
> not read and write.
> 
> I tried to download a book from the iTunes store and got the same error 
> message.
> 
> Now comes the ridiculous situation.  I have successfully downloaded the app 
> and a book using my new iPad.  Therefore my Apple ID connection is OK.
> 
> Are there any suggestions?
> 
> iMac OS X  10.6.8
> 
> iTunes 10.4
> 
> David Nicholas
> 
> 
> 
> 
> 
> 
> 
> -- The WA Macintosh User Group Mailing List --
> Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
> Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
> Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>
> 












-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Permissions problems after installing 10.6.8 update

[Matt Falvey]

Hi Ronni, Ran it again as per your second email and it pretty much did as 
previously stated. So have left it as you recommended, thanks for putting my 
mind at ease.

Every thing else went fine.

Once again thanks for your help.

Matt

On 03/07/2011, at 9:07 PM, Ronda Brown wrote:

> Hi again Matt,
> 
> I have re-read your post. You repair permissions on your System Volume (on 
> the Mounted Drive -Your Startup Volume - Macintosh HD) 
> NOT the WDC WD101EADS-65L5B1 Media.
> Repair Permissions only works properly when performed on the startup volume, 
> not the Main Drive.
> 
> To repair disk permissions:
> 
>   1.  Open Disk Utility on a currently running Mac by opening 
> /Applications/Utilities/Disk Utility
>   2.  Select the system volume you wish to repair from the column on 
> the left.
>   3.  Select the First Aid tab to the right.
>   4.  Click the Repair Disk Permissions button to view and fix any 
> permission problems.
> 
> Cheers,
> Ronni
> 
> On 03/07/2011, at 8:39 PM, Ronda Brown wrote:
> 
>> 
>> Hi Matt,
>> 
>> There is nothing for you to worry about here. They are not actually errors; 
>> it’s just the Permissions database hasn’t been updated for the OS yet. 
>> And you can disregard any that begin with l, as in should be lrwxr-xr-x , 
>> they are lrw-r—r— 
>> 
>> The l before the Permissions is a Unix symlink, somewhat like an alias; it 
>> just means some components have been moved to a different location, but the 
>> old database is still being used. 
>> They are not errors. They can not be "repaired." There is nothing to repair. 
>> 
>> There is nothing you can do to “fix” the “problems” because there is no 
>> problem to fix. As far as the permissions database knows, that is supposed 
>> to be the actual file, not a link to the file (the l in lrwxr-xr-x). 
>> If Apple updates something but doesn’t update the repair permissions 
>> database to reflect the change, it will post the note you see (or something 
>> similar). 
>> 
>> Even though it says “repaired,” it isn’t because it can’t be. 
>> There is nothing wrong; it’s just different. 
>> 
>> They are not truly errors. Note that they begin with “User differs” or 
>> “Permissions differ.” Those are simply alert messages.
>> Same with those containing SUID. Ignore them. They won’t go away and will 
>> appear every time you repair permissions. 
>> They cause no harm.
>> 
>> Have a glass of red, put your feet up and relax, you are ok ;-)
>> 
>> 
>> Cheers,
>> Ronni
>> 
>> 17" MacBook Pro 2.3GHz Quad-Core i7 “Thunderbolt"
>> 2.3GHz / 8GB / 750GB @ 7200rpm HD
>> 
>> OS X 10.6.8 Snow Leopard
>> Windows 7 Ultimate (under sufferance)
>> 
>> 
>> 
>> On 03/07/2011, at 8:25 PM, Matt Falvey wrote:
>> 
>>> 
>>> Hi I have just ran the 10.6.8 update and strictly followed Ronni's  Combo 
>>> Update list.
>>> 
>>> I have just got to Step No. 7. Repair permissions and ran it and had loads 
>>> and loads of events on it. They seemed to be mainly related to two of the 
>>> three Software updates that I ran in Step No 6 Run Software Update, those 
>>> are: Airport Utility and Java.
>>> 
>>> Anyway the final note was Warning: SUID file 
>>> "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ArdAgent"
>>>  has been modified and will not be repaired.
>>> 
>>> Followed by Permissions Repair Complete.
>>> 
>>> This was run on the actual disc WDC WD101EADS-65L5B1 Media.  
>>> 
>>> As it seemed as if the  SUID file, whatever it is, had not been repaired, I 
>>> ran Repair Disk Permissions again expecting it to deal with just it and let 
>>> me know if it could fix it or not.  Instead it went through another 8 or so 
>>> minutes of similar repairs to the files, I would say identical, but I did 
>>> not record them but the system seemed to concentrate on Airport Utility and 
>>> Java and changing -rw-rw-r-- to -rw-r--r-- or lrwxr-xr-x to -rw-r--r-- and 
>>> ended up again with the same warning. Now I know nothing of what the 
>>> Permission repairs is trying to achieve, but if it has already done it 
>>> once, why did it have to do it again?
>>> 
>>> Well, as I was still get the Warning message, I thought I might try and 
>>> repair the permissions on the HD instead.  So I ran Repair on the HD, well 
>>> it told me it was going to take 8 minutes, but took a lot less ti

Re: Permissions problems after installing 10.6.8 update

[Ronda Brown]

Hi again Matt,

I have re-read your post. You repair permissions on your System Volume (on the 
Mounted Drive -Your Startup Volume - Macintosh HD) 
NOT the WDC WD101EADS-65L5B1 Media.
Repair Permissions only works properly when performed on the startup volume, 
not the Main Drive.

To repair disk permissions:

1.  Open Disk Utility on a currently running Mac by opening 
/Applications/Utilities/Disk Utility
2.  Select the system volume you wish to repair from the column on 
the left.
3.  Select the First Aid tab to the right.
4.  Click the Repair Disk Permissions button to view and fix any 
permission problems.

Cheers,
Ronni

On 03/07/2011, at 8:39 PM, Ronda Brown wrote:

> 
> Hi Matt,
> 
> There is nothing for you to worry about here. They are not actually errors; 
> it’s just the Permissions database hasn’t been updated for the OS yet. 
> And you can disregard any that begin with l, as in should be lrwxr-xr-x , 
> they are lrw-r—r— 
> 
> The l before the Permissions is a Unix symlink, somewhat like an alias; it 
> just means some components have been moved to a different location, but the 
> old database is still being used. 
> They are not errors. They can not be "repaired." There is nothing to repair. 
> 
> There is nothing you can do to “fix” the “problems” because there is no 
> problem to fix. As far as the permissions database knows, that is supposed to 
> be the actual file, not a link to the file (the l in lrwxr-xr-x). 
> If Apple updates something but doesn’t update the repair permissions database 
> to reflect the change, it will post the note you see (or something similar). 
> 
> Even though it says “repaired,” it isn’t because it can’t be. 
> There is nothing wrong; it’s just different. 
> 
> They are not truly errors. Note that they begin with “User differs” or 
> “Permissions differ.” Those are simply alert messages.
> Same with those containing SUID. Ignore them. They won’t go away and will 
> appear every time you repair permissions. 
> They cause no harm.
> 
> Have a glass of red, put your feet up and relax, you are ok ;-)
> 
> 
> Cheers,
> Ronni
> 
> 17" MacBook Pro 2.3GHz Quad-Core i7 “Thunderbolt"
> 2.3GHz / 8GB / 750GB @ 7200rpm HD
> 
> OS X 10.6.8 Snow Leopard
> Windows 7 Ultimate (under sufferance)
> 
> 
> 
> On 03/07/2011, at 8:25 PM, Matt Falvey wrote:
> 
>> 
>> Hi I have just ran the 10.6.8 update and strictly followed Ronni's  Combo 
>> Update list.
>> 
>> I have just got to Step No. 7. Repair permissions and ran it and had loads 
>> and loads of events on it. They seemed to be mainly related to two of the 
>> three Software updates that I ran in Step No 6 Run Software Update, those 
>> are: Airport Utility and Java.
>> 
>> Anyway the final note was Warning: SUID file 
>> "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ArdAgent"
>>  has been modified and will not be repaired.
>> 
>> Followed by Permissions Repair Complete.
>> 
>> This was run on the actual disc WDC WD101EADS-65L5B1 Media.  
>> 
>> As it seemed as if the  SUID file, whatever it is, had not been repaired, I 
>> ran Repair Disk Permissions again expecting it to deal with just it and let 
>> me know if it could fix it or not.  Instead it went through another 8 or so 
>> minutes of similar repairs to the files, I would say identical, but I did 
>> not record them but the system seemed to concentrate on Airport Utility and 
>> Java and changing -rw-rw-r-- to -rw-r--r-- or lrwxr-xr-x to -rw-r--r-- and 
>> ended up again with the same warning. Now I know nothing of what the 
>> Permission repairs is trying to achieve, but if it has already done it once, 
>> why did it have to do it again?
>> 
>> Well, as I was still get the Warning message, I thought I might try and 
>> repair the permissions on the HD instead.  So I ran Repair on the HD, well 
>> it told me it was going to take 8 minutes, but took a lot less time, still 
>> gave me loads of Airport Utility and Java errors of the type mentioned above 
>> and finished again with the same SUID warning.
>> 
>> What do I do?  Do I keep repairing permissions 'till I get no errors?  Or do 
>> I presume that the statement "Permissions Repair Complete" is a fact, even 
>> though I know it is not, as each subsequent running of it has shown me?
>> 
>> What does the SUID file warning mean? It has been modified, does that mean 
>> it is broken? Will not be repaired, does that mean it is not necessary to 
>> repair? Does anyone have any idea what it does and how it would have become 
>> modified?
>> 
>> Thanks.
>> 
>> Matt Falvey.
>> 




-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Permissions problems after installing 10.6.8 update

[Ronda Brown]

Hi Matt,

There is nothing for you to worry about here. They are not actually errors; 
it’s just the Permissions database hasn’t been updated for the OS yet. 
And you can disregard any that begin with l, as in should be lrwxr-xr-x , they 
are lrw-r—r— 

The l before the Permissions is a Unix symlink, somewhat like an alias; it just 
means some components have been moved to a different location, but the old 
database is still being used. 
They are not errors. They can not be "repaired." There is nothing to repair. 

There is nothing you can do to “fix” the “problems” because there is no problem 
to fix. As far as the permissions database knows, that is supposed to be the 
actual file, not a link to the file (the l in lrwxr-xr-x). 
If Apple updates something but doesn’t update the repair permissions database 
to reflect the change, it will post the note you see (or something similar). 

Even though it says “repaired,” it isn’t because it can’t be. 
There is nothing wrong; it’s just different. 

They are not truly errors. Note that they begin with “User differs” or 
“Permissions differ.” Those are simply alert messages.
Same with those containing SUID. Ignore them. They won’t go away and will 
appear every time you repair permissions. 
They cause no harm.

Have a glass of red, put your feet up and relax, you are ok ;-)


Cheers,
Ronni

17" MacBook Pro 2.3GHz Quad-Core i7 “Thunderbolt"
2.3GHz / 8GB / 750GB @ 7200rpm HD

OS X 10.6.8 Snow Leopard
Windows 7 Ultimate (under sufferance)



On 03/07/2011, at 8:25 PM, Matt Falvey wrote:

> 
> Hi I have just ran the 10.6.8 update and strictly followed Ronni's  Combo 
> Update list.
> 
> I have just got to Step No. 7. Repair permissions and ran it and had loads 
> and loads of events on it. They seemed to be mainly related to two of the 
> three Software updates that I ran in Step No 6 Run Software Update, those 
> are: Airport Utility and Java.
> 
> Anyway the final note was Warning: SUID file 
> "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ArdAgent"
>  has been modified and will not be repaired.
> 
> Followed by Permissions Repair Complete.
> 
> This was run on the actual disc WDC WD101EADS-65L5B1 Media.  
> 
> As it seemed as if the  SUID file, whatever it is, had not been repaired, I 
> ran Repair Disk Permissions again expecting it to deal with just it and let 
> me know if it could fix it or not.  Instead it went through another 8 or so 
> minutes of similar repairs to the files, I would say identical, but I did not 
> record them but the system seemed to concentrate on Airport Utility and Java 
> and changing -rw-rw-r-- to -rw-r--r-- or lrwxr-xr-x to -rw-r--r-- and ended 
> up again with the same warning. Now I know nothing of what the Permission 
> repairs is trying to achieve, but if it has already done it once, why did it 
> have to do it again?
> 
> Well, as I was still get the Warning message, I thought I might try and 
> repair the permissions on the HD instead.  So I ran Repair on the HD, well it 
> told me it was going to take 8 minutes, but took a lot less time, still gave 
> me loads of Airport Utility and Java errors of the type mentioned above and 
> finished again with the same SUID warning.
> 
> What do I do?  Do I keep repairing permissions 'till I get no errors?  Or do 
> I presume that the statement "Permissions Repair Complete" is a fact, even 
> though I know it is not, as each subsequent running of it has shown me?
> 
> What does the SUID file warning mean? It has been modified, does that mean it 
> is broken? Will not be repaired, does that mean it is not necessary to 
> repair? Does anyone have any idea what it does and how it would have become 
> modified?
> 
> Thanks.
> 
> Matt Falvey.
> 
















-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Permissions problems after installing 10.6.8 update

[Matt Falvey]

Hi I have just ran the 10.6.8 update and strictly followed Ronni's  Combo 
Update list.

I have just got to Step No. 7. Repair permissions and ran it and had loads and 
loads of events on it. They seemed to be mainly related to two of the three 
Software updates that I ran in Step No 6 Run Software Update, those are: 
Airport Utility and Java.

Anyway the final note was Warning: SUID file 
"System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ArdAgent"
 has been modified and will not be repaired.

Followed by Permissions Repair Complete.

This was run on the actual disc WDC WD101EADS-65L5B1 Media.  

As it seemed as if the  SUID file, whatever it is, had not been repaired, I ran 
Repair Disk Permissions again expecting it to deal with just it and let me know 
if it could fix it or not.  Instead it went through another 8 or so minutes of 
similar repairs to the files, I would say identical, but I did not record them 
but the system seemed to concentrate on Airport Utility and Java and changing 
-rw-rw-r-- to -rw-r--r-- or lrwxr-xr-x to -rw-r--r-- and ended up again with 
the same warning. Now I know nothing of what the Permission repairs is trying 
to achieve, but if it has already done it once, why did it have to do it again?

Well, as I was still get the Warning message, I thought I might try and repair 
the permissions on the HD instead.  So I ran Repair on the HD, well it told me 
it was going to take 8 minutes, but took a lot less time, still gave me loads 
of Airport Utility and Java errors of the type mentioned above and finished 
again with the same SUID warning.

What do I do?  Do I keep repairing permissions 'till I get no errors?  Or do I 
presume that the statement "Permissions Repair Complete" is a fact, even though 
I know it is not, as each subsequent running of it has shown me?

What does the SUID file warning mean? It has been modified, does that mean it 
is broken? Will not be repaired, does that mean it is not necessary to repair? 
Does anyone have any idea what it does and how it would have become modified?

Thanks.

Matt Falvey.


-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Permissions Repair

[Joe Mastrella]

Greetings! Thanks for your help.

Cheers, Joe


On Thu, Jul 8, 2010 at 9:33 PM, Ronda Brown  wrote:

>
> On 09/07/2010, at 12:04 PM, Joe Mastrella wrote:
>
> Greetings! I have just purchased a 2009 MacBook. I have run software update
> and repaired permissions. I keep getting this line of text the says, (SUID
> File "SYSTEM/Library/Cores Has been modified and will not be repaired) Does
> any body have a fix.
>
> Cheers, Joe
>
>
> Hi Joe,
>
> You can safely ignore this warning.
> <http://support.apple.com/kb/TS1448?viewlocale=en_US>
>
> Cheers,
> Ronni
>
> 17" MacBook Pro  Intel Core i7
> 2.66GHz / 4GB / 1067 MHz DDR3 / 500GB Serial ATA Drive @ 7200rpm
>
> OS X 10.6.3 Snow Leopard
> Windows 7 Ultimate (under sufferance)
>
>
>
>
>
>
> --
>
> -- The WA Macintosh User Group Mailing List --
> Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
> Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
> Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>
>


-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Permissions Repair

[Ronda Brown]

On 09/07/2010, at 12:04 PM, Joe Mastrella wrote:

> Greetings! I have just purchased a 2009 MacBook. I have run software update 
> and repaired permissions. I keep getting this line of text the says, (SUID 
> File "SYSTEM/Library/Cores Has been modified and will not be repaired) Does 
> any body have a fix.
> 
> Cheers, Joe

Hi Joe,

You can safely ignore this warning.
<http://support.apple.com/kb/TS1448?viewlocale=en_US>

Cheers,
Ronni

17" MacBook Pro  Intel Core i7
2.66GHz / 4GB / 1067 MHz DDR3 / 500GB Serial ATA Drive @ 7200rpm

OS X 10.6.3 Snow Leopard
Windows 7 Ultimate (under sufferance)






-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Permissions Repair

[Joe Mastrella]

Greetings! I have just purchased a 2009 MacBook. I have run software update
and repaired permissions. I keep getting this line of text the says, (SUID
File "SYSTEM/Library/Cores Has been modified and will not be repaired) Does
any body have a fix.

Cheers, Joe


-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Permissions Issues

[Ronda Brown]

Hi Neil,

Sorry for the delay in my reply. I have just arrived back after going up to 
MacWizardry and picking up my new Epson TX810W All-in-One Print / Copy / Scan / 
Photo / Fax.ownership

In answer to your "B2" approach. Yes, it will /should allow the New Account to 
have UID 501

You can change an Account's UID and then switch the items in the account to the 
new UID to recursively change the ownership of files in a folder and all 
subfolders.
I'll supply details in my next email explaining a little about 'User 
Accounts-Permissions-UID & GID'.

> Yes, I love the power and features of Snow Leopard, but sometimes miss the 
> simplicity of Classic! Can’t have it both ways, I guess!

You and me both, Snow Leopard is so exciting and I love learning all it can do. 
Classic never excited me … simplicity has never suited me ;-)

Cheers,
Ronni

On 20/05/2010, at 12:12 PM, Neil Houghton wrote:

> Hi Ronni,
> 
> Thoughts in blue ;-)
> 
> 
> 
> Cheers
> 
> Neil
> -- 
> Neil R. Houghton
> Albany, Western Australia
> Tel: +61 8 9841 6063
> Email: n...@possumology.com
> 
> 
> on 20/5/10 11:23 AM, Ronda Brown at ro...@mac.com wrote:
> 
>> Hi Neil,
>> 
>> Quick reply your comment 
>>>> if deleting the old UID 501 user account has not deleted ALL files with 
>>>> owner 501 then the new account may be allocated a new UID (503) - I think 
>>>> this sort of situation is where you can see the “unknown” user when 
>>>> looking at permissions in finder.
>> 
>> This will happen if you have removed an account or group from the system, 
>> and still have files on the system that were previously associated with that 
>> account.
>> 
> Yes, that’s what I thought – in the event that there would be no UID501 
> account but still files associated with UID 501 that had not been cleared out.
>> 
>> 
>> This happens because the GID, UID, (user and group identifiers),or UUID 
>> (universally unique identifiers) number associated with the file cannot be 
>> matched to the proper account or group in the system. If the user or group 
>> is missing, the system will associate the file to “nobody” or “unknown,” but 
>> sometimes it may think the file belongs to another system account 
>> altogether, and associate it with that one.
>> 
>> I'm working on a post about Owners / Groups / Permissions will port when I 
>> can put it together.
>> 
> Looking forward to it!
>> 
>> 
>> Permissions are so interesting … and confusing at the same time ;-)
>> 
> Yes, I love the power and features of Snow Leopard, but sometimes miss the 
> simplicity of Classic! Can’t have it both ways, I guess!
> 
> 
> 
>> 
>> Cheers,
>> Ronni
>> 
>> On 20/05/2010, at 10:39 AM, Neil Houghton wrote:
>> 
>>> Hi Ronni,
>>> 
>>> HeHe... Yes, I’ve always been wary of the “expert” tag – I used to work in 
>>> an industry with lots of “experts” and the standing joke was something 
>>> about a “spurt” being a drip under pressure and “ex” meaning has-been ;o)
>>> 
>>> However, all on the list appreciate your experience and the time you put 
>>> into your (very comprehensive) answers to various problems.
>>> 
>>> Yes, of course, either approach will require Adam to  have a complete 
>>> backup of his old drive – and we agree that approach A is preferable, if 
>>> more time-consuming.
>>> 
>>> It would be interesting to know just how approach B gets around the change 
>>> of UID – I always thought that “repair permissions” would just change the 
>>> actual read/write/execute permissions – I didn’t think it would change the 
>>> UID.
>>> 
>>> It occurs to me that a “B2” approach, that would cover this, would be to 
>>> create a temporary account to free up UID 501, eg:
>>> 
>>> 
>>>  B2.  Steps 1 to 4 are additional steps to free-up UID 501, steps 5 to 10 
>>> are basically as your original approach B: 
>>> Create a NEW temporary Administrator Account (should have UID 502)
>>> 'Log out' of the OLD Administrator (wrong) Account (UID 501)
>>> 'Log In' to the TEMP Account (UID 502)
>>> DELETE the OLD Account (UID 501)
>>> Create a NEW Administrator Account with exact details of the User Account 
>>> that you have on the backup drive (should be allocated UID 501, which is 
>>> now free)
>>> 'Log out' of the TEMP Account. (UID 502)
>>> 'Log In' to the NEW Administrator Account (UID 501)
>>

Re: Permissions Issues

[Neil Houghton]

Hi Ronni,

Thoughts in blue ;-)



Cheers

Neil
-- 
Neil R. Houghton
Albany, Western Australia
Tel: +61 8 9841 6063
Email: n...@possumology.com


on 20/5/10 11:23 AM, Ronda Brown at ro...@mac.com wrote:

> Hi Neil,
> 
> Quick reply your comment
>>> if deleting the old UID 501 user account has not deleted ALL files with
>>> owner 501 then the new account may be allocated a new UID (503) - I think
>>> this sort of situation is where you can see the ³unknown² user when looking
>>> at permissions in finder.
> 
> This will happen if you have removed an account or group from the system, and
> still have files on the system that were previously associated with that
> account.
> 
Yes, that¹s what I thought ­ in the event that there would be no UID501
account but still files associated with UID 501 that had not been cleared
out.
> 
> 
> This happens because the GID, UID, (user and group identifiers),or UUID
> (universally unique identifiers) number associated with the file cannot be
> matched to the proper account or group in the system. If the user or group is
> missing, the system will associate the file to ³nobody² or ³unknown,² but
> sometimes it may think the file belongs to another system account altogether,
> and associate it with that one.
> 
> I'm working on a post about Owners / Groups / Permissions will port when I can
> put it together.
> 
Looking forward to it!
> 
> 
> Permissions are so interesting Š and confusing at the same time ;-)
> 
Yes, I love the power and features of Snow Leopard, but sometimes miss the
simplicity of Classic! Can¹t have it both ways, I guess!



> 
> Cheers,
> Ronni
> 
> On 20/05/2010, at 10:39 AM, Neil Houghton wrote:
> 
>> Hi Ronni,
>> 
>> HeHe... Yes, I¹ve always been wary of the ³expert² tag ­ I used to work in an
>> industry with lots of ³experts² and the standing joke was something about a
>> ³spurt² being a drip under pressure and ³ex² meaning has-been ;o)
>> 
>> However, all on the list appreciate your experience and the time you put into
>> your (very comprehensive) answers to various problems.
>> 
>> Yes, of course, either approach will require Adam to  have a complete backup
>> of his old drive ­ and we agree that approach A is preferable, if more
>> time-consuming.
>> 
>> It would be interesting to know just how approach B gets around the change of
>> UID ­ I always thought that ³repair permissions² would just change the actual
>> read/write/execute permissions ­ I didn¹t think it would change the UID.
>> 
>> It occurs to me that a ³B2² approach, that would cover this, would be to
>> create a temporary account to free up UID 501, eg:
>> 
>> 
>>  B2.  Steps 1 to 4 are additional steps to free-up UID 501, steps 5 to 10 are
>> basically as your original approach B:
>>> 1. Create a NEW temporary Administrator Account (should have UID 502)
>>> 2. 'Log out' of the OLD Administrator (wrong) Account (UID 501)
>>> 3. 'Log In' to the TEMP Account (UID 502)
>>> 4. DELETE the OLD Account (UID 501)
>>> 5. Create a NEW Administrator Account with exact details of the User Account
>>> that you have on the backup drive (should be allocated UID 501, which is now
>>> free) 
>>> 6. 'Log out' of the TEMP Account. (UID 502)
>>> 7. 'Log In' to the NEW Administrator Account (UID 501)
>>> 8. DELETE the TEMP Account (UID 502)
>>> 9. Transfer your Data across from the Backup Drive.
>> 
>> This should achieve the same as approach B but allow the new account to have
>> UID 501
>> 
>> One problem might be at step 5 ­ if deleting the old UID 501 user account has
>> not deleted ALL files with owner 501 then the new account may be allocated a
>> new UID (503) - I think this sort of situation is where you can see the
>> ³unknown² user when looking at permissions in finder.
>> 
>> Just my thoughts ­ as I say, I still find many aspects of permissions
>> confusing ­ I am basing the above on bits and pieces of my (failing) memory
>> from sorting out past problems I had.
>> 
>> 
>> 
>> Cheers
>> 
>> 
>> 
>> Neil





-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Permissions Issues

[Ronda Brown]

Hi Neil,

Quick reply your comment 
>> if deleting the old UID 501 user account has not deleted ALL files with 
>> owner 501 then the new account may be allocated a new UID (503) - I think 
>> this sort of situation is where you can see the “unknown” user when looking 
>> at permissions in finder.

This will happen if you have removed an account or group from the system, and 
still have files on the system that were previously associated with that 
account.
This happens because the GID, UID, (user and group identifiers),or UUID 
(universally unique identifiers) number associated with the file cannot be 
matched to the proper account or group in the system. If the user or group is 
missing, the system will associate the file to “nobody” or “unknown,” but 
sometimes it may think the file belongs to another system account altogether, 
and associate it with that one.

I'm working on a post about Owners / Groups / Permissions will port when I can 
put it together.
Permissions are so interesting … and confusing at the same time ;-)

Cheers,
Ronni

On 20/05/2010, at 10:39 AM, Neil Houghton wrote:

> Hi Ronni,
> 
> HeHe... Yes, I’ve always been wary of the “expert” tag – I used to work in an 
> industry with lots of “experts” and the standing joke was something about a 
> “spurt” being a drip under pressure and “ex” meaning has-been ;o)
> 
> However, all on the list appreciate your experience and the time you put into 
> your (very comprehensive) answers to various problems.
> 
> Yes, of course, either approach will require Adam to  have a complete backup 
> of his old drive – and we agree that approach A is preferable, if more 
> time-consuming.
> 
> It would be interesting to know just how approach B gets around the change of 
> UID – I always thought that “repair permissions” would just change the actual 
> read/write/execute permissions – I didn’t think it would change the UID.
> 
> It occurs to me that a “B2” approach, that would cover this, would be to 
> create a temporary account to free up UID 501, eg:
> 
> 
>  B2.  Steps 1 to 4 are additional steps to free-up UID 501, steps 5 to 10 are 
> basically as your original approach B: 
> Create a NEW temporary Administrator Account (should have UID 502)
> 'Log out' of the OLD Administrator (wrong) Account (UID 501)
> 'Log In' to the TEMP Account (UID 502)
> DELETE the OLD Account (UID 501)
> Create a NEW Administrator Account with exact details of the User Account 
> that you have on the backup drive (should be allocated UID 501, which is now 
> free)
> 'Log out' of the TEMP Account. (UID 502)
> 'Log In' to the NEW Administrator Account (UID 501)
> DELETE the TEMP Account (UID 502)
> Transfer your Data across from the Backup Drive.
> 
> This should achieve the same as approach B but allow the new account to have 
> UID 501
> 
> One problem might be at step 5 – if deleting the old UID 501 user account has 
> not deleted ALL files with owner 501 then the new account may be allocated a 
> new UID (503) - I think this sort of situation is where you can see the 
> “unknown” user when looking at permissions in finder.
> 
> Just my thoughts – as I say, I still find many aspects of permissions 
> confusing – I am basing the above on bits and pieces of my (failing) memory 
> from sorting out past problems I had.
> 
> 
> 
> Cheers
> 
> 
> 
> Neil
> -- 
> Neil R. Houghton
> Albany, Western Australia
> Tel: +61 8 9841 6063
> Email: n...@possumology.com
> 
> 
> 
> 
> on 19/5/10 2:19 PM, Ronda Brown at ro...@mac.com wrote:
> 
>> Hi Neil,
>> 
>> I have not been avoiding your questions, just time has not permitted me to 
>> answer as yet. I will get back with a more thorough answer to 'Permissions' 
>> in Snow Leopard when possible. Also I don't profess to be an expert on 
>> Permissions, I don't profess to be an expert in anything ;-)
>> 
>> When you start up a brand new Mac, or start up after an Erase and Install, 
>> you will be asked if you want to migrate. 
>> That is the preferred time to migrate from your old Mac or backup to your 
>> New Mac or New Hard Drive.
>> 
>> I would prefer Adam to do A. To do and Erase & clean Install of SL & then 
>> let Migration Assistant run & migrate everything across, which will bring 
>> his User Account / Settings & Files across.
>> 
>> With way B. You DELETE the OLD (wrong) Administrator Account BEFORE you 
>> transfer the data across from the backup drive.
>> This way, when you then 'Repair Permissions', the User should (hopefully) 
>> have the correct permissions on his data. 
>> I have done it this way

Re: Permissions Issues

[Neil Houghton]

Hi Ronni,

HeHe... Yes, I¹ve always been wary of the ³expert² tag ­ I used to work in
an industry with lots of ³experts² and the standing joke was something about
a ³spurt² being a drip under pressure and ³ex² meaning has-been ;o)

However, all on the list appreciate your experience and the time you put
into your (very comprehensive) answers to various problems.

Yes, of course, either approach will require Adam to  have a complete backup
of his old drive ­ and we agree that approach A is preferable, if more
time-consuming.

It would be interesting to know just how approach B gets around the change
of UID ­ I always thought that ³repair permissions² would just change the
actual read/write/execute permissions ­ I didn¹t think it would change the
UID.

It occurs to me that a ³B2² approach, that would cover this, would be to
create a temporary account to free up UID 501, eg:


 B2.  Steps 1 to 4 are additional steps to free-up UID 501, steps 5 to 10
are basically as your original approach B:
> 1. Create a NEW temporary Administrator Account (should have UID 502)
> 2. 'Log out' of the OLD Administrator (wrong) Account (UID 501)
> 3. 'Log In' to the TEMP Account (UID 502)
> 4. DELETE the OLD Account (UID 501)
> 5. Create a NEW Administrator Account with exact details of the User Account
> that you have on the backup drive (should be allocated UID 501, which is now
> free) 
> 6. 'Log out' of the TEMP Account. (UID 502)
> 7. 'Log In' to the NEW Administrator Account (UID 501)
> 8. DELETE the TEMP Account (UID 502)
> 9. Transfer your Data across from the Backup Drive.

This should achieve the same as approach B but allow the new account to have
UID 501

One problem might be at step 5 ­ if deleting the old UID 501 user account
has not deleted ALL files with owner 501 then the new account may be
allocated a new UID (503) - I think this sort of situation is where you can
see the ³unknown² user when looking at permissions in finder.

Just my thoughts ­ as I say, I still find many aspects of permissions
confusing ­ I am basing the above on bits and pieces of my (failing) memory
from sorting out past problems I had.



Cheers



Neil
-- 
Neil R. Houghton
Albany, Western Australia
Tel: +61 8 9841 6063
Email: n...@possumology.com




on 19/5/10 2:19 PM, Ronda Brown at ro...@mac.com wrote:

> Hi Neil,
> 
> I have not been avoiding your questions, just time has not permitted me to
> answer as yet. I will get back with a more thorough answer to 'Permissions' in
> Snow Leopard when possible. Also I don't profess to be an expert on
> Permissions, I don't profess to be an expert in anything ;-)
> 
> When you start up a brand new Mac, or start up after an Erase and Install, you
> will be asked if you want to migrate.
> That is the preferred time to migrate from your old Mac or backup to your New
> Mac or New Hard Drive.
> 
> I would prefer Adam to do A. To do and Erase & clean Install of SL & then let
> Migration Assistant run & migrate everything across, which will bring his User
> Account / Settings & Files across.
> 
> With way B. You DELETE the OLD (wrong) Administrator Account BEFORE you
> transfer the data across from the backup drive.
> This way, when you then 'Repair Permissions', the User should (hopefully) have
> the correct permissions on his data.
> I have done it this way before and I'm fairly sure the UID was 501 Š At least
> I did not experience any permission problems.
> But, I'm open to anyone disagreeing with this.
> 
> Of course neither of these ways will be possible if Adam doesn't  have a
> complete backup of his old drive!
> 
> Cheers,
> Ronni
> 
> On 19/05/2010, at 10:47 AM, Neil Houghton wrote:
> 
>> Hi Ronni & Adam,
>> 
>> I have been following this with interest ­ I have had to sort out permissions
>> problems in the past, I generally get there in the end, but I still find many
>> aspects of permissions confusing.
>> 
>> 
>> I am hoping that Ronni could clarify how one area works:
>> 
>> 
>> I can see how approach A works ­ this is basically just like taking home a
>> new computer and migrating the data over from the old computer.
>> 
>> With approach B, however how does the UID get back in sync ­ or does OSX work
>> around that?
>> 
>> To elaborate on my query:
>> 
>> * It sounds like the old computer was set up with just the primary user
>> account, which would have had the default UID of 501 for the main account ­
>> this is the account now on the back-up disk that we want to restore.
>> * The technician set-up one main account on the new HD ­ which is therefore
>> also UID 501 ­ but with other details wrong (as per Adam¹s id printo

Re: Permissions Issues

[Ronda Brown]

Hi Neil,

I have not been avoiding your questions, just time has not permitted me to 
answer as yet. I will get back with a more thorough answer to 'Permissions' in 
Snow Leopard when possible. Also I don't profess to be an expert on 
Permissions, I don't profess to be an expert in anything ;-)

When you start up a brand new Mac, or start up after an Erase and Install, you 
will be asked if you want to migrate. 
That is the preferred time to migrate from your old Mac or backup to your New 
Mac or New Hard Drive.

I would prefer Adam to do A. To do and Erase & clean Install of SL & then let 
Migration Assistant run & migrate everything across, which will bring his User 
Account / Settings & Files across.

With way B. You DELETE the OLD (wrong) Administrator Account BEFORE you 
transfer the data across from the backup drive.
This way, when you then 'Repair Permissions', the User should (hopefully) have 
the correct permissions on his data. 
I have done it this way before and I'm fairly sure the UID was 501 … At least I 
did not experience any permission problems.
But, I'm open to anyone disagreeing with this.

Of course neither of these ways will be possible if Adam doesn't  have a 
complete backup of his old drive!

Cheers,
Ronni

On 19/05/2010, at 10:47 AM, Neil Houghton wrote:

> Hi Ronni & Adam,
> 
> I have been following this with interest – I have had to sort out permissions 
> problems in the past, I generally get there in the end, but I still find many 
> aspects of permissions confusing.
> 
> 
> I am hoping that Ronni could clarify how one area works:
> 
> 
> I can see how approach A works – this is basically just like taking home a 
> new computer and migrating the data over from the old computer.
> 
> With approach B, however how does the UID get back in sync – or does OSX work 
> around that?
> 
> To elaborate on my query:
> 
> It sounds like the old computer was set up with just the primary user 
> account, which would have had the default UID of 501 for the main account – 
> this is the account now on the back-up disk that we want to restore.
> The technician set-up one main account on the new HD – which is therefore 
> also UID 501 – but with other details wrong (as per Adam’s id printout:
>>> admins-imac:~ adam3$ id
>>> uid=501(adam3) ..
> If Adam creates a NEW Administrator Account with exact details of the User 
> Account that he has on the backup drive it will presumably get a UID of 502 
> (501 is already taken) - so the exact details may be the same but the UID 
> will be different.
> When Adam DELETES the OLD Account – he is deleting the account currently with 
> UID 501.
> 
> 
> So this is where I am unclear as to how things proceed:
> 
> Would deleting account UID 501 result in the new account getting its UID 
> re-assigned from 502 to 501? or
> Would migrating over the OLD account UID 501 result in the new account 
> getting its UID re-assigned from 502 to 501? or
> Would the new account retain the UID 502 but the migrated files get their 
> ownership modified to suit this? or
> I’m missing the point, what happens is 
> 
> If the (new) main account has UID 502, would there be any problems at the 
> next migration to a new computer (with main account UID 501)?
> 
> 
> Ronni, I hope you don’t mind me jumping in with these questions – but I know 
> that many of us find permissions intricacies somewhat confusing.
> 
> 
> I know I had big problems in the past when I set up a new computer with an 
> account that was ALMOST the same as the old one! (I can’t remember now 
> whether the short names were the same but the user names different, or 
> vice-versa, or names the same but UIDs different) - I remember it was a 
> painful process sorting it out.
> 
> 
> Cheers
> 
> 
> 
> Neil
> 
> -- 
> Neil R. Houghton
> Albany, Western Australia
> Tel: +61 8 9841 6063
> Email: n...@possumology.com
> 
> 
> 
> on 19/5/10 9:30 AM, Ronda Brown at ro...@mac.com wrote:
> 
>> Hi Adam,
>> 
>> On 18/05/2010, at 8:35 PM, Adam Lippiatt wrote:
>> 
>>> Ronni
>>> 
>>> Thanks for this.  I did have a backup of the drive but unfortunately after 
>>> having the machine for more than a month I think the technician got 
>>> exasperated and just wanted to see the back of it.  So, I got a new hard 
>>> drive which was, unfortuantely, a little noisier than the original and also 
>>> the install was done on a new user account which did not have the same name 
>>> as the old one.
>>> 
>>> So, perhaps this is the source of the permissions problems.  
>> 
>> Definitely, for sure … You do

Re: Permissions Issues

[Neil Houghton]

Hi Ronni & Adam,

I have been following this with interest ­ I have had to sort out
permissions problems in the past, I generally get there in the end, but I
still find many aspects of permissions confusing.


I am hoping that Ronni could clarify how one area works:


I can see how approach A works ­ this is basically just like taking home a
new computer and migrating the data over from the old computer.

With approach B, however how does the UID get back in sync ­ or does OSX
work around that?

To elaborate on my query:

* It sounds like the old computer was set up with just the primary user
account, which would have had the default UID of 501 for the main account ­
this is the account now on the back-up disk that we want to restore.
* The technician set-up one main account on the new HD ­ which is therefore
also UID 501 ­ but with other details wrong (as per Adam¹s id printout:
>> admins-imac:~ adam3$ id
>> uid=501(adam3) ..
* If Adam creates a NEW Administrator Account with exact details of the User
Account that he has on the backup drive it will presumably get a UID of 502
(501 is already taken) - so the exact details may be the same but the UID
will be different. 
* When Adam DELETES the OLD Account ­ he is deleting the account currently
with UID 501.


So this is where I am unclear as to how things proceed:

* Would deleting account UID 501 result in the new account getting its UID
re-assigned from 502 to 501? or
* Would migrating over the OLD account UID 501 result in the new account
getting its UID re-assigned from 502 to 501? or
* Would the new account retain the UID 502 but the migrated files get their
ownership modified to suit this? or
* I¹m missing the point, what happens is 

If the (new) main account has UID 502, would there be any problems at the
next migration to a new computer (with main account UID 501)?


Ronni, I hope you don¹t mind me jumping in with these questions ­ but I know
that many of us find permissions intricacies somewhat confusing.


I know I had big problems in the past when I set up a new computer with an
account that was ALMOST the same as the old one! (I can¹t remember now
whether the short names were the same but the user names different, or
vice-versa, or names the same but UIDs different) - I remember it was a
painful process sorting it out.


Cheers



Neil

-- 
Neil R. Houghton
Albany, Western Australia
Tel: +61 8 9841 6063
Email: n...@possumology.com



on 19/5/10 9:30 AM, Ronda Brown at ro...@mac.com wrote:

> Hi Adam,
> 
> On 18/05/2010, at 8:35 PM, Adam Lippiatt wrote:
> 
>> Ronni
>> 
>> Thanks for this.  I did have a backup of the drive but unfortunately after
>> having the machine for more than a month I think the technician got
>> exasperated and just wanted to see the back of it.  So, I got a new hard
>> drive which was, unfortuantely, a little noisier than the original and also
>> the install was done on a new user account which did not have the same name
>> as the old one.
>> 
>> So, perhaps this is the source of the permissions problems.
> 
> Definitely, for sure Š You don't 'own' (have Permissions) of the files,
> another User does! As I explained in my previous email.
> 
> A couple of things need clarifying Adam.
> 1. You say you DID have a backup of the old Hard Drive (User Accounts /
> Settings / Data) Š do you still have that backup?
> 
> 2. Did the Technician do the New Install and create a New (different) User on
> the new Hard Drive?
> If so, he would have / or should have told you that you needed to create a new
> Administrator Account with EXACTLY the 'same User Name & Short Name  &
> Password' that your Original Drive (& backup) have.
> Then 'Log Out' of the 'Wrong  Account' , 'Log In' to the New Account (you have
> created exactly as is on the backup drive) & under System Preferences DELETE
> the 'Wrong User Account'.
> ThenTransfer everything across from the firewire 'Backup' Drive.
> 
> What to recommend you do now to sort the mess out???
> A or B?
> 
> A.  Do a complete Erase of your Hard Drive and Clean Install of Snow Leopard.
>  1. Startup from the SL install disk, erase the hard drive with disk
> utility (on the Disc) .
>   2. Quit disk utility,  and proceed with the install.
>   3. On the first reboot it will offer to migrate your data from a Time
> machine backup or an External Drive. Choose your External Drive and  migrate
> from the backup you have.
>  (i.e When your computer restarts with the clean install, DON'T create a
> User Account, let Migration Assistant transfer your User Account / Settings /
> Files from the External Backup Drive Š )
> 
> 
>  B.  Do 2 that I mentioned above:
>   1. Create a NEW Adm

Re: Permissions Issues

[Ronda Brown]

Hi Adam,

On 18/05/2010, at 8:35 PM, Adam Lippiatt wrote:

> Ronni
> 
> Thanks for this.  I did have a backup of the drive but unfortunately after 
> having the machine for more than a month I think the technician got 
> exasperated and just wanted to see the back of it.  So, I got a new hard 
> drive which was, unfortuantely, a little noisier than the original and also 
> the install was done on a new user account which did not have the same name 
> as the old one.

> 
> So, perhaps this is the source of the permissions problems.  

Definitely, for sure … You don't 'own' (have Permissions) of the files, another 
User does! As I explained in my previous email.

A couple of things need clarifying Adam.
1. You say you DID have a backup of the old Hard Drive (User Accounts / 
Settings / Data) … do you still have that backup?

2. Did the Technician do the New Install and create a New (different) User on 
the new Hard Drive? 
If so, he would have / or should have told you that you needed to create a new 
Administrator Account with EXACTLY the 'same User Name & Short Name  & 
Password' that your Original Drive (& backup) have. 
Then 'Log Out' of the 'Wrong  Account' , 'Log In' to the New Account (you have 
created exactly as is on the backup drive) & under System Preferences DELETE 
the 'Wrong User Account'.
ThenTransfer everything across from the firewire 'Backup' Drive.

What to recommend you do now to sort the mess out???
A or B?

A.  Do a complete Erase of your Hard Drive and Clean Install of Snow Leopard.
 1. Startup from the SL install disk, erase the hard drive with disk 
utility (on the Disc) .
  2. Quit disk utility,  and proceed with the install. 
  3. On the first reboot it will offer to migrate your data from a Time 
machine backup or an External Drive. Choose your External Drive and  migrate 
from the backup you have. 
 (i.e When your computer restarts with the clean install, DON'T create a 
User Account, let Migration Assistant transfer your User Account / Settings / 
Files from the External Backup Drive … )


 B.  Do 2 that I mentioned above: 
  1. Create a NEW Administrator Account with exact details of the User 
Account that you have on the backup drive
  2. 'Log out' of the OLD Administrator (wrong) Account.
  3. 'Log In' to the NEW Administrator Account
  4. DELETE the OLD Account
  5. Transfer your Data across from the Backup Drive.

Cheers,
Ronni


> I did the id command and got the following:
> 
> admins-imac:~ adam3$ id
> uid=501(adam3) gid=20(staff) 
> groups=20(staff),101(com.apple.sharepoint.group.1),204(_developer),100(_lpoperator),98(_lpadmin),81(_appserveradm),80(admin),79(_appserverusr),61(localaccounts),12(everyone),401(com.apple.access_screensharing)
> admins-imac:~ adam3$ 
> 
> Thanks for your help.
> 
> Adam 
> 
> Begin forwarded message:
> 
>> Hi Adam,
>> 
>> On 17/05/2010, at 12:03 PM, Adam Lippiatt wrote:
>> 
>>> Thanks Ronda
>>> 
>>> I will look into that. Unfortunately when the hard drive died I had to do a 
>>> lot of manual shifting of things as the service people could only give me a 
>>> fresh install with the data sitting in folders on the desktop. As time goes 
>>> by I am getting through all of the little issues.
>> 
>> Hmmm, this doesn't sound good to me. From reading above, I take it you did 
>> not have a 'Backup' of the Drive before it was corrupted?
>> If the service people have just given you what they recovered from the 
>> corrupted drive … and you are trying to copy these files onto the fresh 
>> install, there could be corruption in some of the files.
>> 
>> Did you create an 'exact' User Account on the Fresh Install as the 'User' 
>> you had on the original hard drive?
>> If you didn't, you will run into Permission problems, as you will find the 
>> UID & GID are not the same.
>> 
>> Mac OS X displays the user name of the account that owns a folder or file, 
>> it’s easy to assume that that account with that user name owns the item. In 
>> reality, it’s not quite so simple. 
>> The owner is actually determined by a number called the UID—the user 
>> identification number, not by the user name. 
>> In addition the group is, in fact, determined by the GID—the group 
>> identification number. 
>> 
>> To reveal your account’s UID and primary GID, type id in a Terminal window 
>> (and then press Return). 
>> The output of the id command looks like this: 
>> ronni$ id
>> uid=501(ronni) gid=20(staff) 
>> groups=20(staff),204(_developer),100(_lpoperator),98(_lpadmin),81(_appserveradm),80(admin),79(_appserverusr),61(localaccounts),12(everyone),401(com.apple.access_screensharing)
> 
> 


-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Fwd: Permissions Issues

[Adam Lippiatt]

Hi Ronda

It shows a very long list of things - some things I spotted that don't appear 
in your list:

.OfflineCache
.dat00f3.001
.identity

All backed up - give your idea a go?

By the way I tried to find the file using Neil's tip in finder and finding 
invisible files - it didn't turn up though (found a bunch of other things).

The search string in terminal did find the file:

"/Users/admin/Library/Mail/Mac-adam.lippiatt/.mboxCache.plist"

I suppose I stay 'admin' forever now?

Thanks

Adam (Admin)

Begin forwarded message:

> From: Ronda Brown 
> Date: 15 May 2010 3:21:31 PM AWST
> To: WAMUG Mailing List 
> Subject: Re: Permissions Issues
> Reply-To: WAMUG Mailing List 
> 
> 
> On 15/05/2010, at 9:31 AM, Adam Lippiatt wrote:
> 
>> 
>> Hi there
>> 
>> I have been having a few permissions problems after a hard drive corrupted 
>> and was replaced.
>> 
>> This is the latest one which I think is causing some bad behaviour in Mail.
>> 
>> 15/05/10 9:28:35 AM  Mail[234]   Error writing to 
>> /Users/admin/Library/Mail/Mac-adam.lippiatt/.mboxCache.plist: Error 
>> Domain=NSCocoaErrorDomain Code=513 UserInfo=0x1299c26c0 "You don’t have 
>> permission to save the file “.mboxCache.plist” in the folder 
>> “Mac-adam.lippiatt”." Underlying Error=(Error Domain=NSPOSIXErrorDomain 
>> Code=13 "The operation couldn’t be completed. Permission denied")
>> 
>> Unfortunately I can't find this file.  No problem though - I just apply 
>> permissions to enclosed items.  But, no luck with that either.
> 
> Hi Adam,
> 
> You need to delete the .mboxCache.plist. Why you can't find it is a hidden 
> file… 
> 
> 1. Quit Mail and try this on the command line (Terminal.app) to find them:
> 2. Open a Terminal window and paste this in:
> 
> find ~/Library/Mail -name .\*
> 
> It should only find cache files like '.DS_Store', '.mboxCache.plist', 
> '.OfflineCache', '.dontIndex', and '.index.ready'. 
> If so, and if everything is backed up, run:
> 
> find ~/Library/Mail -name .\* -delete
> 
> NB: Don't run this if the first listing looks like it's showing e-mails. I 
> also recommend checking that you have a backup first. 
> 
> 3.Now launch mail and select "Mailbox:Rebuild" from the menu. 
> 
> 
> Cheers,
> Ronni
> 
> 17" MacBook Pro  Intel Core i7
> 2.66GHz / 4GB / 1067 MHz DDR3 / 500GB Serial ATA Drive @ 7200rpm
> 
> OS X 10.6.3 Snow Leopard
> Windows 7 Ultimate (under sufferance)
> 
> 
> 
> 
> 
> 
> 
> -- The WA Macintosh User Group Mailing List --
> Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
> Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
> Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>




_
Adam Lippiatt
adam.lippi...@me.com
0402 301 706



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Fwd: Permissions Issues

[Adam Lippiatt]

Ronni

Thanks for this.  I did have a backup of the drive but unfortunately after 
having the machine for more than a month I think the technician got exasperated 
and just wanted to see the back of it.  So, I got a new hard drive which was, 
unfortuantely, a little noisier than the original and also the install was done 
on a new user account which did not have the same name as the old one.

So, perhaps this is the source of the permissions problems.  I did the id 
command and got the following:

admins-imac:~ adam3$ id
uid=501(adam3) gid=20(staff) 
groups=20(staff),101(com.apple.sharepoint.group.1),204(_developer),100(_lpoperator),98(_lpadmin),81(_appserveradm),80(admin),79(_appserverusr),61(localaccounts),12(everyone),401(com.apple.access_screensharing)
admins-imac:~ adam3$ 

Thanks for your help.

Adam 

Begin forwarded message:

> Hi Adam,
> 
> On 17/05/2010, at 12:03 PM, Adam Lippiatt wrote:
> 
>> Thanks Ronda
>> 
>> I will look into that. Unfortunately when the hard drive died I had to do a 
>> lot of manual shifting of things as the service people could only give me a 
>> fresh install with the data sitting in folders on the desktop. As time goes 
>> by I am getting through all of the little issues.
> 
> Hmmm, this doesn't sound good to me. From reading above, I take it you did 
> not have a 'Backup' of the Drive before it was corrupted?
> If the service people have just given you what they recovered from the 
> corrupted drive … and you are trying to copy these files onto the fresh 
> install, there could be corruption in some of the files.
> 
> Did you create an 'exact' User Account on the Fresh Install as the 'User' you 
> had on the original hard drive?
> If you didn't, you will run into Permission problems, as you will find the 
> UID & GID are not the same.
> 
> Mac OS X displays the user name of the account that owns a folder or file, 
> it’s easy to assume that that account with that user name owns the item. In 
> reality, it’s not quite so simple. 
> The owner is actually determined by a number called the UID—the user 
> identification number, not by the user name. 
> In addition the group is, in fact, determined by the GID—the group 
> identification number. 
> 
> To reveal your account’s UID and primary GID, type id in a Terminal window 
> (and then press Return). 
> The output of the id command looks like this: 
> ronni$ id
> uid=501(ronni) gid=20(staff) 
> groups=20(staff),204(_developer),100(_lpoperator),98(_lpadmin),81(_appserveradm),80(admin),79(_appserverusr),61(localaccounts),12(everyone),401(com.apple.access_screensharing)




_
Adam Lippiatt
adam.lippi...@me.com
0402 301 706



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Permissions Issues

[Ronda Brown]

Hi Adam,

Adam, is your User Account name 'admin'?  This has been worrying me all 
week-end, to me it doesn't look right ;-)
Normally it is similar to my User Account i.e:   
/Users/ronni/Library/Mail/Mac-ronni/


If my original suggestion has not solved your problem, you could try using the 
rm command in Terminal to delete the file.

rm /Users/admin/Library/Mail/Mac-adam.lippiatt/.mboxCache.plist

Are you experiencing other problems? You mentioned 
>>> I have been having a few permissions problems after a hard drive corrupted 
>>> and was replaced.

If so we need more details to be able to help. How did you transfer the Data 
from the corrupted drive & are you running OS X 10.6.3?

Cheers,
Ronni


On 16/05/2010, at 6:27 PM, Adam Lippiatt wrote:

> Thanks a lot for this Ronda.  Now that night has fallen on this beautiful 
> day, I will have a look at applying your solution to my problem.  Thanks a 
> lot for spending the time to respond.
> 
> Adam
> 
> ___
> Adam Lippiatt
> 0402 301 706
> 
>  
> On Saturday, May 15, 2010, at 03:21PM, "Ronda Brown"  wrote:
> >
> 
> On 15/05/2010, at 9:31 AM, Adam Lippiatt wrote:
> 
>> 
>> Hi there
>> 
>> I have been having a few permissions problems after a hard drive corrupted 
>> and was replaced.
>> 
>> This is the latest one which I think is causing some bad behaviour in Mail.
>> 
>> 15/05/10 9:28:35 AM  Mail[234]   Error writing to 
>> /Users/admin/Library/Mail/Mac-adam.lippiatt/.mboxCache.plist: Error 
>> Domain=NSCocoaErrorDomain Code=513 UserInfo=0x1299c26c0 "You don’t have 
>> permission to save the file “.mboxCache.plist” in the folder 
>> “Mac-adam.lippiatt”." Underlying Error=(Error Domain=NSPOSIXErrorDomain 
>> Code=13 "The operation couldn’t be completed. Permission denied")
>> 
>> Unfortunately I can't find this file.  No problem though - I just apply 
>> permissions to enclosed items.  But, no luck with that either.
> 
> Hi Adam,
> 
> You need to delete the .mboxCache.plist. Why you can't find it is a hidden 
> file… 
> 
> 1. Quit Mail and try this on the command line (Terminal.app) to find them:
> 2. Open a Terminal window and paste this in:
> 
> find ~/Library/Mail -name .\*
> 
> It should only find cache files like '.DS_Store', '.mboxCache.plist', 
> '.OfflineCache', '.dontIndex', and '.index.ready'. 
> If so, and if everything is backed up, run:
> 
> find ~/Library/Mail -name .\* -delete
> 
> NB: Don't run this if the first listing looks like it's showing e-mails. I 
> also recommend checking that you have a backup first. 
> 
> 3.Now launch mail and select "Mailbox:Rebuild" from the menu. 
> 
> 
> Cheers,
> Ronni
> 
> 17" MacBook Pro  Intel Core i7
> 2.66GHz / 4GB / 1067 MHz DDR3 / 500GB Serial ATA Drive @ 7200rpm
> 
> OS X 10.6.3 Snow Leopard
> Windows 7 Ultimate (under sufferance)
> 
> 



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Permissions Issues

[Neil Houghton]

Hi Adam,

Just to add to what Ronni said ­ Terminal is very powerful and lets you do
all manner of things, however sometimes I find it easier to check out
various hidden file using the Finder.

The trick here is to add ³File Visibility² to the list of finder search
criteria ­ to do this invoke the find command in finder and then in the
pull-down search criteria list (probably showing ³kind² by default) select
³other² and a box will slide open allowing you to ³Select a Search
attribute² and, if you scroll down the list, you can find the entry:

Attribute: File invisible
Description: Whether the file is visible

If you click the ³In menu² checkbox, next to this item, you will now have a
new item ³File Visibility² in your pull-down menu.

You can now do a finder search with the search set as ³File Visibility² is
³Invisible Items² to find this or any other invisible files.


I find this feature very useful to track down these sorts of files ­
particularly where you know there IS a hidden file related to something but
don¹t remember the exact name.


Cheers




Neil
-- 
Neil R. Houghton
Albany, Western Australia
Tel: +61 8 9841 6063
Email: n...@possumology.com




on 15/5/10 3:21 PM, Ronda Brown at ro...@mac.com wrote:

> 
> On 15/05/2010, at 9:31 AM, Adam Lippiatt wrote:
> 
>> 
>> Hi there
>> 
>> I have been having a few permissions problems after a hard drive corrupted
>> and was replaced.
>> 
>> This is the latest one which I think is causing some bad behaviour in Mail.
>> 
>> 15/05/10 9:28:35 AM Mail[234] Error writing to
>> /Users/admin/Library/Mail/Mac-adam.lippiatt/.mboxCache.plist: Error
>> Domain=NSCocoaErrorDomain Code=513 UserInfo=0x1299c26c0 "You don¹t have
>> permission to save the file ³.mboxCache.plist² in the folder
>> ³Mac-adam.lippiatt²." Underlying Error=(Error Domain=NSPOSIXErrorDomain
>> Code=13 "The operation couldn¹t be completed. Permission denied")
>> 
>> Unfortunately I can't find this file.  No problem though - I just apply
>> permissions to enclosed items.  But, no luck with that either.
> 
> Hi Adam,
> 
> You need to delete the .mboxCache.plist. Why you can't find it is a hidden
> fileŠ 
> 
> 1. Quit Mail and try this on the command line (Terminal.app) to find them:
> 2. Open a Terminal window and paste this in:
> 
> find ~/Library/Mail -name .\*
> 
> It should only find cache files like '.DS_Store', '.mboxCache.plist',
> '.OfflineCache', '.dontIndex', and '.index.ready'.
> If so, and if everything is backed up, run:
> 
> find ~/Library/Mail -name .\* -delete
> 
> NB: Don't run this if the first listing looks like it's showing e-mails. I
> also recommend checking that you have a backup first.
> 
> 3.Now launch mail and select "Mailbox:Rebuild" from the menu.
> 
> 
> Cheers,
> Ronni
> 
> 17" MacBook Pro  Intel Core i7
> 2.66GHz / 4GB / 1067 MHz DDR3 / 500GB Serial ATA Drive @ 7200rpm
> 
> OS X 10.6.3 Snow Leopard
> Windows 7 Ultimate (under sufferance)



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Permissions Issues

[Ronda Brown]

On 15/05/2010, at 9:31 AM, Adam Lippiatt wrote:

> 
> Hi there
> 
> I have been having a few permissions problems after a hard drive corrupted 
> and was replaced.
> 
> This is the latest one which I think is causing some bad behaviour in Mail.
> 
> 15/05/10 9:28:35 AM   Mail[234]   Error writing to 
> /Users/admin/Library/Mail/Mac-adam.lippiatt/.mboxCache.plist: Error 
> Domain=NSCocoaErrorDomain Code=513 UserInfo=0x1299c26c0 "You don’t have 
> permission to save the file “.mboxCache.plist” in the folder 
> “Mac-adam.lippiatt”." Underlying Error=(Error Domain=NSPOSIXErrorDomain 
> Code=13 "The operation couldn’t be completed. Permission denied")
> 
> Unfortunately I can't find this file.  No problem though - I just apply 
> permissions to enclosed items.  But, no luck with that either.

Hi Adam,

You need to delete the .mboxCache.plist. Why you can't find it is a hidden 
file… 

1. Quit Mail and try this on the command line (Terminal.app) to find them:
2. Open a Terminal window and paste this in:

find ~/Library/Mail -name .\*

It should only find cache files like '.DS_Store', '.mboxCache.plist', 
'.OfflineCache', '.dontIndex', and '.index.ready'. 
If so, and if everything is backed up, run:

find ~/Library/Mail -name .\* -delete

NB: Don't run this if the first listing looks like it's showing e-mails. I also 
recommend checking that you have a backup first. 

3.Now launch mail and select "Mailbox:Rebuild" from the menu. 


Cheers,
Ronni

17" MacBook Pro  Intel Core i7
2.66GHz / 4GB / 1067 MHz DDR3 / 500GB Serial ATA Drive @ 7200rpm

OS X 10.6.3 Snow Leopard
Windows 7 Ultimate (under sufferance)






-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Permissions Issues

[Adam Lippiatt]

Hi there

I have been having a few permissions problems after a hard drive corrupted and 
was replaced.

This is the latest one which I think is causing some bad behaviour in Mail.

15/05/10 9:28:35 AM Mail[234]   Error writing to 
/Users/admin/Library/Mail/Mac-adam.lippiatt/.mboxCache.plist: Error 
Domain=NSCocoaErrorDomain Code=513 UserInfo=0x1299c26c0 "You don’t have 
permission to save the file “.mboxCache.plist” in the folder 
“Mac-adam.lippiatt”." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=13 
"The operation couldn’t be completed. Permission denied")

Unfortunately I can't find this file.  No problem though - I just apply 
permissions to enclosed items.  But, no luck with that either.

Any ideas?

Thanks

Adam



_
Adam Lippiatt
adam.lippi...@me.com
0402 301 706



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Permissions Problem

[Joe Mastrella]

Thank you James. My problem was I had downloaded a 10.5 up grade. I used
appzaper to remove the app and down loaded the proper 10.4.11 app. and all
is well. For those of you who have not tried PTH Past board, give it a look.
It sure is handy.

Cheers, Joe

On Tue, Mar 16, 2010 at 11:08 AM, James Devenish wrote:

>
> Hi Joe,
>
> > Preferences error can not load PTHPasteboard
>
> This sounds like a PTH problem. It's likely that other customers are
> affected. I suggest you contact PTH directly about their product, or
> see if it is covered by their online help.
>
> While you are usually welcome to move your PTH preferences to the
> trash to resolve the problem, you would of course loose any
> personalisation of your product!
>
> I note that PTH provides the following online help:
>
> 9. PTHPasteboard PRO launches and then quits a few seconds later, how
> do I fix this?
> There's a file in Library/Application Support/PTHPasteboard of your
> Home directory called Main.Buffer. Delete that and relaunch.
>
> James
>
>
> -- The WA Macintosh User Group Mailing List --
> Archives - 
> Guidelines - 
> Unsubscribe - 
>
>


-- The WA Macintosh User Group Mailing List --
Archives - 
Guidelines - 
Unsubscribe - 

Re: Permissions Problem

[James Devenish]

Hi Joe,

> Preferences error can not load PTHPasteboard

This sounds like a PTH problem. It's likely that other customers are
affected. I suggest you contact PTH directly about their product, or
see if it is covered by their online help.

While you are usually welcome to move your PTH preferences to the
trash to resolve the problem, you would of course loose any
personalisation of your product!

I note that PTH provides the following online help:

9. PTHPasteboard PRO launches and then quits a few seconds later, how
do I fix this?
There's a file in Library/Application Support/PTHPasteboard of your
Home directory called Main.Buffer. Delete that and relaunch.

James


-- The WA Macintosh User Group Mailing List --
Archives - 
Guidelines - 
Unsubscribe - 

Permissions Problem

[Joe Mastrella]

Greetings! I use a little program called PTH paste board. I find this
program very useful. I downloaded the new up grade and when I try to install
the program I get a dialog box

Preferences error can not load PTHPasteboard.

I have repaired permissions.

In my Library folder I notice that there are 3 preference items.

Please help.

Joe


-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Permissions Problem

[Joe Mastrella]

Greetings! I use a little program called PTH paste board. I find this
program very useful. I downloaded the new up grade and when I try to install
the program I get a dialog box

Preferences error can not load PTHPasteboard.

I have repaired permissions.

In my Library folder I notice that there are 3 preference items.

Please help.

Joe


-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Permissions Problem

[Joe Mastrella]

Greetings! I use a little program called PTH paste board. I find this
program very useful. I downloaded the new up grade and when I try to install
the program I get a dialog box

Preferences error can not load PTHPasteboard.

I have repaired permissions.

In my Library folder I notice that there are 3 preference items.

Please help.

Joe


-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Permissions not accepted

[Neil Houghton]

Hi Jon,

When I have these sort of problems, I often find that it is down to trying
to share across different user accounts.

For example, assuming that:

1) there are two user accounts - User A and User B and
2) that these two user accounts have been set up identically on all machines
on the network and
3) that file sharing is turned on each computer

Then if User A is logged into his account on the computer he is working from
and:

1) He logs into a network computer as User A, he should be able to:

- Access all User files on the network as if he was logged into the computer
as User A (which he is)
- Read and copy files from User B's public folder
- Write files to User B's drop box

However, if:

2) He logs into a network computer as User B, he should be able to:

- Access all User files on the network as if he was logged into the computer
as User B (which he is)
- Read and copy files from User A's public folder
- Write files to User A's drop box

However when logged into the local computer as User A but logged into the
network computer as User B, if he then copies one of User B's files from the
remote computer to the local computer he would probably only be able to put
it into one of his User A folders (where the copied file privileges will be
as a User A file) or into User B's Public folder.

Note that this scenario can change significantly when you start changing the
default permissions on folders.

I don't know if that will help but it may point you at some of the things to
check if you are having problems, ie;

- What user are you logged into the local machine as
- What user are you logged into the network machine as
- What user do the problem folders/files belong to
- What sharing privileges are given to other users for the problem shared
folders

HTH


Cheers


Neil
-- 
Neil R. Houghton
Albany, Western Australia
Tel: +61 8 9841 6063
Email: n...@possumology.com


on 11/1/10 6:09 PM, Jon Davison at photo...@iinet.net.au wrote:

> 
> Hi everyone
> 
> I am having a lot of trouble sharing files via Airport or Ethernet on
> our work network. I always get 'You don't have sufficient write
> privileges'.
> Sharing is on on all machines in the office, and in options I have
> them set on; Prefs-File Sharing-Options -AFP.
> I have set all folders using 'File Info to Read and Write.
> 
> I am obviously doing something wrong here. How can I set all machines
> up so they can accept any files without these prevention messages?
> 
> MacPro/OS X 10.5.8/2Gb RAM/2x 2.66 GHz Dual-core duo
> 
> MacBookPro/OS 10.5.8/2.5/2Gb RAM/ GHz core duo
> 
> iMac/OS X 10.5.6/2.4 GHx Core duo/2GB RAM
> 
> Everything works using the 'Go Menu' and all HD's appear on the
> desktops, so they are visible, just not able to transfer folders/files
> etc from one machine to the other.
> I still have to get info on every folder in order to unlock it and use
> my password etc. It is really annoying as I cannot see what I may be
> doing wrong.
> 
> Any help would be invaluable
> 
> Thanks
> Jon
> 
> 
> 
> Eye in the Sky Productions
> Image makers to the Aviation Industry
> Unit 5 / 78 Marine Tce, Fremantle
> Western Australia  6160
> € Air-to-air photography
> € Print & web design/production
> € VR panoramas
> € Book production
> € Copywriting
> € Corporate ID
> T: 08 94335541
> M: 0403 235938
> E: j...@eyeinthesky.com.au
> W: <http://www.eyeinthesky.com.au>





-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Permissions not accepted

[Ronda Brown]

On 11/01/2010, at 6:09 PM, Jon Davison wrote:

> 
> Hi everyone
> 
> I am having a lot of trouble sharing files via Airport or Ethernet on our 
> work network. I always get 'You don't have sufficient write privileges'.
> Sharing is on on all machines in the office, and in options I have them set 
> on; Prefs-File Sharing-Options -AFP.
> I have set all folders using 'File Info to Read and Write.
> 
> I am obviously doing something wrong here. How can I set all machines up so 
> they can accept any files without these prevention messages?
> 
> MacPro/OS X 10.5.8/2Gb RAM/2x 2.66 GHz Dual-core duo
> 
> MacBookPro/OS 10.5.8/2.5/2Gb RAM/ GHz core duo
> 
> iMac/OS X 10.5.6/2.4 GHx Core duo/2GB RAM
> 
> Everything works using the 'Go Menu' and all HD's appear on the desktops, so 
> they are visible, just not able to transfer folders/files etc from one 
> machine to the other.
> I still have to get info on every folder in order to unlock it and use my 
> password etc. It is really annoying as I cannot see what I may be doing wrong.

Hi Jon,

Sounds like you have done everything correctly. The only thing I can suggest 
you check.
After you turned on File Sharing in System Prefs > Sharing did you Add what you 
wanted to share by:
1. In the Sharing preference pane, under the Shared Folders list, click the +  
button.
2. Select the folder or drive that you want to share. 
For folders, navigate to the item, and make sure it’s selected. 
For volumes, choose the volume under the Devices list in the left sidebar.
3. Click Add.
There’s no additional “apply” button; the folder or drive is now available for 
sharing, and it appears in the Shared Folders list.

Cheers,
Ronni

17" MacBook Pro Intel Core 2 Duo
2.4 GHz / 4GB / 800MHz / 500GB
OS X 10.6.2 Snow Leopard
Windows 7 Ultimate (under sufferance)



-- The WA Macintosh User Group Mailing List --
Archives - 
Guidelines - 
Unsubscribe - 

Re: Permissions not accepted

[Jon Davison]

Hi everyone

I am having a lot of trouble sharing files via Airport or Ethernet on  
our work network. I always get 'You don't have sufficient write  
privileges'.
Sharing is on on all machines in the office, and in options I have  
them set on; Prefs-File Sharing-Options -AFP.

I have set all folders using 'File Info to Read and Write.

I am obviously doing something wrong here. How can I set all machines  
up so they can accept any files without these prevention messages?


MacPro/OS X 10.5.8/2Gb RAM/2x 2.66 GHz Dual-core duo

MacBookPro/OS 10.5.8/2.5/2Gb RAM/ GHz core duo

iMac/OS X 10.5.6/2.4 GHx Core duo/2GB RAM

Everything works using the 'Go Menu' and all HD's appear on the  
desktops, so they are visible, just not able to transfer folders/files  
etc from one machine to the other.
I still have to get info on every folder in order to unlock it and use  
my password etc. It is really annoying as I cannot see what I may be  
doing wrong.


Any help would be invaluable

Thanks
Jon



Eye in the Sky Productions
Image makers to the Aviation Industry
Unit 5 / 78 Marine Tce, Fremantle
Western Australia  6160
• Air-to-air photography
• Print & web design/production
• VR panoramas
• Book production
• Copywriting
• Corporate ID
T: 08 94335541
M: 0403 235938
E: j...@eyeinthesky.com.au
W: 





-- The WA Macintosh User Group Mailing List --
Archives - 
Guidelines - 
Unsubscribe - 

Re: Repairing Permissions

[Ronda Brown]

Hi Michael,

You can safely ignore this message. It is accurate but not a cause for concern.

Cheers,
Ronni

17" MacBook Pro Intel Core 2 Duo
2.4 GHz / 4GB / 800MHz / 500GB
OS X 10.6.2 Snow Leopard

On 25/11/2009, at 10:01 AM, Michael Hawkins wrote:

> 
> Repairing permissions results in the following warning. Should I be doing
> anything?
> 
> Warning: SUID file 
> "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/AR
> DAgent" has been modified and will not be repaired.
> 
> 
> Thank you,
> 
> Michael Hawkins
> 17" MacBook Pro
> 2.4 GHz Intel Core 2 Duo
> 4 GB 667 MHz DDR2 SDRAM
> OS 10.6.2



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Repairing Permissions

[Michael Hawkins]

Repairing permissions results in the following warning. Should I be doing
anything?

Warning: SUID file 
"System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/AR
DAgent" has been modified and will not be repaired.


Thank you,

Michael Hawkins
17" MacBook Pro
2.4 GHz Intel Core 2 Duo
4 GB 667 MHz DDR2 SDRAM
OS 10.6.2




-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Permissions errors with Warnings

[Ronda Brown]

Hello Tim,

You can safely ignore these warnings.
Apple Support Document: <http://support.apple.com/kb/TS1448>

Cheers,
Ronni

On 27/10/2009, at 12:15 PM, Tim Law wrote:



Hello,

I'm getting the following Warnings when running Disk Utility and  
trying to

Repair Permissions on my startup main disk.

I'm running a 2GHz PowerPC G5 iMac and 10.5.8

I have run Disk Utility several times in a row, including restarting  
and
running DU again.  I have also started from the original DVD and  
used Disk

Utility from there. These Warnings are staying in place.

Guidance would be appreciated on whether there is a better tool to  
use, or

whether I need to take other actions.

Thanks
Tim




Warning: SUID file "System/Library/Filesystems/AppleShare/afpLoad"  
has been

modified and will not be repaired.
Warning: SUID file
"System/Library/PrivateFrameworks/DiskManagement.framework/Versions/ 
A/Resour

ces/DiskManagementTool" has been modified and will not be repaired.
Warning: SUID file "sbin/umount" has been modified and will not be  
repaired.

Permissions differ on "System/Library/CoreServices/Menu
Extras/RemoteDesktop.menu/Contents/CodeResources", should be -rw-r-- 
r-- ,

they are lrw-r--r-- .
Warning: SUID file "usr/bin/quota" has been modified and will not be
repaired.
Warning: SUID file
"System/Library/PrivateFrameworks/DesktopServicesPriv.framework/ 
Versions/A/R

esources/Locum" has been modified and will not be repaired.
Permissions differ on "sbin/restore", should be -r-xr-xr-x , they are
-r-sr-sr-x .
Warning: SUID file "sbin/restore" has been modified and will not be
repaired.
Permissions differ on "sbin/rrestore", should be -r-xr-xr-x , they are
-r-sr-sr-x .
Warning: SUID file "sbin/rrestore" has been modified and will not be
repaired.
Warning: SUID file
"System/Library/Extensions/webdav_fs.kext/Contents/Resources/ 
load_webdav"

has been modified and will not be repaired.
Permissions differ on "usr/sbin/pppd", should be -r-sr-xr-x , they are
-r-s--x--x .
Warning: SUID file "usr/sbin/pppd" has been modified and will not be
repaired.
Permissions differ on "usr/sbin/vpnd", should be -r-sr-xr-x , they are
-r-s--x--x .
Warning: SUID file "usr/sbin/vpnd" has been modified and will not be
repaired.
Permissions differ on "sbin/mount_smbfs", should be -r-xr-xr-x ,  
they are

-r-sr-xr-x .
Warning: SUID file "sbin/mount_smbfs" has been modified and will not  
be

repaired.
Permissions differ on "usr/bin/smbutil", should be -r-xr-xr-x , they  
are

-r-sr-xr-x .
Warning: SUID file "usr/bin/smbutil" has been modified and will not be
repaired.





-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Permissions errors with Warnings

[Tim Law]

Hello,

I'm getting the following Warnings when running Disk Utility and trying to
Repair Permissions on my startup main disk.

I'm running a 2GHz PowerPC G5 iMac and 10.5.8

I have run Disk Utility several times in a row, including restarting and
running DU again.  I have also started from the original DVD and used Disk
Utility from there. These Warnings are staying in place.

Guidance would be appreciated on whether there is a better tool to use, or
whether I need to take other actions.

Thanks
Tim




Warning: SUID file "System/Library/Filesystems/AppleShare/afpLoad" has been
modified and will not be repaired.
Warning: SUID file 
"System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resour
ces/DiskManagementTool" has been modified and will not be repaired.
Warning: SUID file "sbin/umount" has been modified and will not be repaired.
Permissions differ on "System/Library/CoreServices/Menu
Extras/RemoteDesktop.menu/Contents/CodeResources", should be -rw-r--r-- ,
they are lrw-r--r-- .
Warning: SUID file "usr/bin/quota" has been modified and will not be
repaired.
Warning: SUID file 
"System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/R
esources/Locum" has been modified and will not be repaired.
Permissions differ on "sbin/restore", should be -r-xr-xr-x , they are
-r-sr-sr-x .
Warning: SUID file "sbin/restore" has been modified and will not be
repaired.
Permissions differ on "sbin/rrestore", should be -r-xr-xr-x , they are
-r-sr-sr-x .
Warning: SUID file "sbin/rrestore" has been modified and will not be
repaired.
Warning: SUID file 
"System/Library/Extensions/webdav_fs.kext/Contents/Resources/load_webdav"
has been modified and will not be repaired.
Permissions differ on "usr/sbin/pppd", should be -r-sr-xr-x , they are
-r-s--x--x .
Warning: SUID file "usr/sbin/pppd" has been modified and will not be
repaired.
Permissions differ on "usr/sbin/vpnd", should be -r-sr-xr-x , they are
-r-s--x--x .
Warning: SUID file "usr/sbin/vpnd" has been modified and will not be
repaired.
Permissions differ on "sbin/mount_smbfs", should be -r-xr-xr-x , they are
-r-sr-xr-x .
Warning: SUID file "sbin/mount_smbfs" has been modified and will not be
repaired.
Permissions differ on "usr/bin/smbutil", should be -r-xr-xr-x , they are
-r-sr-xr-x .
Warning: SUID file "usr/bin/smbutil" has been modified and will not be
repaired.




-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Permissions warning

[Adrian Skehan]

Thanks for that.


Regards,

Adrian
adrianske...@me.com

On 26/09/2009, at 12:22 PM, Ronda Brown wrote:




On 26/09/2009, at 11:55 AM, Adrian Skehan wrote:



G'day to all,

MacBook Pro & OSX Snow Leopard--Permissions Repair warnings as  
follows:


Repairing permissions for “Macintosh HD”
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ 
ARDAgent.app/Contents/MacOS/ARDAgent" has been modified and will  
not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/ 
DesktopServicesPriv.framework/Versions/A/Resources/Locum" has been  
modified and will not be repaired.


Permissions repair complete

I seem to recall some discussions on this subject some time ago in  
the pre Leopard OS, but I cant find the reference to check what it  
meant.


Should one be concerned and or do anything about these warnings?


Hi Adrian,

No, you don't need to be concerned, you can safely ignore these SUID  
warnings.
Disk Utility's Repair Disk Permissions messages that you can safely  
ignore:


<http://support.apple.com/kb/TS1448?viewlocale=en_US>

Cheers,
Ronni

17" MacBook Pro Intel Core 2 Duo
2.4 GHz / 4GB / 800MHz / 500GB
OS X 10.6.1 Snow Leopard



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>





-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Permissions warning

[Ronda Brown]

On 26/09/2009, at 11:55 AM, Adrian Skehan wrote:



G'day to all,

MacBook Pro & OSX Snow Leopard--Permissions Repair warnings as  
follows:


Repairing permissions for “Macintosh HD”
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ 
ARDAgent.app/Contents/MacOS/ARDAgent" has been modified and will not  
be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/ 
DesktopServicesPriv.framework/Versions/A/Resources/Locum" has been  
modified and will not be repaired.


Permissions repair complete

I seem to recall some discussions on this subject some time ago in  
the pre Leopard OS, but I cant find the reference to check what it  
meant.


Should one be concerned and or do anything about these warnings?


Hi Adrian,

No, you don't need to be concerned, you can safely ignore these SUID  
warnings.
Disk Utility's Repair Disk Permissions messages that you can safely  
ignore:


<http://support.apple.com/kb/TS1448?viewlocale=en_US>

Cheers,
Ronni

17" MacBook Pro Intel Core 2 Duo
2.4 GHz / 4GB / 800MHz / 500GB
OS X 10.6.1 Snow Leopard



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Permissions warning

[Adrian Skehan]

G'day to all,

MacBook Pro & OSX Snow Leopard--Permissions Repair warnings as follows:

Repairing permissions for “Macintosh HD”
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ 
ARDAgent.app/Contents/MacOS/ARDAgent" has been modified and will not  
be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/ 
DesktopServicesPriv.framework/Versions/A/Resources/Locum" has been  
modified and will not be repaired.


Permissions repair complete

I seem to recall some discussions on this subject some time ago in the  
pre Leopard OS, but I cant find the reference to check what it meant.


Should one be concerned and or do anything about these warnings?




Regards,

Adrian
adrianske...@me.com



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Repairing difficult permissions

[Ronda Brown]

Hi Pat,

I think the problem would have been your DLink Router. My installation  
of Snow Leopard went very smoothly and reconnected to my Airport  
Wireless Network / Netgear DG834G v4 Router immediately on restart  
after installation of SL.


Repair Permissions only took 2 minutes ... & only one permissions  
differ & was repaired.


Cheers,
Ronni

17" MacBook Pro Intel Core 2 Duo
2.4 GHz / 4GB / 800MHz / 500GB
OS X 10.6


On 31/08/2009, at 1:58 PM, Pat wrote:




On 30/08/2009, at 12:20 PM, Ronda Brown wrote:

Thanks, Susan, Rhonda and Peter,

So, those are permission problems it is safe  to ignore.  Before  
Peter's email, I tried installing the combo update twice but it  
didn't work.  I went on to install Snow Leopard anyway, and the  
problem permissions were gone.


Most things seem to be working OK now, BUT, I don't know if it was  
coincidental that the 'brain' of our dLink router became scrambled  
at the same time.  I spent more than an hour on the phone this  
morning with a very nice, helpful man at iiNet (Yay for iiNet!) who  
talked me through a messy process of reconfiguring the router.  One  
of the things that was wrong, was that the DNS address in my network  
settings had somehow lost a digit:  it said 17 when it should have  
been 178.


So, fingers crossed.

Pat


Hi Susan,

Interesting article.
If I was Pat, I would download and run the OSX Update Combo 10.5.8  
"Twice" (as recommended on the link you supplied).
<http://www.networkworld.com/news/2009/082809-fixing-permissions-in-leopard-and.html 
>

After installing the Combo twice, then  repair permissions.

Pat might find she needs to Run Repair permissions a few times.

Cheers,
Ronni

On 30/08/2009, at 11:57 AM, Susan Hastings wrote:



Hi Pat, its possible that upgrading to Leopard will fix the  
problem. See the article on this page, with links to discussions  
on repairing permissions problems that other people were having.  
Doesn't sound quite the same as your problem though. regards, Susan.


http://9to5mac.com/
On 30/08/2009, at 11:39 AM, Pat wrote:



Hello, WAMuggers,

A month or two back I upgraded Safari 4 and QuickTime to the most  
recent versions.  Ever since, when I use Disk Utility to repair  
permissions, dozens of entries needing repair come up.  They  
don't stay repaired, and reappear after every restart.


I know how to discard plists to force new ones to be generated,  
but these permissions are buried deep in their packages.  I know  
how to open the packages to see the files, but I hesitated to  
just discard the problem ones.


I would like to upgrade to Snow Leopard, but I thought I should  
probably try to resolve this problem first.  I have put a screen  
shot of the list at this site:


http://www.wanatca.org.au/Xtra/DifficultPermissions.png

I will be grateful for any advice.

Pat
Intel Mac Pro, OS 10.5.8




-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Repairing difficult permissions

[Pat]

On 30/08/2009, at 12:20 PM, Ronda Brown wrote:

Thanks, Susan, Rhonda and Peter,

So, those are permission problems it is safe  to ignore.  Before  
Peter's email, I tried installing the combo update twice but it didn't  
work.  I went on to install Snow Leopard anyway, and the problem  
permissions were gone.


Most things seem to be working OK now, BUT, I don't know if it was  
coincidental that the 'brain' of our dLink router became scrambled at  
the same time.  I spent more than an hour on the phone this morning  
with a very nice, helpful man at iiNet (Yay for iiNet!) who talked me  
through a messy process of reconfiguring the router.  One of the  
things that was wrong, was that the DNS address in my network settings  
had somehow lost a digit:  it said 17 when it should have been 178.


So, fingers crossed.

Pat


Hi Susan,

Interesting article.
If I was Pat, I would download and run the OSX Update Combo 10.5.8  
"Twice" (as recommended on the link you supplied).
<http://www.networkworld.com/news/2009/082809-fixing-permissions-in-leopard-and.html 
>

After installing the Combo twice, then  repair permissions.

Pat might find she needs to Run Repair permissions a few times.

Cheers,
Ronni

On 30/08/2009, at 11:57 AM, Susan Hastings wrote:



Hi Pat, its possible that upgrading to Leopard will fix the  
problem. See the article on this page, with links to discussions on  
repairing permissions problems that other people were having.  
Doesn't sound quite the same as your problem though. regards, Susan.


http://9to5mac.com/
On 30/08/2009, at 11:39 AM, Pat wrote:



Hello, WAMuggers,

A month or two back I upgraded Safari 4 and QuickTime to the most  
recent versions.  Ever since, when I use Disk Utility to repair  
permissions, dozens of entries needing repair come up.  They don't  
stay repaired, and reappear after every restart.


I know how to discard plists to force new ones to be generated,  
but these permissions are buried deep in their packages.  I know  
how to open the packages to see the files, but I hesitated to just  
discard the problem ones.


I would like to upgrade to Snow Leopard, but I thought I should  
probably try to resolve this problem first.  I have put a screen  
shot of the list at this site:


http://www.wanatca.org.au/Xtra/DifficultPermissions.png

I will be grateful for any advice.

Pat
Intel Mac Pro, OS 10.5.8




-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Repairing difficult permissions

[Peter Hinchliffe]

On 30/08/2009, at 11:39 AM, Pat wrote:



Hello, WAMuggers,

A month or two back I upgraded Safari 4 and QuickTime to the most  
recent versions.  Ever since, when I use Disk Utility to repair  
permissions, dozens of entries needing repair come up.  They don't  
stay repaired, and reappear after every restart.


I know how to discard plists to force new ones to be generated, but  
these permissions are buried deep in their packages.  I know how to  
open the packages to see the files, but I hesitated to just discard  
the problem ones.


I would like to upgrade to Snow Leopard, but I thought I should  
probably try to resolve this problem first.  I have put a screen  
shot of the list at this site:


http://www.wanatca.org.au/Xtra/DifficultPermissions.png

I will be grateful for any advice.

Pat
Intel Mac Pro, OS 10.5.8




Have a look at http://support.apple.com/kb/TS1448, with particular  
reference to the ""Resolution" section at the bottom of the page.


Trust in the force...er, sorry, Disk Utility.

--

Peter HinchliffeApwin Computer Services
FileMaker Pro Solutions Developer
Perth, Western Australia
Phone (618) 9332 6482Mob 0403 064 948

Mac because I prefer it -- Windows because I have to.







-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Repairing difficult permissions

[James Devenish]

Hi Pat,

> Ever since, when I use Disk Utility to repair permissions, dozens of entries
> needing repair come up.

If the permissions appear as "should be ..., they are lrwxrwxrwx",
these permissions do NOT need to be repaired despite what Disk Utility
tells you. The critical thing to note is that the permissions start
with the letter 'l', e.g. 'lrwx...' and are merely cross-references
(symbolic links) to other paths. This bug in the repair_packages
utility (underlying Disk Utility) and is fixed in Snow Leopard.

http://support.apple.com/kb/TS1448

James


-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Repairing difficult permissions

[Ronda Brown]

Hi Susan,

Interesting article.
If I was Pat, I would download and run the OSX Update Combo 10.5.8  
"Twice" (as recommended on the link you supplied).
<http://www.networkworld.com/news/2009/082809-fixing-permissions-in-leopard-and.html 
>

After installing the Combo twice, then  repair permissions.

Pat might find she needs to Run Repair permissions a few times.

Cheers,
Ronni

On 30/08/2009, at 11:57 AM, Susan Hastings wrote:



Hi Pat, its possible that upgrading to Leopard will fix the problem.  
See the article on this page, with links to discussions on repairing  
permissions problems that other people were having. Doesn't sound  
quite the same as your problem though. regards, Susan.


http://9to5mac.com/
On 30/08/2009, at 11:39 AM, Pat wrote:



Hello, WAMuggers,

A month or two back I upgraded Safari 4 and QuickTime to the most  
recent versions.  Ever since, when I use Disk Utility to repair  
permissions, dozens of entries needing repair come up.  They don't  
stay repaired, and reappear after every restart.


I know how to discard plists to force new ones to be generated, but  
these permissions are buried deep in their packages.  I know how to  
open the packages to see the files, but I hesitated to just discard  
the problem ones.


I would like to upgrade to Snow Leopard, but I thought I should  
probably try to resolve this problem first.  I have put a screen  
shot of the list at this site:


http://www.wanatca.org.au/Xtra/DifficultPermissions.png

I will be grateful for any advice.

Pat
Intel Mac Pro, OS 10.5.8




-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Repairing difficult permissions

[Susan Hastings]

Hi Pat, its possible that upgrading to Leopard will fix the problem.  
See the article on this page, with links to discussions on repairing  
permissions problems that other people were having. Doesn't sound  
quite the same as your problem though. regards, Susan.


http://9to5mac.com/
On 30/08/2009, at 11:39 AM, Pat wrote:



Hello, WAMuggers,

A month or two back I upgraded Safari 4 and QuickTime to the most  
recent versions.  Ever since, when I use Disk Utility to repair  
permissions, dozens of entries needing repair come up.  They don't  
stay repaired, and reappear after every restart.


I know how to discard plists to force new ones to be generated, but  
these permissions are buried deep in their packages.  I know how to  
open the packages to see the files, but I hesitated to just discard  
the problem ones.


I would like to upgrade to Snow Leopard, but I thought I should  
probably try to resolve this problem first.  I have put a screen  
shot of the list at this site:


http://www.wanatca.org.au/Xtra/DifficultPermissions.png

I will be grateful for any advice.

Pat
Intel Mac Pro, OS 10.5.8


-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>





-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Repairing difficult permissions

[Pat]

Hello, WAMuggers,

A month or two back I upgraded Safari 4 and QuickTime to the most  
recent versions.  Ever since, when I use Disk Utility to repair  
permissions, dozens of entries needing repair come up.  They don't  
stay repaired, and reappear after every restart.


I know how to discard plists to force new ones to be generated, but  
these permissions are buried deep in their packages.  I know how to  
open the packages to see the files, but I hesitated to just discard  
the problem ones.


I would like to upgrade to Snow Leopard, but I thought I should  
probably try to resolve this problem first.  I have put a screen shot  
of the list at this site:


http://www.wanatca.org.au/Xtra/DifficultPermissions.png

I will be grateful for any advice.

Pat
Intel Mac Pro, OS 10.5.8


-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Insight in to " Repairing Permissions "

[Robert Howells]

Worth a read :-




Bob

-- The WA Macintosh User Group Mailing List --
Archives - 
Guidelines - 
Unsubscribe - 

Re: RE Disk Permissions 10.5.6

[Robert Howells]

On 15/04/2009, at 7:38 PM, Peter Sealy wrote:


Bob

You have not said what "problems" are listed but you could look at  
Apple Support Doc TS1448. This may answer your query.



Peter,

Thanks for your suggestion , but that was not the problem .

I note they say ... it's ok if some are not set correctly ,
just worry about anything red !

I consider that a nonsense  ...  If the "  Repair Permission function  
is going to work

it should be working on everything .

I managed to get rid of most of my problems by rebuilding with Disk  
Warrior ,
but permissions will still not reset on a bundle of " Front Row "  
files .


Cheers

Bob










On Wed 105 Apr,, at 9:16 PM, Robert Howells wrote:


Hello list ,  I have a question for you !

Has anybody managed to run Permissions Repair  SUCCESSFULLYFOR  
10.5.6


My Disk Utility  lists problems   but does not repair them  AT  
ALL .


I have tried   COCKTAIL   with the same result !

Bob






Peter Sealy
Thurgoona AUSTRALIA

The Apple Religion: Geek Orthodox





-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Disk Permissions 10.5.6

[Vladimir James]

Just now successfully repaired Permissions with Disk Utility. Running  
2.4 GHz Intel Core 2 Duo with MacOS X 10.5.6. Below is the ending of  
the report showing some of the typical repairs:


Permissions differ on "System/Library/PrivateFrameworks/ 
iPhotoAccess.framework/Versions/A/Resources/Plugins/ 
WipeTransition.IAPlugin/Contents/CodeResources", should be -rw-r-- 
r-- , they are lrwxr-xr-x .

REPAIRED "%S".
Permissions differ on "Library/QuickLook/iWork.qlgenerator/Contents/ 
CodeResources", should be -rw-rw-r-- , they are lrwxr-xr-x .

REPAIRED "%S".
MISSING FILE "%S".
MISSING FILE "%S".
MISSING FILE "%S".
MISSING FILE "%S".

Permissions repair complete

Vladimir James

On 16, Apr 2009, at 5:01, WAMUG Mailing List included:



Re: RE  Disk Permissions   10.5.6
   by Robert Howells 


Hello list ,  I have a question for you !

Has anybody managed to run Permissions Repair  SUCCESSFULLYFOR
10.5.6

My Disk Utility  lists problems   but does not repair them  AT  
ALL .


I have tried   COCKTAIL   with the same result !

Bob





-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: RE Disk Permissions 10.5.6

[Ronda Brown]

Hi again Bob,

On re-reading your email and my reply to WAMUG, perhaps I did not  
answer this part of your question to your satisfaction.


My problem is that at the completion of the process and show details  
check box checked

I can see what has failed
and after the rerun the same details are still there .

It was not repaired .


In the bottom of the window under Show details, you should see  
"Permissions Repair Complete"


Messages displayed during the execution of Repair Disk Permissions are  
generally informational and can usually
be ignored.  Some messages may be repeated every time permissions are  
repaired, as the receipt for an object may
enforce specific permissions for security reasons, even though the  
current permissions are correct; these messages can

also be ignored.
In general, only messages appearing in "red" text should be of concern.

I hope that eases your concerns.

Cheers,
Ronni

On 16/04/2009, at 8:38 AM, Ronda Brown wrote:



On 15/04/2009, at 8:34 PM, Robert Howells wrote:



On 15/04/2009, at 8:08 PM, Ronda Brown wrote:


Hi Bob,

Repairing permissions in Leopard takes anywhere from 10-40  
minutes, depending on what's installed and what's contained in / 
Library/Receipts/bom/.


The repair permissions operation has changed in Leopard. The  
stalled progress bar is an unresolved bug (they haven't figured  
out how to make it work whilst it's checking or rebuilding the  
a.receiptdb, in /Library/Receipts/db/.


To see what's really going on, open that folder in a Finder  
window, select list view, launch Disk Utility, select your boot  
volume, and click on repair permissions. Watch the Finder window  
flash files that are being read and checked against the current  
a.receiptdb file.
That's what's taking all the time and freezing the progress bar.  
Once that's finished, the progress bar starts moving and the  
permissions are being checked and repaired.


Also note, that you won't get any they were repaired message back  
for any that are noted to be incorrect.


Cheers,
Ronni


Thanks Ronni !
No it does not say it has  been repaired which is one reason to run  
the
process a second time to confirm things are clear   ... the fix did  
take place.


My problem is that at the completion of the process and show  
details check box checked

I can see what has failed
and after the rerun the same details are still there .

It was not repaired .

On an installation on one drive I am getting  Permissions differ  
on  ...

System/Library/Coreservices/FrontRow.appand segments of that

and then a stream of   USer differs + Group differs + Permissions  
differ

on  Library/Printers/Xerox  segements , plugins etc .


So my conundrum is   if it does not fix these , does it fix  
anything ?


You need 10.5.6 to run Safari 4, so I am reluctant to go backwards ,
besides the problem needs to be attended to   ... perhaps we need  
to look for 10.5.7


Hi Bob,

To fully understand Permissions in Leopard I would need to send you  
a book, not an email.

I'll try to send a short version ;-)

To be accurate, Disk Utility doesn’t actually repair permissions.  
Rather, it simply resets permissions.
Further, to say Disk Utility repairs permissions implies that  
permissions can “go bad” or become corrupted over time and  
therefore need
repairing because they’re broken. This is not true. Permissions  
stay the way they are set until someone or something comes along and  
sets

them another way.

Installers: Some installers change permissions on existing files and  
folders as a necessary part of the installation process, but fail to  
return them to their proper settings.
To guard against slovenly installers, try running Verify or Repair  
Permissions after installing software, especially third-party  
software.


User Error: Mistakes can lead to problems requiring use of Disk  
Utility. A simple mistake with the chmod command, for instance,

can play havoc with permissions, requiring correction by Disk Utility.

Much of the software you install on your Mac is installed from  
packages. When a package is installed, the installer creates a Bill  
of Materials (.bom) file in that package’s receipts file.  
Installation receipts are stored in /Library/Receipts/. The Bill of  
Materials file lists the files installed by the package and the  
initial permissions for those files.


Disk Utility compares the list of permissions in the Bill of  
Materials file to the actual permissions. If Disk Utility finds any  
differences, it changes the permissions so they match the  
specifications in the Bill of Materials file.


Never throw away receipts. Without receipts, the Repair Permissions  
feature of Disk Utility won’t work. Instead you will receive a  
“No valid packages” error. The files in /Library/Receipts/ are  
reasonably small, so there’s no reason to remove them.


Not all software is installed from packages. For ins

Re: RE Disk Permissions 10.5.6

[Ronda Brown]

On 15/04/2009, at 8:34 PM, Robert Howells wrote:



On 15/04/2009, at 8:08 PM, Ronda Brown wrote:


Hi Bob,

Repairing permissions in Leopard takes anywhere from 10-40 minutes,  
depending on what's installed and what's contained in /Library/ 
Receipts/bom/.


The repair permissions operation has changed in Leopard. The  
stalled progress bar is an unresolved bug (they haven't figured out  
how to make it work whilst it's checking or rebuilding the  
a.receiptdb, in /Library/Receipts/db/.


To see what's really going on, open that folder in a Finder window,  
select list view, launch Disk Utility, select your boot volume, and  
click on repair permissions. Watch the Finder window flash files  
that are being read and checked against the current a.receiptdb file.
That's what's taking all the time and freezing the progress bar.  
Once that's finished, the progress bar starts moving and the  
permissions are being checked and repaired.


Also note, that you won't get any they were repaired message back  
for any that are noted to be incorrect.


Cheers,
Ronni


Thanks Ronni !
No it does not say it has  been repaired which is one reason to run  
the
process a second time to confirm things are clear   ... the fix did  
take place.


My problem is that at the completion of the process and show details  
check box checked

I can see what has failed
and after the rerun the same details are still there .

It was not repaired .

On an installation on one drive I am getting  Permissions differ  
on  ...

System/Library/Coreservices/FrontRow.appand segments of that

and then a stream of   USer differs + Group differs + Permissions  
differ

on  Library/Printers/Xerox  segements , plugins etc .


So my conundrum is   if it does not fix these , does it fix  
anything ?


You need 10.5.6 to run Safari 4, so I am reluctant to go backwards ,
besides the problem needs to be attended to   ... perhaps we need to  
look for 10.5.7


Hi Bob,

To fully understand Permissions in Leopard I would need to send you a  
book, not an email.

I'll try to send a short version ;-)

To be accurate, Disk Utility doesn’t actually repair permissions.  
Rather, it simply resets permissions.
Further, to say Disk Utility repairs permissions implies that  
permissions can “go bad” or become corrupted over time and therefore  
need
repairing because they’re broken. This is not true. Permissions stay  
the way they are set until someone or something comes along and sets

them another way.

Installers: Some installers change permissions on existing files and  
folders as a necessary part of the installation process, but fail to  
return them to their proper settings.
To guard against slovenly installers, try running Verify or Repair  
Permissions after installing software, especially third-party software.


User Error: Mistakes can lead to problems requiring use of Disk  
Utility. A simple mistake with the chmod command, for instance,

can play havoc with permissions, requiring correction by Disk Utility.

Much of the software you install on your Mac is installed from  
packages. When a package is installed, the installer creates a Bill of  
Materials (.bom) file in that package’s receipts file. Installation  
receipts are stored in /Library/Receipts/. The Bill of Materials file  
lists the files installed by the package and the initial permissions  
for those files.


Disk Utility compares the list of permissions in the Bill of Materials  
file to the actual permissions. If Disk Utility finds any differences,  
it changes the permissions so they match the specifications in the  
Bill of Materials file.


Never throw away receipts. Without receipts, the Repair Permissions  
feature of Disk Utility won’t work. Instead you will receive a “No  
valid packages” error. The files in /Library/Receipts/ are reasonably  
small, so there’s no reason to remove them.


Not all software is installed from packages. For instance, many third-  
party applications are distributed as disk images from which you drag
the application. Only software installed from packages creates Bill of  
Materials files, so Disk Utility can check permissions only on software
installed that way. All official Apple software is installed from  
packages.


Cheers,
Ronni



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: RE Disk Permissions 10.5.6

[Robert Howells]

On 15/04/2009, at 8:08 PM, Ronda Brown wrote:


Hi Bob,

Repairing permissions in Leopard takes anywhere from 10-40 minutes,  
depending on what's installed and what's contained in /Library/ 
Receipts/bom/.


The repair permissions operation has changed in Leopard. The stalled  
progress bar is an unresolved bug (they haven't figured out how to  
make it work whilst it's checking or rebuilding the a.receiptdb, in / 
Library/Receipts/db/.


To see what's really going on, open that folder in a Finder window,  
select list view, launch Disk Utility, select your boot volume, and  
click on repair permissions. Watch the Finder window flash files  
that are being read and checked against the current a.receiptdb file.
That's what's taking all the time and freezing the progress bar.  
Once that's finished, the progress bar starts moving and the  
permissions are being checked and repaired.


Also note, that you won't get any they were repaired message back  
for any that are noted to be incorrect.


Cheers,
Ronni


Thanks Ronni !
No it does not say it has  been repaired which is one reason to run the
process a second time to confirm things are clear   ... the fix did  
take place.


My problem is that at the completion of the process and show details  
check box checked

I can see what has failed
and after the rerun the same details are still there .

It was not repaired .

On an installation on one drive I am getting  Permissions differ on  ...
System/Library/Coreservices/FrontRow.appand segments of that

and then a stream of   USer differs + Group differs + Permissions differ
on  Library/Printers/Xerox  segements , plugins etc .


So my conundrum is   if it does not fix these , does it fix  
anything ?


You need 10.5.6 to run Safari 4, so I am reluctant to go backwards ,
besides the problem needs to be attended to   ... perhaps we need to  
look for 10.5.7



Cheers

Bob










On 15/04/2009, at 7:38 PM, Peter Sealy wrote:


Bob

You have not said what "problems" are listed but you could look at  
Apple Support Doc TS1448. This may answer your query.






On Wed 105 Apr,, at 9:16 PM, Robert Howells wrote:


Hello list ,  I have a question for you !

Has anybody managed to run Permissions Repair  SUCCESSFULLYFOR  
10.5.6


My Disk Utility  lists problems   but does not repair them  AT  
ALL .


I have tried   COCKTAIL   with the same result !

Bob






Peter Sealy
Thurgoona AUSTRALIA

The Apple Religion: Geek Orthodox



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: RE Disk Permissions 10.5.6

[Ronda Brown]

Hi Bob,

Repairing permissions in Leopard takes anywhere from 10-40 minutes,  
depending on what's installed and what's contained in /Library/ 
Receipts/bom/.


The repair permissions operation has changed in Leopard. The stalled  
progress bar is an unresolved bug (they haven't figured out how to  
make it work whilst it's checking or rebuilding the a.receiptdb, in / 
Library/Receipts/db/.


To see what's really going on, open that folder in a Finder window,  
select list view, launch Disk Utility, select your boot volume, and  
click on repair permissions. Watch the Finder window flash files that  
are being read and checked against the current a.receiptdb file.
That's what's taking all the time and freezing the progress bar. Once  
that's finished, the progress bar starts moving and the permissions  
are being checked and repaired.


Also note, that you won't get any they were repaired message back for  
any that are noted to be incorrect.


Cheers,
Ronni

On 15/04/2009, at 7:38 PM, Peter Sealy wrote:


Bob

You have not said what "problems" are listed but you could look at  
Apple Support Doc TS1448. This may answer your query.






On Wed 105 Apr,, at 9:16 PM, Robert Howells wrote:


Hello list ,  I have a question for you !

Has anybody managed to run Permissions Repair  SUCCESSFULLYFOR  
10.5.6


My Disk Utility  lists problems   but does not repair them  AT  
ALL .


I have tried   COCKTAIL   with the same result !

Bob






Peter Sealy
Thurgoona AUSTRALIA

The Apple Religion: Geek Orthodox



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: RE Disk Permissions 10.5.6

[Peter Sealy]

Bob

You have not said what "problems" are listed but you could look at  
Apple Support Doc TS1448. This may answer your query.






On Wed 105 Apr,, at 9:16 PM, Robert Howells wrote:


Hello list ,  I have a question for you !

Has anybody managed to run Permissions Repair  SUCCESSFULLYFOR  
10.5.6


My Disk Utility  lists problems   but does not repair them  AT  
ALL .


I have tried   COCKTAIL   with the same result !

Bob






Peter Sealy
Thurgoona AUSTRALIA

The Apple Religion: Geek Orthodox





-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

RE Disk Permissions 10.5.6

[Robert Howells]

Hello list ,  I have a question for you !

Has anybody managed to run Permissions Repair  SUCCESSFULLYFOR  
10.5.6


My Disk Utility  lists problems   but does not repair them  AT ALL .

I have tried   COCKTAIL   with the same result !

Bob

-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Permissions

[David Moyle]

Evening,

What is the actual problem?

Cheers
- Original Message -
From: "Stuart Breden" 
To: "WAMUG Mailing List" 
Sent: Thursday, 19 March, 2009 6:59:34 PM GMT +08:00 Beijing / Chongqing / Hong 
Kong / Urumqi
Subject: Permissions

Hi WA muggers

I have a small Apple network at work with a windows server.

I can't use Disk Utility from the Leopard stat up disk to verify or  
repair either the permissions and the hard drive.

I am having other network issues and I suspect it is a network issue  
rather than a client iMac issue.

Suggestions?

Stuart Breden
PO Box 132
Kalamunda WA 6926
Hm Ph: (08) 9257 1577
Wk Ph: (08) 9291 4599
Mbl: 0417 053 266


-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Permissions

[Stuart Breden]

Hi WA muggers

I have a small Apple network at work with a windows server.

I can't use Disk Utility from the Leopard stat up disk to verify or  
repair either the permissions and the hard drive.


I am having other network issues and I suspect it is a network issue  
rather than a client iMac issue.


Suggestions?

Stuart Breden
PO Box 132
Kalamunda WA 6926
Hm Ph: (08) 9257 1577
Wk Ph: (08) 9291 4599
Mbl: 0417 053 266


-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:wamug-unsubscr...@wamug.org.au>

Re: Permissions

[Neil Houghton]

Hi Stuart,

I can't claim to have any idea what is going on, but first thoughts on the
sort of things I would try might be:

- Fire up the computer in target mode, connect to another computer, and try
repairing from there (this may not be an option for you).

- Are you trying this from an account with admin privileges (I don't
actually know if this makes a difference, but...)

- Create a new user (with admin privileges) and try again logged in as the
new user.

- If you have an external disc & Superduper: Superduper has an option to
repair permissions when cloning and gives you an error log if it fails to
complete its task - this might give you another way to try, though it may
just give you the same problem/error message.

HTH


Cheers


Neil

-- 
Neil R. Houghton
Albany, Western Australia
Tel: +61 8 9841 6063
Email: [EMAIL PROTECTED]


on 29/9/08 7:34 PM, Stuart Breden at [EMAIL PROTECTED] wrote:

> Yes booted from install disk all right!
> 
> Stuart Breden
> PO Box 132
> Kalamunda WA 6926
> Hm Ph: (08) 9257 1577
> Wk Ph: (08) 9291 4599
> Mbl: 0417 053 266
> 
> 
> On 29/09/2008, at 9:46 AM, Neil Houghton wrote:
> 
>> Hi Bob & Stuart
>> 
>> Bob, surely if he is booting from the OS 10 install disk he SHOULD
>> be able
>> to repair both disc and permissions - you just can't repair the
>> actual disc
>> you are booted from?
>> 
>> Stuart, are you sure you have actually booted from the install disc
>> - I have
>> had problems in the past where just holding down the "C" key at
>> start-up
>> DIDN't start from the disk (don't know why) but in that case holding
>> down
>> the option key at startup DID give me the choice between HD and
>> install disc
>> - so I was then able to boot from the installation disc.
>> 
>> 
>> HTH
>> 
>> 
>> Neil
>> -- 
>> Neil R. Houghton
>> Albany, Western Australia
>> Tel: +61 8 9841 6063
>> Email: [EMAIL PROTECTED]
>> 
>> 
>> on 29/9/08 9:19 AM, Robert Howells at [EMAIL PROTECTED] wrote:
>> 
>>> 
>>> On 29/09/2008, at 9:10 AM, Stuart Breden wrote:
>>> 
>>>> Hi there
>>>> 
>>>> I have a 1.8 GHz PowerPC G5 at work and at home running OS 10.5.5
>>>> 
>>>> I am having problems with permissions.  Can;t find anything on the
>>>> WAMUG web site.
>>>> 
>>>> What happens when I boot fro the OS 10 install disk is that I can't
>>>> "Verify or Repair Disk Permissions" and  not "Repair Disk".  I get
>>>> the message 'The desk 'macintosh HD" could not be unmounted'
>>>> 
>>>> Suggestions?
>>>> 
>>> 
>>> From the Disk utility in Utilities in your Applications folder
>>> 
>>> Noyou cannot Repair Disk
>>> 
>>> but  YES  you can repair permissions
>>> 
>>> try that
>>> 
>>> Bob
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>> Stuart Breden
>>>> PO Box 132
>>>> Kalamunda WA 6926
>>>> Hm Ph: (08) 9257 1577
>>>> Wk Ph: (08) 9291 4599
>>>> Mbl: 0417 053 266
>>>> 



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:[EMAIL PROTECTED]>

Re: Permissions

[Stuart Breden]

Yes booted from install disk all right!

Stuart Breden
PO Box 132
Kalamunda WA 6926
Hm Ph: (08) 9257 1577
Wk Ph: (08) 9291 4599
Mbl: 0417 053 266


On 29/09/2008, at 9:46 AM, Neil Houghton wrote:


Hi Bob & Stuart

Bob, surely if he is booting from the OS 10 install disk he SHOULD  
be able
to repair both disc and permissions - you just can't repair the  
actual disc

you are booted from?

Stuart, are you sure you have actually booted from the install disc  
- I have
had problems in the past where just holding down the "C" key at  
start-up
DIDN't start from the disk (don't know why) but in that case holding  
down
the option key at startup DID give me the choice between HD and  
install disc

- so I was then able to boot from the installation disc.


HTH


Neil
--
Neil R. Houghton
Albany, Western Australia
Tel: +61 8 9841 6063
Email: [EMAIL PROTECTED]


on 29/9/08 9:19 AM, Robert Howells at [EMAIL PROTECTED] wrote:



On 29/09/2008, at 9:10 AM, Stuart Breden wrote:


Hi there

I have a 1.8 GHz PowerPC G5 at work and at home running OS 10.5.5

I am having problems with permissions.  Can;t find anything on the
WAMUG web site.

What happens when I boot fro the OS 10 install disk is that I can't
"Verify or Repair Disk Permissions" and  not "Repair Disk".  I get
the message 'The desk 'macintosh HD" could not be unmounted'

Suggestions?



From the Disk utility in Utilities in your Applications folder

Noyou cannot Repair Disk

but  YES  you can repair permissions

try that

Bob









Stuart Breden
PO Box 132
Kalamunda WA 6926
Hm Ph: (08) 9257 1577
Wk Ph: (08) 9291 4599
Mbl: 0417 053 266





-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:[EMAIL PROTECTED]>



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:[EMAIL PROTECTED]>

Re: Permissions

[Stuart Breden]

Done both but neither works.

Stuart Breden
PO Box 132
Kalamunda WA 6926
Hm Ph: (08) 9257 1577
Wk Ph: (08) 9291 4599
Mbl: 0417 053 266


On 29/09/2008, at 9:19 AM, Robert Howells wrote:



On 29/09/2008, at 9:10 AM, Stuart Breden wrote:


Hi there

I have a 1.8 GHz PowerPC G5 at work and at home running OS 10.5.5

I am having problems with permissions.  Can;t find anything on the  
WAMUG web site.


What happens when I boot fro the OS 10 install disk is that I can't  
"Verify or Repair Disk Permissions" and  not "Repair Disk".  I get  
the message 'The desk 'macintosh HD" could not be unmounted'


Suggestions?



From the Disk utility in Utilities in your Applications folder

No  you cannot Repair Disk

but  YESyou can repair permissions

try that

Bob









Stuart Breden
PO Box 132
Kalamunda WA 6926
Hm Ph: (08) 9257 1577
Wk Ph: (08) 9291 4599
Mbl: 0417 053 266



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:[EMAIL PROTECTED]>



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:[EMAIL PROTECTED]>



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:[EMAIL PROTECTED]>

Re: Permissions

[Neil Houghton]

Hi Bob & Stuart

Bob, surely if he is booting from the OS 10 install disk he SHOULD be able
to repair both disc and permissions - you just can't repair the actual disc
you are booted from?

Stuart, are you sure you have actually booted from the install disc - I have
had problems in the past where just holding down the "C" key at start-up
DIDN't start from the disk (don't know why) but in that case holding down
the option key at startup DID give me the choice between HD and install disc
- so I was then able to boot from the installation disc.


HTH


Neil
-- 
Neil R. Houghton
Albany, Western Australia
Tel: +61 8 9841 6063
Email: [EMAIL PROTECTED]


on 29/9/08 9:19 AM, Robert Howells at [EMAIL PROTECTED] wrote:

> 
> On 29/09/2008, at 9:10 AM, Stuart Breden wrote:
> 
>> Hi there
>> 
>> I have a 1.8 GHz PowerPC G5 at work and at home running OS 10.5.5
>> 
>> I am having problems with permissions.  Can;t find anything on the
>> WAMUG web site.
>> 
>> What happens when I boot fro the OS 10 install disk is that I can't
>> "Verify or Repair Disk Permissions" and  not "Repair Disk".  I get
>> the message 'The desk 'macintosh HD" could not be unmounted'
>> 
>> Suggestions?
>> 
> 
>  From the Disk utility in Utilities in your Applications folder
> 
> Noyou cannot Repair Disk
> 
> but  YES  you can repair permissions
> 
> try that
> 
> Bob
> 
> 
> 
> 
> 
> 
> 
> 
>> Stuart Breden
>> PO Box 132
>> Kalamunda WA 6926
>> Hm Ph: (08) 9257 1577
>> Wk Ph: (08) 9291 4599
>> Mbl: 0417 053 266
>> 



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:[EMAIL PROTECTED]>

Re: Permissions

[Robert Howells]

On 29/09/2008, at 9:10 AM, Stuart Breden wrote:


Hi there

I have a 1.8 GHz PowerPC G5 at work and at home running OS 10.5.5

I am having problems with permissions.  Can;t find anything on the  
WAMUG web site.


What happens when I boot fro the OS 10 install disk is that I can't  
"Verify or Repair Disk Permissions" and  not "Repair Disk".  I get  
the message 'The desk 'macintosh HD" could not be unmounted'


Suggestions?



From the Disk utility in Utilities in your Applications folder

No  you cannot Repair Disk

but  YESyou can repair permissions

try that

Bob









Stuart Breden
PO Box 132
Kalamunda WA 6926
Hm Ph: (08) 9257 1577
Wk Ph: (08) 9291 4599
Mbl: 0417 053 266



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:[EMAIL PROTECTED]>



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:[EMAIL PROTECTED]>

Permissions

[Stuart Breden]

Hi there

I have a 1.8 GHz PowerPC G5 at work and at home running OS 10.5.5

I am having problems with permissions.  Can;t find anything on the  
WAMUG web site.


What happens when I boot fro the OS 10 install disk is that I can't  
"Verify or Repair Disk Permissions" and  not "Repair Disk".  I get the  
message 'The desk 'macintosh HD" could not be unmounted'


Suggestions?

Stuart Breden
PO Box 132
Kalamunda WA 6926
Hm Ph: (08) 9257 1577
Wk Ph: (08) 9291 4599
Mbl: 0417 053 266



-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:[EMAIL PROTECTED]>