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@etherboot.org
http://etherboot.org/mailman/listinfo/gpxe
