Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


ilko_t

How to install Windows from USB- WinSetupFromUSB with GUI

Recommended Posts

ISO file size is 4 217 568 KiB x 1024 = 4 318 789 632 bytes. FAT32 maximum supported file size is 4 294 967 295 bytes, so everything is as it should be, the warning is correct, since the whole ISO file is going to be copied.

You have the following options with this ISO:

1) Use FAT32 and 1.0 beta versions, which do not copy the whole ISO, but support only one source of this type. If you need EFI, it should need no further modifications if source is Windows 8.X

2) Use 1.0 and later versions and NTFS, multiple sources of this kind are supported, but no EFI support with NTFS, unless you load a NTFS driver, for EFI or motherboard manufacturer added NTFS EFI driver.

http://www.rodsbooks.com/refind/drivers.html

http://forums.mydigitallife.info/threads/46981-Install-Win8-Windows-8-1-UEFI-With-a-Over-sized%28over-4GB%29-install-wim

Ok, thanks. Thou shalt not return the old way as an additional?

Share this post


Link to post
Share on other sites

One could always use any of the beta versions to add it the old way, I wouldn't add it as an option for now, unless there is lots of interest in such option.

Share this post


Link to post
Share on other sites

Ok. But I still torments the previous question. Program, as I understand it, turns the image to stick, and not at her blankly copies the image file. Then why the author evaluates the maximum size as the image, rather than contained within the image file with a maximum size, ie install.esd?

Share this post


Link to post
Share on other sites

ISO file size is 4 217 568 KiB x 1024 = 4 318 789 632 bytes. FAT32 maximum supported file size is 4 294 967 295 bytes, so everything is as it should be, the warning is correct, since the whole ISO file is going to be copied.

...

Again, the image is copied as is, the whole ISO, it is not extracted. Have a look at the contents of <USB disk>\WINSETUP\W71\ or whatever the name of the directory is, there are boot.wim and WindowsXYZ.ISO. How do you fit larger than 4GB WindowsXYZ.ISO on FAT32? :)

Share this post


Link to post
Share on other sites

ISO file size is 4 217 568 KiB x 1024 = 4 318 789 632 bytes. FAT32 maximum supported file size is 4 294 967 295 bytes, so everything is as it should be, the warning is correct, since the whole ISO file is going to be copied.

...

Again, the image is copied as is, the whole ISO, it is not extracted. Have a look at the contents of <USB disk>\WINSETUP\W71\ or whatever the name of the directory is, there are boot.wim and WindowsXYZ.ISO. How do you fit larger than 4GB WindowsXYZ.ISO on FAT32? :)

I understand that the loader will start directly from the image. And UEFI, respectively, will be. In my case optionally use fat32?

Share this post


Link to post
Share on other sites

I don't quite understand your question, lost in translation.

Vista and later setup currently works like this:

BIOS/legacy mode:
boot device-->MBR-->grub4dos is loaded-->bootmgr (reads BCD store)-->boot.wim -->install imdisk driver and mount the ISO file as virtual DVD-->start Setup

EFI mode:
FAT32 partition/efi/bootx64.efi (reads BCD store)-->boot.wim-->install imdisk driver and mount the ISO file as virtual DVD-->start Setup
Typical EFI firmware supports FAT32, no NTFS.
For NTFS and EFI, load a NTFS driver.

Again:

You have the following options with this ISO:
1) Use FAT32 and 1.0 beta versions, which do not copy the whole ISO, but support only one source of this type. If you need EFI, it should need no further modifications if source is Windows 8.X
2) Use 1.0 and later versions and NTFS, multiple sources of this kind are supported, but no EFI support with NTFS, unless you load a NTFS driver, for EFI or motherboard manufacturer added NTFS EFI driver.

http://www.rodsbooks.com/refind/drivers.html
http://forums.mydigitallife.info/threads/46981-Install-Win8-Windows-8-1-UEFI-With-a-Over-sized(over-4GB)-install-wim

Share this post


Link to post
Share on other sites

Hi all, I am try creating usb mutil boot by winsetupfromusb. I have a trouble, when I add winpe to usb, the program show a notice "... I386, Programs or Program Files ... could not be found ..." I tried find the answer on gg but "could not be found" =.=" what should I do now? ps: I use winsetupfromusb 1.2, and this is link to download win7pex86 [link removed](the name is Julia,named by creator)

Edited by ilko_t
Link removed

Share this post


Link to post
Share on other sites

You are using the option to add PE1, XP/2003 based, whereas your source considering its name seems to be PE3, Windows 7 based. Use the Vista/7.... option and provide path to the ISO file.

Share this post


Link to post
Share on other sites

I'll have this fixed in the next version which should be out soon, just need to accumulate more changes to release it.

The problem with this source is that there is folder EFI but most likely there is no BCD file in \efi\microsoft\boot\ and program fails when trying to update it, since it's missing. I've added a few more checks which should eliminate such errors.

Meanwhile, I think this source could also be added using the third option "Linux ISO/Other Grub4dos compatible ISO" if there are no files needed for the booted WinPE outside boot.wim.

Thanks for reporting.

Share this post


Link to post
Share on other sites

I'll have this fixed in the next version which should be out soon, just need to accumulate more changes to release it.

The problem with this source is that there is folder EFI but most likely there is no BCD file in \efi\microsoft\boot\ and program fails when trying to update it, since it's missing. I've added a few more checks which should eliminate such errors.

Meanwhile, I think this source could also be added using the third option "Linux ISO/Other Grub4dos compatible ISO" if there are no files needed for the booted WinPE outside boot.wim.

Thanks for reporting.

seem you are right with my trouble. I try adding another winpe what version have file BCD in \efi\microsoft\boot\, and this works!

about the third option, I am afraid that I don't have answer. by the ways, thanks for your support!

Edited by damtac84

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...