LOL, I have no Idea why anyone would leak the ADK before they leaked the actual build. Really makes no sense to me :/ EDIT: This seems a lot bigger than the normal ADK's to me, anyone else notice this?
anyone try to activate this ISO with pirated KMS? MICROSOFT.OFFICE.2013.PROFESSIONAL.PLUS.WITH.SP1.RTM.X86.VOLUME.ENGLISH.DVD-WZT Now all we need is 8.1 Update 1 VL MSDN iso that activates through KMS and i'll be happy EDIT: en_windows_8_1_pro_vl_x64_dvd_2971948.iso ---> (still waiting on 8.1 update 1 iso) SW_DVD5_Office_Professional_Plus_2013_W32_English_MLF_X18-55138.iso ---> (SW_DVD5_Office_Professional_Plus_2013w_SP1_W32_English_MLF_X19-35821.iso) both ISO's on the left activate with KMS servers posted here. now i'm hoping both ISO's on the right will activate with kms servers posted here :crystal:
I think I just had movement in my lap and I'm not sure why. Does this mean that we can have an entire windows image booted from a wim file? First person to properly get this to work gets a damn cookie! (>'')> ( : : )
Yep ... But Code: *Limitations: - WIMBoot is available for client editions of Windows 8.1 with Windows 8.1 Update only (not server versions). All architectures are supported, including amd64, x86, and ARM. Some enterprise deployment tools do not yet support WIMBoot. - WIMBoot is available only for UEFI-based PCs running in UEFI mode (legacy BIOS-compatibility mode isn't supported). - WIMBoot is supported for solid-state drives and eMMC (Windows HCK compliant) drives. WIMBoot isn't supported on traditional drives that contain rotational components, or on hybrid drives that contain both solid-state and rotational drive components. WIMBoot works by taking advantage of the capability of solid-state drives to access different areas of the hard drive quickly. - It's OK to have a secondary drive attached to the PC, and the secondary drive can contain rotational components. But the WIMBoot image and pointer files must all be located on the primary solid-state or eMMC drive. - Some backup, antivirus, and encryption tools aren’t compatible with WIMBoot images. I don't have UEFI nor SSD, so i'm out
I don't either but I plan on getting one soon. I was waiting for the 256ers to get cheaper. 128 just doesn't seem like enough space to me.
I have both UEFI and SSD. how does this winboot thing work? Is the winboot image a separate image on the SSD, or the whole OS system is in Winboot format? In other words, on the ssd, does it have the OS AS a wimboot image, or it has an live OS plus a winboot image? Anyone knows?
Well, I'm not exactly sure. Try reading the help file that came with the adk. If I had to guess I'd say it's probably like booting a vhd
I'm on BIOS. So I could use VM EFI mode too. But I installed on my SSD Ubuntu. Waiting for more information. If worth it will throw my Ubuntu into HDD.
you can buy a 120 (it's enough for OS plus programs) i use one for your fab releases anything else on a SATA HD