8-Port UART PCI card doesn't work on WinXPE with PnP Kernel only

[Guest]

Hi Slobodan
As you remember we have 8-Port UART PCI card that work OK on WinXPE with PnP (User mode) component and doesn't work on WinXPE with PnP kernel only component
And as you recommend me I get offline registry image from the first (working) WinXPE (using RegFlushKey() to manually flush registry data). Then I import all registry data related to this card to its component in Component Designer.
I also set cmiIsCriticalDevice = TRUE to this device in TD
But when I start project BUILDING procedure in TD I receive

Building: "OEM Communications Port [Version 2.0.0.0, R5]"..
Warning 1116: Building unreleased component: "OEM Communications Port [Version 2.0.0.0, R5]
Warning 1006: Invalid registry data fixup: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E978-E325-11CE-BFC1-08002BE10318}
As result this device doesn’t work on PnP Kernel WinXPE

Can you explain about “Warning 1006â€
Maybe I need to do additional steps to run this card on PnP Kernel WinXPE

Thank you
Regards
Yur

 

[Slobodan Brcin \(eMVP\)]

Hi Yury,

I don't know what is relation between RegFlushKey and offline registry, but
it is irrelevant.

1006 Error is problem in component designer that is related to named default
value. This value should be "Ports (COM & LPT)" for GUID you mention, and
you will have to enter it manually in CD to make a workaround, but this is
not what prevents your card from working.

If you are making component and register it from scratch from registry then
you will not have in advanced options "cmiIsCriticalDevice".

If you can post this component as attachment in this NG.

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Hi Slobodan,
As you remember we have 8-Port UART PCI card that work OK on WinXPE with

PnP (User mode) component and doesn't work on WinXPE with PnP kernel only
component.

And as you recommend me I get offline registry image from the first

(working) WinXPE (using RegFlushKey() to manually flush registry data). Then
I import all registry data related to this card to its component in
Component Designer.

I also set cmiIsCriticalDevice = TRUE to this device in TD.
But when I start project BUILDING procedure in TD I receive:

Building: "OEM Communications Port [Version 2.0.0.0, R5]"...
Warning 1116: Building unreleased component: "OEM Communications Port [Version 2.0.0.0, R5]"
Warning 1006: Invalid registry data fixup: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E978-E325-11CE-BF
C1-08002BE10318}
As result this device doesn't work on PnP Kernel WinXPE.

Can you explain about "Warning 1006"?
Maybe I need to do additional steps to run this card on PnP Kernel WinXPE?

Thank you.
Regards,
Yury

 

[Slobodan Brcin \(eMVP\)]

1. I have minlogon also.
You can reboot your device with fba -reboot command.
Or with shutdown util.
They will gracefully close XPe registry.

2. You can use outlook express.
News server:
news.microsoft.com

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Hi Slobodan,
1. I have a minlogon WinXPE build, as result registry entries get lost

when I reboot. To save all working registry entries I include to our
application code (we run it as custom shell) RegFlushKey().

2. Please explain how I can post this component as attachment in NG (I

can't see this option in Reply window).

 

[Slobodan Brcin \(eMVP\)]

Yury,

I have looked at your components and inf file.

1. You should make component from windows inf folder or copy required inf
files to your inf files folder before import in CD.
You had errors during the import you forgot to tell us.
You need mf.inf file for import to succeed.

2. You should have four components from two inf files.
oemport.inf will give you one component for one driver.
ser15x.inf will give you three components for one driver.

You should mark all of them as Critical and it should work. If not then you
are on your own with registry values and their meaning, there is too much
values involved to easily pinpoint what is the problem.


Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Hi Slobodan,
1. I have a minlogon WinXPE build, as result registry entries get lost

when I reboot. To save all working registry entries I include to our
application code (we run it as custom shell) RegFlushKey().

2. Please explain how I can post this component as attachment in NG (I

can't see this option in Reply window).