WriteRegistryToOEM/ReadRegistryFromOEM

Hi,
I am looking into WriteRegistryToOEM/ReadRegistryFromOEM to implement saving
of my touch calibration (as everyone is doing all the time)

The documentation confuses me a bit :
"Only a fully saved registry can be restored; attempting to restore a
partial registry produces unpredictable results"

I was planning to only save/restore the branch containing the touch
callibration.
In the simplest form, I would ignore the data parameters passed to the write
function, and just write 1 specific branch or value. Also when reading, I
want to use the read-call only as a trigger to read in that specific branch.

Will this work ?
Is the (RAM BASED) registry already present when the first read call comes
at boot-time ? Can I use regular registry-functions to get the data I need ?
(ignoring the data passed).

From the description it looks like the read is called very early on in the
initialisation process. So I guess my harddisk is not mounted yet. Can I
still use this mechanism when the drive is mounted, or will I not receive a
call to read anymore ?
In that case I would need to read in the data myself at some point (after HD
mount, and before touch-driver-loading), and just use the
WriteRegistryFromOem function, to update the datafile when the calibration
application has run, right ?

If there is a way to re-init the touch driver, I could keep the whole
process of saving and restoring OS-independent. Can I do this using
ActivateDeviceEx() and its counterpart ? (or just launch the touch driver
from the reg-read-app I will create)

I donot want to waste time figuring all this out, escpecially since it has
been done a zillion times. So if you've made a solution, please let me know.

Greetings,
Rob.

Mike
Fri Mar 14 06:12:25 PDT 2008

=?Utf-8?B?Um9i?= <Rob@discussions.microsoft.com> wrote in
news:064D754C-FD77-481A-AB8E-742974E0E78C@microsoft.com:

> Hi,
> I am looking into WriteRegistryToOEM/ReadRegistryFromOEM to implement
> saving of my touch calibration (as everyone is doing all the time)
>
> The documentation confuses me a bit :
> "Only a fully saved registry can be restored; attempting to restore a
> partial registry produces unpredictable results"
>
> I was planning to only save/restore the branch containing the touch
> callibration.
> In the simplest form, I would ignore the data parameters passed to the
> write function, and just write 1 specific branch or value. Also when
> reading, I want to use the read-call only as a trigger to read in that
> specific branch.
>
> Will this work ?
> Is the (RAM BASED) registry already present when the first read call
> comes at boot-time ? Can I use regular registry-functions to get the
> data I need ? (ignoring the data passed).
>
> From the description it looks like the read is called very early on in
> the initialisation process. So I guess my harddisk is not mounted yet.
> Can I still use this mechanism when the drive is mounted, or will I
> not receive a call to read anymore ?
> In that case I would need to read in the data myself at some point
> (after HD mount, and before touch-driver-loading), and just use the
> WriteRegistryFromOem function, to update the datafile when the
> calibration application has run, right ?
>
> If there is a way to re-init the touch driver, I could keep the whole
> process of saving and restoring OS-independent. Can I do this using
> ActivateDeviceEx() and its counterpart ? (or just launch the touch
> driver from the reg-read-app I will create)
>
> I donot want to waste time figuring all this out, escpecially since it
> has been done a zillion times. So if you've made a solution, please
> let me know.
>
> Greetings,
> Rob.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

Why you don't use teh hive based registry?

regards,

Mike

--
Digi International Inc.
http://www.digi.com

Dean
Fri Mar 14 06:16:06 PDT 2008

Read/WriteRegistry OEM functions save and restore the entire registry. So
no, you can't do what you are describing.

If all you care about is the touch calibration, save and restore that value
yourself before the touch driver is loaded. Note that the touch driver is a
native driver that is loaded directly by gwes, not devmgr. So it is not
loaded by ActivateDeviceEx. You just need to ensure that you've restored
the calibration data before gwes loads. You can do that by inserting a
small application in the loading sequence before gwes loads and after the
hard drive is available.

--
Dean Ramsier - eMVP
BSQUARE Corporation


