please, a moment of silence :(
We gather here today to mourn the passing of one Colonel William James Bodsford Panic.
Colonel "Big Billy" Panic was a quiet man, but often misunderstood by the younger
generation when he would come forth to warn the locals of the imminent danger.
A stalwart soldier, though, he stood his ground as his comrades around him would fall
to their knees.
At the age of only six years, it would seem that Colonel Panic has been taken before his
time. Nevertheless, he is survived by Friendly "Gui" Panic, a character of even less
ostentation. Gui promises to carry on the duties of the Colonel and not to waver from
them for an instant. A former student of the Colonel, Gui has become fluent in seven
different languages in the hopes that he can reach out to more people and deliver his
message in a gentler manner.
Please, let us take a moment of silence in memory of our dear friend Colonel Panic.
\
[ 05-21-2002: Message edited by: starfleetX ]
Comments
<strong>
[SNIP]
Please, let us take a moment of silence in memory of our dear friend Colonel Panic.
<img src="graemlins/hmmm.gif" border="0" alt="[Hmmm]" />
[ 05-20-2002: Message edited by: starfleetX ]</strong><hr></blockquote>
LMFAOROTFL!
That is great...
Looks like Apple is making UNIX even more invisible. Though I've never had the oppurtunity to see what the old one looked like , I'm assuming that it is very different.
[EDIT: Cut out stuff ]
[ 05-21-2002: Message edited by: Spart ]</p>
<strong>Has Colonel "Big Billy" Panic fallen prey to the mysterious and powerful jaguar that has been the talk of the town lately?</strong><hr></blockquote>Ah, yes, so you've heard.
He did indeed fall prey to the jaguar.
The beast-cat was just too fast... even for the Colonel.
*sniffle*
[ 05-20-2002: Message edited by: starfleetX ]</p>
sorry I just HATE that!
Mac Guru
Still beats the BSOD.
Did you know in Windows 2000 there is a default setting to immediately reboot upon kernel panic (that's turned off in Windows NT ergo the BSOD)?
So instead of eliminating the BSOD, they just hide it -- for your convenience.
Screed ...still the best thing is not have Colonel over ... ever!
[ 05-21-2002: Message edited by: sCreeD ]</p>
<strong>Why in GOD's name do you people INSIST on replying and quoting the entire god damned post? I read it once, I don't need to read it again... I wish they'd remove that darned reply button from people's posts.
sorry I just HATE that!
Mac Guru</strong><hr></blockquote>
Me too <img src="graemlins/lol.gif" border="0" alt="[Laughing]" />
Too bad its too damn buggy to use as a full time OS. Many apps I used didnt work properly enough for me to justify the use of it any longer.
Still was fun.
If the kernel panics, how do you know the window server can still present an interface for a restart? The text spewing colonel (or even a BSOD) is easy, but an Aquafied window?
I'm glad they did it, though. Those panics were only useful to kernel hackers. And even then only marginally. I bet Apple got very few panic submissions from users. Write the text down verbatim and send it in! Yeah, right.
[ 05-21-2002: Message edited by: spotbug ]</p>
I personally hate the auto-restart thing in Win2K; it's jarring and scary. At least tell me what's going on!
You don't need the window server to do that. I didn't see any problem with using the kernel to spit out a screen like that... of course, there were some naysayers.
<strong>You don't need the window server to do that.</strong><hr></blockquote>
Yeah, ok, not the window server. But you do need Quartz and Aqua (at least), right?
I'm not saying it's bad (read what I wrote). I like it. I was simply curious how it was done. I was always under the impression that when the kernel panics, it's all over; you want to use as little of the services (hopefully still) available to present some sort of message, etc.
<strong>
Yeah, ok, not the window server. But you do need Quartz and Aqua (at least), right?
</strong><hr></blockquote>
Well I guess writing the graphics directly to the FrameBuffer should be enough (although the shadow would be hard to compute).
I can't tell from the screenshot, but I doubt it, since like you said, you don't want to be relying on a whole lot when a kernel panic occurs. I think all they're doing is taking whatever Quartz had on screen and writing over it with that bitmap. I don't know how they go about dimming the screen, but it can't be anything complicated.
[quote]I'm not saying it's bad (read what I wrote).<hr></blockquote>
Hmm? I didn't say you said it was bad.
EDIT:
[quote](although the shadow would be hard to compute). <hr></blockquote>
I can't tell from that screenshot... there's a shadow?
[ 05-21-2002: Message edited by: Dead Member ]</p>
<strong>Hmm? I didn't say you said it was bad.</strong><hr></blockquote>
Oh, oops, sorry. You said something about naysayers and I mistook that.
I hadn't thought that that window might simply be a graphic dumped right into the frame buffer. That makes sense. Also, if you have access to the frame buffer to do that much, you could probably even do an Aqua-style shadow on that "window" without any problems.
This is what I love Apple for
I was about to post the same thing Guru (DOH! I just used the reply button though...)
I guess the 56k people get pissed the most - more images to download. It's even more annoying when people quite an entire large message in their post - when their's is the very next message!
(sorry Spart, we still love you)
1. No, there does not appear to be a shadow. The whole screen dims for a moment and tosses up that window. Obviously, it's hard to know exactly *how* it's done, but I'd venture to guess it's a bitmap being output directly to the screen, bypassing quartz just like the older Colonel did.
2. What about the error message? How can Apple track problems if they don't know what happened? Simple. "The kernel panic technical info is saved in NVRAM and written out to disk when your machine is rebooted (at which time the file system is in a safe state)," says Andrew Welch. Sure enough, afterwards it creates a panic.log in the /Library/Logs/CrashReporter/ directory that contains all the backtrace and kernel information that previously would puke up on your screen.
Oh, and I'm glad you guys were smart enough to realize what this meant. Now I remember why I rarely visit MacOSX.com any more -- those guys are dense!
[ 05-21-2002: Message edited by: starfleetX ]</p>
sorry I just HATE that!
Mac Guru<hr></blockquote>
[quote]Me too <img src="graemlins/lol.gif" border="0" alt="[Laughing]" /> <hr></blockquote>
[quote]I was about to post the same thing Guru (DOH! I just used the reply button though...)
I guess the 56k people get pissed the most - more images to download. It's even more annoying when people quite an entire large message in their post - when their's is the very next message!
(sorry Spart, we still love you)<hr></blockquote>
Yea yea yea...I fixed it. And I don't insist on doing it, it's a product of lazyness.
And I'm one of those poor 56k users as well.
<strong>"The kernel panic technical info is saved in NVRAM and written out to disk when your machine is rebooted (at which time the file system is in a safe state)," says Andrew Welch. Sure enough, afterwards it creates a panic.log in the /Library/Logs/CrashReporter/ directory that contains all the backtrace and kernel information that previously would puke up on your screen.</strong><hr></blockquote>
That is super-cool.