Re: Problem with COM-Port after switching from Hive Based Registry -> RAM based

Tech-Archive recommends: Fix windows errors by optimizing your registry



I think you really mean to fix the Index value? Load order would work, but
Index is the way these things are supposed to be fixed.

If I recall correctly, wasn't this an issue mostly when working with
persistent registries that weren't hive based? The save/restore mechansim
ended up reversing the order of the keys in the registry on every boot,
which mattered if the Index key wasn't there.
--
Dean Ramsier - eMVP
BSQUARE Corporation


"Michel Verhagen [eMVP]" <myfirstname@xxxxxxxxxxxxx> wrote in message
news:eZH3R577JHA.4116@xxxxxxxxxxxxxxxxxxxxxxx
I meant "and *note* the order" (instead of "not")

Good luck,

Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog

GuruCE
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.

Michel Verhagen [eMVP] wrote:
When you switch from hive to RAM based registry (or vice versa) the
driver load order can change. I suspect this is the reason of the
strange behaviour you're seeing. Look closely at the log of the hive
based kernel and not the order of the drivers. Now switch to RAM and do
the same. If it is different you can force the load order by adding
"Order" values to the driver registry settings. Set the order to what it
was in hive and test again.

Good luck,

Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog

GuruCE
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.

Michael Haller wrote:
Hello,

I am working on a PXA270 CE6 platform. First I used an CE-Image with
Hive
Based Registry. Communication through RS232 is working. After I
switched to
RAM based registry, the Open Port is OK, but the WriteFile sends no
data.
Why?

Thank you in advance

Michael




.

Relevant Pages