<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<tt>KernSafe Technology wrote:</tt>
<blockquote type="cite" cite="mid:COL111-W38776C456F42D3F8D1CD58CCE30@phx.gbl">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style><tt>Hi,<br>
<br>
Yes, I mentioned because I just for a test, when a SAN drive registered
and then unregistered, the original local drive lost, so I think it is
the reason.<br>
</tt></blockquote>
<tt><br>
But you just wrote in your last e-mail:<br>
<br>
</tt>
<blockquote type="cite"><tt>Then I type exit to exit gpxe command
line, it will boot from my
harddrive, after booted, I opened computer management console, I can't
see a hard disk (only on local hard disk).<br>
</tt></blockquote>
<tt><br>
How does "original local drive lost" mean "it will boot from my
harddrive"?<br>
<br>
</tt>
<blockquote type="cite" cite="mid:COL111-W38776C456F42D3F8D1CD58CCE30@phx.gbl"><tt>But when there is no local disk, I used<br>
set keep-san 1 to boot from a SAN, the drive can't be seen still
(keep-san 0 also has this problem). It is difficult to understand.<br>
Is the problem might be caused by int13 drive change?</tt></blockquote>
<tt><br>
If you see "Unregistering BIOS drive 0x80", that means that gPXE did
hook INT 13h, but then unhooked it. If you 'set keep-san 1' _before_
the 'sanboot', you should not see this message. If you see the
message, that means that keep-san was not set to 1. If you correctly
'set keep-san 1' _before_ the 'sanboot', you will see this message:<br>
<br>
"Preserving connection to SAN disk"<br>
<br>
- Shao Miller<br>
</tt>
</body>
</html>