Maxim S. Shatskih wrote:
>But depends doesn’t know that it’s supposed to look at .sys files to
>satisfy imports. It’s only going to use the normal system DLL search
>path, which finds only user-mode DLLs.
>
>
Not, it also shows NTOSKRNL and HAL imports fine.
OK, I have to admit that I am ALMOST completely wrong on this. It makes
sense that it would search NTOSKRNL and HAL, since those are located in
system32, and since 99% of all drivers can be satisfied completely from
those two files, that works most of the time.
Further, it will also search for imports in the directory that contains
the target DLL. So, if you run “depends” on a module living in
system32\drivers, it will find dependencies in other .sys files as well.
BUT, if you run “depends” on a .sys file that lives elsewhere, such as
in your own obj_chk_x86\i386 directory, then it will NOT automatically
search in system32\drivers. That can cause it to diagnost missing
dependencies in wmilib.sys or ks.sys, as two common examples.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
You are persisting in error. It works with ks.sys just fine. And it works
from an arbitrary folder, such as C:\ks.
Why dont you try before you post ? It wouldnt take you more than 2 mins.
Dan
----- Original Message -----
From: “Tim Roberts”
To: “Windows System Software Devs Interest List”
Sent: Tuesday, March 14, 2006 7:10 PM
Subject: Re: [ntdev] ERROR_PROC_NOT_FOUND
> Maxim S. Shatskih wrote:
>
>>>But depends doesn’t know that it’s supposed to look at .sys files to
>>>satisfy imports. It’s only going to use the normal system DLL search
>>>path, which finds only user-mode DLLs.
>>>
>>>
>>
>>Not, it also shows NTOSKRNL and HAL imports fine.
>>
>>
>
> OK, I have to admit that I am ALMOST completely wrong on this. It makes
> sense that it would search NTOSKRNL and HAL, since those are located in
> system32, and since 99% of all drivers can be satisfied completely from
> those two files, that works most of the time.
>
> Further, it will also search for imports in the directory that contains
> the target DLL. So, if you run “depends” on a module living in
> system32\drivers, it will find dependencies in other .sys files as well.
>
> BUT, if you run “depends” on a .sys file that lives elsewhere, such as
> in your own obj_chk_x86\i386 directory, then it will NOT automatically
> search in system32\drivers. That can cause it to diagnost missing
> dependencies in wmilib.sys or ks.sys, as two common examples.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
Also, I hope you are aware that latest version can be fully configured with
arbitrary user directories ? I ass this for the sake of other ppl which
might
read the list.
Dan
----- Original Message -----
From: “Tim Roberts”
To: “Windows System Software Devs Interest List”
Sent: Tuesday, March 14, 2006 7:10 PM
Subject: Re: [ntdev] ERROR_PROC_NOT_FOUND
> Maxim S. Shatskih wrote:
>
>>>But depends doesn’t know that it’s supposed to look at .sys files to
>>>satisfy imports. It’s only going to use the normal system DLL search
>>>path, which finds only user-mode DLLs.
>>>
>>>
>>
>>Not, it also shows NTOSKRNL and HAL imports fine.
>>
>>
>
> OK, I have to admit that I am ALMOST completely wrong on this. It makes
> sense that it would search NTOSKRNL and HAL, since those are located in
> system32, and since 99% of all drivers can be satisfied completely from
> those two files, that works most of the time.
>
> Further, it will also search for imports in the directory that contains
> the target DLL. So, if you run “depends” on a module living in
> system32\drivers, it will find dependencies in other .sys files as well.
>
> BUT, if you run “depends” on a .sys file that lives elsewhere, such as
> in your own obj_chk_x86\i386 directory, then it will NOT automatically
> search in system32\drivers. That can cause it to diagnost missing
> dependencies in wmilib.sys or ks.sys, as two common examples.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
Dan Partelly wrote:
You are persisting in error. It works with ks.sys just fine. And it works
from an arbitrary folder, such as C:\ks.
Why dont you try before you post ? It wouldnt take you more than 2 mins.
I DID try it before I posted. I may be dense, but I’m not stupid. It
did NOT find either ks.sys or wmilib.sys.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Ok, then you failed to configure your tool. It just works.
Dan
----- Original Message -----
From: “Tim Roberts”
To: “Windows System Software Devs Interest List”
Sent: Tuesday, March 14, 2006 10:06 PM
Subject: Re: [ntdev] ERROR_PROC_NOT_FOUND
> Dan Partelly wrote:
>
>> You are persisting in error. It works with ks.sys just fine. And it works
>> from an arbitrary folder, such as C:\ks.
>>
>> Why dont you try before you post ? It wouldnt take you more than 2 mins.
>
>
> I DID try it before I posted. I may be dense, but I’m not stupid. It
> did NOT find either ks.sys or wmilib.sys.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer