Jump to content

driver development - signing


Guest tomas

Recommended Posts

Guest tomas

Hi, we are porting a driver to Smarthone

- we finally figured out how to to create a .cab to modify both the protected DriversBuilIn keys and HARDWAREDEVICEMAPKEYBD, but the driver .DLLs do not load at all...

Is it because the IPSMWindows path is wrong at the boot time, or the drivers loaded by device.exe or gwes.exe must have some special level of trust?

If so, how to get it?

Under other WinCE 3.0 platforms it is possible to use absolute paths, even from removable storage.

I think the Smartpone kernel is little modified from standard WinCE3.0 (.MUI support..). Is there something, that prevents ordinary .DLL's be loaded by more trusted components like gwes or device.exe?

Thank you for any help,

tomas

Link to comment
Share on other sites

  • 2 weeks later...

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.