<html xmlns="http://www.w3.org/TR/REC-html40" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:v="urn:schemas-microsoft-com:vml"><head><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
tt
{mso-style-priority:99;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:774639806;
mso-list-type:hybrid;
mso-list-template-ids:791416562 342384446 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0E8;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body vlink="purple" link="blue" lang="EN-US" bgcolor="white"><div class="WordSection1"><p class="MsoNormal"><span style="color:#1F497D">“</span><tt><span style="font-size:10.0pt">So having said that, I'd like to ask: _why_ do you want the drive numbers numbered in this way?</span></tt><span style="color:#1F497D">”<o:p></o:p></span></p><p style="text-indent:-.25in;mso-list:l0 level1 lfo1" class="MsoListParagraph"><![if !supportLists]><span style="font-family:Wingdings;color:#1F497D"><span style="mso-list:Ignore">è<span style="font:7.0pt "Times New Roman""> </span></span></span><![endif]><span style="color:#1F497D">I have some unattended programs that capture and deploy OS images. The user may boot a system from a CDROM/USB Drive and do the capturing. Meanwhile, the deployment occurs from an iSCSI Windows image, which currently changes the numbering of the internal hard drives and this causes the captured images to be deployed to the wrong drives. I can make the deployment program aware of the iSCSI drive but I’m looking for a more thorough solution.<o:p></o:p></span></p><p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="color:#1F497D">Could you please explain for me the relationship between gPXE iSCSI boot and Windows iSCSI Initiator? When does gPXE end and Windows iSCSI Initiator pick up?<o:p></o:p></span></p><p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p><p class="MsoNormal"><span style="color:#1F497D">Thanks<o:p></o:p></span></p><div><p class="MsoNormal"><b><span style="color:#1F497D">Binh Kien Thai</span></b><span style="color:#1F497D"><br><br></span><span style="font-size:9.0pt;color:#1F497D"><o:p></o:p></span></p></div><p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p><div><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> Shao Miller [mailto:Shao.Miller@yrdsb.edu.on.ca] <br><b>Sent:</b> Tuesday, January 18, 2011 12:00 PM<br><b>To:</b> Binh Thai<br><b>Cc:</b> gpxe@etherboot.org<br><b>Subject:</b> [SPAM] - Re: [gPXE] Change drive number of the iscsi boot drive? - Email found in subject<o:p></o:p></span></p></div></div><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal"><tt><span style="font-size:10.0pt">On 1/18/2011 11:42, Binh Thai wrote:</span></tt> <o:p></o:p></p><p class="MsoNormal"><tt><span style="font-size:10.0pt">Hi Shao,</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br></span><tt><span style="font-size:10.0pt;color:#1F497D"> </span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br></span><tt><span style="font-size:10.0pt;color:#1F497D">Thanks for your reply.</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br></span><tt><span style="font-size:10.0pt;color:#1F497D"> </span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br></span><tt><span style="font-size:10.0pt;color:#1F497D">I forgot to mention that I meant “drive 0” in the context of Windows disk drive numbering.</span></tt><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New""><br><tt>Oh, ok.</tt><br><br><br></span><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p></o:p></span></p><p class="MsoNormal"><tt><span style="font-size:10.0pt">My goal is to boot a system from an iscsi target without disrupting the disk drive numbers of the internal hard drives. For example, if I have one internal hard drive, I want to see it detected as Disk 0 whether I boot from it or from the iscsi target. If I boot from the iSCSI target, I want to see the iscsi target as drive 1, not 0. Currently, the iSCSI drive would become Disk 0 and push the internal drive to Disk 1.</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br></span><tt><span style="font-size:10.0pt;color:#1F497D"> </span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br></span><tt><span style="font-size:10.0pt;color:#1F497D">I think the PnP enumeration process in Windows has some relationship with the BIOS drive numbering. Could you please point me to some in-depth documentation regarding the BIOS drive numbering and how int13 is used?</span></tt><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p></o:p></span></p><p style="margin-bottom:12.0pt" class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New""><br><tt>I do not believe that BIOS drive numbers and Windows drive numbers have any correlation. Use Microsoft's SysInternals' LoadOrd.exe to check your driver load order. If you ensure that the drivers responsible for the internal storage adapters are loaded before the iSCSI driver, then I think your odds are better for the iSCSI HDD getting a higher number than the internal HDD(s).</tt><br><br><tt>However, it might be the case that the startup protocol hands an MBR signature from boot-up to the drive number assignment routine; in this case, whatever drive is used for booting (your iSCSI HDD) will be drive 0 no matter what. You can use Microsoft's SysInternals' WinObj.exe to check the mapping of the ARC names (\ArcName\) to the drive numbers (\Device\HarddiskX).</tt><br><br><tt>I can only think of a convoluted way to push the boot drive up and away from Windows drive number 0:</tt><br><tt>- Boot the iSCSI drive</tt><br><tt>- Have GRUB4DOS on the drive</tt><br><tt>- Have GRUB4DOS remap the drive number from 0x80 to 0x81</tt><br><tt>- Chain-load the Windows boot-loader</tt><br><tt>- Have BOOT.INI/BCD attempt to boot multi(0)disk(0)rdisk(1)partition(1) instead of rdisk(0) (0x81 instead of 0x80)</tt><br><tt>- If the iSCSI drive is \Device\Harddisk1 then hopefully Windows would also further connect it as multi(0)disk(0)rdisk(1). ARC _and_ HDD numbers would then be 1 instead of 0. (Untested.)</tt><br><br><tt>So having said that, I'd like to ask: _why_ do you want the drive numbers numbered in this way?</tt><br><br><tt>- Shao Miller</tt></span><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p></o:p></span></p></div></body></html>