Rank: Member
Groups: Member
Joined: 3/2/2007
Posts: 53
Points: 159
|
I ran this tool in beginner mode and went through the logfile it
produced. Some odd entries appeared in the section listed below.
Those below appear in the log and the files don't exist on my
system (the hyphen indicates that in the log), not do they exist
in the registry. So I'm puzzled where it gets them from:
011 HKLM\SYSTEM\CurrentControlSet\Services (drivers)
- c:\windows\system32\drivers\changer.sys (Changer)
- c:\windows\system32\drivers\i2omgmt.sys (i2omgmt)
- c:\windows\system32\drivers\lbrtfdc.sys (lbrtfdc)
- c:\windows\system32\drivers\pcidump.sys (PCIDump)
- c:\windows\system32\drivers\pdcomp.sys (PDCOMP)
- c:\windows\system32\drivers\pdframe.sys (PDFRAME)
- c:\windows\system32\drivers\pdreli.sys (PDRELI)
- c:\windows\system32\drivers\pdrframe.sys (PDRFRAME)
- c:\windows\system32\drivers\wdica.sys (WDICA)
I don't think this is a RS only problem though.
|
Rank: Administration
Groups: Administration
Joined: 2/16/2007
Posts: 141
Points: 192
Location: Belgium
|
See this thread : http://forum.sysinternals.com/forum_posts.asp?TID=11781&PID=53545#53545Quote:A valid driver entry does not necessarily have to include a valid image path. If there is none, then Windows will assume the default driver path which is "%Systemroot%\system32\drivers" plus filename.
 Lansweeper : free software and computer inventory
|
Rank: Member
Groups: Member
Joined: 3/2/2007
Posts: 53
Points: 159
|
Yes I know.  One for the FAQ?
|
