After deploying the wimboot image, any changes or updates will be written as regular data sizes to the disk
Did you do a imagecleanup/reset base, I believe the replaced files do not get the wim treat. Murphy: wimre.wim means it's already in wim format. ... anyway, I don't set the recovery partition, anything goes wrong - reinstall.
According to MS articles, I think you need to put the updates into custom.wim after sysprep, then it will not "balloon" up. Maybe murphy could give more details.
Well... it wouldn't balloon up nearly as much as a non-wimboot install because the previous version would be compressed. Just think of it like this: The initial WIM file is static. It doesn't get modified after install. Any subsequent hotfixes you install will just install on the hard drive rather than into the wim file. You could clean up these hotfixes by doing a custom image pass and making a custom.wim, but if you can do all that, you could easily just re-sysprep/capture your image. There are a few problems with trying to use the custom image option. - The partition you install these images onto is set to recovery. - Recovery partitions are not re-sizeable - You are installing these images to the separate partition using a minimal amount of wasted space - You cannot move the wimboot wim file because the system files are accessed from it. (you'd have to do this in winpe) You could probably just set the partition to 0x800000001 and not use the recovery GUID so that you could resize the image, but this partition is already at the end of your drive and you cannot re-size backwards. It's just... There's not really any good way of working with these custom images. You're better off either starting over with your sysprep, or just leaving the added hotfix information in it's uncompressed state.
abbody1406 Your Post # 170: Create WimBOOT images: Create media: MakeWinPEMedia / ISO C:\WinPE_amd64 C:\WinPE_amd64\WIMBoot_amd64.iso I get an error. Please Help.
Try the manual way: Code: oscdimg -bootdata:2#p0,e,b"C:\WinPE_amd64\fwfiles\etfsboot.com"#pEF,e,b"C:\WinPE_amd64\fwfiles\efisys.bin" -o -h -m -u2 -udfver102 -lWinPE5.1_x64 C:\WinPE_amd64\media C:\WinPE_amd64\WIMBoot_amd64.iso
Sorry man, that's the limit of my knowledge on the situation. You can always try using the oscdimg instructions I gave on the first page.
murphy78 Hi, there! I'd like to ask you if there are any other tutorials about vimboot.vim installations and WMWare? Thanks in advance.
"I'd like to ask any of you who successfully managed to make Win 8.1u1 installation on VMware with winboot.win to send me a private message with precise instructions on how exactly he did it. I tried it with murphy78's tutorial but wasn't successful. Thanks in advance!"
@FaiKee thank you, but I would like guidance on how to make emulation wimboot on the VM. I would not want to do this before wimboot on a PC disk.