From: Paul Fertser <fercerpav@gmail.com>
To: Konstantin Klubnichkin <kitsok@yandex-team.ru>
Cc: openbmc <openbmc@lists.ozlabs.org>,
Alexander Amelkin <a.amelkin@yadro.com>,
Maciej Lawniczak <maciej.lawniczak@linux.intel.com>,
Thaj <tajudheenk@gmail.com>
Subject: Re: Installing Windows Server 2019 from a remotely mounted ISO
Date: Tue, 3 Aug 2021 16:37:07 +0300 [thread overview]
Message-ID: <20210803133707.GO875@home.paul.comp> (raw)
In-Reply-To: <34751627996896@mail.yandex-team.ru>
Hi Konstantin,
On Tue, Aug 03, 2021 at 04:26:52PM +0300, Konstantin Klubnichkin wrote:
> It's about Option 2 (preparing image on Linux).
> The sequence in the instruction is:
> 1. Create empty image using dd;
> 2. Create partition table on it with FAT32 partition;
> 3. Format image to FAT32 filesystem;
> 4. Prepare files from Windows DVD;
> 5. Mount image to some directory;
> 6. Copy files to that directory;
> 7. Unmount image.
>
> I can't get why to create partition table on the image(step 2) if the next step
> (formatting image with mkfs.vfat, step 3) destroys it?
Looks like a typo, s/image/partition/.
That said, booting windows installer shouldn't be anything special
with UEFI, basically you create GPT, EFI System partition on it, put
the windows EFI loader there with the right name plus some files it
needs, and then copy everything else to NTFS partition.
This should explain it with enough details:
https://techbit.ca/2019/02/creating-a-bootable-windows-10-uefi-usb-drive-using-linux/
HTH
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@gmail.com
next prev parent reply other threads:[~2021-08-03 13:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 10:32 Installing Windows Server 2019 from a remotely mounted ISO Alexander Amelkin
2020-10-21 7:32 ` Thaj
2020-10-22 11:37 ` Maciej Lawniczak
2020-10-22 18:14 ` Patrick Williams
[not found] ` <34751627996896@mail.yandex-team.ru>
2021-08-03 13:37 ` Paul Fertser [this message]
[not found] ` <1341627999924@mail.yandex-team.ru>
2021-08-03 14:29 ` Paul Fertser
2021-08-03 13:52 ` i.kononenko
[not found] ` <6631628004052@mail.yandex-team.ru>
2021-08-03 15:40 ` i.kononenko
2021-08-04 1:50 ` Troy Lee
2021-08-04 2:10 ` i.kononenko
2021-08-04 3:17 ` Troy Lee
2021-08-04 11:40 ` i.kononenko
[not found] ` <9921666089829@mail.yandex-team.ru>
2022-10-18 11:01 ` i.kononenko
2022-10-18 11:05 ` Paul Fertser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210803133707.GO875@home.paul.comp \
--to=fercerpav@gmail.com \
--cc=a.amelkin@yadro.com \
--cc=kitsok@yandex-team.ru \
--cc=maciej.lawniczak@linux.intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=tajudheenk@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).