Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.os.windows-10 > #183134 > unrolled thread

BSOD will be green during beta and then black

Started byOliver <ollie@invalid.net>
First post2025-04-01 01:40 -0600
Last post2025-04-01 15:24 +0000
Articles 13 — 11 participants

Back to article view | Back to alt.comp.os.windows-10

Contents

  BSOD will be green during beta and then black Oliver <ollie@invalid.net> - 2025-04-01 01:40 -0600
    Re: BSOD will be green during beta and then black VanguardLH <V@nguard.LH> - 2025-04-01 03:22 -0500
      Re: BSOD will be green during beta and then black Oliver <ollie@invalid.net> - 2025-04-01 11:27 -0600
    Re: BSOD will be green during beta and then black Daniel70 <daniel47@eternal-september.org> - 2025-04-01 19:58 +1100
      Re: BSOD will be green during beta and then black Java Jive <java@evij.com.invalid> - 2025-04-01 11:49 +0100
        Re: BSOD will be green during beta and then black Graham J <nobody@nowhere.co.uk> - 2025-04-01 12:45 +0100
          Re: BSOD will be green during beta and then black Daniel70 <daniel47@eternal-september.org> - 2025-04-02 22:06 +1100
      Re: BSOD will be green during beta and then black micky <NONONOmisc07@fmguy.com> - 2025-04-01 18:14 -0400
        Re: BSOD will be green during beta and then black wasbit <wasbit@REMOVEhotmail.com> - 2025-04-02 09:44 +0100
    Re: BSOD will be green during beta and then black Paul <nospam@needed.invalid> - 2025-04-01 05:07 -0400
    Re: BSOD will be green during beta and then black Andy Burns <usenet@andyburns.uk> - 2025-04-01 11:32 +0100
      Re: BSOD will be green during beta and then black "s|b" <me@privacy.invalid> - 2025-04-01 13:21 +0200
        Re: BSOD will be green during beta and then black Frank Slootweg <this@ddress.is.invalid> - 2025-04-01 15:24 +0000

#183134 — BSOD will be green during beta and then black

FromOliver <ollie@invalid.net>
Date2025-04-01 01:40 -0600
SubjectBSOD will be green during beta and then black
Message-ID<vsg5a9$2ijpd$1@dont-email.me>
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

[toc] | [next] | [standalone]

#183136

FromVanguardLH <V@nguard.LH>
Date2025-04-01 03:22 -0500
Message-ID<y24z3mfaxsyy$.dlg@v.nguard.lh>
In reply to#183134
Oliver <ollie@invalid.net> 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

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.

[toc] | [prev] | [next] | [standalone]

#183146

FromOliver <ollie@invalid.net>
Date2025-04-01 11:27 -0600
Message-ID<vsh7mj$3l8sp$1@dont-email.me>
In reply to#183136
On Tue, 1 Apr 2025 03:22:32 -0500, VanguardLH <V@nguard.LH> wrote 

> 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.

Mostly it was a sarcastic dig at the BSOD (blue) but to address your main
concern, the color will eventually show up as the BSOD (black) to everyone.

It will only be green in the meantime.

[toc] | [prev] | [next] | [standalone]

#183137

FromDaniel70 <daniel47@eternal-september.org>
Date2025-04-01 19:58 +1100
Message-ID<vsg9qr$2n3qi$1@dont-email.me>
In reply to#183134
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)??
-- 
Daniel70

[toc] | [prev] | [next] | [standalone]

#183141

FromJava Jive <java@evij.com.invalid>
Date2025-04-01 11:49 +0100
Message-ID<vsggbe$2tijv$1@dont-email.me>
In reply to#183137
On 2025-04-01 09:58, Daniel70 wrote:
>
> 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.

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

[toc] | [prev] | [next] | [standalone]

#183143

FromGraham J <nobody@nowhere.co.uk>
Date2025-04-01 12:45 +0100
Message-ID<vsgjkl$311u3$1@dont-email.me>
In reply to#183141
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!


-- 
Graham J

[toc] | [prev] | [next] | [standalone]

#183167

FromDaniel70 <daniel47@eternal-september.org>
Date2025-04-02 22:06 +1100
Message-ID<vsj5n4$1ll4q$1@dont-email.me>
In reply to#183143
On 1/04/2025 10:45 pm, Graham J wrote:
> 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!

.... and what's the Bet that that CEO's Phone would be the first in 
which an internal Fault would occur?? ;-)
-- 
Daniel70

[toc] | [prev] | [next] | [standalone]

#183149

Frommicky <NONONOmisc07@fmguy.com>
Date2025-04-01 18:14 -0400
Message-ID<v6poujlsdubj5pfie4k4bto3egmlvbp6rt@4ax.com>
In reply to#183137
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.
>> 
>> 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 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.

[toc] | [prev] | [next] | [standalone]

#183162

Fromwasbit <wasbit@REMOVEhotmail.com>
Date2025-04-02 09:44 +0100
Message-ID<vsitdb$1d9it$2@dont-email.me>
In reply to#183149
On 01/04/2025 23:14, micky wrote:
> 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.
>>>
>>> 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 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.
> 

I thought that's what 'search & replace' was for.


-- 
Regards
wasbit

[toc] | [prev] | [next] | [standalone]

#183139

FromPaul <nospam@needed.invalid>
Date2025-04-01 05:07 -0400
Message-ID<vsgabu$2niqr$1@dont-email.me>
In reply to#183134
On Tue, 4/1/2025 3:40 AM, 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

I wonder if they would ever consider making the error number larger.
I'm kinda sick of the "three point font" idea.

If you want to play with it, you could benefit from a utility
in this orbit.

https://learn.microsoft.com/en-us/sysinternals/downloads/notmyfault

   Paul

[toc] | [prev] | [next] | [standalone]

#183140

FromAndy Burns <usenet@andyburns.uk>
Date2025-04-01 11:32 +0100
Message-ID<m51tmuFegreU1@mid.individual.net>
In reply to#183134
Oliver wrote:

> The BSOD will be green for a short time 
Will it include the date?

[toc] | [prev] | [next] | [standalone]

#183142

From"s|b" <me@privacy.invalid>
Date2025-04-01 13:21 +0200
Message-ID<m520i5FevgsU1@mid.individual.net>
In reply to#183140
On Tue, 1 Apr 2025 11:32:58 +0100, Andy Burns wrote:

> Will it include the date?

(-:

-- 
s|b

[toc] | [prev] | [next] | [standalone]

#183145

FromFrank Slootweg <this@ddress.is.invalid>
Date2025-04-01 15:24 +0000
Message-ID<vsh7dj.k5c.1@ID-201911.user.individual.net>
In reply to#183142
s|b <me@privacy.invalid> wrote:
> On Tue, 1 Apr 2025 11:32:58 +0100, Andy Burns wrote:
> 
> > Will it include the date?
> 
> (-:

  Well, Lifehacker announced it on World Backup Day [1], so all's good!

[1] <https://www.worldbackupday.com/en>
<https://en.wikipedia.org/wiki/World_Backup_Day>

[toc] | [prev] | [standalone]

Back to top | Article view | alt.comp.os.windows-10

csiph-web