Jump to content

WinNTSetup v5.3.5.1


JFX

Recommended Posts

I have used version 3.5b3 and tried Wimboot

Got everything working, but only Boot folder is made on my FAT32 USB-stick used as Boot Drive.

 

It means efi folder is not made, so that UEFI booting did not work initially.

I fixed with bcdboot to get also efi folder on USB-Stick and now everything works as desired. :)

 

My procedure:

After booting with New created Win8.1SE made from Win 8.1 Update 1 Enterprise Evaluation ISO then

I used MBR SATA harddisk with 3 primary NTFS partitions and did copy folder sources from mounted Setup ISO to the last partition.

The copy of install.wim in folder sources on last partition was selected as Setup Source in WinNTSetup3.

The FAT32 USB-Stick made with UFD_FORMAT.exe was Selected as Boot Drive,

Edited by wimb
Link to comment
Share on other sites


Hmm, I changed it to only create EFI boot files if the selected boot disk is an EFI system partition.

Cause there was a report here, that EFI files causing problem in MBR mode.

 

So you mean, you have a MBR USB-Stick with a FAT32 boot partition,

and you can boot that in (U)EFI without compatible mode?

 

Guess I really should add a check box for EFI files (and select it by default) :huh:

Link to comment
Share on other sites

So you mean, you have a MBR USB-Stick with a FAT32 boot partition,

and you can boot that in (U)EFI without compatible mode?

 

 

Yes, my USB-Stick with MBR and FAT32 format has now Boot and efi boot folders 

and I can boot from USB-Stick on UEFI computer in BIOS or UEFI Secure mode without any problem.

My NTFS System drive is on second internal MBR harddisk and install.wim is in folder sources of last partition of that harddisk.

I used this configuration since I did not want to make changes on my first internal GPT harddisk (with Win8 and hidden EFI partition)

 

It would be best when EFI Checkbox is there and selected by default :)

MBR is never a problem for UEFI Secure booting of Windows 8 OS

UEFI_MULTI  and UFD_FORMAT are using MBR for most compatibility and support BIOS + UEFI Secure Boot

http://www.911cd.net/forums//index.php?showtopic=25269

http://reboot.pro/topic/18182-uefi-multi-make-multi-boot-usb-drive/

http://reboot.pro/topic/17877-uefi-windows-8-bios-grub4dos-multiboot-usb-harddisk/

Edited by wimb
Link to comment
Share on other sites

Okay thanks for the info.

I added a combo box to Beta 4, with the 3 firmware option that bcdboot has.

As well as a new cmdline switch: -bcd:{ALL|BIOS|UEFI}

Link to comment
Share on other sites

- added WimBoot support

 

WinNTSetup does support normal WIM files for wimboot, means you don't have to capture them using the WimBoot command.

Can you clarify?

Yes, wimboot works, given a file *.wim already at wimboot format. Thanks.

What about a msdn DVD install.wim or a install.esd?

Do you export this files to wimboot format too?

I get a error message at <DVD:>\sources\install.wim: "Applying System image failed!"

A example to clarify the question

md W:\Scratchmd W:\Win8Dism /Export-Image /WIMBoot /SourceImageFile:D:\sources\Install.wim /SourceIndex:2 /DestinationImageFile:W:\Win8\wimboot.wim /scratchdir:W:\Scratchrd W:\Scratch
Link to comment
Share on other sites

Normally WimBoot only supports optimized WIM files, exported or captured with the /WimBoot parameter.

These files have XPRESS compression with smaller dictionary size.

However, normal XPRESS or LZX compressed WIM files can be used, too. But not esd files.

 

Not sure what's the exact requirement for WIM file placement, definitive not CDFS/UDF, maybe not even removable drives at all.

But for sure local NTFS drives.

Link to comment
Share on other sites

Hi JFX,

 

Thanks for latest winntsetup, it is working beautifully here. :D
 

 

People started to call recovery compressed wim files now install.esd instead of install.wim.

 

Seems Microsoft had the idea to call LZMS compressed wim files esd, too.

 

 

How do I apply an esd file?

 

I tried wimlib 1.6.3

 

wimlib-imagex.exe apply "C:\install.esd" "1" "F:\TEST"

 

[ERROR] Invalid resource entry (offset overflow)
ERROR: Exiting with error code 20:
       An entry in the WIM's lookup table is invalid.

 

Winntsetup latest applies it fine.

Edited by SIW2
Link to comment
Share on other sites

Yes, I am trying to do it without newest dism. Not everybody will have it, and it isn't in XP or pe3 usually. Winntsetup seems to be able to apply esd without 8.1 dism.

 

The idea is to apply esd to a folder, then capture as a wim.

Edited by SIW2
Link to comment
Share on other sites

 

 

- adding support for XP/2003 WIM files

 

JFX , a noob question. How to create a XP wim file to use this feature ?. May i need to use imagex to capture an installed XP ?. 

Link to comment
Share on other sites

JFX , a noob question. How to create a XP wim file to use this feature ?. May i need to use imagex to capture an installed XP ?. 

 

Yes, imagex will do, it.

Here's a small guide that looks good.

Link to comment
Share on other sites

jaclaz, was your second link meant to be the same as the one that JFX gave?  Your link gave me a "Not found" error.

 

Cheers and Regards

Strange, it works here.

The link JFX gave is to:

https://sites.google.com/site/vmwarethewiki/Create-WIM-images-of-Windows-XP-for-system-deployment

Which is wiki that begins with the text:

How to create a hardware independent sysprepped WIM image

which is the link I posted to the "base" document:

http://www.jerryblogger.com/2010/08/create-wim-image-of-windows-xp-for.html

 

jaclaz

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   1 member

×
×
  • Create New...