What casues "big screen startup?"
I had a probelm with Winblows when I used it and now it is the same thing in OSX. Sometimes, my Compaq would start up, and the stuff on the screen would be "blown up" to where it was about 4X too big for my screen and I could not do anything and I just restarted.
Now, lo and behold, it is happening in OSX. I did not have htis occur in Classic, as far as I can remember (Haven't booted into classic since 10.1). It has had "big startup screen" twice today. It is fine with the beachball in the upper left and the happy mac in the middle of the screen, but then when you get the blue "X" icon with the progress bar below indiciating all the stuff startin up, that gets blown up real big and fills up the whole right side of the screen, and it stays big when it is done starting up. All I can do is to "ctrl-openapple-power" and restart, and it is fine.
Is there a reason for this? Is there a preventative measure? It is no biggie really, just an annoyance, but something I hated with my Winblows experieance and I hate to see it here on my Mac now.
Any suggestions?
Now, lo and behold, it is happening in OSX. I did not have htis occur in Classic, as far as I can remember (Haven't booted into classic since 10.1). It has had "big startup screen" twice today. It is fine with the beachball in the upper left and the happy mac in the middle of the screen, but then when you get the blue "X" icon with the progress bar below indiciating all the stuff startin up, that gets blown up real big and fills up the whole right side of the screen, and it stays big when it is done starting up. All I can do is to "ctrl-openapple-power" and restart, and it is fine.
Is there a reason for this? Is there a preventative measure? It is no biggie really, just an annoyance, but something I hated with my Winblows experieance and I hate to see it here on my Mac now.
Any suggestions?
Comments
and maybe trashing the display settings/prefs.
<strong>OK, bear with me, I know I sound like a novice, which I kinda am, but live and learn, and all of you were novices too so excuse my ignorance. Well I found out that the iBook is starting up at 640x480 as opposed to 800x600 so those of you with an iBook simialr to mine can click on that resolution to see the problem. Now that I know the problem I should be able to fix it without restarting, but it is still annoying. Any way to prevent this 100%?</strong><hr></blockquote>
Yep, We've all been novices. I feel like one all over again when I use OS X, it's awesome. Anyway, I have the same model ibook, with 128MB Ram for a few more days. I haven't had this problem yet, but I won't be running 10.1 or greater until tomorrow (long story).
I think this could be some corruption in a system file maybe a display pref. The first solution attempt is zapping the PRAM, which means holding cmd+option+p+r while you restart until you hear the startup chime a second time, or you can use micromat's tech tool to do it for you.
If that doesn't work, consider completely reinstalling your system software. I see you have a burner, so backing up your data should be easy. I would really recommend reformating your Hard Drive and reinstalling everything.
Hope this helps, if not consider emailing Brett Larson at brett@techtv.com. He's Call for Help's mac guy.
Sounds like you machine is remembering the screen size right away. Maybe try trashing the display/monitor prefs as stated earlier.
I just trashed everything and reinstalled a few weeks ago so I cannot believe that would be it. Like I said it is NBD but still annoying. I have not had it happen since my last post so maybe it is over.
Merry Christmas.
<strong>This is a known bug with first-generation (300-466MHz) iBooks. Several iBook owners and myself have spoken to Apple about it. There is no fix, unfortunately.</strong><hr></blockquote>
That sucks...like I said the same thing used to happen with a Compaq I used to have runnig Win95. Kinda sucks.
I don't usually run OS9 as it resets my linux bootstrap partition, so I don't know if this is going to be a recurring thing. I'd be suprised if the PRAM reset didn't fix it.
Hope this helps.
--Mike