UUPMediaCreator icon indicating copy to clipboard operation
UUPMediaCreator copied to clipboard

UUPDownload: please provide a way to select HWID

Open lumag opened this issue 1 year ago • 6 comments

Please provide a way to select the HWID type used for GUID generation. Some devices (e.g. X13s) use HWID other than the current default (4, Manufacturer + Family + Product + SKU).

lumag avatar Sep 02 '24 07:09 lumag

What other types have the oem chosen to use here? I'm curious as I know each oem can chose what they want in mission control but I hardly saw any other combo.

gus33000 avatar Sep 03 '24 07:09 gus33000

X13s uses HWID-11 (just Manufacturer + Family, unless I'm mistaken). And I'm not sure what T14s uses. I wasn't able to get drivers for it by using data from https://github.com/TravMurav/dtbloader/blob/main/scripts/hwids/x1e78100-lenovo-thinkpad-t14s.txt . I found that YogaSlim7x requires build 10.0.26100.1591. Maybe T14s also requires some other build.

Probably I should specify the reason for my questions/requests/issues: I'm using WoA cabinets to create machine-specific firmware packages for Linux installations.

lumag avatar Sep 03 '24 09:09 lumag

Update: T14s also uses non-typical GUID, it is HWID-7, Manufacturer + ProductSky

lumag avatar Sep 06 '24 02:09 lumag

Update: T14s also uses non-typical GUID, it is HWID-7, Manufacturer + ProductSky

Ok interesting, im not sure where you are getting this HWID-X naming by the way, im not familiar with it at least (is this standard?) I created a branch and an initial PR to lay the ground work to a proper tool with a list of current thought through features to enable this outside of specific or PoC use cases.

gus33000 avatar Sep 06 '24 16:09 gus33000

https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/using-chids

lumag avatar Sep 06 '24 16:09 lumag

Ok interesting never seen that documentation before but i was familiar with the computerhardwareids.exe tool in itself.

Also quite funny to see the documentation indexes from 0, while the tool indexes hardwareIdsX starting from 1. That explains the discrepency I had

gus33000 avatar Sep 07 '24 14:09 gus33000