Hi,

We use graphics already, via Inbv & bootvid calls. The same mode the ReactOS boot logo uses J

So this is definitively possible.

Of course we should also check whether the output is not done via headless instead, in which case of course there’s no need for the QR but instead one could just dump what the QR encodes directly on the terminal.

Hermès.

De : Ros-dev [mailto:ros-dev-bounces@reactos.org] De la part de David Quintana (gigaherz)
Envoyé : vendredi 12 janvier 2018 22:00
À : ReactOS Development List
Objet : Re: [ros-dev] Making bluescreens more useful

Wouldn't the QR-enabled BSOD require us to draw the bsod screen in a graphics mode rather than text?

Or are we using a graphics mode already?

On 12 January 2018 at 21:23, Timo Kreuzer <timo.kreuzer@web.de> wrote:

I like it. I recently thought about another possibility to make the BSOD more useful: A QR code.
A QR code can contain up to almost 3 KB of arbitrary data or 4 KB text.

Here's a quick example (1425 characters)
Try it out, use your phone and scan it :)

Am 11.01.2018 um 00:48 schrieb Thomas Faber:

We often get bug reports with just a screenshot of a bluescreen; we then
go ahead and tell people that bluescreens are basically useless, they
should get a debug log and a backtrace, and also remember to tell us
what version they're using.
 
Since there's actually no reason why bluescreens need to be useless, I
thought I'd try to change that.
I've attached an example. The source for this quick PoC can be found at
https://github.com/ThFabba/reactos/commit/6a9f172b76bd11f763598c16e5d47299eec1971c
 
Thoughts?

_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev