KernSafe Technology wrote: > Hi Shao Miller, Hello. :)
> They are two conditions: > > 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. 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. > 2, remote boot (only one san disk, with out harddisk), with keep-san > 1, boot from san, no disk appear in disk management tool. 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. 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. - Shao Miller
_______________________________________________ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
