I installed it today - no problems so far. VI works as before in Logic.
Brave.... or foolish? []

I just found this article at MacFixit:
http://www.macfixit.com/article.php?story="20070622084922319" "="" target="_blank" title="http://www.macfixit.com/article.php?story=20070622084922319">http://www.macfixit.com/article.php?story=20070622084922319">http://www.macfixit.com/article.php?story=20070622084922319
and also this one:
http://www.macfixit.com/article.php?story=20070621085315862

Both are about 10.4.10 affecting audio.

I notice most problems seem related to the Intel Macs. *Hugs Quad G5*. Sure hope Apple gets their Sh*t together for the Intel Side with 10.5.

Hey--

I'm trying to force things to crash, but SO FAR 10.4.10 and VI Cube are working very nicely together-- no problems on old projects or new projects.

I can't stress enough--- Download the COMBO update and don't use automatic Software Update. (this advice comes from several software developers)

1. Remove all dongles and USB peripherals except for the keyboard and mouse

2. Shut down and reboot in Safe mode (hold Shift key will booting)

3. After installation, make sure you RESTART the computer in regular mode. In fact, shut down completely and do a cold boot (ie: a normal boot up)

One other consideration for MacPro users:

Check your System> Library Folder for Expansion Slot Utility IF you are using a PCI interface.

Make sure that you are giving your audio PCI card more than 1x bandwidth-- when you choose a new setting, click Save and Restart.

General consideration for wonky behaviors:

Zapping PRAM was something Mac users did regularly in OS9, but we've taken OSX a little for granted-- thinking that certain routines were a thing of the past.

Hold down OPTION APPLE P R while booting. Does a world of good when things misbehave.

Last word of advice:

When doing OSX repair permissions/ disc utilities, boot from your computer's CD-ROMs to run it and not from the Utilities folder on the hard drive.

Cheers!

Even is the OS DVD is 2 years old ? how can it be safe if many updates have been already applied ?

Should only work with a recent OS DVD ?

basically a good question ... though the permissions for system files shouldn't change with updates i've been always wondering from where the disk utility takes the information which file should have which privileges.
this http://docs.info.apple.com/article.html?artnum=25751 could be part of the answer (in a nutshell: correct permissions are stored in the installer package)
some basic explanation about permissions http://www.gideonsoftwor...om/macosxprivileges.html
christian

There are caveats, and what you've pointed out about the Utility itself being updated is one of them. Problem is that some things can't be fixed as long as the volume is mounted.

I've always sworn by DiskWarrior for such tasks in the past (and still do), but some people have impressed upon me not to underestimate the capabilties of Apple's own utilities. Even where an OS would change (ie: 10.4.9 to 10.4.10), DiskWarrior is still v. 4.0 itself, so using a third-party utility under such circumstances raises the same questions that using Apples Disk Utility would for the same purpose.

Repair Permission is only one part of the Apple Disk Utility. Where running from the volume or install disks might be weighed, cm is onto something with his statement that permissions shouldn't change. But we also have docs and tech notes to refer to before doing maintenance when we're unsure.

The other parts of the Apple Disk Utility include Verify Disk and Repair Disk. In some cases a mounted disk cannot be repaired. There's really no choice but to try to repair from a CD-ROM (or DVD-ROM)-- either from Apple or from a third-party.

In those cases where one might be concerned if their third-party utility is no more up to date than their Apple install discs, then there is the *ugly* option of buying the latest version of OSX discs from Apple even if you already own an earlier version of discs.

When in doubt, contact Apple Tech Support directly. Apple's docs are quite informative, but they also include "safe" statements that don't always address all concerns on a given topic. How the Disk Utility from 10.4.3 discs, for example, impact on permissions or general volume repair on a 10.4.9 volume is something only Apple could answer as per your specific needs.

In response to some posts above:
I keep a separate partition with OSX installed ("Drive B"). I always update it to whatever version of OSX I use on my main drive. Diskwarrior is also present there.

I have had MANY instances where I've been forced to reboot from my Drive B because my main drive has had serious problems. It's way faster than booting from a CD-ROM and DiskWarrior saves my butt every time. (By the way, the DiskWarrior manual warns you NOT to run DiskUtility or any other rescue app first...)

For some OS upgrades in the past, I have done the safe boot/unplug everything/de-install extensions etc etc etc. This time, I backed up my main drive and simply ran the updater.

Not a single problem so far. (No doubt, my whole system will go legs up directly after this post....)

It's all voodoo. []

Regards - Colin

Thanks, JWL, for answering...

...mmm... I've always thought this was true just for "Repair Disk"... isn't it? ...I (still) think so...

...mmm... sorry JWL... I use DW too... but... is not possible to Repair Permissions with it...
Have I misunderstood your post? (my english understanding sometime gives some doubts/troubles to me!) ...it wasn't in response of my questions...? ...aren't we speaking about Repair Permissions...? ops:


...another GOOD point!

I can just agree with that... there are a lot of things that only Apple could answer, and -i think- they never will! (like the meaning of the "log" after Logic have a crash... we can send it to them... but they don't help us to understand, at least partially, it... Yeah! It's a... Forbidden Planet! )


So to speak...

Cheers,
Rino

Yes-- I thought I mentioned that in my last post... sorry if I was too subtle..



Yes, we are talking about Repair Permissions. There *is* something akin to repairing permissions or fixing permissions-- I can't remember the terms at the moment, but you can check various utilities and functions under its Directory, Files, and Hardware menus for more specific repair features.



This is only a theory about the log "sent to Apple" on a crash:

The data is not immediately read by a human, but stored in their data base. Crashes of a certain type are sought out and compiled as needed by their computer only when a quantity of users having the problem bother to report the data to Apple. The only time the user comments are read by a human being (ie: "what were you doing at the time of the crash") is to verify what may have triggered the problem. If enough different users report the same problems, then Apple has no choice (in good conscience) but to address the issue.

That's just my theory, but I report everything to Apple that I can in hopes it helps in some way. It does feel like yelling into an empty cave sometimes: the only thing that comes back to you is the sound of your own voice echoing within the abyss. []