laddanator Posted December 13, 2018 Posted December 13, 2018 3 minutes ago, Lara Ban said: I made image by Gimagex 2.1.1 and 2.2.0, the result is the same. And this image successfully opened in DISM. Curious if you used "Wimlib" to make the wim would the results be different?
Lara Ban Posted December 13, 2018 Posted December 13, 2018 (edited) 21 minutes ago, laddanator said: Curious if you used "Wimlib" to make the wim would the results be different? I don't know exactly, I'm not a professional. Maybe you will try to make wim image from Windows 10 build 1809? Edited December 13, 2018 by Lara Ban
JFX Posted December 13, 2018 Author Posted December 13, 2018 I have not problem with gimagex, it produces a correct wim file.
Lara Ban Posted December 13, 2018 Posted December 13, 2018 4 hours ago, JFX said: I have not problem with gimagex, it produces a correct wim file. Ok, I will check this again tomorrow.
blipton Posted January 20, 2019 Posted January 20, 2019 I'm having some issue, I'm sure it's my setup not WinNtSetup.. but I'm trying to create a windows 7 x86 drive that runs off a usb. When I try to boot it (initially using Virtualbox but eventually on actual x86 pc) the bios complains that there is no operating system. I'm running WinNtstup on a Win7 x64 machine, and the usb drive is 16gb which should be plenty for the Win7x86 ISO I'm trying to use as the source. I haven't tried using the command line interface in fear of wiping out my main drive.. can anyone suggest a command-line to try to create this 'live' usb install?
click-click Posted January 21, 2019 Posted January 21, 2019 (edited) @JFX Does the Disable the new taskbar icons of Windows 10 setting give you the old icons back? Can you post the reg entry for this so I can try it out to see what it does without having to install? Edited January 21, 2019 by click-click
JFX Posted January 21, 2019 Author Posted January 21, 2019 @blipton Make sure the 3 icons next to boot drive are green. @click-click Not sure what you mean with old icons? The tweak only removes cortana, task switch and people icons from taskbar. The 3 options you also have on the taskbar right click menu.
click-click Posted January 21, 2019 Posted January 21, 2019 (edited) Okay, that's what I was thinking, but by chance I thought there might be a different set off system icons for the notification area. I just hate the big "^" icon when not showing all icons. Edited January 21, 2019 by click-click
vladislays Posted January 23, 2019 Posted January 23, 2019 (edited) Tell me please, what is this error? Edited January 23, 2019 by vladislays
JFX Posted January 23, 2019 Author Posted January 23, 2019 The error comes from bcdboot.exe, see G:\Windows\WinNTSetup.log for more informations.
vladislays Posted January 23, 2019 Posted January 23, 2019 I do not understand what's the matter? WinNTSetup.log
JFX Posted January 24, 2019 Author Posted January 24, 2019 Ah, ok my mistake, seems it uses bcdboot.exe from your system32 directory and that one does not accept the firmware switch. I'll fix this later, but older version should work for you: http://jfx.square7.ch/WinNTSetup/WinNTSetup392.rar 1
vladislays Posted January 24, 2019 Posted January 24, 2019 7 hours ago, JFX said: uses bcdboot.exe from your system32 directory Now it is clear. Yes, in version 3.9.2 it works. Thank you for the great program!
alacran Posted January 26, 2019 Posted January 26, 2019 (edited) @JFX I have made several Wimboot installs (Win 7 & Win 8.1) using diferent levels of compression, depending on CPU performance. All working fine even on VHDs. I know the option Wimboot Compact: NONE is there since some time ago, Could you please explain me what is the use of these option? As far as I understand it is a Wimboot install without compression, so far good, but what is the benefit in making a Wimboot install then? I never think about its use before and maybe I am not using a good feature of your great tool. alacran Edited January 26, 2019 by alacran
JFX Posted January 27, 2019 Author Posted January 27, 2019 NONE option does not compress any file, but adds the wofadk.sys driver and copies the WimBootCompress.ini to System32 folder. So this new install can read WOF compressed files and is ready to be compressed later. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now