The BSOD will be green for a short time (during beta) and then black.
https://lifehacker.com/tech/how-to-try-out-windows-new-blue-screen-of-death
The BSOD will be green for a short time (during beta) and then black.
https://lifehacker.com/tech/how-to-try-out-windows-new-blue-screen-of-death
On 1/04/2025 6:40 pm, Oliver wrote:
The BSOD will be green for a short time (during beta) and then black.
https://lifehacker.com/tech/how-to-try-out-windows-new-blue-screen-of-death
How crazy are MicroSoft?? Shouldn't THEY be trying to make US NEVER see
the BSOD rather than telling us the BSOD (Blue) will become the BSOD (Black)??
+1! Someone, I forget who, once said that fundamentally to show an
error message is an error in itself, implying that instead the problem
should have been solved. Perhaps that's not possible in every circumstances, because one cannot predict every possible combination of circumstances, but it has to be the right situation to aim for.
The BSOD will be green for a short time (during beta) and then black.
https://lifehacker.com/tech/how-to-try-out-windows-new-blue-screen-of-death
You neglected to mention in YOUR post that this is a change in the
Insider release channel. Don't just post URLs to articles. Mention
what they are HERE.
On 1/04/2025 6:40 pm, Oliver wrote:
The BSOD will be green for a short time (during beta) and then black.
https://lifehacker.com/tech/how-to-try-out-windows-new-blue-screen-of-death
How crazy are MicroSoft?? Shouldn't THEY be trying to make US NEVER see
the BSOD rather than telling us the BSOD (Blue) will become the BSOD >(Black)??
In alt.comp.os.windows-11, on Tue, 1 Apr 2025 19:58:00 +1100, Daniel70 <daniel47@eternal-september.org> wrote:
On 1/04/2025 6:40 pm, Oliver wrote:
The BSOD will be green for a short time (during beta) and then black.How crazy are MicroSoft?? Shouldn't THEY be trying to make US NEVER see
https://lifehacker.com/tech/how-to-try-out-windows-new-blue-screen-of-death >>
the BSOD rather than telling us the BSOD (Blue) will become the BSOD
(Black)??
In fairness, from my pov, I can't remember the last time I saw one.
Weeks or months ago. Maybe a year.
OTOH, I don't like this because now I have to change all my references
to GSOD and then later to BlSOD. That will take a lot of tiem.
Java Jive wrote:
[snip]
+1! Someone, I forget who, once said that fundamentally to show an
error message is an error in itself, implying that instead the problem
should have been solved. Perhaps that's not possible in every
circumstances, because one cannot predict every possible combination
of circumstances, but it has to be the right situation to aim for.
The logical extension of this is that the telephone number for technical support should be the CEO. The product design is obviously faulty if
the CEO receives any calls!
The BSOD will be green for a short timeWill it include the date?
Will it include the date?
On Tue, 1 Apr 2025 11:32:58 +0100, Andy Burns wrote:
Will it include the date?
(-:
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 508 |
Nodes: | 16 (3 / 13) |
Uptime: | 221:35:50 |
Calls: | 9,974 |
Calls today: | 5 |
Files: | 13,833 |
Messages: | 6,358,948 |