Wonder if they will give the $29 back...

Question

Was it really necessary to break everything in sight just to "improve" Leopard?
Maybe some of you guys have found solution(s) to these issues:
1. sudo command when used in scripts or multiple commands is broken.
2. contextual menu items broken
3. Disk utility breaks the journal file when run on another volume with 10.5 installed
4. Brother (printer) control center won't work and newly supplied brother printer drivers
cause occasional kernel panics.
I've been fighting with Snowie all weekend. I finally had to place it on its own partition,
I am going to have to slowly debug it, too many broken software programs to be able to
use it on a daily basis until I can fix them (at least the ones I depend on daily).
Kj ♘

Answer 1

Hi Kappy:
I have a brother MFC-9440 CN printer. The drivers supplied with Snowie are working, but occasionally
will cause a kernel panic when I print.
The control center will work (Snowie doesn't like it and will remove it from the printers/utilities
folder upon install), but will no longer start automatically and if started manually (with the new
Snowie drivers) it will crash.
I tried a an upgrade and a fresh install with migration assistant. The fresh install had all sorts of
problems, programs that were working, quit working or were unstable.
The best install (for me to date) was simply booting from the Install DVD and installing over a good
healthy 10.5.6 Installation that I knew had no known problems.
Disk utility said it fixed something in the partition on two of my volumes, turned out it hosed
the journal file on the Snowie boot volume and on a 10.5 volume. It made the journal file
visible and set the permissions to no access for everyone. Carbon Copy Cloner would hang up
on the .journal file and would not clone, also Disk Warrior would give a volume information
error every time. Deleting the .journal file (using chmod and rm) and reactivating it in DU
(using 10.5) fixed the problem. I just won't use 10.6 DU any more (for the time being).
Snowie also quit booting and I had to re "bless" it. It showed up in the boot manager as
a bootable EFI partition (and would not boot) until It was "blessed". Afterward it showed up
normally under its own name.
That's just for starters, the rest are programs that need updating. I've done most of them
already (snapz pro X, Speed Download, CCC, 1Password (using Beta), Had to recompile rsync,
testdisk, and the list goes on...
Oh, I listed the "sudo" problem in the UNIX forum and contacted the makers of the CLIX
software (rixstep) as their program is affected by the "sudo" problem too.
I am wore out already.
Kj ♘