@all I strongly recommend to use an extension for your browser called uBlock Origin (not uBlock but uBlock Origin) This way any pop up or opening pages for re-direction which leads to malware download is blocked. Many file servers are using nasty tactics...
Going to be updating the WinTel.cmd (optional addition) with error handling for ip routes that might already be executed. This update will come later this week.
First post updated 11-01-2015. Spoiler Change log 11-01-2015: -Updated optional WinTel.cmd with error handling.
Its been awhile. I've been working on modernizing script stuff with powershell. I wanna add the multi oem project as a module into the powershell oem pack. I think its finally time. Also I can pull the hardware information using powershell to pipe it into the multi oem project on install. I have a prototype that is stable that I'm using to throw from my version to the mdl copy.
So your going through power-shell withdraws? lol Just say no. lmao! Got to mess with you a little bit.
Nah I ran out of stuff to do with the oem stuff on the powershell side. Then I thought up how I can grab the hardware information to use on the script side. I wanna use the multi oem project as a module and if its easy maybe convert the OOBE script to powershell. I looked at it and I have many of the basic variables already implemented. Code: #Multi OEM Project # $ProductName = (gwmi Win32_OperatingSystem).Caption $winver = (gwmi win32_OperatingSystem).Version $Manufacturer = (gwmi win32_bios).Manufacturer $System = (gwmi win32_computersystem).Model $default = "$env:windir\Setup\Scripts" cd $default
@The Guardian The "Force_Theme_[readme].txt" are only write the brand name inside this txt? And also this txt file must located in scripts folder for working to install any brand theme??
@The Guardian Haha! Thx! But the problem is, when I boot Windows 10 Pro 64-bit with OEM added in VMware Workstation 11 while Setup is starting, it gives me an unknown error message: In my attachment Differently my Windows 8.1 Pro 64-bit with OEM are no problem for me, only Windows 10 had problem. So how I gonna to fix it?
If win10 is a upgrade then no need to add key since it is generic anyways. Once online it will connect with M$ server and activate according to hardware id's. No need to use xml file in this case.
Is it feasible to start converting the cmd scripts to powershell? In terms of oobe.cmd, install.cmd, and wintel.cmd? Should be pretty easy because the syntax for powershell is closer to modern programming.