Re: context questions
- From: "Bruce Eitman \(eMVP\)" <beitmannospam@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 29 Jun 2005 21:35:54 -0400
The driver is always running in device.exe (unless you specifically do a
LoadLibrary) so the memory is still accessible to you.
Are you having a problem that you need to solve or is this just
philisophical?
--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net
Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member
"telus" <tobeno1@xxxxxxxxx> wrote in message
news:qNHwe.100195$9A2.18194@xxxxxxxxxxx
> Hi,
>
> I'm developing a driver for PPC 2003. The driver is loaded in device.exe
> address space and is located in slot 0. During Driver_Init I allocate a
> memory and save a pointer in a global variable in the driver. Whenever an
> application opens the driver, I need to save some information in the
memory.
>
> 1) In Driver_Open call of the driver, I'm in the application context, not
> device.exe context, right?
> 2) If 1) is true, how can I access the memory which is allocated in
> Driver_Init which is in device.exe context? Do I have to add the pointer
> with a base address of the slot of device.exe and call MapPtrToProcess?
>
> TIA
>
>
.
- Follow-Ups:
- Re: context questions
- From: telus
- Re: context questions
- References:
- context questions
- From: telus
- context questions
- Prev by Date: context questions
- Next by Date: Re: context questions
- Previous by thread: context questions
- Next by thread: Re: context questions
- Index(es):
Relevant Pages
|
|
