Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. COHi Shaihi, I have looked at DllMain and there is no debug print, I have added one in and will test it on Tuesday morning when I have access to the WM6 device again. I know for a fact no other debug prints are written at startup, so maybe putting in an instant debug may shred light on the issue to if the dll is even loaded. As to a dependency break, i do not know how to do this on a mobile OS. But in thinking about it the driver can be activated manually with ActiviateDevice, so surely all the needed dependencies are already installed, aren't they? Thank you for the suggestions.
      singulars
    2. COI missed the part that it loads under WM with ActivateDevice. This rules out dependency. Did you try to change the `order` filed in the registry? maybe the driver tries to load before some functionality it needs is ready.
      singulars
    3. COHi Shaihi, No problem, all help is appreciated. I did consider order and actually tried to make it load sooner rather than later incase of a COM port in use rather than dependency issue of other files not yet loaded, when I next get in ill set it to 255 and see if that helps. It maybe worth mentioning that someone has pointed out out the possible issue of signing. Whilst I have signed it with our cert, they have recommended to drop back down to the new (Jan 2010) SDK certificates and use cabsigner.exe instead of signtool.exe, and see if it loads. Could you see this been an possible issue? Thx
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload