Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.4: A caution on the functionality of Burn Folders' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: A caution on the functionality of Burn Folders
Authored by: starwxrwx on Sep 15, '05 11:31:47PM

I have found Burn folders to be nothing but trouble.

First off, I still have the problem that sometimes dragging multiple files to the burn folder causes all the aliases to point to the SAME file. So I get a cd/dvd of 10 copies of the same file - this has reappeared for me under 10.4.2. (Opt-cmd-I is the only way to ensure the aliases are correct... but sometimes folders original paths dont turn up properly anyway, and checking each alias can get annoying for large backups).

Secondly, if you try to backup your ~/Library, it can crash halfway through the burn if some random folder has a protected/non-copyable file (what is with these files? Everything should be copy-able). hello, coaster land.

Also, trying to backup your Desktop can cause trouble because thats where the default Burn folder is!

I also find the 'calculate burn size' to be really unreliable, and often quotes larger amounts than "get info" on the folder you wish to burn.

Opt-dragging files helps, but is SLOW, and because it's copying, it still fails for certain Library directories, and you have to go hunt them down to check what files you are missing.

Overall, I have to say it just gives me a headache, and I'm an experienced user...



[ Reply to This | # ]
10.4: A caution on the functionality of Burn Folders
Authored by: sjk on Sep 16, '05 01:23:35AM
Re: it can crash halfway through the burn if some random folder has a protected/non-copyable file (what is with these files? Everything should be copy-able)

Try running:

find ~/Library -not -user yourusername -not -type l -ls

... in a Terminal shell to check for non-symlink files/directories you don't own. For example, you might discover root-owned, read-only-by-owner files under the Preferences directory.

[ Reply to This | # ]
10.4: A caution on the functionality of Burn Folders
Authored by: BohrMe on Sep 18, '05 09:37:47AM
Everything should be copy-able.

No it shouldn't. Whether you want it to be or not, OS X is a multi-user operating environment. And because of that, certain security measures have to be taken so that you or another user of the computer won't muck it up or compromise the system's integrity.

One of the ways a UNIX system does that is to make certain files and/or directories rw by root or daemon or some other user whose UID is less than 50, IIRC. That's why you have to enter your administrator password when installing some software.



[ Reply to This | # ]
10.4: A caution on the functionality of Burn Folders
Authored by: dave1212 on Sep 18, '05 11:47:12AM

I think he was talking about the Home folder. Everything should be copyable/burnable from his own user folder.

Right?

As an aside, the issue could have got me too, as I am used to Toast's behaviour (as I'm sure many Mac users are) of letting you work within the 'burn' window without affecting your actual files. Change names, icons, move to different folders, nothing in the Finder was touched.

This is odd behaviour for something that so many Mac users will expect to act like Toast. Unfortunate, although it shouldn't be any issue for Apple to figure out a fix, they don't worry about their own HIG anymore anyway.



[ Reply to This | # ]
10.4: A caution on the functionality of Burn Folders
Authored by: legacyb4 on Oct 09, '05 08:52:34PM

I've noticed the same thing.

I had a handful of music files I wanted to back up on an external drive since DVD-R is so much cheaper than hard drive space for archiving.

Dutifully, I created a Burn Folder on the Desktop, dragged the folders from the external drive into the BF, noted that all folders were aliased, and burned it only to find that all folders had the same subfolder (probably the one that was clicked on when dragging the group over).

I tried creating another BF on the external drive and did another drag; same result.

I finally moved the folder full of music files to my Desktop, created a BF on the Desktop, dragged the folders in, and now the links work.

Perhaps there is a bug with external FW drives?



[ Reply to This | # ]