Yeah ... only hinted on a way to copy as much files as needed/wanted/wished to any location with only one line . EDIT: WILDCARDS = FTW (For The Win) !!!
For Windows 8.1 (single-index/multi-index aka AIO) Now I think it's time for Win8.1 (as a separate solution, i.e. different boottask script from Win7), however I want to state some points before we commence to get hands dirty: 1. AFAIK on OEM editions and tested/confirmed by me on SKU CoreSingleLanguage a gVLK set/integrated into wim index is needed for an $OEM$ folder to be fired up by setup during installation, otherwise if a generic install key is used $OEM$ folder is ignored, yet a generic install key is preferred to preserve OEM original activation doing the method Tito already posted. 2. As I need inserted gVLKs to make OEM editions to read and run $OEM$ folders activation then cerberus' script won't fit to my needs, again. Just need the OEM Branding part of his script. I guess, and here comes the tricky part, we can use your OA.3.0.activate.cmd file with some tweaks to uninstall gVLK and then set OEMM key to activate online.
Hmmm ... let me summarize a bit: We should start with the beginning and properly implement the OEM Branding. There are still the Key and Cert install for Win 7 and the OA 3.0 activation parts present. First should be cutted off and second separated to an own InstallChoice. CLEANUP isn't working. In the test i saw on your machine, the Scripts folder was still present. I would suggest to use one script for all purposes, since it's easier to maintain. We only need to add a version check (6.1/6.2/6.3 ... 10.0) to assure each system is handled properly. I.e. not offer Loader on Win 8 and later . Normally there's no need to uninstall a key (it's more cosmetic), simply install UEFI/BIOS key and system will activate automatically at first net contact ... even no need for an activation command. Since you have still contact to cerberus i would suggest to ask him, as he knows best and hopefully won't refuse to help . EDIT: Show him the script, he should notice the credits ... :
If you mean on Windows 7, cerberus' script is working fine, stills installing oem branding AND oem activation (didn't know about the latter until yesterday when I serviced a Compaq Presario lappy)
Don't matter mate, I think is fine for many users, it just suits them good. We need to put hands on Windows 8.1, no?
Tell me what the script should do, then we all laugh for a moment and check what will actually work afterwards . Just added last little changes/additions to Powershell Update Module ...: Spoiler Code: ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ PS WU MODULE SPECIFIC UPDATE CHECK ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ KB Number(s)____: 'KBXXXXXX1' or 'KBXXXXXX1, KBXXXXXX2, KBXXXXXX3, KBXXXXXX4' ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ Set Update ID >KB2911106, KB2898785, KB2904440 ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ 05.02.2014 at 22:12:45 KB2911106 Update für Windows 8.1 für x64-Sy... 05.02.2014 at 22:07:03 KB2898785 Kumulatives Sicherheitsupdate für... 05.02.2014 at 22:07:20 KB2904440 Update für Windows 8.1 für x64-Sy... ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ Drücken Sie eine beliebige Taste . . .
1. If OEMM UEFI detected then Choice 1: Install OEM Branding? When installing OEM Branding hopefully it will OEM activates too. 2. If not OEMM UEFI detected then Choice 2: Activate with KMS Server? That's it.
OK that should be easy . Iirc the OEM part installs OEM_SLP Cert and Key for Win 7 and OEM_DM Key for Win 8/8.1 . I 'stole' the nice RWEverything console part from cerberus script and adapted the Powershell FaiKee posted, as already publicily commited. BTW: Would it be an idea to let the BIOS/UEFI tables decide what to start with? Test: SLIC presence on Win 7 systems MSDM presence on Win 8/8.1 Then decide whether to use OEM Branding or KMS, no need for a choice for Retail systems.
I would need a SLIC 2.1 BIOS for VM. MDL afaik only offers packages too big i can download with my connection, would be cool if you (or anybody else) could share a single ROM file. Need to check out how to use the commandline syntax for RWEverything to read the SLIC table, similiar to the MSDM part . Cerberus scripts uses kilometers of code to determine the OEM data on Win 7 systems ... there must be an easier way. OK have the BIOS ... testing ... stay tuned.
As expected SLIC dump gives all needed info: Code: "%~dp0Rw.exe" /Min /NoLogo /command="ACPI Dump SLIC";"RwExit" /logfile="%~dp0slic.log" Code: Software Licensing Description Table: 0x000000003FEFECFD 53 4C 49 43 76 01 00 00 01 37 41 43 52 53 59 53 SLICv....7ACRSYS 41 43 52 50 52 44 43 54 00 00 04 06 44 45 4C 4C ACRPRDCT....DELL 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........ B3 6D 83 60 8D 83 65 6E E6 4B A7 6F 38 04 31 C1 .m.`..en.K.o8.1. E2 45 BF 34 66 1F 17 91 7F 5C 15 12 B7 01 4D 57 .E.4f....\....MW 6D 8E AE 6B E4 CC F8 A0 E1 BB 79 FF 08 53 E3 77 m..k......y..S.w E7 D4 70 5E 5C EF 6F 81 DD 1B 5F 30 E2 99 9B B9 ..p^\.o..._0.... D0 93 46 AB D8 17 7A E0 F0 A7 4C 32 D4 91 86 BA ..F...z...L2.... A1 6C A2 3C 73 CF 86 2D 95 9A 06 50 F3 F7 7E 06 .l.<s..-...P..~. 5B 5E 27 66 01 3A 31 9F 0C B1 91 96 49 5C CC 81 [^'f.:1.....I\.. BA 77 32 52 B2 10 5D 5B CA DE 9D 25 90 95 F7 97 .w2R..][...%.... 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 01 00 02 00 00 00 00 00 00 00 00 00 00 00 S .............. 00 00 00 00 00 00 49 90 AC 34 3B 98 88 52 62 2C ......I..4;..Rb, FB 25 A8 A9 A0 7D 2D 12 70 EE D5 9A 7C CF 0C 83 .%...}-.p...|... B4 29 1B 55 3B 88 A5 F7 E6 29 A9 2C E7 17 5D 7A .).U;....).,..]z EE 38 4D 27 E0 A9 69 7C FC 20 4A 68 0B 5D 83 AD .8M'..i|. Jh.].. E5 D6 6E 49 C1 66 28 E4 D4 CE 72 64 A1 7C BE 93 ..nI.f(...rd.|.. AD 64 32 DA CC 72 24 47 FE B4 97 87 01 55 A0 5D .d2..r$G.....U.] 2F EF 06 93 E8 87 84 59 D3 9B 25 53 27 E7 CA 75 /......Y..%S'..u 65 CF 0E 40 C9 3B AA 03 F2 83 7E 27 E7 CA 47 A4 e..@.;....~'..G. 4B 1F C5 77 DF 8C K..w.. Signature "SLIC" Length 0x00000176 (374) Revision 0x01 (1) Checksum 0x37 (55) OEM ID "ACRSYS" OEM Table ID "ACRPRDCT" OEM Revision 0x06040000 (100925440) Creator ID "DELL" 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 0xB3 0x6D 0x83 0x60 0x8D 0x83 0x65 0x6E 0xE6 0x4B 0xA7 0x6F 0x38 0x04 0x31 0xC1 0xE2 0x45 0xBF 0x34 0x66 0x1F 0x17 0x91 0x7F 0x5C 0x15 0x12 0xB7 0x01 0x4D 0x57 0x6D 0x8E 0xAE 0x6B 0xE4 0xCC 0xF8 0xA0 0xE1 0xBB 0x79 0xFF 0x08 0x53 0xE3 0x77 0xE7 0xD4 0x70 0x5E 0x5C 0xEF 0x6F 0x81 0xDD 0x1B 0x5F 0x30 0xE2 0x99 0x9B 0xB9 0xD0 0x93 0x46 0xAB 0xD8 0x17 0x7A 0xE0 0xF0 0xA7 0x4C 0x32 0xD4 0x91 0x86 0xBA 0xA1 0x6C 0xA2 0x3C 0x73 0xCF 0x86 0x2D 0x95 0x9A 0x06 0x50 0xF3 0xF7 0x7E 0x06 0x5B 0x5E 0x27 0x66 0x01 0x3A 0x31 0x9F 0x0C 0xB1 0x91 0x96 0x49 0x5C 0xCC 0x81 0xBA 0x77 0x32 0x52 0xB2 0x10 0x5D 0x5B 0xCA 0xDE 0x9D 0x25 0x90 0x95 0xF7 0x97 SLIC Marker Structure Type 0x00000001 (1) Length 0x000000B6 (182) Version 0x00020000 (131072) OEM ID "ACRSYS" OEM Table ID "ACRPRDCT" 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 0x49 0x90 0xAC 0x34 0x3B 0x98 0x88 0x52 0x62 0x2C 0xFB 0x25 0xA8 0xA9 0xA0 0x7D 0x2D 0x12 0x70 0xEE 0xD5 0x9A 0x7C 0xCF 0x0C 0x83 0xB4 0x29 0x1B 0x55 0x3B 0x88 0xA5 0xF7 0xE6 0x29 0xA9 0x2C 0xE7 0x17 0x5D 0x7A 0xEE 0x38 0x4D 0x27 0xE0 0xA9 0x69 0x7C 0xFC 0x20 0x4A 0x68 0x0B 0x5D 0x83 0xAD 0xE5 0xD6 0x6E 0x49 0xC1 0x66 0x28 0xE4 0xD4 0xCE 0x72 0x64 0xA1 0x7C 0xBE 0x93 0xAD 0x64 0x32 0xDA 0xCC 0x72 0x24 0x47 0xFE 0xB4 0x97 0x87 0x01 0x55 0xA0 0x5D 0x2F 0xEF 0x06 0x93 0xE8 0x87 0x84 0x59 0xD3 0x9B 0x25 0x53 0x27 0xE7 0xCA 0x75 0x65 0xCF 0x0E 0x40 0xC9 0x3B 0xAA 0x03 0xF2 0x83 0x7E 0x27 0xE7 0xCA 0x47 0xA4 0x4B 0x1F 0xC5 0x77 0xDF 0x8C The interesting part the script will check for: Code: SLIC Ver 0x00020001 (v2.1)
OK the parse loop works and gathers the interesting info if available: Code: -------------------------------------------------------------------------------- SLIC TEST -------------------------------------------------------------------------------- SLIC: v2.1 -------------------------------------------------------------------------------- Drücken Sie eine beliebige Taste . . . Script should check for 6.1/6.2/6.3 and then depending on findings check for either SLIC 2.1 or OEM: DM in MSDM table and send to OEM procedure. For Enterprise it should skip that part automatically i would assume as best.
Came up with some ideas . New checks in :Choice2 Code: if "%winedition%"=="Enterprise" if %verstring% equ 6.1 goto :KMSInstall if "%winedition%"=="Enterprise" if %verstring% gtr 6.1 goto :KMSInstallWithHook if not "%winedition%"=="Enterprise" if %verstring% equ 6.1 if defined slicstring goto :CertKeyInstall if not "%winedition%"=="Enterprise" if %verstring% gtr 6.1 if defined productkey goto :OA3Install if "%winedition%"=="Professional" if %verstring% equ 6.1 if "%layout%"=="MBR" goto :ActivationChoice if "%winedition%"=="Professional" if %verstring% equ 6.1 if "%layout%"=="GPT" goto :KMSInstall if not "%winedition%"=="Professional" if %verstring% equ 6.1 if "%layout%"=="GPT" goto :MessageBox if not "%winedition%"=="Enterprise" if %verstring% gtr 6.1 goto :KMSInstallWithHook For Enterprise it now offers one of two KMS install ways. Win 8.1 needs additionaly the local host bypass installed. Then it checks if either SLIC or MSDM table is present and (will) offer to install Cert and Key for Win 7 or the OA 3.0 key for Win 8/8.1. If none of those is found it will offer for Win 7 Pro the Activation Choice on MBR systems and the KMS Install for GPT. In case no option matched so far it will offer :Messagebox for Windows 7 and skip activation part. For all Win 8/8.1 systems that slipped through to this point KMS with hook install will be offered. That should cover all possibilities i can think of so far. Three new message boxes and some code to add. Only challenge left would be key and cert install on Win 7 GPT systems when Branding is skipped.
GOTCHA for Loader on GPT (if SLIC is present): Code: "%windir%\Loader\Windows Loader.exe" /bios /silent
GOTCHA Part II: WindSLIC was also very cooperative i must commit, very nice . Spoiler Code: -------------------------------------------------------------------------------- SLIC TEST -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- WindSLIC INSTALL -------------------------------------------------------------------------------- Press any key to start the Tool, then click on "Install", wait a moment ... ...and close Tool, script will proceed. -------------------------------------------------------------------------------- installing certificate: success installing key: success Reboot mandatory. -------------------------------------------------------------------------------- Drücken Sie eine beliebige Taste . . . After reboot: Spoiler Code: User...: s1ave77 at: S1AVE77-PC Version: Windows 7 Professional x64 Edition: 6.1.7601.18409 Professional Channel: OEM_SLP PID....: YKHFT-KW986-GK4PY-FDWYH-7TP9F Status.: 1 = PERMANENTLY < LICENSED >
Reworked the script to solve the challenges ... now it also uses calls to avoid the redundancies . Should have covered most options now. On Win 8.1 it will always offer KMS if no MSDM table is found. Just tested on Win 8.1 ProWMC (no MSDM) and the script offers to install KMS-QAD-Hooker (similiar to the Win 7 KMS it installs Tasks and script for reactivation) and activate instantly: Spoiler Code: ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ KMS Server by QAD ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ Registry Entry of SppExtComObj.exe for has been created. KMS-QADhooker.dll and KMS-QADhooker.exe have been copied to C:\Windows\System32. Installation completed. ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ ERFOLGREICH: Die geplante Aufgabe "Reactivate Service DAILY" wurde erfolgreich e rstellt. ERFOLGREICH: Die geplante Aufgabe "Reactivate Service ONLOGON" wurde erfolgreich erstellt. ERFOLGREICH: Die geplante Aufgabe "Reactivate Service ONSTART" wurde erfolgreich erstellt. ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ Microsoft (R) Windows Script Host, Version 5.8 Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten. Der Product Key XXXXX-XXXXX-XXXXX-XXXXX-J8D3P wurde erfolgreich installiert. Microsoft (R) Windows Script Host, Version 5.8 Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten. Der Schlüsselverwaltungsdienst-Computername wurde erfolgreich auf 81.0.0.2:1688 festgelegt. Microsoft (R) Windows Script Host, Version 5.8 Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten. ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ Windows(R), ProfessionalWMC edition (096ce63d-4fac-48a9-82a9-61ae9e800e5f) wird aktiviert... Das Produkt wurde erfolgreich aktiviert. ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ Afterwards it offers to enable .NET 3.x since 4.x is already installed on Win 8/8.1. On Win 7 it offers the usual .Net 4.x Install: Spoiler Code: ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ .NET 4.x INSTALL ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ Enabling .Net 3.x using D:\sources\sxs. ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ Tool zur Imageverwaltung für die Bereitstellung Version: 6.3.9600.17031 Abbildversion: 6.3.9600.17031 Features werden aktiviert [==========================100.0%==========================] Der Vorgang wurde erfolgreich beendet. ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ Also the tests on Win 7 MBR/GPT went flawlessly. Loader activates GPT and installs Cert/Key on GPT if SLIC 2.1 is found; else WindSlic is offered. Couldn't test Enterprise, but it should offer either KMS Win 7 or Hooked KMS Win 8/8.1 (will work on both).
©BLIND GUIDE DOG PRODUCTION® PROUDLY PRESENTS: ************ s1ave77s S-M-R-T Setupcomplete Pack v.0.99.9 ************ featuring S-M-R-T Media Wizard v.0.0.0,666 ************ HOW-TO-USE: Windows Setup Media Integration: All needed files, except the OEM Branding files from cerberus8855 are shipped with that release Download Multi OEM Project: http://forums.mydigitallife.net/threads/57880-Multi-OEM-Project Using included MediaWizard v.0.0.0,666: [*=1]Start mediawizard.cmd and follow instructions. [*=1]Tool will recognize Setup files in Workfolder, else it will ask to copy from DVD/Mounted ISO one points to [*=1]Check the install.wim/esd [*=1]Copy pack files (general one and OEM Project [skippable]) to Workfolder [*=1]Offer to create ei.cfg [*=1]Offer to add generic tokens to all ProfessionalWMC indices (Win 8/8.1) with wimlib-imagex (included) [*=1]Create BIOS/UEFI ISO [skippable] with oscdimg.exe (included) Using any ISO-TOOL: [*=1]Open your Windows Setup ISO with an ISO-Tool (i.e. UltraISO). [*=1]Copy the content of cerberus' pack to the ISO ($OEM$\$$\Setup\Scripts\) and delete OOBE.cmd (it's not needed here since integrated to boottask.cmd). [*=1]Copy the content of boottask.zip to the same folder (boottask.cmd, Setupcomplete.cmd and files folder). [*=1]Re-build ISO. DONE! Run on Windows directly: Unpack Content of boottask.zip to any folder (boottask.cmd and files folder). Unpack the cerberus pack and copy content of $OEM$\$$\Setup\Scripts\ to same folder, except OOBE.cmd Run the boottask cmd Take a number ... or two/three. DONE! HASHES: Code: Windows Loader.exe 3.76 MB MD5: 3976BD5FCBB7CD13F0C12BB69AFC2ADC SHA-1: 3B6BDCA414A53DF7C8C5096B953C4DF87A1091C7 SHA-256: BF5070EF8CF03A11D25460B3E09A479183CC0FA03D0EA32E4499998F509B1A40 KMS Server Service x64.exe 243 kB MD5: 2399D35AE123607625ED278475B3605C SHA-1: B5D778D9BFE77755093007C2EE3A266F8B4B1DFC SHA-256: 1E33EC85E4F877F9F4AF14342ED1A15AFD277D2F7671C860844CEAC5FA5E5AAB KMS Server Service x86.exe 207 kB MD5: 1FE4528C1D6C9A303094C1A48EFCB193 SHA-1: F0D8AC5473E155CBD0D0DE19134387743A387EA5 SHA-256: 0DD1F361D0D7B521B214CE3E17086863F06B7073D7763128749D76F765066E93 Installer_EFI_gui.exe 187 kB MD5: EA94D4F3CA40D3B113CE76EF407B8FD2 SHA-1: 08DAF88756D9DF73D4A1610160F5BA361AACA076 SHA-256: 84EBE5B435E2E8863F1CC278DDE7F0A84C4839D9A5E9718EDDB268408947EAF4 KMS-QADhooker.exe (x64) 3 KB MD5: 6B2870D268828B8DB59D013A8111F8CF SHA-1: A9D18C56DE0373B444BBD1D49A5B0B1CCF2D1F2A SHA-256: A715DF664F7478F464E12D766876A6E1EEE7BB60E4D729C2D28094C5A0F69093 KMS-QADhooker.exe (x86) 3 KB MD5: 5C973B759AEC8E053189359832EA1A28 SHA-1: B0646B97530456561A8FBB0211A302EAC4DE9558 SHA-256: F6A791EE28E220FE017BB996F5D67389AA2C6347E888EA1A40B538EB84179265 boottask.cmd 41 kB MD5: F6A02F7709DECCB7D5E446006DD775D0 SHA-1: CDDCFA9520C6660C7C157C7BEAF93B9B6A62E2E3 SHA-256: E1DC21367A059AE97ACE43A8A72A9D06AB3BF2FC396AB34B3EAA77F9439EBBD2 mediawizard.cmd 12 kB MD5: A19BF8B4D02A69C066BE89D0DAFA8AEC SHA-1: 03A6863B1960A89247DD524BE6F6C6AC42D9BD98 SHA-256: E411AC3A42CAD9892DC548500142671DD6D62E745C3532BE30E3804FD86596CE CHANGELOG: Changelog v.0.99.9 Script reworked. Should cover nearly all possible challenges one throws at. All needed files added to the package. Added an optional MediaWizzard to create the ISO. v.0.01-0.99.9 some pre-alpha/beta versions to warm-up the brain DOWNLOAD: Spoiler Code: Pass: #iluv_mdl_77 Code: https://mega.co.nz/#!0MhQSAZI!GQIEZpz0XyUVxAzjGta9F8NtievrhKcqFQBZRU6VfOc
How can i import the latest Daz Loader v2.2.2 and is there a way to make this script to work only with Windows 7 so it can detect the Bios and Manufacturer from alone to activate it later.