<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body text="#000000" bgcolor="#ffffff">
<tt>Andrew Bobulsky wrote:</tt>
<blockquote type="cite" cite="mid:FCE0159C-B85B-42D8-827B-39A7DD464BAF@gmail.com">
<title>Re: [gPXE] Iscsi booting an HP thin client with gPXE 1.0.0</title>
<!-- Converted from text/plain format -->
<p><tt><font size="2">Mark,<br>
<br>
Can you try disabling Automatic Restart on boot failure and tell us
what the error code on the blue screen is? Try tapping F8 after the
gpxe connects to the iSCSI target and you should get an advanced boot
options menu.<br>
<br>
If the error is something like "Inaccessible boot device," then you're
likely missing a NIC driver in your Win7 image, or the appropriate
driver isn't set to load at boot time.<br>
<br>
FWIW though, since you do manage to get the Windows Boot Manager
loaded, I doubt this is a gPXE issue.</font></tt></p>
</blockquote>
<tt><br>
I agree 100% with Andrew's process and conclusion suggestions. :)
Mark, you mentioned that other workstations boot just fine from the
same image. I think that you should take your image, DD it to an HDD,
boot the thin client with that HDD (somehow, maybe with an IDE ribbon),
install the NIC in Windows, then DD the image back to your SAN. That
should make sure the Windows drivers are available for the iSCSI
connection to persist past the point where it's no longer gPXE's
responsibility to provide disk I/O.<br>
<br>
You could also consider using a Windows PE and adapting the following
guide to pre-install the NIC into the SAN image:<br>
<br>
<a href="http://www.etherboot.org/wiki/appnotes/port_winnt_sanboot" class="moz-txt-link-freetext">http://www.etherboot.org/wiki/appnotes/port_winnt_sanboot</a><br>
<br>
- Shao Miller<br>
</tt>
</body>
</html>