MapPtrToProcess vs MapCallerPtr
From: Alain Roberge (floroberge1_at_hotmail.com)
Date: 09/28/04
- Next message: Tom Gensel \(eMVP\): "Re: MapPtrToProcess vs MapCallerPtr"
- Previous message: Bruce Eitman \(eMVP\): "Re: Unable to configure CE.NET for more than 3 serial ports."
- Next in thread: Tom Gensel \(eMVP\): "Re: MapPtrToProcess vs MapCallerPtr"
- Reply: Tom Gensel \(eMVP\): "Re: MapPtrToProcess vs MapCallerPtr"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 28 Sep 2004 12:39:04 -0700
Hi,
I writed, a long time ago, a CE 2.11 stream interface driver. today, i use
source code and compile it with PB 5.0. My driver work fine but,
On each IOCTRL call , the driver call MapPtrToProcess. I use it to map the
input parameter. This parameter is a pointer to a structure.
I've see in the documentation that the MapPtrToProcess is deprecated. Use
MapCallerPtr function instead. But the MapCallerPtr is use to validate
parameter, not to map adress into the caller process. Do i must use
MapPrtToProcess again?
Thank you
- Next message: Tom Gensel \(eMVP\): "Re: MapPtrToProcess vs MapCallerPtr"
- Previous message: Bruce Eitman \(eMVP\): "Re: Unable to configure CE.NET for more than 3 serial ports."
- Next in thread: Tom Gensel \(eMVP\): "Re: MapPtrToProcess vs MapCallerPtr"
- Reply: Tom Gensel \(eMVP\): "Re: MapPtrToProcess vs MapCallerPtr"
- Messages sorted by: [ date ] [ thread ]