If the QT report has the wording of Aorus and OMEN within, then i should be able to add them to the database. If not then the only way would be to use the Custom method as mentioned above. As it late here (almost midnight) and a busy day tomorrow daytime i will take a more in depth look at your brand folder when i get time and check that all are within the limitations of the Windows theme system.
Thankyou Mate, and here is files that you requested Plus I changed the wallpaper to OEM And i hope you will like those wallpapers as well, and let me know if you need help in updating the logos or wallpapers, i will be happy to volunteer, And thankyou once again for helping me, i really appreciate your help and time. Thankyou very very much
Nice it looks like Aorus can be checked via DMI - makes things a bit easier Will have a play tomorrow when i get time and do a test install on a VM with the DMI information cloned to it to make it think it's Aorus... I'm quietly confident it will work.
Thank you very much i am glad i could help, and i will post HP Omen series files tomorrow, if you dont mind, And thankyou very very much
I will do my best, it may take a bit of extra code as there is a word before the Aorus one... But i will see if i can find a way around that.... I can usually. Using a debug QT i use for testing with a tweak to the database... Code: SCANNED ======= #01 CSPRODUCT NAME - Z370 AORUS Gaming 3 #02 COMPUTERSYSTEM MODEL - Z370 AORUS Gaming 3 #03 BASEBOARD PRODUCT - Z370 AORUS Gaming 3 #04 CSPRODUCT VENDOR - Gigabyte Technology Co., Ltd. #05 COMPUTERSYSTEM MFR - Gigabyte Technology Co., Ltd. #06 BASEBOARD MFR - Gigabyte Technology Co., Ltd. #07 SERIAL/SERV TAG - 454545 #08 BIOS ID - ALASKA #09 SLIC OA - v2.1 #10 INSTALLED KEY - =====================-3V66T #11 MSDM KEY - Un-Listed #12 BIOS MODE - LEGACY #13 CERTIFICATE - Un-Listed #08 BIOS or SLIC ID - ALASKA - 128880 #14 License Status - Non Genuine Grace {0x12345678} SUMMARY ======= THEME - Aorus [id:-'#01'] ACTIVATION - Un-listed VALID [OEM OS] - Vista/Win7 Only ... Looks possible..
see debug test result above it detected the brand... had to do a debug test before i went bed or i not sleep lol. As MRP uses almost the same detection routine it should be quite easy to add that brand... OMEN hopefully be same , will see.
Here is Querry Tool Report for OMEN Series by HP I will be uploading the project soon, i have acquired the original OEM Wallpaper and theme from OMEN laptop. Cheers
OMEN debug test... Code: SCANNED ======= #01 CSPRODUCT NAME - OMEN by HP Laptop 15-ce0xx #02 COMPUTERSYSTEM MODEL - OMEN by HP Laptop 15-ce0xx #03 BASEBOARD PRODUCT - 838F #04 CSPRODUCT VENDOR - HP #05 COMPUTERSYSTEM MFR - HP #06 BASEBOARD MFR - HP #07 SERIAL/SERV TAG - Debug Test #08 BIOS ID - HPQOEM - #09 SLIC OA - v2.1 #10 INSTALLED KEY - Debug Test Not Shown/Used #11 MSDM KEY - Debug Test #12 BIOS MODE - Debug Test #13 CERTIFICATE - Un-Listed #08 BIOS or SLIC ID - HPQOEM - #14 License Status - Non Genuine Grace {0xtestinfo} SUMMARY ======= THEME - Omen [id:-'#01'] ACTIVATION - HP [id:-'#08'] VALID [OEM OS] - Vista/Win7 Only
@l30, I will do a special Qtool for you to test if that ok on the two systems. Will convo/pm you a link once i get it compiled. If that works as intended then i can then put together MRP to detect them too. (fingers crossed)
Sure I am up for it, PM me and I will post the results and can you tell me on how can I safely Extract OEM branding files from HP OMEN laptop, I mean from recovery drive, I was thinking to extract via 7zip
navigate to C:\Windows\System32\Oobe\Info hopefully most of the data is stored there, like wallpapers, logo's etc. the oobe.xml wont be but that can be created manually once the filenames are known. The recovery bit may be wim/swm type files that can be opened by 7zip (wim does). But it may not be needed if the info folder has most of them.
Have added Aorus and Omen to the Config-Creator v2.9 brands listing. Also added the names into the MRP database and code base, plus added the Aorus brand folder. Just awaiting the files for Omen to be added into a brand folder as Aorus brand is now in the OEM's.7z file ready. These two brands wont be available to activate via SLIC for win7 but they will just be able to brand and the MSDM or HWID will activate as normal for w10 editions they are for. Correction, i believe the Aorus would use the cert/key/slic (if one was present) for Gigabyte and the OMEN would use the HP Cert/key/SLIC for HPQOEM etc for win7. But by the looks of the QT reports they are for Win10 so that not matter, branding should take place. I have added all the Aorus Wallpapers from your files so you could create a slideshow for desktop backgrounds. MRP will detect more than one wallpaper and automatically create the Backgrounds folder with named backgrounds (up to 10) for that purpose.
Thanks for the test QT reports, all working even the conflict resolution routine made sure they got the right names for the branding.
Here are the OMEN Branding Files, and i didn't knew about that logo thingy let me fix it and i will reupload it xD
I'll do a test install for Omen a bit later as need a break from that noisy test pc lol. Will add the Brand folder into OEM's.7z ready for testing. Logo's can look ok in the editor but when used in Windows installation they can look odd. Its because it uses a transparent background for the .png image file. I think it's the MCE logo one.
Updated the OEM's.7z with the new Aorus brand and added the OMEN one in as well. Will install test a bit later with test pc's DMI edited with the Omen data., it should work ok as Aorus did.