<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body text="#000000" bgcolor="#ffffff">
Hello Shao,<br>
<br>
The PE I was using is based of a 2k3 SP2 Version, so I build a new one
based on the Install CD (XP SP3) of my boot image.<br>
<br>
Devices by connection:<br>
ROOT\ACPI_HAL\0000<br>
ACPI\PNP0A03\0 --> pnp.reg<br>
PCI\VEN_10DE&DEV_054C&SUBSYS_054C1849&REV_A2\3&267A616A&0&50
--> bus.reg<br>
{1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV054C\4&266E55D&0&00
--> net.reg<br>
<br>
ACPI\PNP0A03\0 looks like a pci device, I attached .REG files of the
three devices.<br>
<br>
my motherboard is this
<a href="http://www.asrock.com/mb/overview.asp?model=alivenf7g-glan" class="moz-txt-link-freetext">http://www.asrock.com/mb/overview.asp?model=alivenf7g-glan</a> but the
drivers are pretty much the same with the one you linked because both
using the same NVIDIA chipset und onboard nic.<br>
<br>
I still get 0x7E, even with the CriticalDeviceDatabase entries.<br>
I also tried to import the Reg information for the ACPI\PNP0A03\0
Device, still get 0x7E.<br>
<br>
- Marc Hammer<br>
<br>
<br>
Shao Miller schrieb:
<blockquote type="cite" cite="mid:4E554899.2020905@YRDSB.Edu.On.Ca">On
8/24/2011 14:09, Shao Miller wrote:
<br>
<blockquote type="cite">Ok. I have a couple of suggestions:
<br>
<br>
The PE that you use in order to capture the devices' Registry detail
_must_ use the same versions of Windows files as the Windows that you
import it into. That is, for example, the PCI.SYS file should be the
same within your PE as within your VM. I believe that this helps to
ensure that the scheme for generating the ParentIdPrefix values
matches. Please verify that this file is the same, and that your
kernel and HAL versions match.
<br>
<br>
In the PE's Device Manager, please use View -> Devices by
connection. Please find out which device is the parent of the NVIDIA
Network Bus Enumerator. Its ParentIdPrefix ought to be
'3&267a616a&0', according to your one of your .REG files.
Please report some detail about this device; possibly a .REG file would
be good.
<br>
<br>
If, when your VM's Windows installation boots on the target hardware,
Windows does not use the same ParentIdPrefix values for the devices it
finds as the PE used, then the spoofing process of the
port_winnt_sanboot article is going to spoof those devices on
"branches" that don't (and won't) exist. Using matching Windows
versions is pretty important.
<br>
</blockquote>
<br>
A few more thoughts...
<br>
<br>
If I'm not mistaken, this is your motherboard:
<br>
<br>
<a href="http://asrock.com/mb/overview.asp?Model=ALiveNF7G-HDready" class="moz-txt-link-freetext">http://asrock.com/mb/overview.asp?Model=ALiveNF7G-HDready</a>
<br>
<br>
I spoofed your devices on my own computer and installed the devices
(and their drivers).
<br>
<br>
Please try importing the attached Registry file in the VM, too,
assuming your non-present devices are still installed!
<br>
<br>
- Shao Miller
<br>
<pre wrap=""><pre wrap="">
<hr width="90%" size="4">
_______________________________________________
gPXE mailing list
<a href="mailto:gPXE@etherboot.org" class="moz-txt-link-abbreviated">gPXE@etherboot.org</a>
<a href="http://etherboot.org/mailman/listinfo/gpxe" class="moz-txt-link-freetext">http://etherboot.org/mailman/listinfo/gpxe</a>
</pre></pre>
</blockquote>
<br>
</body>
</html>