On 8/24/2011 14:09, Shao Miller wrote:
Ok. I have a couple of suggestions:
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.
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.
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.
A few more thoughts...
If I'm not mistaken, this is your motherboard:
http://asrock.com/mb/overview.asp?Model=ALiveNF7G-HDready
I spoofed your devices on my own computer and installed the devices (and
their drivers).
Please try importing the attached Registry file in the VM, too, assuming
your non-present devices are still installed!
- Shao Miller
ÿþW i n d o w s R e g i s t r y E d i t o r V e r s i o n 5 . 0 0
[ H K E Y _ L O C A L _ M A C H I N E \ S Y S T E M \ C u r r e n t C o n t r o l S e t \ S e r v i c e s \ n v n e t b u s ]
"