Syslinux - Nov 2017 - FW: Help for setting up windows unattended installation

Hi.

I have looked at
PXElinux<http://www.syslinux.org/wiki/index.php?title=PXELINUX> to
understand all this, but I'm very sorry I don't.

I have managed to setup to boot from PXELinux, but I'm not an expert on how
to setup a menu file for making a windows unattended installation.

Could someone help me with that?

Is there some kind of a forum for this or is it just by email?

Best regards / Med venlig hilsen
Kenneth Vandb?k
This e-mail is intended solely for the use of the individual or entity to whom
it is addressed and its
content shall be regarded as confidential unless explicitly stated otherwise. If
you have received this e-mail
by mistake, please notify the sender immediately by e-mail and delete this
e-mail from your system.
[cid:image003.png at 01D25AC2.9D676540]Please consider the environment before
printing this message

-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1338 bytes
Desc: image001.png
URL:
<http://www.zytor.com/pipermail/syslinux/attachments/20171124/045f795c/attachment.png>

On Fri, Nov 24, 2017 at 8:24 AM, Kenneth Vandb?k via Syslinux
<syslinux at zytor.com> wrote:
> Hi.
>
> I have looked at
PXElinux<http://www.syslinux.org/wiki/index.php?title=PXELINUX> to
understand all this, but I'm very sorry I don't.
>
> I have managed to setup to boot from PXELinux, but I'm not an expert on
how to setup a menu file for making a windows unattended installation.
So you're at the point where PXELINUX successfully loads and you have
a config loading of some sort?  What's your config currently look
like?  Is this a BIOS/legacy system?

Regarding an unattended install of Windows, how do you plan to do
this?  Do you want to chain-load to a WDS system?  Restore an image
with a tool like Clonezilla??  There's lots of options here without
knowing the details.
> Could someone help me with that?
>
> Is there some kind of a forum for this or is it just by email?
Web forum?  No.  IRC?  Yes, but unless you find someone active at the
time, you might have to wait for any sort of answer.
> Best regards / Med venlig hilsen
> Kenneth Vandb?k

-- 
-Gene

On Fri, Nov 24, 2017 at 09:07:22AM -0500, Gene Cumm
wrote:
> On Fri, Nov 24, 2017 at 8:24 AM, Kenneth Vandb?k wrote:
> > Hi.
> >
> > I have looked at
> > PXElinux<http://www.syslinux.org/wiki/index.php?title=PXELINUX>
> > to understand all this, but I'm very sorry I don't.
> >
> > I have managed to setup to boot from PXELinux, but I'm not an
> > expert on how to setup a menu file for making a windows unattended
> > installation.
> 
> So you're at the point where PXELINUX successfully loads and you have
> a config loading of some sort?  What's your config currently look
> like?  Is this a BIOS/legacy system?
> 
> Regarding an unattended install of Windows, how do you plan to do
> this?  Do you want to chain-load to a WDS system?  Restore an image
> with a tool like Clonezilla??  There's lots of options here without
> knowing the details.
> 
> > Could someone help me with that?
> >
> > Is there some kind of a forum for this or is it just by email?
> 
> Web forum?  No.  IRC?  Yes, but unless you find someone active at the
> time, you might have to wait for any sort of answer.
> 
Karma bonus points for publishing / documenting install procedure.


Groeten
Geert Stappers
-- 
Leven en laten leven

Hi,

I'm not sure what you call it, but I do not use EFI, so I guess it is
BIOS/legacy system.

My idea was to have the option to install windows 7 on my computer and it
should install drivers that's not recognized in the install progress.

My default file is this:

DEFAULT menu.c32
 PROMPT 0

 MENU TITLE PXE Special Boot Menu
 MENU INCLUDE pxelinux.cfg/graphics.conf
 MENU AUTOBOOT Starting Local System in # seconds

 LABEL bootlocal
   MENU LABEL ^Boot Point of Sale
   MENU DEFAULT
   LOCALBOOT 0
 TIMEOUT 80
 TOTALTIMEOUT 9000

 LABEL SetupMenu
   MENU LABEL ^Setup Menu
   KERNEL menu.c32
   APPEND pxelinux.cfg/graphics.conf pxelinux.cfg/setup.menu

