locked
CeSetUserNotificationEx and IOCTL_KLIB_GETALARMRESOLUTION RRS feed

  • Question

  • CeSetUserNotificationEx ( http://msdn.microsoft.com/en-us/library/ms928547.aspx ) seems to be a documentated function.
    The header file ( Notify.h ) is available in the SDK

    The link also points to IOCTL_KLIB_GETALARMRESOLUTION ( http://msdn.microsoft.com/en-us/library/ms903190.aspx )

    However, this is defined in header file ( Pkfuncs.h ) which is NOT available in the SDK ... (I've found another blog-post saying that it was in the platform builder).

    ---

    So, two question-parts:
       1 - How can I obtain Pkfuncs.h (to get the value of the IOCTL to cal)
       2 - Is there a "better" way to obtain the alarm-resolution of a particular device.


    Steven Wilmot Director, Data Utilities Ltd. (SQL Server Consultancy, .NET Development)
    Wednesday, February 10, 2010 5:19 PM

Answers

  • Hi Steven,

    Yes, like you said, it is not in WM SDK, but in WinCE. If you have installed Platform Builder 6.0, we can find it:
    \WINCE600\PUBLIC\COMMON\OAK\INC\pkfuncs.h


    Best regards,
    Guang-Ming Bian - MSFT
    Please remember to mark the replies as answers if they help and unmark them if they provide no help
    Monday, February 15, 2010 6:18 AM

All replies

  • Hi Steven,

    Yes, like you said, it is not in WM SDK, but in WinCE. If you have installed Platform Builder 6.0, we can find it:
    \WINCE600\PUBLIC\COMMON\OAK\INC\pkfuncs.h


    Best regards,
    Guang-Ming Bian - MSFT
    Please remember to mark the replies as answers if they help and unmark them if they provide no help
    Monday, February 15, 2010 6:18 AM
  • You seem to miss the point..

    This problem is very similar to http://social.msdn.microsoft.com/Forums/en-GB/windowsmobiledev/thread/b5b09c3f-fb52-4d26-88d6-29143f6d3c08

    1 - I am a Third-Party developer (not an OEM) - I do NOT have Platform Builder installed, and it seems that this is only available to OEMs

    2 - The "CeSetUserNotificationEx" (by its very name) is an api-function intented for USERS, not just hardware manufacturers.

    The documentation of the function is made publicly available by Microsoft, but yet you seem to be preventing access to the header-files which are needed in order to use the function. I cannot understand the reason behind this (having the documentation public but the header-files restricted)

    I have been trying to look for the "proper channels" to raise this as in issue with Microsoft, but could not find anywhere on the Connect site that was relevant to Windows Mobile development.


    Steven Wilmot Director, Data Utilities Ltd. (SQL Server Consultancy, .NET Development)
    Wednesday, February 17, 2010 9:29 AM