[ipxe-devel] SAN Boot Windows XP with USB-NIC.

[jerrycheng-hinet]

Thanks, Michael.

> Could you build with DEBUG=undinet and tell me what is shown for the lines
>
>  UNDINIC 0x<address> has type <type>, speed <speed>, flags <flags>
>  UNDINIC 0x<address> uses IRQ <irq>

> That message must be coming from NTLDR rather than iPXE.  Could you try
> building with DEBUG=int13, so we can see what is happening?

I will try to get a a null-modem cable, enable the debug options for the 
build, and then provide the information soon. Thanks again.

Regards,
Jerry

----- Original Message ----- 
From: "Michael Brown" <mbrown at fensystems.co.uk>
To: <ipxe-devel at ipxe.org>
Cc: "jerrycheng-hinet" <jaspers.cheng at msa.hinet.net>
Sent: Friday, March 04, 2011 3:06 AM
Subject: Re: [ipxe-devel] SAN Boot Windows XP with USB-NIC.


> On Thursday 03 Mar 2011 18:12:39 jerrycheng-hinet wrote:
>> The patch works! I don't know how to express my gratitude to you!
>>
>> After applying your patch, I can see the consistent result with ipxe and
>> gpxe.
>
> You're welcome.  Unfortunately, we can't just apply this patch as-is, 
> since it
> would break some other configurations.
>
> Could you build with DEBUG=undinet and tell me what is shown for the lines
>
>  UNDINIC 0x<address> has type <type>, speed <speed>, flags <flags>
>  UNDINIC 0x<address> uses IRQ <irq>
>
> I'm most interested in the "flags" value, which is where your UNDI driver 
> is
> supposed to indicate that it supports IRQs.  Knowing the IRQ number may 
> also
> be relevant.
>
>> In gpxe, the screen hanged at "Registerd as BIOS drive 0x80/Booting from
>> BIOS drive 0x80".
>>
>> In ipxe, I got more detail fail reason. The screen hanged at "Couldn't 
>> open
>> driver multi(0)disk(0)rdisk(0)partition(1)".
>
> That message must be coming from NTLDR rather than iPXE.  Could you try
> building with DEBUG=int13, so we can see what is happening?
>
> Michael