Kernel Extension - bernie90210

What a pain. What happens if we have to do an archive and install, or a reformat and install?

Reply to This

Monday, February 02 2004 @ 07:53 PM PST

Kernel Extension - brossow

Umm ... just a thought, but how about reinstalling Snapz? How tough is that?

Reply to This

Monday, February 02 2004 @ 07:58 PM PST

Kernel Extension - macsolu

The point is NOT that it is "tough" to reinstall the app; rather, the whole idea of the OS is that there are certain places (i.e, where kernel extensions live) that should be untouchable/unalterable/off-limits to ALL 3rd-party software, thus allowing for Archive & Install to get the end-user back up to a fully-functioning state with a minimum of hassle. And it IS a hassle to keep a list of which software will need to be reinstalled because the Archive & Install process ignored certain parts and pieces of that program. Furthermore, I'm willing to bet that Ambrosia doesn't bother to mention/warn prior to installation that v2 installs a kernel extension and the possible implications of this tactic.

Reply to This

Tuesday, February 03 2004 @ 01:20 AM PST

Kernel Extension - Derren W

After an Archive & Install you simply drag "AmbrosiaAudioSupport.kext", from the old "/System/Library/Extensions/" folder, drag it into your new "/System/Library/Extensions/" folder, authenticate, and you're golden. Snapz Pro X is far from the only program out there that installs files that don't fully survive an Archive & Install. There's Toast 6, Studio MX 2004, Virtual PC, etc. It's a fact of life that you simply have to live with.

Reply to This

Tuesday, February 03 2004 @ 06:41 PM PST

Kernel Extension - macsolu

Then all users will have to "live with" the fact that they cannot, at all, trust ANY program they've installed to once again be 100% fully functional after performing an Archive & Install. Instead, they will be faced with having to reinstall EVERY SINGLE application & doo-dad that could have, without their knowledge, just happened to stick some obscure (or critical) piece of code into the main System directory (since virtually no software installation nowadays bothers to tell you what is being installed where.) This SUCKS. Why would anybody think and Archive & Install would be a useful and quick problem-solver, if it intentionally leaves behind parts and pieces of third-party software?

The answer is either to have Apple LOCK (and they might as well hide it too) the System directory to prevent any alteration at all, or "upgrade" the Archive & Install feature to alert the user about what specific third-party software was installed and give them the option to archive it and reinstall it. Isn't the goal to have the OS and its associated actions conform to the needs of the typical end-user than the other way around?

Reply to This

Saturday, April 03 2004 @ 10:17 PM PST