Jump to content











Photo
- - - - -

Vistape PXE boot with tftpd32


  • Please log in to reply
9 replies to this topic

#1 guimenez

guimenez

    Frequent Member

  • Advanced user
  • 168 posts
  •  
    Portugal

Posted 01 April 2010 - 03:48 PM

Hi

i'm trying to create a tftpd32 server to boot vistape from Lan and then restore WIM images to
computers. does anyone know how can i start?

What configurations i need to make with tftpd32 server?

many thanks

Guimenez

#2 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14520 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 01 April 2010 - 03:55 PM

Check the guides in the tftpd32 section stickies, first thing:
http://www.boot-land...hp?showforum=58

:)
Wonko

#3 dera

dera

    Gold Member

  • .script developer
  • 1335 posts
  •  
    Hungary

Posted 02 April 2010 - 09:08 AM

http://diddy.boot-la...t/pxe/index.htm

#4 guimenez

guimenez

    Frequent Member

  • Advanced user
  • 168 posts
  •  
    Portugal

Posted 03 April 2010 - 07:54 PM

many thanks for the reply

i followed this two tutorial

http://diddy.boot-la...t/pxe/index.htm
http://www.etherboot.org/wiki/winpe

but when my pc boot with pxe it gives me this error:

\Boot\BCD
Status: 0xc0000001

this is my folder structure

\PXE
\PXE\tftpd32
\PXE\tftpboot
\PXE\tftpboot\menu.lst
\PXE\tftpboot\pxelinux.cfg
\PXE\tftpboot\Boot
\PXE\tftpboot\Boot\BCD
\PXE\tftpboot\Boot\boot.sdi
\PXE\tftpboot\Boot\bootmgr.exe
\PXE\tftpboot\Boot\pxeboot.n12
\PXE\tftpboot\Boot\winpe.wim

my tftpd32 dhcp boot file is /Boot/pxeboot.n12

many thanks

#5 dera

dera

    Gold Member

  • .script developer
  • 1335 posts
  •  
    Hungary

Posted 04 April 2010 - 05:41 AM

for me the bootmgr.exe located in the tftp root folder
'\PXE\tftpboot\bootmgr.exe'

as first try
use the original BCD which comes from e.g. the
'\Program Files\Windows AIK\Tools\PETools\x86\boot' folder and use path
'\PXE\tftpboot\sources\boot.wim'

if it works then try to rename the boot.wim to winpe.wim and move it to the \Boot folder
try modify this original BCD using the commands:
bcdedit.exe /store C:\PXE\tftpboot\Boot\BCD /set {default} osdevice ramdisk=[boot]\Boot\winpe.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
bcdedit.exe /store C:\PXE\tftpboot\Boot\BCD /set {default} device ramdisk=[boot]\Boot\winpe.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}

in many case i also had problem with creating a brand new BCD using the commands
'bcdedit.exe /createstore'
'bcdedit.exe /create {ramdiskoptions}'
etc...
seems somehow this BCD is fragile (breakable)
i think the sort order of commands is important to create a working one

this works for me:
[codebox]set path=C:\PXE\tftpboot\Boot\BCD
del %path%
bcdedit.exe /createstore %path%
bcdedit.exe /store %path% /create {ramdiskoptions} /d "Ramdisk options"
bcdedit.exe /store %path% /set {ramdiskoptions} ramdisksdidevice boot
bcdedit.exe /store %path% /set {ramdiskoptions} ramdisksdipath \Boot\boot.sdi
bcdedit.exe /store %path% /create {bootmgr} /d "WinPE BootManager"
bcdedit.exe /store %path% /set {bootmgr} timeout 10
for /f "tokens=3" %%a in ('bcdedit.exe /store %path% /create /d "WinPE Boot Image" /application osloader') do set guid=%%a
bcdedit.exe /store %path% /set %guid% osdevice ramdisk=[boot]\Boot\winpe.wim,{ramdiskoptions}
bcdedit.exe /store %path% /set %guid% device ramdisk=[boot]\Boot\winpe.wim,{ramdiskoptions}
bcdedit.exe /store %path% /set %guid% path \windows\system32\boot\winload.exe
bcdedit.exe /store %path% /set %guid% systemroot \Windows
bcdedit.exe /store %path% /set %guid% detecthal Yes
bcdedit.exe /store %path% /set %guid% winpe Yes
bcdedit.exe /store %path% /displayorder %guid% /addlast
bcdedit.exe /store %path% /enum all
pause[/codebox]

#6 guimenez

guimenez

    Frequent Member

  • Advanced user
  • 168 posts
  •  
    Portugal

Posted 10 April 2010 - 04:51 PM

Thanks for the reply

After doing this steps:

for me the bootmgr.exe located in the tftp root folder
'\PXE\tftpboot\bootmgr.exe'

as first try
use the original BCD which comes from e.g. the
'\Program Files\Windows AIK\Tools\PETools\x86\boot' folder and use path
'\PXE\tftpboot\sources\boot.wim'

if it works then try to rename the boot.wim to winpe.wim and move it to the \Boot folder
try modify this original BCD using the commands:
bcdedit.exe /store C:\PXE\tftpboot\Boot\BCD /set {default} osdevice ramdisk=[boot]\Boot\winpe.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
bcdedit.exe /store C:\PXE\tftpboot\Boot\BCD /set {default} device ramdisk=[boot]\Boot\winpe.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}


it gives me the same error message :cheers:

when i try to create the new BCD it gives me errors on all steps after this step:

for /f "tokens=3" %%a in ('bcdedit.exe /store %path% /create /d "WinPE Boot Image" /application osloader') do set guid=%%a


thanks

#7 dera

dera

    Gold Member

  • .script developer
  • 1335 posts
  •  
    Hungary

Posted 10 April 2010 - 05:50 PM

if you use 'boot.wim' and place it in the folder 'sources' located in the tftp root
and the original BCD doesn't work
then i don't know what can be the problem

for /f "tokens=3" %%a in etc...
run as a batch
make a .cmd file, copy paste the lines from the CODE BOX
run the .cmd

#8 guimenez

guimenez

    Frequent Member

  • Advanced user
  • 168 posts
  •  
    Portugal

Posted 10 May 2010 - 07:52 PM

Thanks, now it works

the main problems it that take too much time to start winpe :lol:

many thanks

#9 Datsspeed

Datsspeed

    Newbie

  • Members
  • 19 posts
  •  
    Germany

Posted 09 June 2010 - 01:20 PM

hello guys ^^

my problem with tftp32 is that all PCS, that have PXE Boot as Alive, are booting from PXE = vista pe.

its there a possibility to start only definited macadresses with pxe?

and the rest of pc´s cant take the vista pe files via pxe?

thx for help

datsspeed

#10 Sha0

Sha0

    WinVBlock Dev

  • Developer
  • 1682 posts
  • Location:reboot.pro Forums
  • Interests:Booting
  •  
    Canada

Posted 09 June 2010 - 01:47 PM

...its there a possibility to start only definited macadresses with pxe?

and the rest of pc´s cant take the vista pe files via pxe?...

You can use PXELINUX as a middle-man, if you aren't already. PXELINUX clients first attempt to download a config-file called 01-XX-XX-XX-XX-XX-XX, where the XX pieces are the MAC address. The config-file for Vista clients can be:
DEFAULT vistape

LABEL vistape

  COMBOOT pxechain.com

  APPEND pxeboot.n12
and the config-file for the other clients can be something else entirely.

You will need pxelinux.0 and pxechain.com, found in Syslinux' core/ and modules/ directories, respectively.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users