Have you injected the drivers into the hard drive after the image is deployed? Are you using Sysprep?
No i haven't injected the drivers because i don't have them.
I manage to extract VirtualMachineAdditions.msi but i didn't found the drivers.
I use sysprep and the installing driver process works good on real computer.
Do you know where i can found the Virtual PC drivers ...
When using VMware if you install the VMware tools it will install the drivers for network adapter, video card and so on. I am not sure if Virtual PC has such similar tools.
Virtual PC as additional tools two for graphic, lan, sound, but the problem is for other devices ....
So that key is populated the moment you run Sysprep. Pointing to a Sysprep file later does NOT populate that key. So if you did not have a value when you ran Sysprep on the machine you were going to image, there would be nothing in that key.
It has been a while since I have done this, but isn't that the main reason that Jan Buelens wrote ldprep, so he could populate that key later in the process.
I already use ldprep, and on real machine it well populate the devicepath by adding the différent c:\drivers paths.
But in the case of my virtual machine as it is empty it populate nothing but maybe there is a bug that flush the existing key.
I just make another test with some drivers folder in the c:\drivers (Lan, video, sound) and all seems to work fine
I have noticed the same thing with ldprep.exe
Its like it opens up devicepath, then tries to append to it, but if it was blank to begin with, it doesn't populate it with anything.
Try putting "c:\windows\inf" in there first by hand.
I no more have the problem, since i put driver folders on c:\drivers.
But i will communicate this bug to LDprep developpers..