[ACTIVE] Output drivers not found on carrona.org DRT

jcgriff2

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)
Staff member
Joined
Feb 19, 2012
Posts
21,541
Location
New Jersey Shore

​
After seeing THIS POST (scroll about 1/2-way down), I saw the DRT area as listed below in its usual fashion:

Read More:
Granted that list is unusual in its size (the number of drivers not found in the DRT); my attention was drawn to it because in all honesty it is difficult to discern due to the many missing DRT drivers.

I did a little editing with TextPad adding FONT, COLOR, SIZE (size=1, which I believe to be the default in code boxes).

I thought for readability's sake that the missing DRT driver lines may be easier to discern if greyed out (hex color = #777777) with driver name itself colored differently (hex color #4b0082 - or other).

I am not sure if this is done in the template that Mike designed or in Mike's BSOD Processing app itself.

This is what I came up with during a quick edit of Carrona's post:
Read More:

https://www.sysnative.com/forums/bs...keeps-occuring-my-asus-vivotab.html#post45857

Just a thought.

Thanks,

John
 
Thanks John. I'll look into adding that to 2.15.2 for release this weekend. Let me know if different coloring would be better. I think it looks good myself, but other input is appreciated in regards to colors to use.
 
I have a further suggestion, for the apps in particular, and of which I might also add to my list of TODO's. What about a feature implementation that allows users to decide whether they want to submit the name of drivers that don't exist in the DRT to the people that manage the DRT modifications?

For example, kind of like the "Send error to Microsoft" dialogs you see when an application crashes.

edit: And actually lol! That is another good idea in itself for the development and bugfixes of an application if this could be implemented too. That would be up to writhziden however. :)
 
writhziden said:
Thanks John. I'll look into adding that to 2.15.2 for release this weekend. Let me know if different coloring would be better. I think it looks good myself, but other input is appreciated in regards to colors to use.
Click to expand...

Agree 100% on color choices.

Mine are not the best, although I do prefer light grey for most areas, e.g. hex #777777, #888888, #999999 - or similar.

AceInfinity said:
I have a further suggestion, for the apps in particular, and of which I might also add to my list of TODO's. What about a feature implementation that allows users to decide whether they want to submit the name of drivers that don't exist in the DRT to the people that manage the DRT modifications?

For example, kind of like the "Send error to Microsoft" dialogs you see when an application crashes.

edit: And actually lol! That is another good idea in itself for the development and bugfixes of an application if this could be implemented too. That would be up to writhziden however. :)
Click to expand...

We do have the 95 bulk upload file that I implemented in the original batch/VBS scripts & Mike coded his app to output a similar file that can be uploaded directly to carrona.org DRT -- but only by Carrona site Admins.
 
The problem with letting folks upload drivers was encountered with the original HTML version.
The people involved would upload incomplete data leaving it to the site admin's to double check/correct/complete their submissions.
There were so many submissions that we couldn't keep up with them (and only from a few people) - and I actually had to tell one person that we didn't want anything from them anymore. :(
 
usasma said:
The problem with letting folks upload drivers was encountered with the original HTML version.
The people involved would upload incomplete data leaving it to the site admin's to double check/correct/complete their submissions.
There were so many submissions that we couldn't keep up with them (and only from a few people) - and I actually had to tell one person that we didn't want anything from them anymore. :(
Click to expand...

That's the problem though, you need it automated, doing things manually in the web world won't get you anywhere. Perhaps a php script that would be given the names of drivers, and if not in the DRT, would be sent to a queue which is moderated by the people who update the DRT to check that the drivers being submitted are valid or not. Then just having a list that you would go through, and check off along the way, to be submitted for automatically adding to the official DRT.

That's the way I would probably do it.
 
Ace,

From my perspective this is the issue. By bulk uploading drivers, even to a TempDB, you still need manual work to find all the update links and add a description etc.. The bulk upload puts the names in, but the majority of the work is done manually by DRT Admins such as Carrona and John. Finding URLs and adding descriptions takes time.

I would love a bulk upload feature, but I don't think it's even feasible with the amount of work needed to find links etc.
 
Tekno Venus said:
Ace,

From my perspective this is the issue. By bulk uploading drivers, even to a TempDB, you still need manual work to find all the update links and add a description etc.. The bulk upload puts the names in, but the majority of the work is done manually by DRT Admins such as Carrona and John. Finding URLs and adding descriptions takes time.

I would love a bulk upload feature, but I don't think it's even feasible with the amount of work needed to find links etc.
Click to expand...

That's not related to the point I was after though at all. There is always going to be manual work done no matter what you try to automate... Automating the process of not allowing duplicates to be reviewed by the DRT managers however both in the queue for pending additions, and drivers that already exist in the DRT, will save a lot of time though, in relation to the amount of manual work that needs to be done. Just like converting the table over to PHP saved time from having to manually add entries by the HTML, and that in itself came with lots of benefits too perhaps; being able to search for drivers, maybe even sort if you wanted, among many other things.
 
Last edited:
I have completed this for 2.15.3, and I am currently implementing it in 2.7.2.1 for the secondary release. It should be available tomorrow night or Tuesday night as time permits through work and school.
 
Last edited:
Just a quick comment. I wasn't all that enthused about this little change when it was discussed.
But now that I see it in action- WOW!!!
It makes reading the list of drivers much, much easier!

Thanks John!
 
This is what I was referring to:
jcgriff2 said:

​
After seeing THIS POST (scroll about 1/2-way down), I saw the DRT area as listed below in its usual fashion:

Read More:
Granted that list is unusual in its size (the number of drivers not found in the DRT); my attention was drawn to it because in all honesty it is difficult to discern due to the many missing DRT drivers.

I did a little editing with TextPad adding FONT, COLOR, SIZE (size=1, which I believe to be the default in code boxes).

I thought for readability's sake that the missing DRT driver lines may be easier to discern if greyed out (hex color = #777777) with driver name itself colored differently (hex color #4b0082 - or other).

I am not sure if this is done in the template that Mike designed or in Mike's BSOD Processing app itself.

This is what I came up with during a quick edit of Carrona's post:
Read More:

https://www.sysnative.com/forums/bs...keeps-occuring-my-asus-vivotab.html#post45857

Just a thought.

Thanks,

John
Click to expand...
Example of new changes in the post here: https://www.sysnative.com/forums/bs...06-windows-8-blue-screen-death.html#post47375
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top