Well I can see pretty much no one here gives a ratsass to help. Anyway, I
did the Migration Assistant thing and Leopard still crashes when I ask it
to
do anything.
So- I would say that Leopard doesn't work with pre '06 G5 multiprocessors.
I'm going back to 10.4.11
Crap.
On 6/29/08 4:20 PM, in article C48D66E0.A6F7%ghost_topper@[EMAIL PROTECTED]
"George Kerby" <ghost_topper@[EMAIL PROTECTED]
> wrote:
> Just replaced 10.4.11 with Leopard and in checking the function of Apps,
I
> found that FCS2 Motion would not open properly. All other components
seemed
> OK. The disk indicated that several other parts of other components of
the
> suite should be reloaded, among them DVD Studio.
>
> Resuming today my app check before turning on Time Machine (don't want
to
> start with any bad apples-pun intended), I continued fine until I
> double-clicked DVD StudioPro, which opened the "about" screen, without
the
> owner****p, s/n, etc. Giving it ample time to open, I got tired of
watching
> the spinning beach ball of trouble, and tried force quitting. No joy.
Tried
> from the apple menu: 'not responding' was the reply. When I tried to
reload
> the finder, everything froze: the clock, cursor, everything. I felt like
I
> was back in OS9 again-I think that is the first time that this has
happened
> in X.
>
> Restarts again and again have resulted in the same thing - from
immediate to
> several seconds before halting. Sometimes accompanied by high-speed fan
> work.
>
> Finally, I had time to open the CD drawer and put Disk Warrior to work,
and
> it found directory issues and I replaced and ran other tests. Restarting
> again, same thing: frozen.
>
> I am considering wiping the drive clean, installing Leopard and it's
updates
> to 10.5.3 and using a "Target Disk" replacement of the other stuff,
because
> I think that the Archive & Install is what confused my FCS in the first
> place: Some of the stuff is still in the Previous System Folder.
Aperture
> also insisted on a new s/n.
>
> Has anyone here done the Migration Assistant using an External FireWire
or
> eSATA connected drive to the other computer which will be the Source?
Or,
> could I just connect it to the computer directly. I know this may sound
> dumb, but the only time that I have done this is from my old G4 Titanium
PB
> to a Mac Book Pro and that was last year.
>
> OR, by my description does anyone feel that there might be other issues?
>
> € PRAM reset-or battery? Date/time seems OK
>
> € Bad DRAM?
>
> € Motherboard?
>
>
> TIA for any suggestion before I start pulling out what few hairs I have
> left.
>
|
