Re: how to load in a build in driver whose index is greater 10 in Windows CE

In my VCA_Init function, I have this:
lStatus = RegQueryValueEx( hKey, TEXT("Name"), NULL, &dwValType,
(LPBYTE) szName, &dwSize) ;
it failed at here, RegQueryValueEx return failed.

Paul G. Tobey [eMVP] wrote:
I don't understand what you're saying the problem is. You *do* already have
an entry for the driver to load it at boot time. Maybe there's confusion
about the fact that numbers in the registry files are all hexadecimal, as
Bruce said.

Further, as Steve said, you *cannot* have a COM23: that you can open as
"COM23:". You must use the $device mount point to reference such a driver.

Paul T.

<suqian99@xxxxxxxxxxx> wrote in message
news:1167244326.253599.158140@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Yes,

I want to suport maxium 60 ports.
Bruce Eitman [eMVP] wrote:
That isn't index 12, it is index 0x12 or 18. Is that what you mean and
does
your code support DeviceArrayIndex 0x12?

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

<suqian99@xxxxxxxxxxx> wrote in message
news:1167243157.385773.133820@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi, Steve, thank you for your reply.

I know I can open it with the $device mount point: "\$device\VCA12".
But I likt this VCA12 as a build in driver, which will be load when the
sytem boots up. I already have VCA0 to VCA9. All of them have a
registry key like this:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Sample]
"Prefix"="VCA"
"Dll"="sample.dll"
"DeviceArrayIndex"=dword:12
"Index"=dword:0
"Order"=dword:30

the question is how to create a registry key for the VCA12, so it can
load in at the boot time.

thanks,

Mike.
Steve Schrock [MS] wrote:
Why is VCA_Init failing?

If it is failing due to a device naming issue, here is the answer. The
prefix-index-colon name is limited to 10 instances (0-9). If you are
using
CE 5.0 or greater, you can actually use an index greater than 9.
However
instead of opening "VCA12:", you will need to open the driver instance
from
the $device mount point: "\$device\VCA12"

Take a look at the "Device File Names" topic in PB Help or MSDN for
more
information about this.

--
Steve Schrock
Windows Devices Core BSPs

This posting is provided "AS IS" with no warranties, and confers no
rights.

<suqian99@xxxxxxxxxxx> wrote in message
news:1167238862.302385.148420@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi, All.

I want to load in a WinCE driver, its index is 12. How to do it?

My registry file is like this:

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Sample]
"Prefix"="VCA"
"Dll"="sample.dll"
"DeviceArrayIndex"=dword:12
"Index"=dword:12
"Order"=dword:30

But i failed at the VCA_Init function.

any trick to do this?

thanks,

Mike.




.

Relevant Pages

  • Re: "No .rel file found for module "
    ... Do you have the debug output from loading with KITL enabled? ... Bruce Eitman (eMVP) ... I2C driver when it is launched through KITL. ... I thought maybe it was the registry data too, ...
    (microsoft.public.windowsce.app.development)
  • Re: "No .rel file found for module "
    ... about your dll, assuming it has gotten far enough to attempt to load it. ... I thought maybe it was the registry data too, ... The driver is straight from freescale and is supposedly good, ...
    (microsoft.public.windowsce.app.development)
  • Re: "No .rel file found for module "
    ... Bruce Eitman (eMVP) ... beitman AT applieddata DOT net ... different BSP and trying to integrate a driver from freescale. ... I thought maybe it was the registry data too, ...
    (microsoft.public.windowsce.app.development)
  • Re: CE Event Log
    ... I guess it depends on *how* the registry is set, ... logging turned on in the driver, ... registry entries that you changed and why you're loading this driver, ... This is a Wifi device and I have a driver which does load and works. ...
    (microsoft.public.windowsce.embedded)
  • Re: "No .rel file found for module "
    ... it will only load if I launch the image with KITL enabled. ... I2C driver when it is launched through KITL. ... "Dean Ramsier" wrote: ... I thought maybe it was the registry data too, ...
    (microsoft.public.windowsce.app.development)