and my setup.menu file is this:

 MENU TITLE Setup Menu

 LABEL MainMenu
   MENU LABEL ^Return to Main Menu
   KERNEL menu.c32
   APPEND pxelinux.cfg/default

 LABEL E6320
   MENU LABEL ^Latitude E6320
   KERNEL   "<---- Don't know what to choose here"
   APPEND   "<---- Don't know what to choose here"

Br Kenneth

> -----Original Message-----
> From: Gene Cumm [mailto:gene.cumm at gmail.com]
> Sent: 24. november 2017 15:07
> To: Kenneth Vandb?k <kenneth.vandbek at alfalaval.com>
> Cc: syslinux at zytor.com
> Subject: Re: [syslinux] Help for setting up windows unattended installation
>
> On Fri, Nov 24, 2017 at 8:24 AM, Kenneth Vandb?k via Syslinux <
> syslinux at zytor.com> wrote:
> > Hi.
> >
> > I have looked at PXElinux<http://www.syslinux.o
> rg/wiki/index.php?title=PXELINUX> to understand all this, but I'm
very
> sorry I don't.
> >
> > I have managed to setup to boot from PXELinux, but I'm not an
expert on
> how to setup a menu file for making a windows unattended installation.
>
> So you're at the point where PXELINUX successfully loads and you have a
> config loading of some sort?  What's your config currently look like? 
Is
> this a BIOS/legacy system?
>
> Regarding an unattended install of Windows, how do you plan to do this?
> Do you want to chain-load to a WDS system?  Restore an image with a tool
> like Clonezilla??  There's lots of options here without knowing the
details.
>
> > Could someone help me with that?
> >
> > Is there some kind of a forum for this or is it just by email?
>
> Web forum?  No.  IRC?  Yes, but unless you find someone active at the
> time, you might have to wait for any sort of answer.
>
> > Best regards / Med venlig hilsen
> > Kenneth Vandb?k
>
>
> --
> -Gene
>

Hi,

I'm not sure what you call it, but I do not use EFI, so I guess it is
BIOS/legacy system.

My idea was to have the option to install windows 7 on my computer and it should
install drivers that's not recognized in the install progress.

My default file is this:

DEFAULT menu.c32
 PROMPT 0
 
 MENU TITLE PXE Special Boot Menu
 MENU INCLUDE pxelinux.cfg/graphics.conf
 MENU AUTOBOOT Starting Local System in # seconds
 
 LABEL bootlocal
   MENU LABEL ^Boot Point of Sale
   MENU DEFAULT
   LOCALBOOT 0
 TIMEOUT 80
 TOTALTIMEOUT 9000
 
 LABEL SetupMenu
   MENU LABEL ^Setup Menu
   KERNEL menu.c32
   APPEND pxelinux.cfg/graphics.conf pxelinux.cfg/setup.menu

and my setup.menu file is this:

 MENU TITLE Setup Menu
 
 LABEL MainMenu
   MENU LABEL ^Return to Main Menu
   KERNEL menu.c32
   APPEND pxelinux.cfg/default
 
 LABEL E6320
   MENU LABEL ^Latitude E6320
   KERNEL   "<---- Don't know what to choose here"
   APPEND   "<---- Don't know what to choose here"