"Rob" <Rob@discussions.microsoft.com> wrote in message
news:064D754C-FD77-481A-AB8E-742974E0E78C@microsoft.com...
> Hi,
> I am looking into WriteRegistryToOEM/ReadRegistryFromOEM to implement
> saving
> of my touch calibration (as everyone is doing all the time)
>
> The documentation confuses me a bit :
> "Only a fully saved registry can be restored; attempting to restore a
> partial registry produces unpredictable results"
>
> I was planning to only save/restore the branch containing the touch
> callibration.
> In the simplest form, I would ignore the data parameters passed to the
> write
> function, and just write 1 specific branch or value. Also when reading, I
> want to use the read-call only as a trigger to read in that specific
> branch.
>
> Will this work ?
> Is the (RAM BASED) registry already present when the first read call comes
> at boot-time ? Can I use regular registry-functions to get the data I need
> ?
> (ignoring the data passed).
>
> From the description it looks like the read is called very early on in the
> initialisation process. So I guess my harddisk is not mounted yet. Can I
> still use this mechanism when the drive is mounted, or will I not receive
> a
> call to read anymore ?
> In that case I would need to read in the data myself at some point (after
> HD
> mount, and before touch-driver-loading), and just use the
> WriteRegistryFromOem function, to update the datafile when the calibration
> application has run, right ?
>
> If there is a way to re-init the touch driver, I could keep the whole
> process of saving and restoring OS-independent. Can I do this using
> ActivateDeviceEx() and its counterpart ? (or just launch the touch driver
> from the reg-read-app I will create)
>
> I donot want to waste time figuring all this out, escpecially since it has
> been done a zillion times. So if you've made a solution, please let me
> know.
>
> Greetings,
> Rob.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

Rob
Fri Mar 14 06:32:01 PDT 2008

I donot want to use Hyve because the booting of the device should not be
dependent on a file somewhere on disk. RAM based always boots the same, I
like that. If for some reason my data cannot be read, the OS is still up, and
my app is running, too bad that there is no touch-calibration, but the
process is running....

Greetings,
Rob.


"Mike E." wrote:

> =?Utf-8?B?Um9i?= <Rob@discussions.microsoft.com> wrote in
> news:064D754C-FD77-481A-AB8E-742974E0E78C@microsoft.com:
>
> > Hi,
> > I am looking into WriteRegistryToOEM/ReadRegistryFromOEM to implement
> > saving of my touch calibration (as everyone is doing all the time)
> >
> > The documentation confuses me a bit :
> > "Only a fully saved registry can be restored; attempting to restore a
> > partial registry produces unpredictable results"
> >
> > I was planning to only save/restore the branch containing the touch
> > callibration.
> > In the simplest form, I would ignore the data parameters passed to the
> > write function, and just write 1 specific branch or value. Also when
> > reading, I want to use the read-call only as a trigger to read in that
> > specific branch.
> >
> > Will this work ?
> > Is the (RAM BASED) registry already present when the first read call
> > comes at boot-time ? Can I use regular registry-functions to get the
> > data I need ? (ignoring the data passed).
> >
> > From the description it looks like the read is called very early on in
> > the initialisation process. So I guess my harddisk is not mounted yet.
> > Can I still use this mechanism when the drive is mounted, or will I
> > not receive a call to read anymore ?
> > In that case I would need to read in the data myself at some point
> > (after HD mount, and before touch-driver-loading), and just use the
> > WriteRegistryFromOem function, to update the datafile when the
> > calibration application has run, right ?
> >
> > If there is a way to re-init the touch driver, I could keep the whole
> > process of saving and restoring OS-independent. Can I do this using
> > ActivateDeviceEx() and its counterpart ? (or just launch the touch
> > driver from the reg-read-app I will create)
> >
> > I donot want to waste time figuring all this out, escpecially since it
> > has been done a zillion times. So if you've made a solution, please
> > let me know.
> >
> > Greetings,
> > Rob.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> Why you don't use teh hive based registry?
>
> regards,
>
> Mike
>
> --
> Digi International Inc.
> http://www.digi.com
>

Rob
Fri Mar 14 06:34:04 PDT 2008

Thanks, I'll try that....
Isn't gwes normally loaded before the devmgr ? (CE6.0)
if so, Can I swap that without consequences ?

Greetings,
Rob



"Dean Ramsier" wrote:

