<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body text="#000000" bgcolor="#ffffff">
<tt>KernSafe Technology wrote:</tt>
<blockquote type="cite" cite="mid:COL111-W97A569D195D075BFB2C01CCE30@phx.gbl">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style><tt>Yes,
in the condition 1 local hard disk boot, I can't see the SAN disk after
local disk boot, I can understand, but I even can't see the local hard
drive, there is not hard drive in disk management tool.<br>
</tt></blockquote>
<tt>I wrote:<br>
<br>
</tt>
<blockquote type="cite"><tt>This is by
design; correct behaviour. If you do not use keep-san, gPXE will not
create an iBFT in memory. Windows will not find an iBFT, so you will
not have the SAN connection at all.<br>
</tt><tt><br>
This is an error. The iBFT is populated regardless of the INT 13h
hook. I apologize to anyone still reading this thread.<br>
</tt></blockquote>
<tt><br>
It was something of a technical correction... Even though the iBFT is
populated regardless of the keep-san setting, if you do not use
keep-san, then gPXE can completely unload when you do 'exit'. If gPXE
is completely unloaded, I don't believe the iBFT is guaranteed to stay
intact. So the only way to guarantee the iBFT is to use 'keep-san', as
far as I know, in the context of your situation.<br>
<br>
Can you see the local hard disk drive when you do not boot gPXE at all?<br>
<br>
Good luck,<br>
<br>
- Shao Miller<br>
</tt>
</body>
</html>