Nr
Kenneth
> Den 25. nov. 2017 kl. 16.23 skrev Kenneth Vandb?k <valnurat at
gmail.com>:
> 
> Hi,
> 
> I'm not sure what you call it, but I do not use EFI, so I guess it is
BIOS/legacy system.
> 
> My idea was to have the option to install windows 7 on my computer and it
should install drivers that's not recognized in the install progress.
> 
> My default file is this:
> 
> DEFAULT menu.c32
>  PROMPT 0
>  
>  MENU TITLE PXE Special Boot Menu
>  MENU INCLUDE pxelinux.cfg/graphics.conf
>  MENU AUTOBOOT Starting Local System in # seconds
>  
>  LABEL bootlocal
>    MENU LABEL ^Boot Point of Sale
>    MENU DEFAULT
>    LOCALBOOT 0
>  TIMEOUT 80
>  TOTALTIMEOUT 9000
>  
>  LABEL SetupMenu
>    MENU LABEL ^Setup Menu
>    KERNEL menu.c32
>    APPEND pxelinux.cfg/graphics.conf pxelinux.cfg/setup.menu
> 
> and my setup.menu file is this:
> 
>  MENU TITLE Setup Menu
>  
>  LABEL MainMenu
>    MENU LABEL ^Return to Main Menu
>    KERNEL menu.c32
>    APPEND pxelinux.cfg/default
>  
>  LABEL E6320
>    MENU LABEL ^Latitude E6320
>    KERNEL   "<---- Don't know what to choose here"
>    APPEND   "<---- Don't know what to choose here"
> 
> Br Kenneth
> 
>> 
>> -----Original Message-----
>> From: Gene Cumm [mailto:gene.cumm at gmail.com]
>> Sent: 24. november 2017 15:07
>> To: Kenneth Vandb?k <kenneth.vandbek at alfalaval.com>
>> Cc: syslinux at zytor.com
>> Subject: Re: [syslinux] Help for setting up windows unattended
installation
>> 
>> On Fri, Nov 24, 2017 at 8:24 AM, Kenneth Vandb?k via Syslinux
<syslinux at zytor.com> wrote:
>> > Hi.
>> >
>> > I have looked at
PXElinux<http://www.syslinux.org/wiki/index.php?title=PXELINUX> to
understand all this, but I'm very sorry I don't.
>> >
>> > I have managed to setup to boot from PXELinux, but I'm not an
expert on how to setup a menu file for making a windows unattended installation.
>> 
>> So you're at the point where PXELINUX successfully loads and you
have a config loading of some sort?  What's your config currently look like?
Is this a BIOS/legacy system?
>> 
>> Regarding an unattended install of Windows, how do you plan to do this?
Do you want to chain-load to a WDS system?  Restore an image with a tool like
Clonezilla??  There's lots of options here without knowing the details.
>> 
>> > Could someone help me with that?
>> >
>> > Is there some kind of a forum for this or is it just by email?
>> 
>> Web forum?  No.  IRC?  Yes, but unless you find someone active at the
time, you might have to wait for any sort of answer.
>> 
>> > Best regards / Med venlig hilsen
>> > Kenneth Vandb?k
>> 
>> 
>> --
>> -Gene
>

On Sat, Nov 25, 2017 at 10:23 AM, Kenneth Vandb?k <valnurat at gmail.com>
wrote:
> Hi,
>
> I'm not sure what you call it, but I do not use EFI, so I guess it is
> BIOS/legacy system.
Correct.
> My idea was to have the option to install windows 7 on my computer and it
> should install drivers that's not recognized in the install progress.
Let's re-order this and tune it.
> My default file is this:
# default begin
DEFAULT bootlocal
PROMPT 0
UI menu.c32
TIMEOUT 80
TOTALTIMEOUT 9000

MENU TITLE PXE Special Boot Menu
MENU INCLUDE pxelinux.cfg/graphics.conf
MENU AUTOBOOT Starting Local System in # seconds

LABEL bootlocal
  MENU LABEL ^Boot Point of Sale
  MENU DEFAULT
  LOCALBOOT 0

# I can't be certain the hotkey works
MENU INCLUDE pxelinux.cfg/setup.menu ^Setup Menu

# Or run this with a MENU BEGIN/MENU END
# default end

# setup.menu begin
MENU TITLE Setup Menu

LABEL MainMenu
  MENU LABEL ^Return to Main Menu
  MENU GOTO .top

LABEL E6320
  MENU LABEL ^Latitude E6320
  KERNEL   "<---- Don't know what to choose here"
  APPEND   "<---- Don't know what to choose here"
# setup.menu end


OK, now that we have some basic style solved...


