<!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-W60147F035605C79EFE7508CCE30@phx.gbl">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style><tt>Hi
Shao Miller,<br>
</tt></blockquote>
<tt><br>
Hello. :)<br>
<br>
</tt>
<blockquote type="cite" cite="mid:COL111-W60147F035605C79EFE7508CCE30@phx.gbl"><tt>They are two conditions:<br>
<br>
1, Local hard (only one) drive boot, without keep-san, just do a
sanboot, it will register and unregister int13 drive, and then boot
from local hard drive, no disk appear in disk management.<br>
</tt>
</blockquote>
<tt><br>
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>
<br>
</tt>
<blockquote type="cite" cite="mid:COL111-W60147F035605C79EFE7508CCE30@phx.gbl"><tt>2, remote boot (only one san disk, with out harddisk),
with keep-san 1, boot from san, no disk appear in disk management tool.<br>
</tt></blockquote>
<tt><br>
This seems more like your original problem description, and still seems
like a Windows misconfiguration somewhere. If you are booted from the
SAN disk, you should really see it in both Device Manager as well as
Disk Management tools. I always see all of my SAN disks in both areas.<br>
<br>
There were a lot of things I suggested that you could try. Many of
them included reporting your findings. You've not yet reported _any_
of them.<br>
<br>
- Shao Miller</tt>
</body>
</html>