Hi, I need to switch my Coreaudio.framework (in system folder/frameworks) for another one...
I tried many ways such as booting in various mode but I cant seem to have the permission to replace this with a new one. Any suggestions?

thanks!

moving Coreaudio from a system folder to another one is highly dangerous and this framework should be present in the other system folder

Anyway, if you like to live dangerously you can launche the terminal an type:

"sudo mv /System/Library/Frameworks/CoreAudio.framework Path_to_your_other_disk/System/Library/Frameworks/CoreAudio.framework"

replacing Path_to_your_other_disk with the Path to your other disk (something like /Volumes/Name_of_your_disk)

be sure that permissions/ownerships are identical in both systems

I thank you for the answer, but the problem is I'm a music maker, not as much of a system tweaker, but for now on, I think it's my only chance to start working with my new computer instead of being stuck with a CPU overloading Imac DV g3 500 Mhz. So, on my G4 dual 1.25 Gig, how do I launch the terminal? and could I type the exchange command wrote earlier while both computer are linked within a firewire local path?
Also, there is this permission problem, I'm the one who configured both of my computer and the permission to move a new Coreaudio.framework, which I had copied and then tried to replace with the other one, as been denied...but how can I not have the permission if I'm the only owner?????

thanks again!
sincerely

in all respect to *nix operating systems.
You should use the program tar from the terminal
to move system folders (or any folder that you have to retain permissions on) from disk to disk.
if done correctly it keeps the permissions.
you wont have to worry about that issue.

eaks, why do you want to replace your coreaudio.framework? Why not use the one already provided with the system?

Well, I just spent all my cash on a new computer, I have tons of contract to finish and I'm too poor to buy myself a real version of cubase SX. So I'm trying to install the K one I run on my Imac G3 500 Mhz, while I earn money to buy the real one. So expensive.

Oh well... but what the relationship with coreaudio.framework?

I strongly advise you to bite the bullet - go to your local bank and borrow
the money to afford the original Panther install disks - if you havent got them already.
Also borrow enough money the get a fresh copy of Cubase SX to
install on your new computer.

Although it is possible to move system stuff around in a unix-system -
IF you KNOW- what your doing.
Down that road also lies disaster if you misstype something.

You can always activate your root-account if really want to what we suspect you want to do.
Log on as root and start moving things around but -
beware you have been fairly warned.

You have professed yourself to be "NOT MUCH OF SYSTEM TWEAKER" -
so if this is indeed the case - what you'r trying to do is a stupid idea.
( excuse my frankness - I urge you by all means to learn your ropes around
the unix-system in the Mac OS underpinnings - as much as you feel you have the time and inclination to )

Cheers & good luck: Dixiechicken

hehe, I've been messing around a lot with my old Imac and i've done a few incredible things, in fact, it's the first time I need advices to workout things the way I want to. But there's a time when you have to admit it's too much, and now is that time for me. I don't have time to learn UNIX or whatever to tweak my system, it would be considerable loss of time that I dont have. I'm a studio engineer. In fact, I'm already negociating the purchase of Cubase SX3. And by the way, I already have the original OSX panther. Just because I use a K version doesnt mean all my softwares are. Who never used k version of various softwares?

thanks everyone for the advices.
a future SX3 owner!

eaks, whatever you do , is up to you, but please teach me: what is the relationship between your old coreaudio.framework and Cubase?

Well, after I tried everything I thought would make it work and still it wouldnt work, I found a text where a solution for my exact problem was written. It is said in this text that I have to replace the latest coreaudio.framework with the previous version. So that's what I tried. Apparently it worked for some but maybe it was before the arrival of dual processor machines...