Re: [ros-dev] Making bluescreens more useful
Yep, there's plenty of QR readers that we can use, that's really not a problem at all. On 14 January 2018 at 12:32, Alexander Rechitskiywrote: > https://github.com/libern/qr-code-reader > > https://github.com/schmich/instascan > > > 14.01.2018, 14:24, "Javier Agustìn Fernàndez Arroyo" : > > i like the QR thing. But, take in mind that we will need some kind of > decoder into JIRA, website, or wherever, so that they are easily > uploadable/reportable > > On Sat, Jan 13, 2018 at 12:41 PM, Amine Khaldi > 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. > As our friends at Haiku have already implemented something like this ages > ago, it would be nice to finally have this in ReactOS too :) > > https://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output/ > > > ___ > 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 > > > > -- > Best regards, > Alexander Rechitskiy > +79286331900 > > > ___ > 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
Re: [ros-dev] Making bluescreens more useful
https://github.com/libern/qr-code-reader https://github.com/schmich/instascan 14.01.2018, 14:24, "Javier Agustìn Fernàndez Arroyo":i like the QR thing. But, take in mind that we will need some kind of decoder into JIRA, website, or wherever, so that they are easily uploadable/reportable On Sat, Jan 13, 2018 at 12:41 PM, Amine Khaldi 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.As our friends at Haiku have already implemented something like this ages ago, it would be nice to finally have this in ReactOS too :)https://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output/___Ros-dev mailing listRos-dev@reactos.orghttp://www.reactos.org/mailman/listinfo/ros-dev,___Ros-dev mailing listRos-dev@reactos.orghttp://www.reactos.org/mailman/listinfo/ros-dev -- Best regards,Alexander Rechitskiy+79286331900 ___ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Re: [ros-dev] Making bluescreens more useful
i like the QR thing. But, take in mind that we will need some kind of decoder into JIRA, website, or wherever, so that they are easily uploadable/reportable On Sat, Jan 13, 2018 at 12:41 PM, Amine Khaldiwrote: > 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. >> > As our friends at Haiku have already implemented something like this ages > ago, it would be nice to finally have this in ReactOS too :) > > https://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output/ > > > ___ > 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
Re: [ros-dev] Making bluescreens more useful
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. As our friends at Haiku have already implemented something like this ages ago, it would be nice to finally have this in ReactOS too :) https://www.haiku-os.org/blog/mmlr/2012-07-01_qr_encode_your_kdl_output/ ___ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Re: [ros-dev] Making bluescreens more useful
Let's just start with the basic idea, a bsod with a stacktrace. Then, we can add onto that, maybe a qr code, or translate the addresses etc.. On 13-1-2018 12:24, Hermès BÉLUSCA - MAÏTO wrote: I suppose the idea of putting an idiotic smiley was the "idea" of an intern ^^ Also our qr code would be actually useful, instead of the hardcoded ones win10 seems to display (as it looks the idea of thomas would include the backtrace in it). H. De : David Quintana (gigaherz) Date : 13 janvier 2018 11h17 À : ros-dev@reactos.org Cc : Objet : Re: [ros-dev] Making bluescreens more useful Whatever we do, DO NOT put a smiley in it. It feels like an insult. On 13 January 2018 at 10:36, Ged Murphy <gedmurphy.mailli...@gmail.com <mailto:gedmurphy.mailli...@gmail.com>> wrote: You’ve been looking at too many Win10 blue screens *From:*Ros-dev [mailto:ros-dev-boun...@reactos.org <mailto:ros-dev-boun...@reactos.org>] *On Behalf Of *Timo Kreuzer *Sent:* 12 January 2018 20:23 *To:* ros-dev@reactos.org <mailto:ros-dev@reactos.org> *Subject:* Re: [ros-dev] Making bluescreens more useful 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 <https://github.com/ThFabba/reactos/commit/6a9f172b76bd11f763598c16e5d47299eec1971c> Thoughts? ___ Ros-dev mailing list Ros-dev@reactos.org <mailto:Ros-dev@reactos.org> http://www.reactos.org/mailman/listinfo/ros-dev <http://www.reactos.org/mailman/listinfo/ros-dev> ___ Ros-dev mailing list Ros-dev@reactos.org <mailto:Ros-dev@reactos.org> http://www.reactos.org/mailman/listinfo/ros-dev <http://www.reactos.org/mailman/listinfo/ros-dev> ___ 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 ___ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Re: [ros-dev] Making bluescreens more useful
___ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Re: [ros-dev] Making bluescreens more useful
Hi, yes, that would be very, very nice! Michael On 11.01.2018 11:45, Colin Finck wrote: > I'm supporting Thomas idea and Pierre's additional suggestions. > Let's show the world that BSODs can be useful! > > - Colin > > > Am 11.01.2018 um 07:36 schrieb Pierre Schweitzer: >> Good idea! >> I would just have a few suggestions to make it even more useful: >> - "Consider filing a ticket at https://jira.reactos.org/ if it wasn't >> already reported there. To do so, provide information on what..." >> >> - "Ideally, try to reproduce the problem while capturing a debug log >> that you should translate afterwards. >> See https://; >> >> Cheers, >> Pierre >> >> Le 11/01/2018 à 00:48, Thomas Faber a écrit : >>> 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 >> > > > > ___ > Ros-dev mailing list > Ros-dev@reactos.org > http://www.reactos.org/mailman/listinfo/ros-dev > signature.asc Description: OpenPGP digital signature ___ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Re: [ros-dev] Making bluescreens more useful
I'm supporting Thomas idea and Pierre's additional suggestions. Let's show the world that BSODs can be useful! - Colin Am 11.01.2018 um 07:36 schrieb Pierre Schweitzer: > Good idea! > I would just have a few suggestions to make it even more useful: > - "Consider filing a ticket at https://jira.reactos.org/ if it wasn't > already reported there. To do so, provide information on what..." > > - "Ideally, try to reproduce the problem while capturing a debug log > that you should translate afterwards. > See https://; > > Cheers, > Pierre > > Le 11/01/2018 à 00:48, Thomas Faber a écrit : >> 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 > signature.asc Description: OpenPGP digital signature ___ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Re: [ros-dev] Making bluescreens more useful
Good idea! I would just have a few suggestions to make it even more useful: - "Consider filing a ticket at https://jira.reactos.org/ if it wasn't already reported there. To do so, provide information on what..." - "Ideally, try to reproduce the problem while capturing a debug log that you should translate afterwards. See https://; Cheers, Pierre Le 11/01/2018 à 00:48, Thomas Faber a écrit : > 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 > -- Pierre Schweitzer System & Network Administrator Senior Kernel Developer ReactOS Deutschland e.V. signature.asc Description: OpenPGP digital signature ___ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Re: [ros-dev] Making bluescreens more useful
Let’s bring the NT-4-type BSODs back!! \o/ De : Ros-dev [mailto:ros-dev-boun...@reactos.org] De la part de David Quintana (gigaherz) Envoyé : jeudi 11 janvier 2018 00:53 À : ReactOS Development List Objet : Re: [ros-dev] Making bluescreens more useful Looks nice! On 11 January 2018 at 00:48, Thomas Faber <thomas.fa...@reactos.org> wrote: 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
Re: [ros-dev] Making bluescreens more useful
Looks nice! On 11 January 2018 at 00:48, Thomas Faberwrote: > 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/6a9f172b76bd11f763598c16e5d472 > 99eec1971c > > 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
[ros-dev] Making bluescreens more useful
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