Would be nice to see if I can add additional ini for language translations in query tool. I will have to investigate that a little.
Yeah it is nice but a little tricky to implement I am finding. Seems to be working now...when I implemented new fix for oem conflict it caused an issue which I wasn't aware of. Its been addressed now.
In order to add to INFO in ini file we must first see what the query would look for...does it say AMD in query results or something else? We need to find out that info first before trying images. I don't have access to a AMD board to test on to find out the needed info for the ini file.
Sorry, had a typo that cause extraction to fail...Uploading corrected version now for project only. First post link updated...sorry about that.
@Baltagy, No need to make images for AMD because they don't make motherboards, only cpu's. Other motherboard manufactures create compatible motherboards, most of which are already included in the project.
After looking at White-Bones's Results.txt files (a lot of them)....the project installs correct themes on all but will not activate for no slic in bios thus no activation (these are custom builds). Looks as if my fix for the conflicts is working like it should also. Overall, I am happy with all the results.
Acer Test Spoiler Code: OEM INFORMATION FOR THIS MACHINE -------------------------------- Windows 7 Professional 6.1.7600.16399.amd64fre.win7_gdr.090722-1835 Bios Version - V1.20 [03/11/2009] SCANNED ------- #1 CSPRODUCT NAME - ASPIRE 4730Z #2 COMPUTERSYSTEM MODEL - ASPIRE 4730Z #3 BASEBOARD PRODUCT - ASPIRE 4730Z #4 CSPRODUCT VENDOR - acer #5 COMPUTERSYSTEM MFR - acer #6 BASEBOARD MFR - Acer #7 SERVICE TAG - LXAT90X0248391B0EC1601 #8 BIOS ID - ACRSYS #9 SLIC OA - v2.0 #10 INSTALLED KEY - Removed #11 MSDM TABLE [OEM:DM] - Un-Listed #12 BIOS MODE - LEGACY #13 CERTIFICATE - Un-Listed SUMMARY ------- USER DISPLAY [*-incl.] - 1280X800 [Un-Listed] THEME - ACER [id:-`#4'] ACTIVATION - ACER [id:-`#8'] VALID [OEM OS] - Vista SLIC TABLE ---------- Software Licensing Description Table: 0x000000007BAF8000 53 4C 49 43 76 01 00 00 01 00 41 43 52 53 59 53 SLICv.....ACRSYS 41 43 52 50 52 44 43 54 01 00 00 00 31 30 32 35 ACRPRDCT....1025 13 00 00 01 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........ 1D A3 8F F3 A1 9D F1 F2 31 B4 B5 17 6C CE 4D 17 ........1...l.M. 64 6A F9 79 29 50 CE 0A B2 13 70 71 6E 28 AD DB dj.y)P....pqn(.. 55 1C A6 23 3E 0C 8A 4F 02 49 C9 DF 6D AB CB E7 U..#>..O.I..m... C0 2C 18 7D 43 5C 45 82 3D FC 32 B0 92 F8 C2 00 .,.}C\E.=.2..... 65 0D B9 A0 CD 16 EA 40 13 CE 9D 3B 39 ED 87 34 e......@...;9..4 98 C4 D9 C7 98 49 11 77 03 D4 A7 6A D6 3B 88 71 .....I.w...j.;.q DB 1A D3 AA 56 42 2E AD 32 91 29 59 9D 4D 27 AD ....VB..2.)Y.M'. 95 DF 53 90 83 82 21 52 92 2F 9D 33 EF CB C3 AE ..S...!R./.3.... 01 00 00 00 B6 00 00 00 00 00 02 00 41 43 52 53 ............ACRS 59 53 41 43 52 50 52 44 43 54 57 49 4E 44 4F 57 YSACRPRDCTWINDOW 53 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 S .............. 00 00 00 00 00 00 A0 34 06 3A FD 7B 4C BA 3F 2D .......4.:.{L.?- FB FF 1F F5 78 A8 DA 2E 38 D6 CA 84 DF A1 4C DB ....x...8.....L. F6 33 22 90 0E BA 42 B9 A1 D1 43 10 54 79 F0 3D .3"...B...C.Ty.= 22 41 86 F3 D9 1D 5D 29 59 92 95 CD E6 C0 E5 2F "A....])Y....../ 1D 32 C9 49 98 CB 30 F9 E8 E3 D9 0E 29 BB 3A AD .2.I..0.....).:. CA 3D FC 1E 84 C4 25 A6 8E 52 8C 9D EB 70 2F 63 .=....%..R...p/c 53 34 97 6C 6E 19 59 26 E0 32 9F A5 22 B1 2E EF S4.ln.Y&.2.."... 1B 45 E8 CC 8A E5 E3 01 97 B2 7B BF 56 F8 E9 B4 .E........{.V... CD 35 EC 01 63 18 .5..c. Signature "SLIC" Length 0x00000176 (374) Revision 0x01 (1) Checksum 0x00 (0) OEM ID "ACRSYS" OEM Table ID "ACRPRDCT" OEM Revision 0x00000001 (1) Creator ID "1025" Creator Revision 0x01000013 (16777235) 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 0x1D 0xA3 0x8F 0xF3 0xA1 0x9D 0xF1 0xF2 0x31 0xB4 0xB5 0x17 0x6C 0xCE 0x4D 0x17 0x64 0x6A 0xF9 0x79 0x29 0x50 0xCE 0x0A 0xB2 0x13 0x70 0x71 0x6E 0x28 0xAD 0xDB 0x55 0x1C 0xA6 0x23 0x3E 0x0C 0x8A 0x4F 0x02 0x49 0xC9 0xDF 0x6D 0xAB 0xCB 0xE7 0xC0 0x2C 0x18 0x7D 0x43 0x5C 0x45 0x82 0x3D 0xFC 0x32 0xB0 0x92 0xF8 0xC2 0x00 0x65 0x0D 0xB9 0xA0 0xCD 0x16 0xEA 0x40 0x13 0xCE 0x9D 0x3B 0x39 0xED 0x87 0x34 0x98 0xC4 0xD9 0xC7 0x98 0x49 0x11 0x77 0x03 0xD4 0xA7 0x6A 0xD6 0x3B 0x88 0x71 0xDB 0x1A 0xD3 0xAA 0x56 0x42 0x2E 0xAD 0x32 0x91 0x29 0x59 0x9D 0x4D 0x27 0xAD 0x95 0xDF 0x53 0x90 0x83 0x82 0x21 0x52 0x92 0x2F 0x9D 0x33 0xEF 0xCB 0xC3 0xAE SLIC Marker Structure Type 0x00000001 (1) Length 0x000000B6 (182) Version 0x00020000 (131072) OEM ID "ACRSYS" OEM Table ID "ACRPRDCT" Windows Flag "WINDOWS " SLIC Ver 0x00000000 (v2.0) Reserved 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Signature 0xA0 0x34 0x06 0x3A 0xFD 0x7B 0x4C 0xBA 0x3F 0x2D 0xFB 0xFF 0x1F 0xF5 0x78 0xA8 0xDA 0x2E 0x38 0xD6 0xCA 0x84 0xDF 0xA1 0x4C 0xDB 0xF6 0x33 0x22 0x90 0x0E 0xBA 0x42 0xB9 0xA1 0xD1 0x43 0x10 0x54 0x79 0xF0 0x3D 0x22 0x41 0x86 0xF3 0xD9 0x1D 0x5D 0x29 0x59 0x92 0x95 0xCD 0xE6 0xC0 0xE5 0x2F 0x1D 0x32 0xC9 0x49 0x98 0xCB 0x30 0xF9 0xE8 0xE3 0xD9 0x0E 0x29 0xBB 0x3A 0xAD 0xCA 0x3D 0xFC 0x1E 0x84 0xC4 0x25 0xA6 0x8E 0x52 0x8C 0x9D 0xEB 0x70 0x2F 0x63 0x53 0x34 0x97 0x6C 0x6E 0x19 0x59 0x26 0xE0 0x32 0x9F 0xA5 0x22 0xB1 0x2E 0xEF 0x1B 0x45 0xE8 0xCC 0x8A 0xE5 0xE3 0x01 0x97 0xB2 0x7B 0xBF 0x56 0xF8 0xE9 0xB4 0xCD 0x35 0xEC 0x01 0x63 0x18 RW Exit MSDM TABLE ---------- Table not found. RW Exit CERTIFICATE ----------- Certificate not found. Exit
This project does not support Server editions because you can not oem brand them. This is a known limitation per M$ site thus the reason I do not support it. I have tried in the past without success (wallpapers and themes).
Actually the guardian I have been OEM branding Server copies. You can actually do it. I can give you the scripting involved if you wish to pull it off. I have incorporated into my oem pack the ability to turn on the desktop experience for Server 2008 R2 - Server 2016.
something like this... I don't know if this would be good for businesses though...they like servers to look like servers. Plus allows desktop users the environment they are use to which raises security risks. Servers are meant for IT Admins only not for common users thus I say no to this. Plus IT ppl should setup their servers to fit their business needs. I really don't want to touch the servers personally. To be honest IT personnel should be able to make their own custom install if needed...they get paid the bucks for it. lol If they cant do it then they need to be fired or go back to college, if not both.
First we need to enable the desktop experience on server to make themes possible. Code: dism /online /Enable-Feature /FeatureName:DesktopExperience /NoRestart Then we have to turn on the themes service by doing a registry modification. This will start the themes service after the setupcomplete.cmd phase. Code: reg add "HKLM\System\CurrentControlSet\Services\Themes" /v "Start" /t "REG_DWORD" /d "2" /f This will mean on boot up the themes feature will start along with the themes service which leaves us able to do OEM Branding. I converted this from the powershell way I do things . Keep in mind you will need to run an edition check.
Actually there is an entire forum dedicated to Server conversion to Workstation. My desktop has a copy of Server 2012 R2 on it that has been converted in such a way. It's not my decision to make as I just wanted to show how it could be done.
I know if I ran a company I would not want that enabled personally because it is too familiar to end users thus easier for them tamper with it. This is a security risk that I see and I will not support it for this project. I have never seen a server with desktop environment turned on yet myself thus why I say I don't want to tamper with server iso's. Thanks for sharing the info but I choose not to go that direction for security reasons. Let businesses that use servers handle their own.