sed "s/^ */$(printf "\x09")/g" > Makefile
disk1s10: I/O error
My other quad has this cooling system. I'm only going to repaste it. It cools well and doesn't leak. It will likely never leak. At best, I'll flush the system. I dread doing it.Attempted to repaste CPUs (G5 Quad). First half completed (pair of screws undoecumented or I didn't read manuals well). Second part - reassembly - is large PiA, incompleted for now (take quite entire day, not to mention some family activities). This is hell - to unscrew all this screws of different kind, and to operate inside... (m.b. I'm doing something entirely wrong.)
Ah nice trick to fix the Makefiles!
Can you please document it with pictures? When you decide to do it, of course . And how anybody have to access that 2 screws, under big heathink (left, if we look after cover removed) ?I'm only going to repaste it.
Did you repair permissions before installing it? Remember Sorbet is a disk image of someone else's computer.What can I do to fix this bug?
Do you get any logs?After first run & setting InterWeb as default browser - it crashes, even if no pages opened (can't even open our beloved forums.macrumors.com ). What can I do to fix this bug?
Yes - it's a recommended procedure with Sorbet as far as I know.Can it really help?
Last time I checked it was in the official installation instructions over on MG.Yes - it's a recommended procedure with Sorbet as far as I know.
That cool !Today i made a small app based on neofetch to display some system info. You can get it on the garden here:
https://macintoshgarden.org/apps/infoppc
View attachment 2178802
Cheers
The forced downclocking to 667 MHz and disabling of the L3 cache is “connected” to the main battery being dead or missing AFAIK. But maybe some power management feature is causing it? I remember that Mac OS 9 on my 800 MHz TiBook reported the CPU speed as “667–800 MHz” in System Profiler.Now, I’ve read that « Ti downclock cpu when the battery is dead »… I suppose that is PRAM battery right ? Cause the main one on this machine seems Ok.
sysctl -a | grep machdep.cpu
and see if that reports anything of interest, or run e.g. Geekbench 2 and see if the results are as high as expected for a 1 GHz G4.