Re: Wow - M$ Fixes Everything - Blue Screen-of-Death Replaced by BLACK Screen-of-Death

On 6/29/25 16:21, c186282 wrote:

On 6/29/25 8:19 AM, Chris Ahlstrom wrote:

Nuno Silva wrote this post while blinking in Morse code:
>

On 2025-06-28, LV-426 wrote:
>

On 2025-06-27 11:41 p.m., c186282 wrote:

https://www.gadgets360.com/laptops/news/microsoft-windows-11-blue- screen-of-death-bsod-black-error-message-8776837?pfrom=home-ndtv_tech
>
The new black screen appears to be identical to the green one
shared by the company in March. It bears an uncanny resemblance
to the Windows 11 update screen, with centre-aligned text telling
users that the computer is restarting because of an error and
the percentage that reveals the progress of the crash log
collection process.

>
A percentage? Will they then finally re-add progress bars?
>

Users will also see a stop code with an error that can be
shared with system administrators, while the black screen
will also inform them about the process that failed (for
example, it will tell users that a particular driver file
failed, such as rdbss.sys).
>
It's also worth noting that this isn't the first time that
Microsoft has announced that the BSOD warning would be
changed from blue. Back in 2021, the company tested a
black version of the warning message, but that version
also included the text emoticon with a colon and a
bracket (a frown).
>
. . .
>
   Well THAT fixes it ! When in doubt, just change
   the color  :-)

>
Windows 4 did it better, couldn't you just choose the background color
of your preference from a set of colors? It was blue by default, but
could be e.g. green.
>

>
   Admittedly Linux boot-failure messages/logs are
   also almost impossible to interpret unless you
   are an ultra-anal hyper-nerd who hasn't moved
   from the PC for ten years .........

>
A lot of messages do provide information to try to address the
problem. This is often much more than certain systems provide.
>
No need to insult people who have at least some knowledge to get
something from these messages.
>

>
   Clue - we need a generally BETTER fail-mode
   solution - much clearer defs of what bombed
   and why and maybe some automated fixes or at
   least really good instructions. In short a
   "system spy" routine that runs even before
   official boot.

>
Maybe they finally decided to follow IBM's idea with the black trap screens
of death on OS/2.

>
I always liked the Atari ST's cherry bombs.

     Amiga "Guru Meditation" messages with the huge
   number following were fun  :-)
    Got so many with my A-1000 that I dumped the box.

Maybe you should have looked those big numbers up.
I got tired of the problems but loved the AmigaOS and went with it
from 1.3 to 3.9. Amiga 1000 to Amiga 2000b But AmigaOS had no memory
protection due to the costs of including chips to manage the memory.
So when CBM went down the tubes I moved to GNU/ Linux and am narly
as happy with it as I was with AmigaOS.  I am older now and find memory
protection a very valuable matter. I even used XP in the transition from
Amiga to the Mandriva Linux 2006.  But the AmigaOS was a real operating
system and I learned a lot from using it much more than I learned from
the Commodore 64 or the 64/128 on which I used native mode, CP/M and
GEOS.  I still have all the bookmarks I gathered on the Amiga and some
few of them are still active.
bliss-Dell Precision 7730-PCLOS 2025.06- Linux 6.12.35 pclos1-KDE Plasma 5.27.11