BSOD "restyling" :)

Davy Bartoloni · Post by **Davy Bartoloni** » Sun Jan 25, 2009 12:20 am

blue screens of windows are very distressing...

...reactos can be better

this is a possible BSOD from the 90's that makes me remember good memories...

[ external image ]

implementing this BSOD... in the future... some people may laugh, after a computer-crash

Amiga Rulez

gonzoMD · Post by **gonzoMD** » Sun Jan 25, 2009 11:09 am

this is very cool, maybe it would be good to if it is with the BSOD's so like if you shutdown ROS. Maybe, there could be a random error screen, maybe the original, maybe your Amiga Style or something mac-like or a screen that looks like C64. This could weir the users, but it would be cool too

The123king · Post by **The123king** » Sun Jan 25, 2009 12:29 pm

I agree that ReactOS BSoD's should be restyled a bit more, maybe providing better diagnostic info (which would be useful for debuggers) and maybe cut down the unnecesary gibberish out of it.

Blackcrack · Post by **Blackcrack** » Sun Jan 25, 2009 4:00 pm

Hy,
hihi, jea, very nice idea... jea shold be get a new style to have,
the blue one it's rater old .. shold be a little fresh
"multisysteminternationalism" air on it

or so..
mayby mus be the System MS conform but the style it dont mus be the same..
can be like so as programming all programmers on it, Amiga, C64, PC, Mac
around of the World to have one Standart and why not let see it.. i tell it too..
Amiga rulez but why not with other colors ? Mayby C64 colors

to be not so aggressive red..
best regards
Blacky

Davy Bartoloni · Post by **Davy Bartoloni** » Sun Jan 25, 2009 5:45 pm

[ external image ]

with these colors would be more relaxing...

gonzoMD · Post by **gonzoMD** » Sun Jan 25, 2009 5:55 pm

then the B in BSOD will match again

Davy Bartoloni · Post by **Davy Bartoloni** » Sun Jan 25, 2009 6:02 pm

right!

Blackcrack · Post by **Blackcrack** » Sun Jan 25, 2009 6:37 pm

Hy

no, i had mean, not an fullscreen , like the Amiga one, but with lighten blue Collor of Fond
and not red one or an other design between(¿middle?) of Amiga and C64 ..
in this direction easy a new one banner and not a fully blobb blue screen who if you work
by night to become an blue hammer

dongghhkk i stay and nothing go anymore..
no, half screen, like Amiga in blue Fond and black background and maby a little bomb by side
who i think on linux... to get an lil' honor to greetings the "Brother"System on Open Source or so on ;D
(to have pease, you know the flameware about Linux and Win32 at starttime of Linux?)
[ external image ]
he,he, i stopped the System befor hardware fail.. Boouumm !
say, Thank you !
yo' Systemrobott

best Regards

Blacky

Post by **hto** » Sun Jan 25, 2009 6:37 pm

Themes for BSOD. :)

Blackcrack · Post by **Blackcrack** » Sun Jan 25, 2009 6:55 pm

Hy hto,

crewl, if it is supportet , will be very nice !

best regards
Blacky

Aape · Post by **Aape** » Mon Jan 26, 2009 6:42 am

"Restyling" the BSOD to make it more attractive is counter-productive. After all, why would we want to make something look good if our ultimate goal is that the end user never sees it? The entire point of it anyway is to strip down into a failsafe environment to tell the user what's going on.

With that in mind, the best thing to do with the BSOD is to allow it to display more information that's more relevant to the end user. The ultimate goal of the BSOD should be to never appear, the secondary goal should be to inform and help with making sure it doesn't appear again. Say the display system crashes and ROS can't recover it, so it's forced to go into a BSOD. The output should look something like this:

"The display system has crashed and ReactOS cannot recover. If this is the first time you have seen this screen, rebooting your computer should do the trick. Otherwise, you may have a problem with your Video Card. Below is more detailed technical information, which your system administrator and/or tech support would like to see.

"*Technical Babble*

"Now we're going to present to you a command-line interface. If you don't know what to do, don't panic! A tech support personnel on the phone may give you instructions which involve typing commands here."

