<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<tt><a href="mailto:carlyoung@keycomm.co.uk" class="moz-txt-link-abbreviated">carlyoung@keycomm.co.uk</a> wrote:</tt>
<blockquote type="cite" cite="mid:1161.1289310915@keycomm.co.uk">
<tt><b>On Tue 09/11/10 1:40 PM , Shao Miller
<a href="mailto:Shao.Miller@yrdsb.edu.on.ca" class="moz-txt-link-abbreviated">Shao.Miller@yrdsb.edu.on.ca</a> sent:<br>
</b></tt>
<blockquote style="border-left: 2px solid rgb(81, 103, 198); padding-left: 5px; padding-right: 0px; margin-left: 5px; margin-right: 0px;"><tt><DEFANGED_META content="text/html;" http-equiv="Content-Type"></DEFANGED_META><DEFANGED_BODY bgcolor="#ffffff" text="#000000"></DEFANGED_BODY></tt><tt>As a matter
of fact, we do have a problem with such an odd filename. You see, some
HTTP URIs sometimes go something like <a href="http://webserver/page#section" class="moz-txt-link-freetext" moz-do-not-send="true">http://webserver/page#section</a>
and we do some processing with #.<br>
<br>
While looking at this, I'd like to ask, though: Are you quite certain
that the DHCP + PXE service is configured correctly? Could it be that
#MPCPathBoot# is intended as a place-holder in the CA-Unicenter Managed
PC Boot Server settings? A palce-holder for whatever the TFTP directory
is supposed to be?<br>
<br>
- Shao Miller<br>
</tt></blockquote>
<tt>Hi Shao,</tt>
<br>
<tt>The #MPCPathBoot# prefix is a special path within the bootserver
as far as I am aware - sort of a virtual root I guess. It is a legal
file name on Windows and *NIX (though not a name I would use...)</tt>
<br>
<tt>In my reading of this then, I should be asking HP to get this
addressed in the gPXE source code as it's not a bug in the TFTP server,
though I may be wise asking for an enhancement for that too to use more
"friendly" path names...?</tt>
<br>
<tt>Many thanks for your assistance so far!</tt></blockquote>
<br>
<tt>Yes. HP might already have a new firmware image available for you
to try, but I already see in the most recent source code that it's an
issue, so I doubt it will resolve this. It's worth approaching HP
about, who will most likely then approach QLogic.</tt><br>
<br>
<tt>There were a few other changes to the Phantom driver (your NIC's
driver) that Michael Brown has worked on, so the next time QLogic or HP
provide a firmware image, you might find that it has iPXE included.</tt><br>
<br>
<tt>In the meanwhile, if anyone comes up with a change to the source
code which resolves your issue, I'm not sure how you could flash it
into the NIC, or if that'd void any warranty you might have, since it
didn't come from HP. However, if we can resolve your issue, you could
build a CD or USB stick or even a floppy disk and change the boot order
on the HP computer so that it boots such a device, rather than the
NIC. The device would then boot a version of iPXE/gPXE which could
work for you. I only suggest that as an interim measure until HP could
provide an update.</tt><br>
<br>
<tt>I hope this information is useful.</tt><br>
<br>
<tt>- Shao Miller</tt><br>
</body>
</html>