Pool Tag를 이용하여 3rd Party Driver를 찾을 수 있다.
아래 굵게 표시된 부분을 꼭 읽어 보시기 바랍니다.
To find files that (potentially) use a given pool tag, use the Search tool in Windows 2000:
- Click Start, point to Search, and then click For Files or Folders.
- In the Search for files or folders named box, type *.sys.
- In the Containing text box, type the pool tag you want to search for.
- In the Look in box, type the path to the system root drivers, for example, C:\WINNT\system32\drivers, and then clickSearch Now.
You should receive a list of drivers that contain the tag. Although there may be some false hits here (as the text string may naturally occur in other files), this method should allow you to narrow the scope of your search.
You can use the findstr command (in all versions of Windows) instead of Windows Explorer. To minimize the occurrence of false hits, change to the system root\drivers folder at a command prompt. If needed, use Windows Explorer to find this folder. Run thefindstr /m /l tag *.sys command, where the /m switch is used to list only the file name. If you receive multiple files, try to reduce the amount of files returns by adding the letter "h" to the tag before you run the search. This is mainly useful when the tag is comprised of three letters.
Note You may find that this query may not find the appropriate driver because the driver is not loaded from %SYSTEMROOT%\drivers. In this case, run more global searches such as findstr /m /l tag *.sys that start from %SystemRoot%, %ProgramFiles%, %SystemDrive%, %ProgramData%. For examples, use the findstr /m /l hTCPt *.sys command to return Tcpip.sys and findstr /m /l hCPnp *.sys to return Classpnp.sys or Acpiec.sys depending on which operating system you are running.
참조 - http://support.microsoft.com/kb/298102/en-us
'Microsoft > Windows Server' 카테고리의 다른 글
Task Scheduler Log / 작업 스케줄러 로그 (0) | 2015.01.06 |
---|---|
그룹 정책 / Group Policy (0) | 2015.01.06 |
드라이버란? (0) | 2014.11.27 |
Windows Server 2012 R2 / .NET Framework 3.5 실패 (0) | 2014.11.19 |
서비스팩 1 설치 후 Remote Desktop Service 예상치 않은 종료 이슈 (0) | 2014.11.17 |