Tommy says this is not supposed to happen, because Windoze is soDisco said:OK - I'm at a loss. Done the internet search with no help - contacted
MS Vista support and their canned solution didn't help.
ANY ideas how to resolve this error???
Thanks
Tommy says this is not supposed to happen, because Windoze is so
"smart", updates never fail to install.
<snicker>
Top tip for Windoze users, create a shortcut to regedit.exe, and drag it
into the startup folder so the registry editor is running in the
background, ready to deal with the latest ****-up in Windoze.
It will also save you having to start -> run and type 'regedit' all day
long!
Tommy Troll said:
jon.in.durham said:Tommy says this is not supposed to happen, because Windoze is so "smart",
updates never fail to install.
<snicker>
Top tip for Windoze users, create a shortcut to regedit.exe, and drag it
into the startup folder so the registry editor is running in the
background, ready to deal with the latest ****-up in Windoze.
It will also save you having to start -> run and type 'regedit' all day
long!
No....
LOL
"1.. Open Start menu, select Run, type cmd, and then press Enter.
2.. To view the current proxy settings, at Command Prompt, type
Proxycfg.exe and then press Enter to run the command.
3.. To clear the existing proxy settings, type Proxycfg -d and then
press Enter.
4.. Finally, ensure that the Background Intelligent Transfer Service is
running on the computer by performing the following steps:
1.. Open Start menu, select Run, type Services.msc, and then press
Enter.
2.. Scroll down the Services window and double-click on Background
Intelligent Transfer Service.
3.. If the service is not running, on the General tab, click the
Start button.
5.. Run Windows Vista update on the PC again. "
--
Alan Baker
Vancouver, British Columbia
<http://gallery.me.com/alangbaker/100008/DSCF0162/web.jpg>- Hide quoted text -
- Show quoted text -
Tommy Troll said:Yeh, just like this "intuitively obvious" solution to a Mac OS X
problem after the 10.5.6 update:
After updating to Mac OS X 10.5.6, many users are experiencing
problems with Time Machine backups, wherein the system will show an
error stating the users does not have sufficient privileges on
required files for the backups.
Apple Discussions poster GreggSymington writes:
"After the 10.5.6 update today my backup is no longer recognized, and
when trying to reselect the drive i get this error: You do not have
appropriate access privileges to save the files '.001b6397c156' in
folder 'Backup'."
Time Machine associates backups to the computer based on the
computer's MAC address, which is a unique identifier number associated
with the ethernet card. The computer stores this information in an
invisible file that has the computer's MAC address as it's name. This
file is stored at the root of the Time Machine drive, enabling the
drive to be used with multiple computers. For some reason, the latest
OS update has altered either the file or how permissions are read from
the file. Basically, this file has become corrupted, and users should
be able to manually reset ownership and permissions on the file with
the terminal.
Fix: Change ownership and permissions on the file In the "Terminal"
application, perform the following steps to figure out what the file
is called, and then change the permissions on it accordingly.
1. Type "cd" followed by a single space, and then drag the Time
Machine drive to the Terminal window. The command should then look
something like this:
cd /Volumes/Backup
2. Press enter to submit that command, and then enter the following
command:
ls -la
3. Note the name of the file that begins with a period and has 12
characters in the name, such as ".001b6397c156" mentioned in the quote
above.
4. Now enter the following commands, substituting "FILENAME" in the
commands with the file name exactly as it's shown both in the error as
well as in the output of the command in step 2, including the period
before it (ie: ".001b6397c156"):
sudo chown `id -un` FILENAME
sudo chmod 400 FILENAME
Boy, I had that one figured out as soon as I heard about the problem!
Right? or Touché?
Yeh, just like this "intuitively obvious" solution to a Mac OS X
problem after the 10.5.6 update:After updating to Mac OS X 10.5.6, many users are experiencing
problems with Time Machine backups, wherein the system will show an
error stating the users does not have sufficient privileges on
required files for the backups.Apple Discussions poster GreggSymington writes:"After the 10.5.6 update today my backup is no longer recognized, and
when trying to reselect the drive i get this error: You do not have
appropriate access privileges to save the files '.001b6397c156' in
folder 'Backup'."Time Machine associates backups to the computer based on the
computer's MAC address, which is a unique identifier number associated
with the ethernet card. The computer stores this information in an
invisible file that has the computer's MAC address as it's name. This
file is stored at the root of the Time Machine drive, enabling the
drive to be used with multiple computers. For some reason, the latest
OS update has altered either the file or how permissions are read from
the file. Basically, this file has become corrupted, and users should
be able to manually reset ownership and permissions on the file with
the terminal.Fix: Change ownership and permissions on the file In the "Terminal"
application, perform the following steps to figure out what the file
is called, and then change the permissions on it accordingly.1. Type "cd" followed by a single space, and then drag the Time
Machine drive to the Terminal window. The command should then look
something like this:cd /Volumes/Backup
2. Press enter to submit that command, and then enter the following
command:ls -la
3. Note the name of the file that begins with a period and has 12
characters in the name, such as ".001b6397c156" mentioned in the quote
above.4. Now enter the following commands, substituting "FILENAME" in the
commands with the file name exactly as it's shown both in the error as
well as in the output of the command in step 2, including the period
before it (ie: ".001b6397c156"):sudo chown `id -un` FILENAME
sudo chmod 400 FILENAMEBoy, I had that one figured out as soon as I heard about the problem!
Right? or Touché?
You were claiming that there was "no Regedit needed[!]" as if the
solution was easier.
It was not.
So, no. Not touché, sorry.
--
Alan Baker
Vancouver, British Columbia
<http://gallery.me.com/alangbaker/100008/DSCF0162/web.jpg>- Hide quoted text -
- Show quoted text -
Tommy Troll said:Tommy Troll <[email protected]> wrote:Disco wrote:
OK - I'm at a loss. Done the internet search with no help -
contacted
MS Vista support and their canned solution didn't help.ANY ideas how to resolve this error???
Tommy says this is not supposed to happen, because Windoze is so
"smart", updates never fail to install.
Top tip for Windoze users, create a shortcut to regedit.exe, and
drag
it
into the startup folder so the registry editor is running in the
background, ready to deal with the latest ****-up in Windoze.It will also save you having to start -> run and type 'regedit' all
day
long!
No Regedit needed.
"1.. Open Start menu, select Run, type cmd, and then press Enter.2.. To view the current proxy settings, at Command Prompt, type
Proxycfg.exe and then press Enter to run the command.3.. To clear the existing proxy settings, type Proxycfg -d and then
press Enter.4.. Finally, ensure that the Background Intelligent Transfer Service is
running on the computer by performing the following steps:1.. Open Start menu, select Run, type Services.msc, and then press
Enter.2.. Scroll down the Services window and double-click on Background
Intelligent Transfer Service.3.. If the service is not running, on the General tab, click the
Start button.5.. Run Windows Vista update on the PC again. "--
Alan Baker
Vancouver, British Columbia
<http://gallery.me.com/alangbaker/100008/DSCF0162/web.jpg>- Hide quoted
text -- Show quoted text -Yeh, just like this "intuitively obvious" solution to a Mac OS X
problem after the 10.5.6 update:After updating to Mac OS X 10.5.6, many users are experiencing
problems with Time Machine backups, wherein the system will show an
error stating the users does not have sufficient privileges on
required files for the backups.Apple Discussions poster GreggSymington writes:"After the 10.5.6 update today my backup is no longer recognized, and
when trying to reselect the drive i get this error: You do not have
appropriate access privileges to save the files '.001b6397c156' in
folder 'Backup'."Time Machine associates backups to the computer based on the
computer's MAC address, which is a unique identifier number associated
with the ethernet card. The computer stores this information in an
invisible file that has the computer's MAC address as it's name. This
file is stored at the root of the Time Machine drive, enabling the
drive to be used with multiple computers. For some reason, the latest
OS update has altered either the file or how permissions are read from
the file. Basically, this file has become corrupted, and users should
be able to manually reset ownership and permissions on the file with
the terminal.Fix: Change ownership and permissions on the file In the "Terminal"
application, perform the following steps to figure out what the file
is called, and then change the permissions on it accordingly.1. Type "cd" followed by a single space, and then drag the Time
Machine drive to the Terminal window. The command should then look
something like this:cd /Volumes/Backup
2. Press enter to submit that command, and then enter the following
command:ls -la
3. Note the name of the file that begins with a period and has 12
characters in the name, such as ".001b6397c156" mentioned in the quote
above.4. Now enter the following commands, substituting "FILENAME" in the
commands with the file name exactly as it's shown both in the error as
well as in the output of the command in step 2, including the period
before it (ie: ".001b6397c156"):sudo chown `id -un` FILENAME
sudo chmod 400 FILENAMEBoy, I had that one figured out as soon as I heard about the problem!
Right? or Touché?
You were claiming that there was "no Regedit needed[!]" as if the
solution was easier.
It was not.
So, no. Not touché, sorry.
--
Alan Baker
Vancouver, British Columbia
<http://gallery.me.com/alangbaker/100008/DSCF0162/web.jpg>- Hide quoted
text -
- Show quoted text -
No, I was claiming that solving OS X issues can be as technically
difficult as Vista.
So, touché.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.