<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.5726" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>Hi, Andrew,</DIV>
<DIV> </DIV>
<DIV>> Windows only uses ARC paths for BIOS level operations. As such, you
could be seeing an issue with either iPXE *or* your system's BIOS at this point.
You *might* have better luck if you try a different motherboard/bios
combo.<BR><FONT face=新細明體 size=2>></FONT></DIV>
<DIV>> I wanted to mention also that I understand Windows 7 has been more
gracefully(?) booted from USB sources. If you're trying to use Windows XP or
2003 for this, it may be worth starting with Windows 7 and working your way
back. The forums at http://reboot.pro are a good place to start.<BR></DIV>
<DIV>Thanks very much for your suggestion and good forum sharing. I know
Windows 7 is more friendly in supporting boot from USB devices, but still
have no chance to try it. I will try to find out the answer from the
forum. Thanks again!</DIV>
<DIV><FONT face=新細明體 size=2></FONT> </DIV>
<DIV>Regards,</DIV>
<DIV>Jerry</DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt 新細明體">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt 新細明體; font-color: black"><B>From:</B>
<A title=rulerof@gmail.com
href="mailto:rulerof@gmail.com">rulerof@gmail.com</A> </DIV>
<DIV style="FONT: 10pt 新細明體"><B>To:</B> <A title=jaspers.cheng@msa.hinet.net
href="mailto:jaspers.cheng@msa.hinet.net">jerrycheng-hinet</A> </DIV>
<DIV style="FONT: 10pt 新細明體"><B>Cc:</B> <A title=mbrown@fensystems.co.uk
href="mailto:mbrown@fensystems.co.uk">Michael Brown</A> ; <A
title=ipxe-devel@ipxe.org
href="mailto:ipxe-devel@ipxe.org">ipxe-devel@ipxe.org</A> </DIV>
<DIV style="FONT: 10pt 新細明體"><B>Sent:</B> Friday, March 04, 2011 2:44 AM</DIV>
<DIV style="FONT: 10pt 新細明體"><B>Subject:</B> Re: Re: [ipxe-devel] SAN Boot
Windows XP with USB-NIC.</DIV>
<DIV><BR></DIV>Hello Jerry,<BR><BR>You're likely right about this:<BR><BR>>
I think it should be the similiar issue like "booting windows xp from USB
device". Do you have any idea or suggestion about this issue?<BR><BR>Booting
Windows from USB has had a very long and buggy history. I don't think that
Windows will ever, by default, consider the USB or its attached devices to be
considered "boot critical," so booting from a USB NIC is likely to encounter
the same and more obstacles than booting from a USB Flash drive or USB HDD
does. <BR><BR>Though seeing this:<BR><BR>> In ipxe, I got more detail fail
reason. The screen hanged at "Couldn't open driver
multi(0)disk(0)rdisk(0)partition(1)".<BR><BR>Windows only uses ARC paths for
BIOS level operations. As such, you could be seeing an issue with either iPXE
*or* your system's BIOS at this point. You *might* have better luck if you try
a different motherboard/bios combo.<BR><BR><BR>I wanted to mention also that I
understand Windows 7 has been more gracefully(?) booted from USB sources. If
you're trying to use Windows XP or 2003 for this, it may be worth starting
with Windows 7 and working your way back. The forums at http://reboot.pro are
a good place to start.<BR><BR>Best of luck with this, too. It's kinda neat
:)<BR><BR>Cheers,<BR>Andrew Bobulsky<BR><BR>On Mar 3, 2011 1:12pm,
jerrycheng-hinet <jaspers.cheng@msa.hinet.net> wrote:<BR>> Thanks,
Michael.<BR>> <BR>> <BR>> <BR>> The patch works! I don't know how
to express my gratitude to you!<BR>> <BR>> <BR>> <BR>> After
applying your patch, I can see the consistent result with ipxe and
gpxe.<BR>> <BR>> <BR>> <BR>> In gpxe, the screen hanged at
"Registerd as BIOS drive 0x80/Booting from BIOS drive 0x80".<BR>> <BR>>
<BR>> <BR>> In ipxe, I got more detail fail reason. The screen hanged at
"Couldn't open driver multi(0)disk(0)rdisk(0)partition(1)".<BR>> <BR>>
<BR>> <BR>> By comparing wireshark trace, both of them seemed to fail to
read LUN0 (LBA:0x007ff5f7, Len: 8).<BR>> <BR>> <BR>> <BR>> I think
it should be the similiar issue like "booting windows xp from USB device". Do
you have any idea or suggestion about this issue?<BR>> <BR>> <BR>>
<BR>> Thanks again for your great help!<BR>> <BR>> <BR>> <BR>>
Regards,<BR>> <BR>> Jerry<BR>> <BR>> <BR>> <BR>> -----
Original Message ----- From: "Michael Brown"
mbrown@fensystems.co.uk><BR>> <BR>> To: "jerrycheng-hinet"
jaspers.cheng@msa.hinet.net>; ipxe-devel@ipxe.org><BR>> <BR>>
Sent: Friday, March 04, 2011 1:07 AM<BR>> <BR>> Subject: Re:
[ipxe-devel] SAN Boot Windows XP with USB-NIC.<BR>> <BR>> <BR>>
<BR>> <BR>> <BR>> <BR>> On Thursday 03 Mar 2011 16:56:37
jerrycheng-hinet wrote:<BR>> <BR>> <BR>> > a) try running the
"dhcp" command at the command line and, after it > fails<BR>> <BR>>
> with<BR>> <BR>> > the same "Connection timed out" error message,
run the "ifstat" command<BR>> <BR>> >
(http://ipxe.org/cmd/ifstat)<BR>> <BR>> <BR>> <BR>> Still got
connection timeout message. Then run the "ifstat" command, it<BR>> <BR>>
showed:<BR>> <BR>> net0: 00:50:fc:8e:c7:8d on UNDI (closed)<BR>>
<BR>> [Link:up, TX:4 TXE:0 RX:0 RXE:0]<BR>> <BR>> <BR>>
<BR>> <BR>> That confirms that iPXE is seeing no received
packets.<BR>> <BR>> <BR>> <BR>> <BR>> > b) try setting a
static IP address as described on the error page<BR>> <BR>> >
(http://ipxe.org/4c106035), and see if you can ping it from the DHCP<BR>>
<BR>> > server.<BR>> <BR>> <BR>> <BR>> Fail to ping the
static IP address. Got "Destination Host Unreachable"<BR>> <BR>>
message.<BR>> <BR>> <BR>> <BR>> <BR>> That is consistent with
not seeing any received packets in iPXE.<BR>> <BR>> <BR>> <BR>>
<BR>> It's weird that by using the same USB-NIC, and almost identical
DHCP<BR>> <BR>> configuration, DHCP function seems to be ok in
gpxe.<BR>> <BR>> <BR>> <BR>> <BR>> If you have a known-working
version tag (e.g. v1.0.0, which is common with<BR>> <BR>> gPXE), then
you could use git bisection (http://ipxe.org/howto/bisect) to<BR>> <BR>>
track down the commit that causes the problem.<BR>> <BR>> <BR>>
<BR>> The only change I can think of that might be relevant to the UNDI
driver is<BR>> <BR>> <BR>> <BR>>
http://git.ipxe.org/ipxe.git/commitdiff/006d9f1<BR>> <BR>>
<BR>> <BR>> It's possible that your card is erroneously reporting that
it doesn't support<BR>> <BR>> interrupts, when in fact it requires the
interrupt-triggered call to<BR>> <BR>> PXENV_UNDI_ISR_IN_START in order
to make packet reception work. You could try<BR>> <BR>> overriding
the interrupts-supported detection logic using the attached patch.<BR>>
<BR>> <BR>> <BR>> Michael<BR>> <BR>> <BR>> <BR>> <BR>>
<BR>> <BR>> _______________________________________________<BR>>
<BR>> ipxe-devel mailing list<BR>> <BR>>
ipxe-devel@lists.ipxe.org<BR>> <BR>>
https://lists.ipxe.org/mailman/listinfo/ipxe-devel<BR>>
<BR>></BLOCKQUOTE></BODY></HTML>