Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About vocaro

  • Rank
  1. I'm getting persistent errors when trying to backup my home directory to DVD using Toast. At first I thought I was suffering from a lot of bad discs, but then I tried backing up to a disc image on an external hard disk, and I'm seeing the same problems. So it's not a disc burning issue; it seems to be some corruption of the files in my home directory. I keep getting error messages like this one: The file "Untitled Workspace 3.oww" could not be accessed. (Data fork, -43) I then click OK and get another error message: Couldn't complete the last command because a file couldn't be found. Result Code = -43 I click OK and then Toast aborts the backup. Ick. All right, so there's some corruption of my hard disk directory somewhere. Fine. I rebuilt the disk with Disk Warrior, repaired disk permissions, and rebooted, then tried another backup with Toast. The same "file could not be accessed" error came up, but this time with a different file. Okay, no big deal, I can cope with a few files not being accessed. If Toast can't back them up, it can log the error and continue with the rest of the files, right? Wrong! Do you know what Toast does? It aborts the entire backup! One file error and the whole backup set is ruined. I have to throw away whatever discs I had burned so far in that backup set. Why does Toast do this? Why can't it just ignore the error and continue? Is this a bug? I'm using Toast 7.1 on Mac OS X 10.4.7. Format is "Mac Only"; the Compressed and Encrypted options are turned off. Data size is about 36GB spanning 9 DVDs.
  2. vocaro

    Compression Is Useless?

    Yes. But I am in the Data tab, not the Video tab. You are referring to the DVD video compression that was introduced in Toast 7 (borrowed from Roxio's Popcorn product). If you look at the FAQ for Toast 6 -- which did not have the DVD video compression you are referring to -- you will see that they talk about compressing data, not video. That is a workaround I'm sure would work (assuming I create a compressed disk image). But the thing is, I shouldn't have to do that. In the Data tab, there's an option for compression that should do this for me automatically. However, if Toast refuses to burn the data if the uncompressed size is larger than the media size, then this option is completely useless. It appears to be a bug in Toast.
  3. vocaro

    Compression Is Useless?

    Yes, 7.0.2 on Mac OS X 10.4.4. I didn't abandon anything. Here's what I did: I started Toast, dragged the folder onto the main window (which automatically created a new disc set with the folder's files in it), made sure the Compression option was enabled, then clicked the Burn button. This opened a dialog box that allowed me to select a drive and optionally specify advanced options. I then selected my drive and clicked Record. That's when I saw the Verifying Files dialog box, which ran to completion -- I did not cancel it -- and then I was given the message about not enough space on the disc. In other words, Toast abandoned the process, not me.
  4. vocaro

    Compression Is Useless?

    I have a folder on my hard drive that I want to burn to a single DVD-R. Toast says the directory is only 4.35GB, so there shouldn't be any problem fitting all of it onto one disc. Just to be sure, I turn on the Compressed option; the data happens to be highly compressible (lots of text files), so it should shrink down a lot. After clicking the burn button, I see a Verifying Items dialog box, followed by this message: There's not enough free space on this disc: 2309949 sectors (4.41 GB) are needed, 2298496 sectors (4.38 GB) are available. It appears that Toast didn't even attempt to compress the data before writing it to the disc! The only option at this point is to abort the burn. Apparently, there seems to be no purpose whatsoever in turning on compression. It doesn't do any good to calculate disc space according to compressed size; compression won't save me any discs that way. Am I right in thinking that the compression option is therefore absolutely useless? If not, what am I missing?