> Read/WriteRegistry OEM functions save and restore the entire registry. So
> no, you can't do what you are describing.
>
> If all you care about is the touch calibration, save and restore that value
> yourself before the touch driver is loaded. Note that the touch driver is a
> native driver that is loaded directly by gwes, not devmgr. So it is not
> loaded by ActivateDeviceEx. You just need to ensure that you've restored
> the calibration data before gwes loads. You can do that by inserting a
> small application in the loading sequence before gwes loads and after the
> hard drive is available.
>
> --
> Dean Ramsier - eMVP
> BSQUARE Corporation
>
>
> "Rob" <Rob@discussions.microsoft.com> wrote in message
> news:064D754C-FD77-481A-AB8E-742974E0E78C@microsoft.com...
> > Hi,
> > I am looking into WriteRegistryToOEM/ReadRegistryFromOEM to implement
> > saving
> > of my touch calibration (as everyone is doing all the time)
> >
> > The documentation confuses me a bit :
> > "Only a fully saved registry can be restored; attempting to restore a
> > partial registry produces unpredictable results"
> >
> > I was planning to only save/restore the branch containing the touch
> > callibration.
> > In the simplest form, I would ignore the data parameters passed to the
> > write
> > function, and just write 1 specific branch or value. Also when reading, I
> > want to use the read-call only as a trigger to read in that specific
> > branch.
> >
> > Will this work ?
> > Is the (RAM BASED) registry already present when the first read call comes
> > at boot-time ? Can I use regular registry-functions to get the data I need
> > ?
> > (ignoring the data passed).
> >
> > From the description it looks like the read is called very early on in the
> > initialisation process. So I guess my harddisk is not mounted yet. Can I
> > still use this mechanism when the drive is mounted, or will I not receive
> > a
> > call to read anymore ?
> > In that case I would need to read in the data myself at some point (after
> > HD
> > mount, and before touch-driver-loading), and just use the
> > WriteRegistryFromOem function, to update the datafile when the calibration
> > application has run, right ?
> >
> > If there is a way to re-init the touch driver, I could keep the whole
> > process of saving and restoring OS-independent. Can I do this using
> > ActivateDeviceEx() and its counterpart ? (or just launch the touch driver
> > from the reg-read-app I will create)
> >
> > I donot want to waste time figuring all this out, escpecially since it has
> > been done a zillion times. So if you've made a solution, please let me
> > know.
> >
> > Greetings,
> > Rob.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>

Bruce
Fri Mar 14 06:36:52 PDT 2008

You can use the OEMIoControl IOCTL_HAL_INITREGISTRY to put the calibration
data into the registry.

--
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

"Rob" <Rob@discussions.microsoft.com> wrote in message
news:B0155729-ACFE-4B29-B696-BA8626836E1A@microsoft.com...
>I donot want to use Hyve because the booting of the device should not be
> dependent on a file somewhere on disk. RAM based always boots the same, I
> like that. If for some reason my data cannot be read, the OS is still up,
> and
> my app is running, too bad that there is no touch-calibration, but the
> process is running....
>
> Greetings,
> Rob.
>
>
> "Mike E." wrote:
>
>> =?Utf-8?B?Um9i?= <Rob@discussions.microsoft.com> wrote in
>> news:064D754C-FD77-481A-AB8E-742974E0E78C@microsoft.com:
>>
>> > Hi,
>> > I am looking into WriteRegistryToOEM/ReadRegistryFromOEM to implement
>> > saving of my touch calibration (as everyone is doing all the time)
>> >
>> > The documentation confuses me a bit :
>> > "Only a fully saved registry can be restored; attempting to restore a
>> > partial registry produces unpredictable results"
>> >
>> > I was planning to only save/restore the branch containing the touch
>> > callibration.
>> > In the simplest form, I would ignore the data parameters passed to the
>> > write function, and just write 1 specific branch or value. Also when
>> > reading, I want to use the read-call only as a trigger to read in that
>> > specific branch.
>> >
>> > Will this work ?
>> > Is the (RAM BASED) registry already present when the first read call
>> > comes at boot-time ? Can I use regular registry-functions to get the
>> > data I need ? (ignoring the data passed).
>> >
>> > From the description it looks like the read is called very early on in
>> > the initialisation process. So I guess my harddisk is not mounted yet.
>> > Can I still use this mechanism when the drive is mounted, or will I
>> > not receive a call to read anymore ?
>> > In that case I would need to read in the data myself at some point
>> > (after HD mount, and before touch-driver-loading), and just use the
>> > WriteRegistryFromOem function, to update the datafile when the
>> > calibration application has run, right ?
>> >
>> > If there is a way to re-init the touch driver, I could keep the whole
>> > process of saving and restoring OS-independent. Can I do this using
>> > ActivateDeviceEx() and its counterpart ? (or just launch the touch
>> > driver from the reg-read-app I will create)
>> >
>> > I donot want to waste time figuring all this out, escpecially since it
>> > has been done a zillion times. So if you've made a solution, please
>> > let me know.
>> >
>> > Greetings,
>> > Rob.
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>>
>> Why you don't use teh hive based registry?
>>
>> regards,
>>
>> Mike
>>
>> --
>> Digi International Inc.
>> http://www.digi.com
>>

