0128 Ver. Not installed oem theme pack~ 0127 Installed oem theme pack So, I used 0127 scripts & 0128 theme pack~
I even put it on the first post in big red letters and still people refuse read. lol Like my grandfather said, you can lead a horse to water but you cant make him drink. lol Quote from first post... If you don't feel comfortable posting in the main thread here then send me the Results.txt file in a pm.
Instead of using searchengines method of searching for the string, "findstr /I ". I can add this to specify only words in ini file instead..."findstr /I /C:" So for this example lets say like my bios for id-1 and id-2 says HP ENVY yada yada...it would skip those id's because the whole string isn't in the ini and default to id-4 for branding where it is listed specifically Hewlett-Packard. This might help with the conflicts. I need a test subject with issues first to see if this would work better. Just brainstorming... See, most ppl would just edit the ini or the cmd file for conflicts....this is like putting a band aid on a huge wound. I like finding more permanent solutions. Editing for findstr /I /C: would get rid of the conflict resolutions in the cmd file all together. Would be no need to edit the cmd file anymore. This is just theory but it should work better. Need a test subject before I can say yes or no on this method. Query Tool Example: Before: After:
I have Hp Compaq computer if you want to test it before the owner take it lol, Also mine Gigabyte and another one Asus and HP laptop I can give you results for each one
Please....lol If I can get Results.txt files I can edit the query tool to set those variables as yours so I can reproduce the problem myself then implement my theory to see if it works like I think it should.
You will edit id 1 only right or i must edit all of them, i changed id 1 like yours and ready to test results for Gigabyte with only id 1 changed like yours Spoiler OEM INFORMATION FOR THIS MACHINE -------------------------------- Windows 8.1 Pro 6.3.9600.17085.amd64fre.winblue_gdr.140330-1035 Bios Version - F8 [09/30/2010] SCANNED ------- #1 CSPRODUCT NAME - P55-USB3L #2 COMPUTERSYSTEM MODEL - P55-USB3L #3 BASEBOARD PRODUCT - P55-USB3L #4 CSPRODUCT VENDOR - Gigabyte Technology Co., Ltd. #5 COMPUTERSYSTEM MFR - Gigabyte Technology Co., Ltd. #6 BASEBOARD MFR - Gigabyte Technology Co., Ltd. #7 SERVICE TAG - Un-Listed #8 BIOS ID - GBT #9 SLIC OA - Un-Listed #10 INSTALLED KEY - Removed #11 MSDM TABLE [OEMM] - Un-Listed #12 BIOS MODE - LEGACY #13 CERTIFICATE - Un-Listed SUMMARY ------- USER DISPLAY [*-incl.] - 1440X900 [Un-Listed] THEME - GIGABYTE [id:-`#4'] ACTIVATION - Un-Listed VALID [OEM OS] - Un-Listed SLIC TABLE ---------- Table not found. RW Exit MSDM TABLE ---------- Table not found. RW Exit CERTIFICATE ----------- Certificate not found. Exit
I take it this machine did not have a conflict thus changing id-1 or id-2 would not have mattered. I would like to see Results.txt file from one with a conflict for that is where we shall see if my new method would work or not. In this case, the query would skip 1 and 2 anyways since nothing is similar in the ini file. See what I mean? I have plans to change id-1 and id-2 only so far for that is what is causing conflicts. Still say this would solve a lot of the conflicts found in the past. Thanks anyways. Usually id-1 and id-2 are the model of the oem computer...sometimes has manufacture but not mostly. Some have nothing but numbers, it varies. But id-1 and id-2 is what causes the conflict with searchengines method. Not putting him down by no means. I think it could be handled better is all. Let me explain further... findstr /I will look for anything similar in the ini file...lets use HP and Fuj for this example which is a good one to use. Because some model names have numbers and letters it confuses the query. Hp has a envy model with ts in the id-1 and id-2 so when the script query's for HP it sees TS which is also in FUJITSU. The ini file is in alphabetical order so Fuj. comes first so it is assigned first. See the conflict? If I add the /C: to the query of the ini file then it would be skipped and HP would then be assigned from id-4.
I tried 2 hp one computer and a laptop but two of them don't have conflicts , I have the results if you want them
Yes please just out of curiousity. I like seeing what id-1 through id-8 are. I will look back in this thread later today and see if I can reproduce some past conflicts and try new method to see how it works and what other conflicts it might bring up. I don't expect more problems but you never know. lol
Dang, you Baltagy...lol I see another conflict in the HP2 results. This will be a problem...id-1 for example say HP Compaq and the other id's are HP. Technically it should be branded by Compaq not HP...HP is a pain. I will look into this. Give me some time.
I need to rethink this new method because like you see in the above results....conflict then arises with HP/Comaq. Thanks for sharing that info brother. I will get back with you later...let me brainstorm a bit.
I added one line of code to query tool and project to handle these conflicts....seems to be working with the mentioned manufactures by white bone. Also this one line of code handles the hp/fuj. conflict as well. I'm a happy now.
First post updated with the new query tool v5.6 and the new project 01-29-2015. Change log: Spoiler Change log 01-29-2015: -Added one line of code to resolve branding conflicts in query tool v5.6 and the project.
another HP Test Spoiler Code: OEM INFORMATION FOR THIS MACHINE -------------------------------- Windows 8.1 Pro 6.3.9600.17415.amd64fre.winblue_r4.141028-1500 Bios Version - F.06 [03/01/2012] SCANNED ------- #1 CSPRODUCT NAME - HP Pavilion dv6 Notebook PC #2 COMPUTERSYSTEM MODEL - HP Pavilion dv6 Notebook PC #3 BASEBOARD PRODUCT - 181B #4 CSPRODUCT VENDOR - Hewlett-Packard #5 COMPUTERSYSTEM MFR - Hewlett-Packard #6 BASEBOARD MFR - Hewlett-Packard #7 SERVICE TAG - Removed #8 BIOS ID - HPQOEM #9 SLIC OA - v2.1 #10 INSTALLED KEY - Removed #11 MSDM TABLE [OEM:DM] - Un-Listed #12 BIOS MODE - LEGACY #13 CERTIFICATE - Un-Listed SUMMARY ------- USER DISPLAY [*-incl.] - 1366x768* THEME - HP [id:-`#1'] ACTIVATION - HP [id:-`#8'] VALID [OEM OS] - Vista/Win7 SLIC TABLE ---------- Software Licensing Description Table: 0x000000009AFE4000 53 4C 49 43 76 01 00 00 01 D9 48 50 51 4F 45 4D SLICv.....HPQOEM 53 4C 49 43 2D 4D 50 43 01 00 00 00 48 50 20 20 SLIC-MPC....HP 00 00 04 00 00 00 00 00 9C 00 00 00 06 02 00 00 ................ 00 24 00 00 52 53 41 31 00 04 00 00 01 00 01 00 .$..RSA1........ 5B AB 60 56 BC 58 1E E8 C1 D2 A1 5C E5 4F BB FD [.`V.X.....\.O.. 1D A9 8C 94 B4 AE 08 11 DC 13 59 D3 7F F6 3E 87 ..........Y...>. 31 B9 95 74 10 DA 3B A4 5B B5 19 82 7C 39 D7 0D 1..t..;.[...|9.. 7C 22 AC 1C 2A 84 E9 0A 88 6D FA B1 E2 D8 E8 21 |"..*....m.....! 96 E1 2E 68 9A BF 44 45 3E 3C 8E 99 90 DE 37 38 ...h..DE><....78 57 0B 92 15 BC DE FF F2 07 7E B5 40 8C 51 3A C3 [email protected]:. 02 48 F6 13 12 72 FB 42 78 E6 47 88 54 C7 B0 F0 .H...r.Bx.G.T... 93 9E FB 04 B7 B8 B8 90 DE DB ED 32 E1 FB 54 A6 ...........2..T. 01 00 00 00 B6 00 00 00 00 00 02 00 48 50 51 4F ............HPQO 45 4D 53 4C 49 43 2D 4D 50 43 57 49 4E 44 4F 57 EMSLIC-MPCWINDOW 53 20 01 00 02 00 00 00 00 00 00 00 00 00 00 00 S .............. 00 00 00 00 00 00 30 90 1F B4 A4 BE 80 1E E9 33 ......0........3 EC 7F FC B1 28 0E A6 CE 43 72 8C 79 30 B4 F4 59 ....(...Cr.y0..Y EA 7D CF B7 11 8B DA 70 C5 C8 3F 79 20 08 6F 64 .}.....p..?y .od CA 07 88 B3 B1 16 B4 BA 1A F1 85 52 B1 F5 07 55 ...........R...U B5 70 61 EF 44 8C AA 5F 78 14 66 98 9C F3 58 D8 .pa.D.._x.f...X. AA 48 E0 37 F8 F6 AB 64 FA DA 17 2A 62 E3 04 1D .H.7...d...*b... 32 2D D5 EA 33 66 5C 5B 3B 0E F7 09 66 42 32 AA 2-..3f\[;...fB2. 14 99 C3 EE 1A 62 3B 07 5F F0 48 44 C4 E6 32 59 .....b;._.HD..2Y 1F 14 3E F1 B2 38 ..>..8 Signature "SLIC" Length 0x00000176 (374) Revision 0x01 (1) Checksum 0xD9 (217) OEM ID "HPQOEM" OEM Table ID "SLIC-MPC" OEM Revision 0x00000001 (1) Creator ID "HP " Creator Revision 0x00040000 (262144) OEM Public Key Structure Type 0x00000000 (0) Length 0x0000009C (156) Key Type 0x06 (6) Version 0x02 (2) Reserved 0x0000 (0) Algorithm 0x00002400 (9216) Magic "RSA1" Bit Length 0x00000400 (1024) Exponent 0x00010001 (65537) Modulus 0x5B 0xAB 0x60 0x56 0xBC 0x58 0x1E 0xE8 0xC1 0xD2 0xA1 0x5C 0xE5 0x4F 0xBB 0xFD 0x1D 0xA9 0x8C 0x94 0xB4 0xAE 0x08 0x11 0xDC 0x13 0x59 0xD3 0x7F 0xF6 0x3E 0x87 0x31 0xB9 0x95 0x74 0x10 0xDA 0x3B 0xA4 0x5B 0xB5 0x19 0x82 0x7C 0x39 0xD7 0x0D 0x7C 0x22 0xAC 0x1C 0x2A 0x84 0xE9 0x0A 0x88 0x6D 0xFA 0xB1 0xE2 0xD8 0xE8 0x21 0x96 0xE1 0x2E 0x68 0x9A 0xBF 0x44 0x45 0x3E 0x3C 0x8E 0x99 0x90 0xDE 0x37 0x38 0x57 0x0B 0x92 0x15 0xBC 0xDE 0xFF 0xF2 0x07 0x7E 0xB5 0x40 0x8C 0x51 0x3A 0xC3 0x02 0x48 0xF6 0x13 0x12 0x72 0xFB 0x42 0x78 0xE6 0x47 0x88 0x54 0xC7 0xB0 0xF0 0x93 0x9E 0xFB 0x04 0xB7 0xB8 0xB8 0x90 0xDE 0xDB 0xED 0x32 0xE1 0xFB 0x54 0xA6 SLIC Marker Structure Type 0x00000001 (1) Length 0x000000B6 (182) Version 0x00020000 (131072) OEM ID "HPQOEM" OEM Table ID "SLIC-MPC" Windows Flag "WINDOWS " SLIC Ver 0x00020001 (v2.1) Reserved 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Signature 0x30 0x90 0x1F 0xB4 0xA4 0xBE 0x80 0x1E 0xE9 0x33 0xEC 0x7F 0xFC 0xB1 0x28 0x0E 0xA6 0xCE 0x43 0x72 0x8C 0x79 0x30 0xB4 0xF4 0x59 0xEA 0x7D 0xCF 0xB7 0x11 0x8B 0xDA 0x70 0xC5 0xC8 0x3F 0x79 0x20 0x08 0x6F 0x64 0xCA 0x07 0x88 0xB3 0xB1 0x16 0xB4 0xBA 0x1A 0xF1 0x85 0x52 0xB1 0xF5 0x07 0x55 0xB5 0x70 0x61 0xEF 0x44 0x8C 0xAA 0x5F 0x78 0x14 0x66 0x98 0x9C 0xF3 0x58 0xD8 0xAA 0x48 0xE0 0x37 0xF8 0xF6 0xAB 0x64 0xFA 0xDA 0x17 0x2A 0x62 0xE3 0x04 0x1D 0x32 0x2D 0xD5 0xEA 0x33 0x66 0x5C 0x5B 0x3B 0x0E 0xF7 0x09 0x66 0x42 0x32 0xAA 0x14 0x99 0xC3 0xEE 0x1A 0x62 0x3B 0x07 0x5F 0xF0 0x48 0x44 0xC4 0xE6 0x32 0x59 0x1F 0x14 0x3E 0xF1 0xB2 0x38 RW Exit MSDM TABLE ---------- Table not found. RW Exit CERTIFICATE ----------- Certificate not found. Exit