Your last label is where things get rather interesting.  You could use
wimboot ( http://ipxe.org/wimboot ) to load a WIM that has sufficient
drivers to load the installer from another location like say a
SMB/Samba/CIFS share.  You could boot CloneZilla though this won't
give you the option of loading more drivers very well.


-- 
-Gene
>> -----Original Message-----
>> From: Gene Cumm [mailto:gene.cumm at gmail.com]
>> Sent: 24. november 2017 15:07
>> To: Kenneth Vandb?k <kenneth.vandbek at alfalaval.com>
>> Cc: syslinux at zytor.com
>> Subject: Re: [syslinux] Help for setting up windows unattended
>> installation
>>
>> On Fri, Nov 24, 2017 at 8:24 AM, Kenneth Vandb?k via Syslinux
>> <syslinux at zytor.com> wrote:
>> > Hi.
>> >
>> > I have looked at
>> >
PXElinux<http://www.syslinux.org/wiki/index.php?title=PXELINUX> to
>> > understand all this, but I'm very sorry I don't.
>> >
>> > I have managed to setup to boot from PXELinux, but I'm not an
expert on
>> > how to setup a menu file for making a windows unattended
installation.
>>
>> So you're at the point where PXELINUX successfully loads and you
have a
>> config loading of some sort?  What's your config currently look
like?  Is
>> this a BIOS/legacy system?
>>
>> Regarding an unattended install of Windows, how do you plan to do this?
>> Do you want to chain-load to a WDS system?  Restore an image with a
tool
>> like Clonezilla??  There's lots of options here without knowing the
details.
>>
>> > Could someone help me with that?
>> >
>> > Is there some kind of a forum for this or is it just by email?
>>
>> Web forum?  No.  IRC?  Yes, but unless you find someone active at the
>> time, you might have to wait for any sort of answer.

On Sun, Nov 26, 2017 at 8:38 AM, Kenneth Vandb?k <valnurat at gmail.com>
wrote:
> I looked at the link and it seems to this is what I need to do.
> I have copied wimboot file to my \tftpboot directory, but it seems it
can't
> find the file in the progress.
>
> I have a QNAP nas for this.
>
> This is my setup.menu file:
>
>  MENU TITLE Setup Menu
>
>  LABEL MainMenu
>    MENU LABEL ^Return to Main Menu
>    KERNEL menu.c32
>    APPEND pxelinux.cfg/default
>
>  LABEL E6320
>    MENU LABEL ^Latitude E6320
>    KERNEL Wimboot pause
>    APPEND initrd=Suse/initrd92 ramdisk_size=65536 vga=0 textmode=1
> install=http://IPADDR serverdir=/9.2/install
> autoyast=http://IPADDR/9.2/scripts/ay92.xml  "<---- Don't know
what to
> choose here"
>
> When I run it can't find my wimboot file. My logfile looks like this:
>
> This is the logfile:
> /share/MD0_DATA/Public/tftpboot/pxelinux.0, 34 Blocks Served
> /share/MD0_DATA/Public/tftpboot/ldlinux.c32, 88 Blocks Served
>
/share/MD0_DATA/Public/tftpboot/pxelinux.cfg/44454c4c-3100-1044-8031-c3c04f52334a,
> No Such File/No Access
> /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/01-00-21-70-94-87-c4, No Such
> File/No Access
> /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/C0A80178, No Such File/No
> Access
> /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/C0A8017, No Such File/No
Access
> /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/C0A801, No Such File/No Access
> /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/C0A80, No Such File/No Access
> /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/C0A8, No Such File/No Access
> /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/C0A, No Such File/No Access
> /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/C0, No Such File/No Access
> /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/C, No Such File/No Access
> /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/default, 2 Blocks Served
> /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/graphics.conf, 2 Blocks Served
> /share/MD0_DATA/Public/tftpboot/menu.c32, 20 Blocks Served
> /share/MD0_DATA/Public/tftpboot/libutil.c32, 19 Blocks Served
> /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/default, 2 Blocks Served
> /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/graphics.conf, 2 Blocks Served
> /share/MD0_DATA/Public/tftpboot/menu.c32, 20 Blocks Served
> /share/MD0_DATA/Public/tftpboot/libutil.c32, 19 Blocks Served
> /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/graphics.conf, 2 Blocks Served
> /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/setup.menu, 2 Blocks Served
> /share/MD0_DATA/Public/tftpboot/Wimboot, No Such File/No Access
> /share/MD0_DATA/Public/tftpboot/Wimboot, No Such File/No Access
> /share/MD0_DATA/Public/tftpboot/Wimboot, No Such File/No Access
> /share/MD0_DATA/Public/tftpboot/Wimboot, No Such File/No Access
> /share/MD0_DATA/Public/tftpboot/Wimboot, No Such File/No Access
> /share/MD0_DATA/Public/tftpboot/Wimboot, No Such File/No Access
Case matters.  Permissions matter.  Wimboot is not wimboot.

> I'm not sure I do this right, but it looks like I need to create a
boot.ipxe
> file. So maybe this is wrong what I do.
> Should I do create this file and how do you load that file?
iPXE is a PXE-firmware replacement and bootloader.  In this instance,
it's not necessarily required yet.  You need to worry about filenames
and permissions first.

-- 
-Gene
> 2017-11-25 22:03 GMT+01:00 Gene Cumm <gene.cumm at gmail.com>:
>>
>> On Sat, Nov 25, 2017 at 10:23 AM, Kenneth Vandb?k <valnurat at
gmail.com>
>> wrote:
>> > Hi,
>> >
>> > I'm not sure what you call it, but I do not use EFI, so I
guess it is
>> > BIOS/legacy system.
>>
>> Correct.
>>
>> > My idea was to have the option to install windows 7 on my computer
and
>> > it
>> > should install drivers that's not recognized in the install
progress.
>>
>> Let's re-order this and tune it.
>>
>> > My default file is this:
>>
>> # default begin
>> DEFAULT bootlocal
>> PROMPT 0
>> UI menu.c32
>> TIMEOUT 80
>> TOTALTIMEOUT 9000
>>
>> MENU TITLE PXE Special Boot Menu
>> MENU INCLUDE pxelinux.cfg/graphics.conf
>> MENU AUTOBOOT Starting Local System in # seconds
>>
>> LABEL bootlocal
>>   MENU LABEL ^Boot Point of Sale
>>   MENU DEFAULT
>>   LOCALBOOT 0
>>
>> # I can't be certain the hotkey works
>> MENU INCLUDE pxelinux.cfg/setup.menu ^Setup Menu
>>
>> # Or run this with a MENU BEGIN/MENU END
>> # default end
>>
>> # setup.menu begin
>> MENU TITLE Setup Menu
>>
>> LABEL MainMenu
>>   MENU LABEL ^Return to Main Menu
>>   MENU GOTO .top
>>
>> LABEL E6320
>>   MENU LABEL ^Latitude E6320
>>   KERNEL   "<---- Don't know what to choose here"
>>   APPEND   "<---- Don't know what to choose here"
>> # setup.menu end
>>
>>
>> OK, now that we have some basic style solved...
>>
>>
>> Your last label is where things get rather interesting.  You could use
>> wimboot ( http://ipxe.org/wimboot ) to load a WIM that has sufficient
>> drivers to load the installer from another location like say a
>> SMB/Samba/CIFS share.  You could boot CloneZilla though this won't
>> give you the option of loading more drivers very well.
>>
>>
>> --
>> -Gene
>>
>> >> -----Original Message-----
>> >> From: Gene Cumm [mailto:gene.cumm at gmail.com]
>> >> Sent: 24. november 2017 15:07
>> >> To: Kenneth Vandb?k <kenneth.vandbek at alfalaval.com>
>> >> Cc: syslinux at zytor.com
>> >> Subject: Re: [syslinux] Help for setting up windows unattended
>> >> installation
>> >>
>> >> On Fri, Nov 24, 2017 at 8:24 AM, Kenneth Vandb?k via Syslinux
>> >> <syslinux at zytor.com> wrote:
>> >> > Hi.
>> >> >
>> >> > I have looked at
>> >> >
PXElinux<http://www.syslinux.org/wiki/index.php?title=PXELINUX> to
>> >> > understand all this, but I'm very sorry I don't.
>> >> >
>> >> > I have managed to setup to boot from PXELinux, but
I'm not an expert
>> >> > on
>> >> > how to setup a menu file for making a windows unattended
>> >> > installation.
>> >>
>> >> So you're at the point where PXELINUX successfully loads
and you have a
>> >> config loading of some sort?  What's your config currently
look like?
>> >> Is
>> >> this a BIOS/legacy system?
>> >>
>> >> Regarding an unattended install of Windows, how do you plan to
do this?
>> >> Do you want to chain-load to a WDS system?  Restore an image
with a
>> >> tool
>> >> like Clonezilla??  There's lots of options here without
knowing the
>> >> details.
>> >>
>> >> > Could someone help me with that?
>> >> >
>> >> > Is there some kind of a forum for this or is it just by
email?
>> >>
>> >> Web forum?  No.  IRC?  Yes, but unless you find someone active
at the
>> >> time, you might have to wait for any sort of answer.

On Tue, Dec 5, 2017 at 1:11 PM, Kenneth Vandb?k <valnurat at gmail.com>
wrote:
> I found out that "wimboot" has to be lowercase.
Merely match what the tftpd will work with.
> Now wimboot, but I get this problem as the attachmen shows.
>
> My configfile is like this:
>
> # setup.menu begin
> MENU TITLE Setup Menu
> LABEL MainMenu
>   MENU LABEL ^Return to Main Menu
>   MENU GOTO .top
>
> LABEL E6320
>   MENU LABEL ^Latitude E6320
>   KERNEL wimboot
>   append initrd=Windows7SP2/boot/bcd
>   append initrd=Windows7SP2/boot/boot.sdi
>   append initrd=Windows7SP2/sources/boot.wim
APPEND
initrd=Windows7SP2/boot/bcd,Windows7SP2/boot/boot.sdi,Windows7SP2/sources/boot.wim

Multiple APPENDs override each other, hence why ONLY the last file was loaded.
> 2017-11-26 16:18 GMT+01:00 Gene Cumm <gene.cumm at gmail.com>:
>>
>> On Sun, Nov 26, 2017 at 8:38 AM, Kenneth Vandb?k <valnurat at
gmail.com>
>> wrote:
>> > I looked at the link and it seems to this is what I need to do.
>> > I have copied wimboot file to my \tftpboot directory, but it seems
it
>> > can't
>> > find the file in the progress.
>> >
>> > I have a QNAP nas for this.
>> >
>> > This is my setup.menu file:
>> >
>> >  MENU TITLE Setup Menu
>> >
>> >  LABEL MainMenu
>> >    MENU LABEL ^Return to Main Menu
>> >    KERNEL menu.c32
>> >    APPEND pxelinux.cfg/default
>> >
>> >  LABEL E6320
>> >    MENU LABEL ^Latitude E6320
>> >    KERNEL Wimboot pause
>> >    APPEND initrd=Suse/initrd92 ramdisk_size=65536 vga=0 textmode=1
>> > install=http://IPADDR serverdir=/9.2/install
>> > autoyast=http://IPADDR/9.2/scripts/ay92.xml  "<----
Don't know what to
>> > choose here"
>> >
>> > When I run it can't find my wimboot file. My logfile looks
like this:
>> >
>> > This is the logfile:
>> > /share/MD0_DATA/Public/tftpboot/pxelinux.0, 34 Blocks Served
>> > /share/MD0_DATA/Public/tftpboot/ldlinux.c32, 88 Blocks Served
>> >
>> >
/share/MD0_DATA/Public/tftpboot/pxelinux.cfg/44454c4c-3100-1044-8031-c3c04f52334a,
>> > No Such File/No Access
>> > /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/01-00-21-70-94-87-c4,
No
>> > Such
>> > File/No Access
>> > /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/C0A80178, No Such
File/No
>> > Access
>> > /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/C0A8017, No Such
File/No
>> > Access
>> > /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/C0A801, No Such
File/No
>> > Access
>> > /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/C0A80, No Such
File/No
>> > Access
>> > /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/C0A8, No Such File/No
>> > Access
>> > /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/C0A, No Such File/No
Access
>> > /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/C0, No Such File/No
Access
>> > /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/C, No Such File/No
Access
>> > /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/default, 2 Blocks
Served
>> > /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/graphics.conf, 2
Blocks
>> > Served
>> > /share/MD0_DATA/Public/tftpboot/menu.c32, 20 Blocks Served
>> > /share/MD0_DATA/Public/tftpboot/libutil.c32, 19 Blocks Served
>> > /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/default, 2 Blocks
Served
>> > /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/graphics.conf, 2
Blocks
>> > Served
>> > /share/MD0_DATA/Public/tftpboot/menu.c32, 20 Blocks Served
>> > /share/MD0_DATA/Public/tftpboot/libutil.c32, 19 Blocks Served
>> > /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/graphics.conf, 2
Blocks
>> > Served
>> > /share/MD0_DATA/Public/tftpboot/pxelinux.cfg/setup.menu, 2 Blocks
Served
>> > /share/MD0_DATA/Public/tftpboot/Wimboot, No Such File/No Access
>> > /share/MD0_DATA/Public/tftpboot/Wimboot, No Such File/No Access
>> > /share/MD0_DATA/Public/tftpboot/Wimboot, No Such File/No Access
>> > /share/MD0_DATA/Public/tftpboot/Wimboot, No Such File/No Access
>> > /share/MD0_DATA/Public/tftpboot/Wimboot, No Such File/No Access
>> > /share/MD0_DATA/Public/tftpboot/Wimboot, No Such File/No Access
>>
>> Case matters.  Permissions matter.  Wimboot is not wimboot.
>>
>>
>> > I'm not sure I do this right, but it looks like I need to
create a
>> > boot.ipxe
>> > file. So maybe this is wrong what I do.
>> > Should I do create this file and how do you load that file?
>>
>> iPXE is a PXE-firmware replacement and bootloader.  In this instance,
>> it's not necessarily required yet.  You need to worry about
filenames
>> and permissions first.
>>
>> --
>> -Gene
>>
>> > 2017-11-25 22:03 GMT+01:00 Gene Cumm <gene.cumm at
gmail.com>:
>> >>
>> >> On Sat, Nov 25, 2017 at 10:23 AM, Kenneth Vandb?k <valnurat
at gmail.com>
>> >> wrote:
>> >> > Hi,
>> >> >
>> >> > I'm not sure what you call it, but I do not use EFI,
so I guess it is
>> >> > BIOS/legacy system.
>> >>
>> >> Correct.
>> >>
>> >> > My idea was to have the option to install windows 7 on my
computer
>> >> > and
>> >> > it
>> >> > should install drivers that's not recognized in the
install progress.
>> >>
>> >> Let's re-order this and tune it.
>> >>
>> >> > My default file is this:
>> >>
>> >> # default begin
>> >> DEFAULT bootlocal
>> >> PROMPT 0
>> >> UI menu.c32
>> >> TIMEOUT 80
>> >> TOTALTIMEOUT 9000
>> >>
>> >> MENU TITLE PXE Special Boot Menu
>> >> MENU INCLUDE pxelinux.cfg/graphics.conf
>> >> MENU AUTOBOOT Starting Local System in # seconds
>> >>
>> >> LABEL bootlocal
>> >>   MENU LABEL ^Boot Point of Sale
>> >>   MENU DEFAULT
>> >>   LOCALBOOT 0
>> >>
>> >> # I can't be certain the hotkey works
>> >> MENU INCLUDE pxelinux.cfg/setup.menu ^Setup Menu
>> >>
>> >> # Or run this with a MENU BEGIN/MENU END
>> >> # default end
>> >>
>> >> # setup.menu begin
>> >> MENU TITLE Setup Menu
>> >>
>> >> LABEL MainMenu
>> >>   MENU LABEL ^Return to Main Menu
>> >>   MENU GOTO .top
>> >>
>> >> LABEL E6320
>> >>   MENU LABEL ^Latitude E6320
>> >>   KERNEL   "<---- Don't know what to choose
here"
>> >>   APPEND   "<---- Don't know what to choose
here"
>> >> # setup.menu end
>> >>
>> >>
>> >> OK, now that we have some basic style solved...
>> >>
>> >>
>> >> Your last label is where things get rather interesting.  You
could use
>> >> wimboot ( http://ipxe.org/wimboot ) to load a WIM that has
sufficient
>> >> drivers to load the installer from another location like say a
>> >> SMB/Samba/CIFS share.  You could boot CloneZilla though this
won't
>> >> give you the option of loading more drivers very well.
>> >>
>> >>
>> >> --
>> >> -Gene
>> >>
>> >> >> -----Original Message-----
>> >> >> From: Gene Cumm [mailto:gene.cumm at gmail.com]
>> >> >> Sent: 24. november 2017 15:07
>> >> >> To: Kenneth Vandb?k <kenneth.vandbek at
alfalaval.com>
>> >> >> Cc: syslinux at zytor.com
>> >> >> Subject: Re: [syslinux] Help for setting up windows
unattended
>> >> >> installation
>> >> >>
>> >> >> On Fri, Nov 24, 2017 at 8:24 AM, Kenneth Vandb?k via
Syslinux
>> >> >> <syslinux at zytor.com> wrote:
>> >> >> > Hi.
>> >> >> >
>> >> >> > I have looked at
>> >> >> >
PXElinux<http://www.syslinux.org/wiki/index.php?title=PXELINUX> to
>> >> >> > understand all this, but I'm very sorry I
don't.
>> >> >> >
>> >> >> > I have managed to setup to boot from PXELinux,
but I'm not an
>> >> >> > expert
>> >> >> > on
>> >> >> > how to setup a menu file for making a windows
unattended
>> >> >> > installation.
>> >> >>
>> >> >> So you're at the point where PXELINUX
successfully loads and you
>> >> >> have a
>> >> >> config loading of some sort?  What's your config
currently look
>> >> >> like?
>> >> >> Is
>> >> >> this a BIOS/legacy system?
>> >> >>
>> >> >> Regarding an unattended install of Windows, how do
you plan to do
>> >> >> this?
>> >> >> Do you want to chain-load to a WDS system?  Restore
an image with a
>> >> >> tool
>> >> >> like Clonezilla??  There's lots of options here
without knowing the
>> >> >> details.
>> >> >>
>> >> >> > Could someone help me with that?
>> >> >> >
>> >> >> > Is there some kind of a forum for this or is it
just by email?
>> >> >>
>> >> >> Web forum?  No.  IRC?  Yes, but unless you find
someone active at
>> >> >> the
>> >> >> time, you might have to wait for any sort of answer.
>
>


-- 
-Gene

On Wed, Dec 6, 2017 at 2:58 PM, Kenneth Vandb?k <valnurat at gmail.com>
wrote:
> I have changed my setup.menu file as mentioned, but I get this error now:
>
> command line: "BOOT_IMAGE= wimboot
>
initrd=Windows7SP2/boot/bcd,Windows7SP2/boot/boot.sdi,Windows7SP2/sources/boot.wim"
> Unrecognised argument
>
"initrd=Windows7SP2/boot/bcd,Windows7SP2/boot/boot.sdi,Windows7SP2/sources/boot.wim"
> Press a key to reboot...
>
> My setup.menu file looks like this now.
>
> # Setup.Menu Begin
> MENU TITLE Setup Menu
> LABEL MainMenu
>   MENU LABEL ^Return to Main Menu
>   MENU GOTO .top
>
> LABEL E6320
>   MENU LABEL ^Latitude E6320
>   KERNEL wimboot
>   append
>
initrd=Windows7SP2/boot/bcd,Windows,7SP2/boot/boot.sdi,Windows7SP2/sources/boot.wim
> # Setup.Menu End
>
> What should I do now?
Apparently wimboot is intolerant of this particular commandline style.

SYSLINUX appears intolerant of this style which is probably more in
tune with what wimboot likes:


LABEL E6320
  MENU LABEL ^Latitude E6320
  KERNEL wimboot
  APPEND initrd=Windows7SP2/boot/bcd initrd=Windows7SP2/boot/boot.sdi
initrd=Windows7SP2/sources/boot.wim


SYSLINUX only loads the first file.  It seems you'll need to load iPXE
(unless someone else knows a workaround...)


-- 
-Gene

What about using linux.c32?? It has some special initrd features, which 
someone has very kindly documented:

 ? http://www.syslinux.org/wiki/index.php?title=Linux.c32

Shao Miller
Synthetel Corporation
W: https://www.synthetel.com