don't understand your post. Doesn't sound like native speaker. I'm neither. As you clarify, I assume direct improvement proposals may result. That's why I reply in the form of a reply-post.
necros wrote: ↑
Fri Jan 15, 2016 3:27 am
do you update your db with direct official software`s sites new version info, or just users submitted data
Indeed I can't find much documentation for the working of DUMo. The software provides a hint that it seems working similarly as SUMo by the button to each other as does the similarity in naming. Although also limited there exists significantly more documentation on SUMo. Accordingly Kyle already answered the latter. And his reply has different meanings.
In contrast to SUMo, I've just seen a few manual user reports for fixing missing or false updates. Nevertheless obviously not all claims of available updates reported by DUMo are correct. It's worth investigating. I already found and reported two reasons accepted into a feature request (not yet implemented) and I'm sure there are more reasons. The standard means for updating the database is not user intervention but the data sent by the local DUMo to the database server when querying if an update exists for that driver detected locally for that operating system. That's also user data but not data the user enters or sends. It's data that the locally running DUMo software automatically sends as long as there are no network problems resp. limitations.
What do you mean by "direct official software's sites new version info"?
Which of these words refers to which other?
Obviously, DUMo uses the software version info of a locally detected driver if there exists one. DUMo usually assumes local drivers as official. Usually a version info of a driver doesn't change without a change of the driver. So an unmodified driver usually doesn't alter its version info and hence there does not exist a new version info for the same driver. An update of that driver results into a new driver with usually a new version info. Do you refer to this change due to local update usually either via Windows Update or by OEM update service?
To which word do you refer in your expression by direct?
What do you mean by official and to does this word relate to any resp. which other word in your expression?
I consider a release declaration and decision by the device manufacturer as official for a given driver. But not always does the device manufacturer also develop or publish one or several drivers for its devices. And sometimes you'll find a community of open source developers developing and releasing drivers as well as original equipment manufacturers (OEM) for the same device with their own official release process, decision and declaration. That's not less official. And the OEM may decide to certify every driver version, some driver versions or no driver versions for one or several Windows operating systems by Microsoft (WHQL certification). Which of these driver versions do you consider official?
The business reality for drivers is even more complicated. I'm writing these lines on a computer with an Intel CPU with integrated graphics GPU and NO dedicated GPU in addition on the main board. It is
- Windows Update service,
- (large computer manufacturer) system integrator OEM support assistant service,
- device OEM (in this case Intel) driver and support assistant service, and
- DUMo service and
- another commercial driver update tool
checking for available updates for this integrated Intel GPU on the Intel CPU. Often they differ in their results on the integrated Intel GPU. Which report and claim do you consider official?
Which report and claim do you consider direct?
And to which version info of the installed and the claimed available driver for that integrated Intel GPU do you refer?
I tell you what each of them consider:
Windows Update service claims the installed driver Intel GPU driver up to date. It does not mention that there exist more recent Intel GPU official drivers for this CPU/GPU combination. The same applies for the computer manufacturer which integrated the system and its support assistant service. The Intel driver and support assistant also claims it up to date and doesn't report available driver updates released by Intel at the standard reporting level. When one year old versions of Intel driver and support assistant were actual, they reported differently even at this level, mentioning the released update by Intel and nevertheless refusing to update and even warning against update with the officially released driver by Intel! The current version of Intel driver and support assistant still has the same information, hidden more deeply. This assistant reports installed and available driver version. If you query this information in that report of this assistant, it provides further details, providing the same information as the former assistant version that there exists an officially released driver update by Intel and warns against updating because the driver installed is detected by the assistant as officially adapted by the original system integrator. This adaptation may be for performance reasons, thermal reasons, power reasons or other. That's one of the reasons why notebooks with same CPU, chipset and several other common components still differ widely in their power consumption. Then Intel driver and support assistant allows even query of further information on this device (GPU). This opens a deep link onto the corresponding release announcement with available update, release information, system requirements, variations and so on for this GPU as well as references to different driver versions and their release informations. DUMo and the other commercial driver update tool both report the available update without providing the warning that Intel as OEM provides. All four are right, all relying on official information. In the past I experience that this large system integrator doesn't seem to provide any updates anymore after two years for another device of the consumer product line and still provides updates for this business line product, taking between two and nine months after Intel releases its driver update. The last update by the system integrator for the GPU was in the last quarter of last year. So all support tools were in sync with up to date for 6-8 weeks. Since, Intel released two further updates while the system integrator did not yet. And concerning the version information, I found it difficult to relate installed version to reported version information as even Intel support assistant uses seamingly different version informations due to device dependency in its product family and release policy. You'll find an explanation in a corresponding SUMo forum post by another user with deeper knowledge of this relationship for Intel driver version and version reporting.
Reality is not quite as simple as the case of Intel above. On the same notebook there are devices onboard where the large device manufacturers claim not to release drivers as they do not do system integration. They claim instead that it's the task of the system integrators to release drivers and that the device manufacturer provide device details, support packages and development kits to these system integrators. For some of them, DUMo reports available updates. I don't have the DUMo Pro. But probably for some of these manufacturers even DUMo Pro provides either a Google search query or a link to the manufacturer home page, not a deep link into the manufacturers support section of its site. Knowing the variety of similar devices of the manufacturer, I probably don't want to update such drivers as long as not provided by the system integrator. So even in DUMo Pro I wouldn't want DUMo to automatically update the corresponding driver. DUMo Pro provides a corresponding configuration option. DUMo and the other commercial driver update tool don't. DUMo let's me execute the Google query without doing any harm and the other tool would automatically update the driver in the professional version of that tool. I've their professional version of the tool on one device, the basic one on another device. I contacted their support with their promise of 24 hour unto a support reaction. But it's now more than 10 days without any reaction. And they have a larger user base and larger driver database than DUMo. So market share does not relate to quality. DUMo detect much less drivers than Windows and than this other commercial driver update tool. But DUMo let's me decide what to do with the report results and doesn't force me into the danger of broken system. And Windows doesn't provide such information nor configuration option and is also more careful on updates than this other commercial driver update tool.
So what's the meaning of "site" in your expression above, especially in such cases where such manufacturers don't distribute to consumers but to system integrators only instead?
According to my understanding software including driver can and should carry version information. And I see that this version information does not necessarily differ between device OEM and system integrator OEM even if the latter is an adapted one based on the former one. So how does DUMo handle such a situation and how should it?
I didn't check what how Intel driver and support assistant detected the adaptation by the system integrator. I can only guess that the driver carries the same version info but with digital signature by the authorized system integrator instead of device manufacturer or unauthorized third party.
And I don't see any version information on device manufactures web sites. When I see version information then it is inside software including drivers and can be queried by the operating system and its management tools. For several device manufacturers I see release announcements for drivers often including a subset of the version information in the driver, but including other information like device dependency, operating system dependency and other requirements. Even if a web site has its own version information, this is not directly related to these driver release announcements nor to the driver version information.
necros wrote: ↑
Fri Jan 15, 2016 3:27 am
do you update your db with direct official software`s sites new version info, or just users submitted data, if not sumo would be more up to date informer if such auto scripts which check sites will be implemented.
To what kind of auto scripts do you refer?
I don't know such things neither in DUMo nor SUMo.
A consequence of the above described variety of drivers, I don't see a generic method for improving DUMo detection and reporting in a uniform manner. Only for a subset of drivers, it seems possible to do so.
- Does DUMo or DUMo database server check its findings with Microsoft WHQL certification before deciding or handling on database updates?
- What's the relation of considering drivers in beta state if some versions for a given device are WHQL certified while other driver versions are not, even if such checks with WHQL are implemented?