Dean
Fri Mar 14 11:28:46 PDT 2008

No, it's not. Devmgr loads before gwes.

--
Dean Ramsier - eMVP
BSQUARE Corporation


"Rob" <Rob@discussions.microsoft.com> wrote in message
news:BB29911A-4D02-453B-A42D-418A7F559C55@microsoft.com...
> Thanks, I'll try that....
> Isn't gwes normally loaded before the devmgr ? (CE6.0)
> if so, Can I swap that without consequences ?
>
> Greetings,
> Rob
>
>
>
> "Dean Ramsier" wrote:
>
>> Read/WriteRegistry OEM functions save and restore the entire registry.
>> So
>> no, you can't do what you are describing.
>>
>> If all you care about is the touch calibration, save and restore that
>> value
>> yourself before the touch driver is loaded. Note that the touch driver
>> is a
>> native driver that is loaded directly by gwes, not devmgr. So it is not
>> loaded by ActivateDeviceEx. You just need to ensure that you've restored
>> the calibration data before gwes loads. You can do that by inserting a
>> small application in the loading sequence before gwes loads and after the
>> hard drive is available.
>>
>> --
>> Dean Ramsier - eMVP
>> BSQUARE Corporation
>>
>>
>> "Rob" <Rob@discussions.microsoft.com> wrote in message
>> news:064D754C-FD77-481A-AB8E-742974E0E78C@microsoft.com...
>> > Hi,
>> > I am looking into WriteRegistryToOEM/ReadRegistryFromOEM to implement
>> > saving
>> > of my touch calibration (as everyone is doing all the time)
>> >
>> > The documentation confuses me a bit :
>> > "Only a fully saved registry can be restored; attempting to restore a
>> > partial registry produces unpredictable results"
>> >
>> > I was planning to only save/restore the branch containing the touch
>> > callibration.
>> > In the simplest form, I would ignore the data parameters passed to the
>> > write
>> > function, and just write 1 specific branch or value. Also when reading,
>> > I
>> > want to use the read-call only as a trigger to read in that specific
>> > branch.
>> >
>> > Will this work ?
>> > Is the (RAM BASED) registry already present when the first read call
>> > comes
>> > at boot-time ? Can I use regular registry-functions to get the data I
>> > need
>> > ?
>> > (ignoring the data passed).
>> >
>> > From the description it looks like the read is called very early on in
>> > the
>> > initialisation process. So I guess my harddisk is not mounted yet. Can
>> > I
>> > still use this mechanism when the drive is mounted, or will I not
>> > receive
>> > a
>> > call to read anymore ?
>> > In that case I would need to read in the data myself at some point
>> > (after
>> > HD
>> > mount, and before touch-driver-loading), and just use the
>> > WriteRegistryFromOem function, to update the datafile when the
>> > calibration
>> > application has run, right ?
>> >
>> > If there is a way to re-init the touch driver, I could keep the whole
>> > process of saving and restoring OS-independent. Can I do this using
>> > ActivateDeviceEx() and its counterpart ? (or just launch the touch
>> > driver
>> > from the reg-read-app I will create)
>> >
>> > I donot want to waste time figuring all this out, escpecially since it
>> > has
>> > been done a zillion times. So if you've made a solution, please let me
>> > know.
>> >
>> > Greetings,
>> > Rob.
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>>
>>
>>