Re: Thread waiting when started from console
From: Peter Wieland [MSFT] (peterwie_at_online.microsoft.com)
Date: 07/12/04
- Next message: Jeff Henkels: "Re: Network adapter order (W2k)"
- Previous message: Eli Aran: "Re: USB driver for the palm m515"
- In reply to: sanjay: "Thread waiting when started from console"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 12 Jul 2004 12:06:24 -0700
i can't imagine why it would be different for a console app than a windows
app (unless the windows app is actively terminating the thread, but that
would requre that you support cancellation).
have you tried debugging your driver to see why it's not waking up the
thread?
-p
-- This posting is provided "AS IS" with no warranties, and confers no rights. "sanjay" <skanadeNOSPAM@vsnl.com> wrote in message news:eJJhNcAZEHA.716@TK2MSFTNGP11.phx.gbl... >I am posting this question here because this seems to be the right group. > > We have a virtual disk device driver developed by a third party that > mounts > a file as a disk drive. Basically the Windows application issues a > DeviceIoControl to the driver to mount the dos drive number. Then on > success, the application uses a DefineDosDevice to map the device. > > This all works fine from a normal application. > > But the moment it is done from a console application, after return from > the > Main, the console application fails to exit because the thread waits in > the > driver. The thread comes back only after the device is unloaded from > another > application. > > My question is what is different when done from console application. Why > should the thread wait? I am using Windows XP. > > Thanks. > > >
- Next message: Jeff Henkels: "Re: Network adapter order (W2k)"
- Previous message: Eli Aran: "Re: USB driver for the palm m515"
- In reply to: sanjay: "Thread waiting when started from console"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading