devdevadev

https://drive.google.com/folderview?id=0B7k-l_4omFECNWRGNHBEdVBsTTA&usp=sharing#list Regards...

What may be the reason behind disabling 'Hibernate' if booting from native VHD by Windows ? I think 'WinNTSetup v3.7' should show 'Enable Hibernate' checkbox under 'Tweaks' instead of 'Disable Hibernate' checkbox. So that we can 'Enable Hibernate' if booting is performed from VHD by Windows. Otherwise there is no meaning of 'Disable Hibernate' checkbox if booting is going to be performed from native VHD by Windows. If possible then please replace 'Disable Hibernate' checkbox with 'Enable Hibernate' checkbox under 'Tweaks' if booting from native VHD by Windows. Is it possible to implement following configuration ? http://reboot.pro/topic/20097-is-there-any-way-to-enable-hibernate-in-dual-vhdvhdx-booting-of-win-10-tp/#entry187946 Thanks & Regards.....

Hi 'JFX'..... Thanks for useful info........... I prefer Dual Boot of latest Windows OS (Win10TP) but I don't want to use two Partitions for two OSes. I want to keep all Installation files and folders of Both OS in a single partition. It's why I using 'WIMBoot + VHDX'. I am using 'VHDX' because it allow me to keep two OSes in a single partition. And If one OS is corrupted then I re-install it within form second OS and vice-versa. And there is no need to format two Partitions again and again. And It very comfortable for me to just delete a 'VHDX' file in order to remove a OS completely without formatting a whole partition. And Before deleting 'VHDX' file I can cut-paste my Imp. Data within fro 'VHDX' to the root of same Partition which contains 'VHDX'. And By this way I don't have backup my Imp. Data to any other Storage Device. And After re-installation of Windows within 'VHDX'. I reverse the cut-paste process. As I am using tetra boot of 'Mac OS X' , 'Win 10 TP' , 'Win X TP' and 'Ubuntu 14.10'. So I want to keep minimum number of partition in my Hard Disk. You mean 'VHDX' require/consume more size in order to hold WINDOWS? If 'Yes' , then what about 'VHD' or any other 'Virtual Disk Drive' ? Does 'VHD' also require more size ? I can not compromise with 'Hibernate' feature so what should I do so that I can keep two Windows OS in one partition along with WIMBoot ? Is there any solution ? I have only 3GB RAM. So Will it be safer to disable 'pagefile.sys' in my Case ? or not ? Please suggest me a trick/method by which I can keep two WIMBooted OS within same partition with 'Hibernate' features.... Thanks & Regards....

My Laptop is 'Dell Inspiron 1545' which is a MBR/BIOS type........ I have recently installed WIN10TP as 'WIMBoot + VHDX' configuration in my system which is created with the help of 'WinNTSetup v3.7'. Everything is working just fine. But there is no option for 'Sleep'. Why ? Does 'Sleep' feature is not supported in WIMBoot ? Why I am unable to use 'Sleep/hibernate' features if I use 'WIMBoot + VHDX' configuration ? Is there any role of 'WinNTSetup' for not accessing 'Sleep/hibernate' feature ? I want to keep My Installation Drive as small as possible so I want to disable 'pagefile.sys'. Is there any serious drawback of disabling 'Pagefile.sys' ? Regards....

Hi 'JFX' Which/What type of advance feature 'WinNTSetup' does provide if we add 'wimlib' files within it ? Can you please enumerate about that advance features ? And I am unable to create WIMBoot of 'Windows 10 Technical Preview'. What may be the reason ? Does 'Windows 10 Technical Preview' not support 'WIMBoot' ? Regards...

Hello 'JFX'... I am using 'WinNTSetup_x86 v3.7.0' . And I want to put wimlib files within WinNTSetup3\Tools\x86\wimli directory. There are three wimlib files in the download section. Can you please tell me about the exact file which I should have to choose. There are many files within wimlib.zip. Can you please specify the list of wimlib files which I should put within wimlib directory. Why you not adding wimlib files within WinNTSetup ? 1- wimlib-1.7.2-windows-x86_64-bin.zip < 4 hours ago 638.2 kB2- wimlib-1.7.2-windows-i686-bin.zip < 4 hours ago 661.5 kB3- wimlib-1.7.2.tar.gz < 4 hours ago 961.8 kB Out of three which one I should download for 'WinNTSetup_x86 v3.7.0' ? Regards....

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 &lt;&lt;spam&gt;&gt; 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.&lt;&lt;spam&gt;&gt;.co/doublespace.html. &lt;&lt;spam&gt;&gt; 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.......

Hi 'JFX'.... Suppose I have a 64-bit UEFI firmware/system based PC along with UEFI/GPT 'WINDOWS' drive partition as follows- After booting through 'Win8.1U1SE_x64_boot.wim' in 64-bit UEFI firmware/system , I will use 'WinNTSetup v3.61' in order to install 32-bit 'install.wim' into 'WINDOWS Drive'. Will 'WINDOWS Drive' boot in '64-bit UEFI mode' after windows installation ? Can I use 32-bit 'install.wim' in order to install 'Win 8.1 U1' in 64-bit UEFI firmware/system in place of 64-bit 'install.wim' ? Is it necessary to use 64-bit 'install.wim' file in order to install in 'WINDOWS Drive' in 64-bit UEFI mode ? Regards........

Hello 'Atari800XL' I want to read current issue (2014-17) of "c't magazin" about SSD and Wimboot.. Can you please send me the PDFs of the article ? Thanks in Advance

Hello JFX..... As my 'Win8.1ToGO.vhdx' is Dynamically Expanding VHDX so I do not want to keep more spare space within 'Win8.1ToGO.vhdx'. I want to keep 'Win8.1ToGO.vhdx' as smallest as possible so that it just contain extracted files required for WIMBoot. What would be the smallest sizes of 'Win8.1ToGO.vhdx' so than I can just apply x86/x64 'WIMBoot.wim' into 'Win8.1ToGO.vhdx' with the help of 'WinNTSetup v.3.6.1' ? Regards......

Hello JFX I want to request you for a little advancement in next release of 'WinNTSetup' which is as follow- If possible then can you please introduce a new 'Check Box' option in next release of 'WinNTSetup' in such a way so that when we choose 'install.esd' as a source along with 'WIMBoot' option then 'Check Box' become activated automatically and convert 'install.esd' to 'WIMBoot.wim' with the help of 'wimlib' , Copy 'WIMBoot.wim' to the root of Boot Drive, Capture WIMBoot Installation and Apply 'WIMBoot.wim' to the 'Installation Drive' ? If interested then you can also allow us to Check/Uncheck new 'Check Box' option when we choose 'install.wim' as a source along with 'WIMBoot' option and perform exactly the same process as described above for 'install.esd' + 'WIMBoot' combination. Note- New 'Check Box' option will be activated only when we choose 'WIMBoot' option otherwise 'WinNTSetup' behave as usual for both 'install.esd' and 'install.wim' . I have thousands of hope from JFX for above advancement............ Thanks in Advance Regards.......

I could not understand Where I have to copy 'WIMBoot.wim' before using WinNTSetup ? What do you mean by UDF ? Should I have to copy 'WIMBoot.wim' into 'UFD- USB Flash Drive' ? Can you please describe in little detailed steps ? Regards

Hello JFX Sir, First thousands of thanks and regards for such a useful information........ Can I use 'WIMBoot.wim' as a Source in 'WinNTSetup v.3.6.1' in order to create 'WTG + WimBoot + VHDX' combo ? Do you know about a Script/Tool/Commands/Method in order to convert 'install.esd' into 'WIMBoot.wim' directly ? Regards...........

HEy JFX....... Thanks, Now after uncheck 'WIMboot' option my 'install.esd' work properly. It means it is not encrypted. But How can I decide that 'install.esd' is encrypted/Un-encrypted ? I had created 'WTG + WimBoot + VHDX' Setup using 'WinNTSetup v.3.6.1' and 'install.wim' file. And it successfully completed and worked. I had not added anything (wimlib dll files to "Tool\x??\wimlib" folder and "-wimlib" commandline parameter ) in the WinNTSetup3\Tools\x86\wimlib folder, then why 'WIMBoot' successfully created ? Does you mean that 'WinNTSetup 3' and 'wimlib' uses different technique for creating WIMBoot ? Does 'WinNTSeteup v.3.6.1' uses any other technique for 'WIMBoot' other than WimLib way ? Which of the following three method will save maximum Disk Space ? 1- WTG + WimBoot + VHDX 2- WTG + VHDX 3- Normal WTG Which of the above method is best in term of 'Disk Space' , 'Speed' and 'Performance' ? Question- Will I have to use 'Dynamically Expanding VHD' in order to keep the size of the 'Windows81.vhdx' as minimum as possible so that there will be NO free space wastage within the 'Windows81.vhdx' ? Regards.....

Hello Sir, I got following error message for my 'install.esd' file. Does following error occur for encrypted ESD files or I am doing else wrong How can I find out that my 'install.esd' is either encrypted or un-encrypted ? Can I expect supports of encrypted ESD files from 'WinNTSetup 3' in near future ? Regards......

Hello Sir, Which of the following method is more better (in terms of occupied Disk Space ) in order to create smallest 'WTG + WimBoot + VHDX' Setup ? 1- WimLib way here (does NOT require win8.1u1 winpe). 2- WinNTSetup v3.6.1 way here Note- WimLib way end up with a C drive occupied by only 250 MB (before 1st boot where pagefile.sys and hyberfil.sys will be created). Thanks and Regards

Hi 'JFX'........ http://www.msfn.org/board/topic/170546-win81se/page-8#entry1080980 What you think about this ? Thanks..........

Hello Everyone Specially 'ChrisR', 'JFX' & 'wimb'................................ AFAIK, For UEFI + BIOS booting from USB then Windows 8.1 x64 need to be used as Source.There are now three Universal solutions for booting from USB on UEFI + BIOS computers:- Win8.1SE x64 boot.wim of size 400 MB booting from RAMDISK- Portable W864USP1.vhd of size 3.5 GB booting as FILEDISK- Full Windows 8.1 Pro installed in 15 GB VHD or any Windows 8.1 on USB SYSTEM partition of size 50 GB According to 'wimb' - Windows 8 VHD files make use of Microsoft VHD driver which allows in Boot Manager Menu to boot VHD as FILEDISK. Booting VHD files from Grub4dos Menu as FILEDISK or as RAMDISK requires to Install in Source VHD either FiraDisk Or WinVBlock driver. Additinally Installed Programs and Drivers and Settings are remembered in FILEDISK just like in normal Windows OS. Loading the VHD into RAMDISK is much faster when the VHD file is located on the internal NTFS harddisk drive. 1- FiraDisk Or WinVBlock driver can be Installed in Source for booting Win 8 VHD from RAMDISK using Grub4dos Menu. 2- Grub4dos Menu for booting Win8 VHD as FILEDISK or as RAMDISK is made when FiraDisk or WinVBlock driver is found in Win8 Source. So, Finally I want to ask some questions which are as follows---------------------------------------------------------------------------------------------------------------Is 'FiraDisk Or WinVBlock driver' already installed in the Source of 'Win8.1SE_x64_ _boot.wim' ? Does 'Win8.1SE' already contains a script for installing 'FiraDisk Or WinVBlock driver' into Source of 'Win8.1SE x64 boot.wim' ? Is it possible to make a Grub4dos Menu for booting 'Win8.1SE x64 boot.wim' as FILEDISK or as RAMDISK ?-------------------------------------------------------------------------------------------------------------- Actually I want to use 'Win8.1SE x64 boot.wim' in the 'Easy2boot' as a Payload file. Is it possible ? Thanks in Advance.......

Hello 'JFX' Can 'WinNTSetup v3.6.1' install 'Win 8.1 Update1' in both 'BIOS/MBR' drive partitions and 'UEFI/GPT' drive partition without changing Partition scheme ? 1- 2- I mean Can 'WinNTSetup v3.6.1' install 'Win 8.1 Update1' into 'Windows Partition' of both 'BIOS/MBR' and 'UEFI/GPT' partition scheme without converting partition scheme ? Please confirm if it works for both................. Thanks...........

devdevadev, As for your questions: - esd files are not supported, so get a normal sources with install.wim or learn how to convert esd to wim. - reconsider why you need to have two partitions available at the same time, or try karyonix diskmod ______________________________________________________________________________ Hello 'JFX' Sir, First thanks for your precious reply........... 1- Actually I know how to convert '.install.esd' to 'install.wim' . I also know that there are lots of tutorial in the Internet for the same. But I still want 'install.esd' support in 'Win8.1SE' because I always download 'ESD based ISO's' due to it's compression size. If I convert 'install.esd' files to 'install.wim', then i always have to face shortage of storage problem. Currently most of the USB booting tool support 'install.esd'. It's why I request to add support of 'install.esd' in 'Win8.1SE'... 2- Actually I do not want two partitions available at the same time, But I want 'Partition 2' of 'Removable USB Drive' which normally become 'Invisible to Windows'. I want to access 'Partition 2' because I always put my all '.imgPTN files, ISOs, all Important software and tool and Boot files' within hidden 'Partition 2'. I do not want to put any software/Payload file within 'Partition 1'. I want to use 'Parition 1' only for DATA Storage purpose. Sometime I use 'Partition 1' for copying Important files and Data form corrupted Windows PC during emergency. I want to use 'WinNTSetup_x64.exe' in order to mount 'Win_7/8/8.1_Inst.imgPTNLBAa' (within from \_ISO\WIN folder of Partition 2) in ImDisk Virtual Drive. Actually I want optimum utilization of each and every Tools and Resources at low cost and quick time............. Thanks for Everything...............

Hello Everyone............. This is the 'Advanced USB Configuration' exactly what I want to use in my 32 GB Transcend JetFlash 780 3.0 'Removable' USB Drive/Key/Stick. Partition 1 - FAT32 - 5 GB - Visible to Windows - This Partition will be use only for 'Data Storage' and contain bare minimum ‘EFI Files’ hidden by attrib commands. S:\EFI Directory S:\EFI\Boot\bootia32.efi - x86 hardware / firmware S:\EFI\Boot\bootx64.efi (bootmgfw.efi) - amd64 hardware / firmware S:\EFI\Microsoft\Boot\BCD - (Relocated to boot.sdi, Win8.1U1SE_x64_boot.wim, Win8.1U1SE_x64.vhd and Win8.1ToGO) S:\EFI\Microsoft\Boot\Fonts\wgl4_boot.ttf - Recommended Partition 2- FAT32 - Set Active - 25 GB - Invisible to Window - This Partition will contain Win8.1ToGO, 'Win8.1U1SE_x64_boot.wim', 'Win8.1U1SE_x64.vhd', 'Easy2Boot' files and many more Payload Files (ISOs, IMGs, .imgPTN etc……) hidden by attrib commands. K:\Boot Directory K:\BOOTNXT K:\WIMBoot.wim K:\Win8.1ToGO.vhdx K:\Bootmgr (For direct booting of ‘ Win8.1ToGO + WIMBoot + VHDX’ combo within from E2B Menu ) K:\Boot\BCD (relocated to “Win8.1ToGO + WIMBoot + VHDX” combination and boot.sdi) K:\Bootmgr1 (For direct booting of 'Win8.1U1SE_x64_boot.wim' within from E2B Menu ) K:\Boot\BC1 (relocated to Win8.1U1SE_x64_boot.wim and boot.sdi) K:\Bootmgr2 (For direct booting of 'Win8.1U1SE_x64.vhd' within from E2B Menu) K:\Boot\BC2 (relocated to Win8.1U1SE_x64.vhd and boot.sdi) K:\Boot\boot.sdi K:\EFI Directory K:\EFI\Boot\bootia32.efi - x86 hardware / firmware K:\EFI\Boot\bootx64.efi (bootmgfw.efi) - amd64 hardware / firmware K:\EFI\Microsoft\Boot\BCD - (Relocated to boot.sdi, Win8.1U1SE_x64_boot.wim, Win8.1U1SE_x64.vhd and Win8.1ToGO) K:\EFI\Microsoft\Boot\Fonts\wgl4_boot.ttf - Recommended K:\grldr K:\menu.lst K:\my.usb K:\_ISO\MAINMENU\Win8.1U1SE_x64_boot.wim K:\_ISO\MAINMENU\Win8.1U1SE_x64.vhd K:\_ISO\MAINMENU\{WIM + VHD + (Win8.1ToGO + WIMBoot + VHDX) }.mnu K:\_ISO\MAINMENU\Ultimate DLCD Boot 2014 v2-1.imgPTN K:\_ISO\MAINMENU\Spotmau BootSuite 2012.imgPTN K:\_ISO\MAINMENU\Easy Rescue Suite 2014.imgPTN K:\_ISO\MAINMENU\KonBoot_24.imgPTN K:\_ISO\MAINMENU\E2B_PTN_SWAP.mnu K:\_ISO\WIN\WIN 7 Ultimate.imgPTN K:\_ISO\WIN\WIN 8.1 Update 1_x86_x64.imgPTN K:\Smart Apps\WinNTSetup 3.6.1 (BootIce included in tools folder). K:\autorun.inf K:\autounattend.xml K:\e2b.ico K:\FASTLOAD.YES K:\HitmanPro.exe K:\HitmanPro_x64.exe K:\Kickstarter.exe K:\PassPass.bak K:\Readme.txt K:\unattend.xml Note- In K:\_ISO\MAINMENU\{WIM + VHD + (Win8.1ToGO + WIMBoot + VHDX) }.mnu , I will put following entries in order to directly boot Win8.1U1SE_x64_boot.wim, Win8.1U1SE_x64.vhd and “Win8.1ToGO + WIMBoot + VHDX” combination within from Easy2Boot Menu in BIOS/MBR mode. __________________________________________title Win8.1ToGO + WIMBoot + VHDXchainloader /bootmgr title Win8.1U1SE_x64_boot_WIMchainloader /bootmgr1 title Win8.1U1SE_x64_VHDchainloader /bootmgr2_________________________________________ 1- BIOS " I will use BCD edit function inside bootice to edit S:\Boot\ (BCD, BC1, BC2) for creating boot entries for my 'Win8.1U1SE_x64_boot.wim' , 'Win8.1U1SE_x64.vhd' and ‘Win8.1ToGO + WIMBoot + VHDX’ in BIOS mode (winload.exe to be put as loader). " 2-UEFI " I will use BCD edit function inside bootice to edit S:\efi\Microsoft\Boot\BCD for creating boot entries for my 'Win8.1U1SE_x64_boot.wim' , 'Win8.1U1SE_x64.vhd' and ‘Win8.1ToGO + WIMBoot + VHDX’ ‘in UEFI mode (winload.efi to be put as loader). " BIOS mode: 1- BIOS -> MBR -> grubdos -> grldr/menu.lst -> Easy2Boot Menu 2- BIOS -> MBR -> grubdos -> grldr/menu.lst -> bootmgr -> s:\boot\(BCD, BC1, BC2) -> 'Win8.1U1SE_x64_boot.wim' , 'Win8.1U1SE_x64.vhd' and ‘Win8.1ToGO + WIMBoot + VHDX’ combination UEFI mode: UEFI-> /efi/bootmgfw.efi -> winload.efi -> S:\efi\Microsoft\Boot\BCD -> 'Win8.1U1SE_x64_boot.wim' , 'Win8.1U1SE_x64.vhd' and ‘Win8.1ToGO + WIMBoot + VHDX’ combination Note - After booting from 'Win8.1U1SE_x64_boot.wim' or 'Win8.1U1SE_x64.vhd' or ‘Win8.1ToGO + WIMBoot + VHDX’ in BIOS/UEFI mode. Then I will use portable App 'WinNTSetup 3.6.1_x64.exe' in order to mount 'Win_7/8/8.1_Inst.imgPTN' (within from \_ISO\WIN folder of Partition 2) in ImDisk Virtual Drive. 'WinNTSetup 3' will prepare local harddisk for Install of Win 7/8/8.1 Please take a look of my whole Configuration carefully. And confirm if it may work................. Please provide me your precious suggestions in order to improve above configuration...... Thousands of Thanks and Regards to Steve, ktp, alacran, cdob, misty, wimb, JFX, HALIKUS, Wonko etc........

Hello 'ChrisR' Please add a script for 'cfadisk' windows disk driver in next release of 'Win8.1SE' so that we can access both 'Partition 1' and 'Partition 2' of 'Removable USB Drive within from running 'Win8.1SE_x65_boot.wim'. If you like then you can also add 'Fab's AutoBackup 5 Pro script V4' script within 'Win8.1SE'. http://reboot.pro/files/file/88-fabs-autobackup-5-pro/ Thanks in Advance

Hello 'ChrisR' ............................. First tons of thanks for 'Win8.1SE' . I found a DVD from Microsoft which contains 'install.esd' file. And I am unable to use 'Win8.1SE' with my Win 8.1 ISO (install.esd) becasue 'Win8.1SE' is currently not supporting 'install.esd' files. I want to create both 'Win8.1UpdateSE x64 boot.wim' and 'Win8.1_x64.iso' by using your 'Win8.1SE'. I do not want to convert 'install.esd' to 'install.wim' because of low storage problem. Current 'WinNTSetup 3.6.1' also support 'install.esd' files. so please provide support of 'install.esd' files in the next release of 'Win8.1SE'. I highly need standalone 'Win8.1UpdateSE_x64_boot.wim' file. If you don't have any problem then please share a Resumable Download link of standalone 'Win8.1UpdateSE_x64_boot.wim' file with me. So that I can use both 'Win8.1UpdateSE_x64_boot.wim' and 'Easy2Boot' together in my USB Drive. ------------------------------------------------------------------------------------------------------------------------------- If possible then please add support of 'install.esd' in next version of 'Win8.1SE' -------------------------------------------------------------------------------------------------------------------------------- Thanks in Advance...............