Thanks to all who have helped so far. My friend doesn't know a lot about Macs but does know Unix pretty well. he's already "hacked" into the system which is where I got the info posted earlier. It's actually his wife's computer so we're already third-hand here. She has the original start up disk and he tried booting from that and it still froze. We think it's pinned somewhere around those lines I posted earlier: about block counts and key lengths. He doesn't have any disk utilities but the IT guys at her school tried Disk Warrior and couldn't repair it. He actually got as far as seeing that it's a Toshiba disk drive in the Powerbook when he tried to boot from the restore disk but it still hung on him. Like I say, he lives an hour away so if we all don't help him long distance, he's going to drive over this weekend and I'm going to try Tech Tool and maybe Norton Utilities. Any other ideas, keep 'em coming but thanks for everything so far. I knew I'd come to the right place. Ron in Memphis 1. panic(cpu0): 0x300 - Data Access 2. panic: We are hanging here. 3. Incorrect block count for filesystem.log It should be 15987 instead of 15988 (---or is it file system.log---probably just one word.) 4. Invalid key length (4, 9807) 5. Volume check failed 6. Warning: blocks on volume MacIntosch HD not allocated On Oct 27, 2005, at 11:31 PM, Jim Manley wrote: > > On Oct 27, 2005, at 9:18 PM, Philip J Robar wrote: > >>>>>> Just a guess but sound like he needs to boot from the OS install >>>>>> and try disk repair. >>>>>> >>>>> >>>>> I agree, but repair permissions as well wouldn't hurt. >>>>> >>>> >>>> Well, yes it could. Any writing to a disk with problems like this >>>> one is having, not associated with fixing its problems, is almost >>>> certainly only going to make matters worse. >>>> >>> >>> Macfixit.com had problems like this when OSX first came out & >>> repairing permissions fixed the problem. They recommend it very >>> strongly. >>> >> >> A reference would be useful. I can't think of anyway that fixing >> permissions is going to help with a damaged file system - as this one >> clearly is. It's almost certainly only going to make matters worse. > > It was a while back. If the system is damaged then I agree with you, > but without seeing the machine we really don't know. Permissions can > prevent the machine from doing all sorts of things. > > I have never had a system become damaged since I left OS9. I did have > that happen with OS9 many times. > --- > James Paul Manley > jpmanley at gmail.com > > > > _______________________________________________ > G4 mailing list > G4 at listserver.themacintoshguy.com > http://listserver.themacintoshguy.com/mailman/listinfo/g4 > > Listmom is trying to clean out his closets! Vintage Mac and random > stuff: > http://search.ebay.com/_W0QQsassZmacguy1984 >