<HTML>
<P><B></B></P>
<P><B>On Tue 09/11/10 1:40 PM , Shao Miller Shao.Miller@yrdsb.edu.on.ca sent:<br>
</B></P>
<BLOCKQUOTE style="BORDER-LEFT: #5167c6 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<P><DEFANGED_META http-equiv="Content-Type" content="text/html;charset=UTF-8"></DEFANGED_META http-equiv="content-type" content="texthtml;charset=utf-8"><DEFANGED_BODY text="#000000" bgcolor="#ffffff"></DEFANGED_BODY text="#000000" bgcolor="#ffffff"><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 class=moz-txt-link-freetext href="http://webserver/page#section">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></P></BLOCKQUOTE>
<P>Hi Shao,</P>
<P>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...)</P>
<P>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...?</P>
<P>Many thanks for your assistance so far!</P>
<P>Regards,</P>
<P>Carl</P>
<P> </P><BR></HTML>