Page 1 of 1

Chaning BSOD color

PostPosted: Tue Jan 16, 2018 5:51 am
by reactosuser7
In http://toastytech.com/files/bsod.html there is a program that claims changing BSOD color:

<< This program makes use of some old Windows 3.1 options in the system.ini file that have been long forgotten, but are still present in Windows 95, 98, and ME. Unfortunately this program has no effect on Windows NT 3.x, 4, 2000, or XP.

What this program does is simply takes your selection and places it in
two lines in the [386Enh] section of your SYSTEM.INI file. The lines are:

MessageTextColor=C
MessageBackColor=0

In this case "C" is the hexadecimal number for bright red, and "0" is
black.

Here is a complete list of colors:

0 - Black
1 - Blue
2 - Green
3 - Cyan
4 - Red
5 - Magenta
6 - Yellow/brown
7 - White
8 - Gray
9 - Bright blue
A - Bright green
B - Bright cyan
C - Bright red
D - Bright magenta
E - Bright yellow
F - Bright white
>>

Maybe in ReactOS 0.4.x works or not, but in testing will see.
In 0.3.x should work if anyone want to test. Earlier 0.3.x versions was like Windows 98.

Re: Chaning BSOD color

PostPosted: Tue Jan 16, 2018 9:43 am
by EmuandCo
No ReactOS version was like Windows 98, never ever.

Re: Chaning BSOD color

PostPosted: Tue Jan 16, 2018 10:40 am
by Konata
If you're looking to change the color of the BSOD I think you're having a little too much fun with the system :lol:

If you're curious, a major issue here is how Windows 9x and Windows NT work. 9x BSOD's aren't actually blue screens of "death", they're warning screens. They're only for application crashes and can be recovered from. With this assumption in the minds of the OS developers, they can still read from disk and add customization options to the blue screen.
NT is a whole lot different. NT's BSOD truly is a blue screen of death, it's the kernel panic screen and only deploys when the system has reached an unstable state and cannot continue operation without risking data corruption, which is absolutely unacceptable. There is no chance here to read from disk. So customizing an NT blue screen isn't an option. At least not with how NT's architecture is laid out.

Re: Chaning BSOD color

PostPosted: Tue Jan 16, 2018 11:16 am
by dizt3mp3r
If we are allowed to change the colour then I'd like to be the first to reserve some space for advertising.

The BSOD could be the screen ReactOS users see most, so it makes sense to think about exploiting it...

Re: Chaning BSOD color

PostPosted: Tue Jan 16, 2018 12:08 pm
by hbelusca
As the original post citation mentions:
Unfortunately this program has no effect on Windows NT 3.x, 4, 2000, or XP.

So it's the same concerning ReactOS.

BUT...

... You can programmatically change the BSoD color in the kernel code here:
https://git.reactos.org/?p=reactos.git; ... 22ff4#l661
Change the last parameter of the InbvSolidColorFill() call to some other number to change the colour.
You can also change the text colour by modifying the parameter of the InbvSetTextColor() call.

Another option would be to have a set of registry values to customize the BSoD colors... (this would be ReactOS-specific).

Re: Chaning BSOD color

PostPosted: Wed Jan 17, 2018 6:09 am
by reactosuser7
hbelusca wrote:As the original post citation mentions:
Unfortunately this program has no effect on Windows NT 3.x, 4, 2000, or XP.

So it's the same concerning ReactOS.

BUT...

... You can programmatically change the BSoD color in the kernel code here:
https://git.reactos.org/?p=reactos.git; ... 22ff4#l661
Change the last parameter of the InbvSolidColorFill() call to some other number to change the colour.
You can also change the text colour by modifying the parameter of the InbvSetTextColor() call.

Another option would be to have a set of registry values to customize the BSoD colors... (this would be ReactOS-specific).


Thanks for this detail.
The point is to change BSOD in a finish compilation and installed ReactOS for a normal user, with hacks or with a program.

Re: Changing BSOD color

PostPosted: Thu Jan 18, 2018 11:16 am
by middings
Changing BSOD color.

Because no one would know what a GSOD or RSOD is, only colors that begin with the letter 'b' may be used. A black screen might frighten people to death and a beige screen doesn't look deadly. So a BSOD is blue or nothing.
:lol:

Re: Chaning BSOD color

PostPosted: Sun Jan 21, 2018 7:50 am
by reactosuser7
middings wrote:Changing BSOD color.

Because no one would know what a GSOD or RSOD is, only colors that begin with the letter 'b' may be used. A black screen might frighten people to death and a beige screen doesn't look deadly. So a BSOD is blue or nothing.
:lol:


It is focusing on advanced users. :D

Re: Chaning BSOD color

PostPosted: Sun Jan 21, 2018 11:10 am
by justincase
middings wrote:Because no one would know what a GSOD or RSOD is, only colors that begin with the letter 'b' may be used.
What about Brown? ;)
In fact there are some other colors too: https://en.wikipedia.org/wiki/List_of_colors:_A-F#B :lol:

reactosuser7 wrote:The point is to change BSOD in a finish compilation and installed ReactOS for a normal user, with hacks or with a program.
It should be possible to do it with a hex editor if someone's determined enough, but I don't know that there's anyone who thinks it's worth it enough to bother, and I have my doubts anyone wants to write a program to automate the hack. It seems more likely to me that someone would either compile their own fork of the ReactOS kernel as a drop-in replacement (as long as the revision matches), or that the team might accept a patch that adds a registry key/value that can override the default color (which would be ReacOS specific, like hbelusca mentioned) if someone wants it enough to write the code for it.

Re: Chaning BSOD color

PostPosted: Sun Jan 21, 2018 9:42 pm
by DGMurdockIII
what about doing what windows 8 and windows 10 have done for the BSOD and have it show useful info that can make it easier to diagnose why it crashed

Re: Chaning BSOD color

PostPosted: Mon Jan 22, 2018 4:19 am
by reactosuser7
DGMurdockIII wrote:what about doing what windows 8 and windows 10 have done for the BSOD and have it show useful info that can make it easier to diagnose why it crashed


Do a JIRA request.

Re: Chaning BSOD color

PostPosted: Mon Jan 22, 2018 10:37 am
by oldman
An improved BSOD screen is in the pipeline; it was discussed over a week ago by the developers.

Re: Chaning BSOD color

PostPosted: Mon Jan 22, 2018 9:42 pm
by DGMurdockIII
That's nice to hear as I don't like to get blue screen it just nice when you get usable information on it

Re: Chaning BSOD color

PostPosted: Tue Jan 23, 2018 10:04 am
by PurpleGurl
I'd love to see such a registry key, but there are much more serious things to focus on now.