Search the Community
Showing results for tags 'WIMBoot'.
Found 3 results
VHD_WIMBOOT - Apply and Capture of WIM Files for OS in VHD Download: VHD_WIMBOOT-26.zip and at Reboot.pro Forum APPLY of WIM File in wimboot mode to VHD gives Operating System with only variable and boot essential files total about 1 GB in VHD. The VHD contains also pointers to the non variable files in the WIM archive, so that it seems that the complete OS is present in the VHD. The VHD content can be generated in 2 minutes from the WIM archive of about 9 GB, so that a backup of the system is always available. The VHD + WIM set can be copied to any drive so that we have a portable Operating System. The WIM file cannot be changed by viruses or other malware so that the system is reliable and if needed it is easy to generate new VHD. The VHD can boot as 25 GB FILEDISK from Portable SSD to allow changes, but also booting always Fresh from 3.9 GB RAMDISK is possible. VHD WIMBOOT has support for Office and Printer and any program can be installed, which is all not possible in case of WinPE In case of VHD WIMBOOT on each machine it takes extra boottime and space to adjust the drivers for that machine The VHD WIMBOOT solution is Portable, but not as flexible as Win10XPE, where boottime is not dependant on machine hardware Credits and Thanks to: Microsoft for making WIMBOOT - https://msdn.microsoft.com/en-us/library/dn631793.aspx and https://docs.microsoft.com/en-us/windows/win32/w8cookbook/windows-image-file-boot--wimboot- synchronicity aka Eric Biggers for making wimlib - https://wimlib.net/ schtrom for making SVBus Virtual SCSI Host Adapter for GRUB4DOS - http://reboot.pro/topic/21787-svbus-virtual-scsi-host-adapter-for-grub4dos/ alacran for support and info - http://reboot.pro/topic/21957-making-the-smallest-win10-install-wimboot-mode-on-512-mb-vhd/ and http://reboot.pro/topic/21972-reducing-wimboot-source-wim-file-using-lzx-compression-and-vhd-using-gzip-or-lz4-compression-to-save-room-and-also-load-faster-on-ram/ JFX for making WinNTSetup to Install Windows 2k/XP/2003/Vista/7/8/10 x86/x64 - https://msfn.org/board/topic/149612-winntsetup-v394/ Uwe Sieber for making ListUsbDrives - http://www.uwe-sieber.de/english.html Pauly for making BOOTICE - available via http://reboot.pro/files/file/592-bootice-v1332/ and https://sites.google.com/site/gbrtools/home/software/bootice-portable/bootice-downloads chenall, yaya, tinybit and Bean for making Grub4dos - http://grub4dos.chenall.net/categories/downloads/ Thanks to karyonix, alacran, Wonko the Sane, tinybit, yaya, chenall, cdob, JFX, steve6375, ReTokener, synchronicity, schtrom and Microsoft Development is described here - http://reboot.pro/topic/18182-uefi-multi-make-multi-boot-usb-drive/page-5 The program is released "as is" and is free for redistribution, use or changes as long as original author, credits part and link to the reboot.pro support forum are clearly mentioned VHD_WIMBOOT - http://reboot.pro/topic/21977-vhd-wimboot-apply-and-capture-of-wim-files-for-os-in-vhd/ Author does not take any responsibility for use or misuse of the program.
Hello Everyone... Most of us are always worrying about the Low Disk Space problem within Windows Installation Drive (C drive) of our PC/Tablet/Laptop. All of us who can't afford greater storage within C: drive install only limited and lightweight third party software. Sometimes we stuck in big trouble whenever free space reached to 50-150 MB. And we don't want to re-format C: drive at that time. Don't worry guys..... Microsoft introduces 'WIMBoot' features in 'Win 8.1 U1' in order to keep size of C: drive smaller. But it require fresh Windows Installation within from PE Environment. So in real sense WIMBoot doesn't help for those guys who have left only50-150 MB free space in their C: drives. Don't worry guys once again..... Actually I was also facing low free space problem till now. But now low free space is not a big problem. All thanks to Simon King for creating magical tool <<spam>> 12.2 (DoubleSpace, DriveSpace, Stacker). Simon King have built truly one-click software which converts any pre-existing Windows 8.1 Update 1 system to WIMBoot. This tool is called DoubleSpace and is available from http://www.<<spam>>.co/doublespace.html. <<spam>> DoubleSpace uses WIMBoot technology to safely double storage on your boot disk. You will not need external storage, a Windows PE environment, manually created images - or anything of the sort - to use DoubleSpace. DoubleSpace runs in one-click, and all you need to choose is compression strength - 4 are available, between MaxSpeed - MaxSpace. You can even re-compress a disk that has been previously compressed. I trust you will enjoy using the tool as much as I enjoyed it. Try it..........It works just like magic ! Regards.......
I have a history of jumping into "improvements" to my PC setup without first making sure that they are actually improvements... This time, I thought I would get some outside insight and advice, prior to the actual undertaking... I'll start with my current setup, and then outline the idea that is floating around in my brain. Comments and criticisms are welcome at any point in the process... Currently, I run my system from VHDX, primarily for the differencing, and as a space-saving measure (differencing disks are denoted by indentation level): "Base" vhdx, simply a blank vhdx, with the OS (8.1) applied via DISMHardware Base vhdx -> contains drivers & programs common to various boot scenariosDaily Use vhdx -> has Office & various other odds & endsGaming vhdx -> Screens setup for surround gaming, extraneous programs stripped outTesting vhdx -> useful for testing out new hardware / software(List expands & contracts as needed)VPC Base vhdx -> Drivers & programs common for VMsVMs (varies)To-Go VHDX -> I have a Win to go setup, very useful for the inevitable family & friends service calls. I run it as a VHDX for ease in un-doing any potential changes In the setup I am considering moving to, I would add a top level WIM file, and enable booting from WIM for all of the listed scenarios. I am also planning on moving from my single (x86) to-go to a dual x86 / x64 setup... I'm not terribly concerned about any potential speed hits, saving space on my SSDs (in my main PC, and for my to-go setup) is of more importance... Are there any "gotcha" scenarios I should be aware of? Any potential system breaking issues? I am currently working on updating my Windows 8.1 ISOs to update 1, then I am planning on slipstreaming any & all of the updates that are out so far... Thanks for reading, and any comments are much appreciated!