Welcome to the MacNN Forums.

Amorya · May 17, 2003, 11:22 AM

OK, this thing is cursed!

Once again it won't boot. It gets past the bit with the progress bar, then the screen goes blue (like normal)... but then nothing happens.

If I restart in verbose mode, it starts up fine (with text on the screen instead of a progress bar), then the screen goes blue and nothing happens, as above. However, every 25 seconds or so, there's a flicker on the screen, like one black frame in a video.

I recorded the flicker with my digital camera, then extracted the frame that showed what it was saying, and it was this:

It looks to me as if it says:

May 17 16:46:48 Powerbook WindowServer[438]: loginwindow connection stopped

Anyone any clue what to do about it? Don't suggest reinstalling, since this version of the OS was installed by the insurance company when we sent it off (it's 10.2.2 I think)... I won't get my 10.2 disks from Apple for another 2-3 weeks. (They're in the post but on a really slow delivery service).

BTW, I can connect to its disk using Target Disk Mode... I have another computer with the same OS version too. Are there any files I can replace that might be corrupted?

Amorya

Since EBCDIC · May 17, 2003, 03:43 PM

I feel your pain.

You don't mention why you say this happens "again". What was the resolution last time?

I suspect that either you have hard disk corruption or a prefs file corruption. Since you don't have system disks your options are obviously limited. Perhaps a friendly local computer store would lend them to you; is there an Apple Store near-by?

Oh, and you might consider this: Hold down Shift key as soon as you see blue background (not before). Release when desktop appears._

This will disable login item and all kext files (kernel extensions) except those absolutely required. Let us know whether this works.

Amorya · May 18, 2003, 07:25 AM

Originally posted by Since EBCDIC:
I feel your pain.

You don't mention why you say this happens "again". What was the resolution last time?

I suspect that either you have hard disk corruption or a prefs file corruption. Since you don't have system disks your options are obviously limited. Perhaps a friendly local computer store would lend them to you; is there an Apple Store near-by?

Oh, and you might consider this: Hold down Shift key as soon as you see blue background (not before). Release when desktop appears._

This will disable login item and all kext files (kernel extensions) except those absolutely required. Let us know whether this works.

Absolutely no change with shift - I see "Safe Boot" appear on the startup panel thing but still nothing after that.

Last time was a slightly different problem - it was a persistent flashing question mark, inability to boot off any disk, and seemingly a corrupted hard drive. We fixed it by sending it to the insurance company, who eventually (after it was returned three times) got it sort of working - they replaced the DVD drive, the hard drive, and the keyboard for some reason. Then they copied over some of my documents - they refused to copy any MP3 files in case of piracy, so I lost some recordings of my performances and compositions. They also refused to copy applications (same reason), and they didn't copy the MySQL databases because they didn't have a clue. Anyway, the whole thing sort of worked afterwards, except that the permissions were shot to hell... I think they'd been running it as root.

System disks... my mum's a teacher so is allowed a free copy of 10.2, so that's in the post. Apple said yesterday it'd be there in 2-3 weeks... so I guess I'll wait if there's no easy fix.

I think it's a software problem 'cos I tried booting the iMac off the Powerbook's hard drive, and it gave the same error. Just dumb luck it happened twice to me in the space of two months, then. Oh well - at least I'll now be buying a 970 come summer (if Apple come through with a winning Powermac and if my student loan comes through!)

Amorya

Toyin · May 19, 2003, 08:11 AM

If you've got another Mac this is what I'd do.
Start up the powerbook holding "T", this will put in in firewire disk target mode.

Connect the iMac to the Powerbook. The Hardrive of the Powerbook will mount on your iMacs desktop.

1st I'd repair the Powerbook's disk with disk utility (don't repair permissions). Then I'd drag your user's library folder (HD->Users->your user name->Libray and drag it to your desktop (HD->Users->your user name->Desktop.

Reboot the Powerbook and a new Library folder should be created upon logging in.

Good luck.

typoon · May 19, 2003, 12:54 PM

Fire up Diskwarrior and check it out. You might also have a disk that is going bad.

SMacTech · May 19, 2003, 01:46 PM

Originally posted by Amorya:
Absolutely no change with shift - I see "Safe Boot" appear on the startup panel thing but still nothing after that.

Amorya

It is because you are at post 666 on MacNNN. Post one more time and should fix it. My cube froze after my 666th post here.
I would do as Toyin said, FW target and copy files before anything else, in case drive is on the fritz.

Since EBCDIC · May 19, 2003, 02:13 PM

Originally posted by Amorya:
...I think it's a software problem 'cos I tried booting the iMac off the Powerbook's hard drive, and it gave the same error. Just dumb luck it happened twice to me in the space of two months, then...

Several points, Amorya,

You can't tell whether it's a software problem or a flaky hard drive from these signs and symptoms, only that something is screwed up right now. If you re-install everything after wiping the drive and it happens again you still won't know if it's some software you're using (especially something beta or unsupported, like Haxies) or your drive is starting to go bad.

I third the suggestion that you pull off the files you want from that drive in case it's hours away from going dead forever.

Then, when you get the Jag-u-ar disks, format the drive, re-install the OS, copy your apps and documents over, and see what happens.

Backup very, very often.

Good luck.

OpenStep · May 19, 2003, 03:08 PM

Try booting single user mode and repairing permissions. Anyone know what the command line command to repair permissions is? It's gotta be diskutil something...

Amorya · May 19, 2003, 05:24 PM

Originally posted by OpenStep:
Try booting single user mode and repairing permissions. Anyone know what the command line command to repair permissions is? It's gotta be diskutil something...

When I booted in Single User mode (command-option-S-U, right?) then it showed the startup bit on a console, but then it went to the same blue screen as before, I didn't get access to anything I could type on.

Amorya

Amorya · May 19, 2003, 05:25 PM

Originally posted by typoon:
You might also have a disk that is going bad.

Again? The disk was replaced a month ago!

Complete reinstall. I've not installed anything that modifies the system, I don't think... I run the usual web apps (Fire, Photoshop, Omni etc) and not much else that isn't Apple. If this new disk is screwed, I really can't be sure why. I don't think there's anything I've done to it! Since it was repaired last time I've not done anything taxing to it at all!

Amorya

Toyin · May 19, 2003, 05:59 PM

Sorry, I don't think I made myself clear in my 1st post. I had similar symptoms when I upgraded from 10.1 to 10.2. The problem was corrupt preferences in my Library folder (~/Library not System/Library or /Library). I removed the Library folder after booting into OS9 and then I was able to log in with no problems.

I suggest you do something similar (after backing up your data as suggested above). You can remove your Library folder either by using target disk mode, or by booting into OS9.

OpenStep · May 19, 2003, 09:20 PM

I think single user mode is apple s after the chime, it should give you instructions to run fsck and mount the file system when it comes up. If fsck finds errors keep running it until it says the disk is ok. I'll try and find the command line tool for repairing permissions.

OpenStep · May 19, 2003, 09:22 PM

If you can get it into single user mode "diskutil repairPermissions /" should repair the permissions on the boot drive