Hello,

 An array failed and I performed an off-line backup across the network to an external SATA HDD.  I have tried restoring to a physical machine and a virtual machine via VMWare's Converter and via booting the SP recovery CD in a VM. 

(P2P): Restoring to a physical machine made HIR to request the driver for IntelPPM.SYS and it's INF.  I could not find anything on the Internet for a download source for these files.  Ignoring and rebooting resulted with a registry hive missing, if I recall.  (P2V): So, in my attempt to do an end-run around the issue, I thought I might try VMWare's Converter thinking that it might handle the problem.  The converter indicated that a registry problem was fixed but later failed during the conversion process.  (P2V): After this failure, I tried restoring to a VM with the same issue of HIR requesting the IntelPPM.SYS and IntelPPM.INF.  Ignoring the driver causes a BSOD of C0000263 (Driver Entry Point Not Found) and referenced FLTMGR.SYS.

I've found the IntelPPM.SYS but there is no INF.  I've looked within the backup and on the physical server and the INF is not to be found.  I am out of ideas.

Any assistance on how to solve this problem would be greatly appreciated!

Also, the enviroment of the source is and Intel P3 running windows 2000 server and is being moved to an Intel Dual Core (either P or V).

did you ever manage to locate the inf file, if so , where?

No. I ended up mounting the backup and extracting the data.

Slightly late....but if anyone stumbles on this and needs some help......

A range of Microsoft drivers are actually delivered in Service Packs and Hotfixes. They do not, necessarily, have a matching *.inf file. IntelPPM.SYS is an example of this. In many cases, the driver files are bundled as part of a group, together with a single *.inf file that covers the range of *.sys files. In other words the name of the *.inf file may not match the name of the driver.

There are 3 ways to find the matching *.inf file:
(1) Search for the name of the driver (in this case IntelPPM) and look for the corresponding *.cab file. You should then be able to unpack the cab and find a suitable *.inf in there, albeit with a different name. If there is only one *.inf file it's easy.

(2) Search through the registry for "IntelPPM". In many cases there are will a key that marked with something like "InfPath" and it will list the corresponding *.inf. In your case, the matching *.inf file is:

C:\WINDOWS\inf\cpu.inf 

(3) Run a search against the C:\WINDOWS\inf\ directory, looking for the driver name INSIDE the file.