Re: and yet another suggestion
@ Mike - assuming for the moment that "Usual Causes" will be left out -- is it possible to give the user the capability to input a URL somewhere (similar to what we now have for DRT URL) and then have the app use that URL + a "hard-coded" tag that the app would assemble (for lack of a better term)?
...\dmpOptions\driverInOut.txt on my system contains:
Code:
https://www.sysnative.com/drivers/driver.php?id=
http[i]:[/i]//www.sysnative.com/drivers/driver.php?id=<driver Name>
Example:
-
x1 =
%userprofile%\SysnativeBSODApps\
-
x2 =
dmpOptions\bugcheckURL.txt
Where the contents of
%x1%%x2% would be something like:
Code:
[url=http://www.carrona.org/bsodindx.html#<bugcheck>]
http[I]:[/I]//www.carrona.org/bsodindx.html#[color=#cc00ff]<bugcheck>[/color][/url]
- the app would perform a one-time read of
%x1%%x2%
- SET
x3 =
contents of file
%x1%%x2%
- SET
<bugcheck> = bugcheck only, i.e., parms 1-4 NOT included
- when the
BugCheck Info: line is encountered while writing 98, 97, other (??), substitute
%x3%<bugcheck>
The hyper-linked output (with
<bugcheck> to be populated by the app) =
The one area that I have not given thought to is where to obtain the
bugcheck info, i.e.,
Code:
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
We could create a SQL file at carrona.org containing 2 fields -
- Bugcheck
- Bugcheck Description
Such a table could easily be maintained at carrona.org via PHP screens or direct SQL DB editing and write a text file to -
http://www.carrona.org/drivers/files
I estimate such a text file to be <10k in size.
It is possible for PHP to strip off/ carve out the info needed (bugcheck, bugcheck desc) from a carrona.org HTML page, update a SQL file or simply bypass SQL and write directly to a text file. I think downloading then parsing a 1 MB+ HTML page at the local level (by the app during runtime) would significantly increase the app's run-time and would therefore be counter-productive.
Info on bugchecks; bugcheck descriptions -
https://www.sysnative.com/forums/showthread.php/3285-Bugchecks-CHM
I am fairly certain that the attachment to that post came from carrona.org; however, I am unable to find the page ATM. I'm attaching a copy of the attachment to this post.
Personally, I don't like the idea of including "Usual Causes" in the dump output summary as (1) the info is one click away; (2) it may lead to confusion by the OP (seeing something different than what the BSOD Analyst is having the OP focus on; (3) if given the option, I myself would not use it
Please know, Mike, that the above are simply my suggestions and initial thoughts. You obviously know your code better than anyone. :dsmile:
Also, this is my 1st attempt at comment after reading this entire thread after a long day in Philadelphia, so apologies in advance if there are typos or other mistakes in logical flow.
