Doesn't work either.I downloaded another server 2008 R2 and it works now fine in my AIO (i use a windows 8.1 x86 as a base).I will download vista x86 from another source and i'm pretty sure that it will work too. The annoying part is still with 7 embedded.Tried 3 isos so far (x86 ,x64 and a custom made one i'd really like to add) and none are working in my AIO.Same thing goes for W Thin PC (downloaded from here). About the code you provided, correct me if i'm wrong, but isn't this the same thing than copying the license folder manually? By the way, none of my 7 embedded isos have a license folder, but they still boot and install perfectly well by themselves. Thanks a lot for your help.
Thanks a lot for the explanations.Like i suspected, using a different source iso fixed the vista x86 error. Another question though : is the language of the iso important when copying licenses?I mean the 7 Embedded i'm trying to add is a french iso, your files and others i found are from an english version.Does it matter? Happy new year to you and all members.
Can someone run Windows 8.1 AIO (6 GB and more) with VMware Player or virtualbox ? It seems that ISO's with more than 5 GB can´t run. I tried with small AIO´s and worked. But with AIO with more than 5 GB doesn´t work and I get error. Does anyone have this issue too ?
No I don't, see I got a 7.25 GB AIO and runs smoothly in VMware latest version. And an $oem$ folder for auto-activation.
when creating a multi-lang windows 7/8 aio, language pack is important but don't know about license files because they are just plain text/rtf document files, so I think it doesn't matter in which language it is.
Hi guys. I found out what the problem was. It isn´t possíble to create an AIO with: Windows 8.1 retail Windows 8.1 Pro retail Windows 8.1 VL Windows 8.1 Pro VL After creating a new AIO without using VL versions of Windows 8.1, it worked well. Now I want to know, what is better. Creating an AIO with retail versions of Windows 8.1 and the Enterprise version, or making an AIO only with VL versions ? I have both. And how will be the "ei.cfg" file, if I use an AIO only with VL versions ?
That's not the thing, you can do AIO with Windows 8.1 Retail and VL. I have created a Windows 8.1 AIO with Windows 8.1 Pro Retail, Windows 8.1 Pro VL, Windows 8.1 ProWMC Retail, Windows Embedded 8.1 Industry Pro VL. It Works fine. I The Syntax of EI.cfg is Code: [EditionID] {Edition ID} [Channel] {Channel Type} [VL] {Volume License} where {Edition ID} must be a valid Windows edition ID; {Channel Type} must be either "OEM" or "Retail"; and {Volume License} must be either 1, if this is a volume license, or 0, if this is not a volume license. For example: Code: [EditionID] SKU [Channel] OEM [VL] 0 The EI.cfg file contents for AIO with Only VL Versions of OS Code: [EditionID] [Channel] [VL] 1
Well here is the EI.cfg syntax for Windows 8.1 AIO Versions.. EI.cfg for Windows 8.1 AIO Retail Version Only Code: [EditionID] [Channel] Retail [VL] 0 EI.cfg for Windows 8.1 AIO OEM Version Only Code: [EditionID] [Channel] OEM [VL] 0 EI.cfg for Windows 8.1 AIO Volume Version Only Code: [EditionID] [Channel] Volume [VL] 1 EI.cfg for Windows 8.1 AIO Retail+Volume Versions Code: [EditionID] [Channel] [VL] 0
Thanks for it. I will try GImageX to rename the indexes. But how does GImageX work ? Any tutorial ? The other problem is that when I add 'ei.cfg' file, my AIO doesn´t start. Tried with virtualbox and VMware player. Both with error. So, I put the AIO into a pendrive and tried to launch it, and also didn´t work. Without the 'ei.cfg' file AIO works fine. With 'ei.cfg' file, my AIO doesn´t work.
building an iso for 8.1 is the instructions on post 1 accurate for making an aio installation dvd for core and pro in both x32 and x64, oem and retail, for installation without inputting a pk ?