One of my application calls EnumPrinter API. It hangs on
a PC and exact hanging point is that EnumPrinter call.
Namely, EnumPrinter called and it doesn't return.

I checked the call stack of the thread when it hanged and
found a call via autochk.exe!0xXX.
Call stack looked something like :
- - - -
ntkrnlpa.exe!Something+0xXX
..
ntdll.dll!Something+0xXX
autochk.exe+0xXX
...
MyApp.exe!EnumPrinter+0xXX
- - - -
Why should autochk.exe be there? What does it do?
Could it be an virus?

Thanx.

--
Daewon YOON

On Feb 15, 4:47*pm, Tony <lizandtony at orcon dot net dot nz> wrote:
> TheOne <daewon.y...@gmail.com> wrote:
> >One of my application calls EnumPrinter API. It hangs on
> >a PC and exact hanging point is that EnumPrinter call.
> >Namely, EnumPrinter called and it doesn't return.
>
> >I checked the call stack of the thread when it hanged and
> >found a call via autochk.exe!0xXX.
> >Call stack looked something like :
> >- - - -
> > ntkrnlpa.exe!Something+0xXX
> > ..
> > ntdll.dll!Something+0xXX
> > autochk.exe+0xXX
> > ...
> > MyApp.exe!EnumPrinter+0xXX
> >- - - -
> >Why should autochk.exe be there? What does it do?
> >Could it be an virus?
>
> >Thanx.
>
> >--
> >Daewon YOON
>
> It is a Microsoft *function.
> Seehttp://www.processlibrary.com/directory/files/autochk/24826/
> Tony

I also read that explanation. What I don't really understand is that
some part of the autochk.exe code is shown in the stack of
one of myapp.exe's stack. autochk.exe is not executed at all.
It looks like autochk.exe is loadlibrary'ed like an dll, when myapp
is not explicitely loaded the exe.

Could anybody give me an answer or guess?

--
Daewon YOON