[gPXE] Download from TFTP server:

Andrew Bobulsky rulerof at gmail.com
Fri Dec 17 09:44:40 EST 2010


Hello Anton,

It has been awhile since I've loaded startrom via TFTP, so this is only a
guess, but here goes :)

If your regular (Intel?) PXE is booting startrom correctly, I assume that
the boot file name is being picked up from your DHCP options 66 and 67, as
"your.server.ip.or.dns.name" and "\windows\i386\startrom.com" respectively.
It's possible that startrom is looking for these values to determine the
TFTP boot directory to find the rest of its files and boot your client.

Try modifying your boot script like so, from:

> dhcp net0
> imgfetch -n startrom /windows/i386/startrom.com
> imgload startrom
> boot startrom

To:

> dhcp net0
> set next-server your.server.ip
> set filename \windows\i386\startrom.com			(Note:  I'm
not clear whether you should use forwardslashes or backslashes here, you may
need to try both)
> chain ${filename}

Granted, this will only work if startrom is behaving this way for the
reasons I suspect, but it's worth a shot ;)

Cheers,
Andrew Bobulsky


-----Original Message-----
From: gpxe-bounces at etherboot.org [mailto:gpxe-bounces at etherboot.org] On
Behalf Of Anton Yakovlev
Sent: Thursday, December 16, 2010 10:19 AM
To: gpxe at etherboot.org
Subject: [gPXE] Download from TFTP server:

Hello!

I have one TFTP related question.:)

I try to boot over network some Windows PE 1.x image.
What did I do, before using gPXE?

I had some TFTP server with following tftproot structure:

tftrproot -> /tftproot

ls /tftproot/windows/i386:
ntdetect.com
Ntldr
startrom.com
winpe.iso

I set up "boot filename" DHCP option to value of
"\windows\i386\startrom.com" and everything worked fine. PXE ROM
downloaded files ("Ntldr" and so on) from the directory
"\windows\i386".

Now I try to use gPXE,  and, from loaded gPXE, invoke next commands:

> dhcp net0
> imgfetch -n startrom /windows/i386/startrom.com
> imgload startrom
> boot startrom

And the question is why PXE client try to download all other binaries
("Ntldr" and so on) not from "\windows\i386", as I expected, but from
"\" directory?

Where is this part of software, how remembers such "current directory"
setting? :)
Is it some part of Intel ROM or, maybe, gPXE can rule this nuance?

-- 
Regards,
Anton Yakovlev
_______________________________________________
gPXE mailing list
gPXE at etherboot.org
http://etherboot.org/mailman/listinfo/gpxe



More information about the gPXE mailing list