Search results

Do you normally have your system set up to autologin as your admin user? Maybe what happened was something crashed your whole login session (as the not-admin user) and the system dumped back to the loginwindow process-- which, if you have autologin turned on, would probably then have logged you...

I take it you have OS 9.1 and OS X on the same disk partition? (I think that's how the restore CD lays things down.)

First: Do NOT do recursive chowns and chmods on your system, especially against high-level directories such as /. There are uncountable system files which *have* to be owned by a certain user/daemon, and/or *have* to have certain permissions set on them, in order for the system to work. Changing...

All these third party docklings are pretty much reverse-engineered hacks; I don't think any public documentation on the API exists at all. I know that some of the stuff in the Magic 8 Ball app wrapper specifically breaks the dock if it detects that the OS version has changed out from under it...

I am seeing a lot of threads all over the place about Docklings being screwed up post-10.0.2 and the common element in all of them is the use of Magic 8 Ball dockling. Looks like nasty third party software exposing some sort of OS-internal bug. (I have only stock docklings on my TiBook, and have...

update_prebinding runs for a pretty long time. There is also a bug where it will hang indefinitely if your hard drive has certain files on it with bad characters in their name. The chief culprit is an invisible file called (as I recall) "Aladdin User Information" or something like that, with...

What's the Magic 8 Ball? I have 10.0.2 on my TiBook and all the stock docklings (Airport, Displays, Battery) work just fine, no errors.

By logging you off, do you mean dumping you back to the login panel? Does it happen at a point that would otherwise involve some sort of display/system sleep? (i.e. after some amount of inactivity?) Or does it occur in full use, while you're typing and all that? If the loginwindow process...

Re the vertical banding problem when you drag windows under 10.0.2, let me guess: You have SETI@home installed. Turn off its screensaver mode.

I assume the target hard drive was HFS+, not HFS Standard? If it was Standard, that's why it failed.

mapski, that panic is (I'm pretty sure) being caused by the SCSI CD-ROM drive. Dig up your original ATAPI (or some relatively reasonable other ATAPI drive) and try installing through it.

Hm. Those permissions look okay... I was going to ask if the affected machine(s) were upgrade installs over existing Public Beta installs-- but some folks are seeing it after a totally clean (erase the disk) install? That "unknown user id: unknown" thing is sort of odd. Maybe something...

Oh! That's the problem, then. Classic won't launch if the main OS install is on UFS; it needs to be HFS+. I, um, hate to say this, but you'll probably need to reinstall OS X as a clean HFS+ install instead of UFS. I could have sworn this was in the Read Before You Install but it doesn't...

If you fiddle with permissions of anything under /System, or in any of the hidden / directories (/Volumes, /private, etc.) you pretty much are playing russian roulette with your machine... :)

If you are getting the "cannot connect" problem even though you definitely have a live connection to the net, try doing "ping www.apple.com" in a terminal window to force a refresh of your DNS records, then try to make the SWU connection again.

You should be able to see 1920x resolutions if you uncheck the "Show Only Recommended Modes" box in the Display prefs.

The error occurs when you try to mount the disk image that the app is on? Does Disk Copy successfully launch and then you get the error, or does the error occur before Disk Copy even gets going?

Can you try booting from the 9.1 CD and running DiskFirstAid to see if there is filesystem corruption? That sounds seriously thrashed. You should be able to do a clean install of 9.1 on the same disk, even with OS X already there, no problem. Note that your Previous System Folder may still...

So if you have the Console open while you do the disk insertion, no messages get dumped into it?

The dosfs/webdav errors should be harmless. If you do an "ls -la /Volumes" in the Terminal, what does it show?