(Note: The command-line interface should be perfectly capable of scrolling, and the technical information on the screen shouldn't scroll away after the user enters some commands. Also, replace the first and third sentences depending on what the problem is.)

Also: Whatever you do, don't do the equivalent of the old MacOS bomb icon! That's actually the opposite of what you want to do :/

Blackcrack · Post by **Blackcrack** » Mon Jan 26, 2009 7:51 am

Hy Aape,

the Bombicon was at first at Amiga Aape, how i know
and what it is speak against, if you can make it more personaly..
or more factory like to..
"Call Technical Personal on internal Phone Number -666 Mr.BAFH "
or on Software problems by Mail /office/ System / Software or like so
"Call Operater ! Internal Phone Number 999 Mr. BOFH"

How ever, as default BOSD, GOSD, YOSD .. we must look for a
better one, a new one and a modern one, to get the User an
Systemstop/Errorscreen who be acceptable for an Enduser and the
Rest can be as Dumb on "C:\dump.txt" who by sending per mail to
Reactos copy in "support-sendet-folder" can be saved
as "%Windir%//dumb-mailed//01.01.09-9:00am.txt" by date and time
of the dump-file to can copy ..
oky, this it is an other thing.. /idea....

how ever ,the user whant know, like i see it, what it is do in words,
like the system get an error number and this it is tranlated by an texfile
and tell in words and not in numbers what it is for an problem, like

[ external image ]

"The Reactos have an error ba an IRQ-Handler it is not less or Equal"
"If it is the first time to become this Error so help us to develope and send us the Dump-file at C:/dumb.txt to error@reactos.org "
( or an error-automatismen let running)
Technical information be in file C:\dump.txt

echo dump > C:\dump.txt // (not ">>")
copy C:\dump.txt %windir%//dumpfiles/%date%-%time%.txt

"The Problem was in Hardware %Driver%" / The Problem was in Software %File%
in the string %errorstring% "

and there one we need only an half screen and let show the users to be stay all..

more to see as informations not need, it is enoug to know to be in hardware or in software
if it is more to know so can take a look for detairte/more informations in the dumpfile who can get all
informations for more technicals or Extended Users who it is need. To know if mus be
kick the Nvidia on nirvana or it is the ATI-chipset and shoot this one in nirvana.. *rofl*
And Reactos-Developer can become all informations with the dump-file to creating
an patch to sent it per online-update-routine... or per online-uptate-numbers-paching-routine
so can be a space to have a numerous call to a spezific patch.

ros-patch-2342342342.exe = Patch for Mainboardmsiblabla+Nvidia-Card8600GT to fixup a irqproblem.
ros-update-435353534.exe = Explorerupdate No32 to become an haedbanger on Desktop.
ros-reg-43435453.exe = A Regestry patch to have blabla on HKblabla..
ros-etc.-etc.exe = etc..
humm.. only so als lil' "idea"runner..

best regards
Blacky

Post by **hto** » Mon Jan 26, 2009 9:59 am

Aape wrote: After all, why would we want to make something look good if our ultimate goal is that the end user never sees it?

To sweeten the pill. :)

Is there any OS which allows users to choose styles of BSOD? ReactOS can become the first. :)

With that in mind, the best thing to do with the BSOD is to allow it to display more information that's more relevant to the end user.

The BSOD would be also the right place to utter a word of wisdom to console the user. :)

gonzoMD · Post by **gonzoMD** » Mon Jan 26, 2009 10:03 am

this with console is very good, but like the others allready said, its most important, that the user knows what is wrong whith his/her computer. th bsod errorcodes must be parsed to detailled and NOT geeky descriptions in easy native language that there is to read that the graphics card or the RAM maybe is defect, or that this or this program crashed. Maybe a black screen, where the message is at an normal messagebox then you can decide to restart, send errorlog, go into console or launch something like memtest86 but more user friendly, so that the errors maybe immediately will be removed or excluded.
BUT DEFINITEVE NOT JUST COLORED SCREEN WITH OTHER COLORED TEXT, this is ugly

Blackcrack · Post by **Blackcrack** » Mon Jan 26, 2009 11:09 am

Hy,

humm.. it is enabling to give diffrent events? like user whant.. ? once by dialog (yes/no/send/reboot) , once by
screen background half/full with textarena to say with hotkey's like y/n/s/r ? easy like modding ?
controlling by cpl on control ? To use Bootingup, diffrents Pictures, Using by reboot or by Shut down.. an animated picture..
and for BOSD an own picture too.. to enabling to creating an zip-pack with pictures with an ini and theme-folder.
an Standarttheme and to possible the users to can make themes.. or use system own dialog..
And all will be peaseful

any can take what they whant.. it must make the possibility to be get..
the rest, the themes, make the user around of the world.. take alone a look on skinz.org
or kde-look, gnome-look.org all user take the possibility and make some themes,
but it must be only let and give they are the possibility.

best regards
Blacky

BSOD "restyling" :)

BSOD "restyling" :)

Re: BSOD "restyling" :)

Re: BSOD "restyling" :)

Re: BSOD "restyling" :)

Re: BSOD "restyling" :)

Re: BSOD "restyling" :)

Re: BSOD "restyling" :)

Re: BSOD "restyling" :)

Re: BSOD "restyling" :)

Re: BSOD "restyling" :)

Re: BSOD "restyling" :)

Re: BSOD "restyling" :)

Re: BSOD "restyling" :)

Re: BSOD "restyling" :)

Re: BSOD "restyling" :)

Who is online