×

Discussion Board

Results 1 to 6 of 6
  1. #1
    Super Contributor
    Join Date
    Nov 2004
    Location
    Wiltshire, UK
    Posts
    3,644

    PowerMgmt capability and Carbide .vs

    When importing a 3rd editions MMP file into Carbide.vs I get an error that capability PowerMgmt is not supported.

    Looking in the capabilities dialog, the capability is called PowerManagement

    The SDK however calls it PowerMgmt so has anyone use powermanagement/PowerMgmt capability in an mmp file?

  2. #2
    Regular Contributor
    Join Date
    Jan 2005
    Location
    Estonia
    Posts
    350

    Re: PowerMgmt capability and Carbide .vs

    I stumbled to the same problem. If I use PowerMgmt, then I get errormessage during compiling in VS. If I use PowerManagement then I get error in compilation log " Unknown capability "PowerManagement" ignored"

    Seems like the Carbide was released without nobody testing it.

    BTW, have you found any solution? I need this capability fo killing processes. Now I get -46 panic when I try to do it

  3. #3
    Regular Contributor
    Join Date
    Jan 2005
    Location
    Estonia
    Posts
    350

    Re: PowerMgmt capability and Carbide .vs

    Solved it by hardcoding Powermgmt into MMP file and ignoring the errormessage that Carbide pops up.

    If someone knows Carbide developers/testers - give them a good kick.

  4. #4
    Super Contributor
    Join Date
    Sep 2004
    Posts
    1,048

    Re: PowerMgmt capability and Carbide .vs

    Hm, so seems we have a small bug. Even with (if my memory serves me right) in the excess of 700 test cases, this can happen., sorry about that.. Suggestions on how to make absolutely error free code on a limited budget are most welcome!

    Be advised that if you modify the powermgmt keyword, the uid.cpp file (which is used by the emulator to know what capabilities exist) will not be set up correctly. So if you want to get both the cpp.uid and the final code correct, suggest you do as follows:

    - First set powermanagement "incorrectly" the way carbide.vs wants it
    - Do a WINSCW build, this will set up the uid.cpp file correctly
    - Disable uid.cpp autoupdate from Carbide properties
    - Manually change the value in the mmp file
    - Build for target ignoring the pop-up

    ps: I know quite a few Carbide developers/testers and will NOT kick them based on this.

  5. #5
    Regular Contributor
    Join Date
    Jan 2005
    Location
    Estonia
    Posts
    350

    Re: PowerMgmt capability and Carbide .vs

    Thanks for a tip. That was useful

  6. #6
    Super Contributor
    Join Date
    Sep 2004
    Posts
    1,048

    Lightbulb Re: PowerMgmt capability and Carbide .vs

    Suggestion that I got (did not test it)

    In the .mmp file, you could try this:

    Code:
    #ifndef WINS  
            capability                    PowerMgmt 
    #endif  
    
    capability                              PowerManagement ReadUserData
    It should still complain about the GCCE build but aside from that, both builds should work correctly.
    No guarantees given though.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×