Jump to content

Iskander Novena

Member
  • Posts

    10
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Netherlands

Posts posted by Iskander Novena

  1. I know, but however I set it, it does not trigger.

    I know the value is Organisation, but when I set the condition to check for RegKeyValue("HKLM\...\Organisation") == "Organisation" and thus only show the option if this condition is true, the program does not list.

    When I set this exact same thing to gcond, it does not get grayed out.

    I absolutely know that I'm checking for the value that is in the registry on the machine I test it on, but can't get it to work....

  2. I've got a problem with the RegKeyValue-option in either Condition or Greyedout Condition.

    I use the following:

    RegKeyValue("HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\RegisteredOrganization")=="Organisation"

    Where, in my registry, my registered organisation is the value that is checked against.

    However, either when in Condition or Greyedout Condition, this does not trigger!

    Also tried with the full root (HKEY_LOCAL_MACHINE) but that does not make any difference...

  3. I just downloaded WPI and am trying to set it up.. Although trying is not so much the case as it's pretty much just setting it up..

    I get the same error as mentioned earlier about excludorIsChecked.

    It happens with me for an app that I have set a language-condition for.

    When I remove that condition, no error pops up.

    Also, I cannot find the getOSlang-function in ANY of the WPIScripts... Is this part of the code-REDUCTION mentioned in the changelist? ;)

    EDIT: Sorry, got posted as a reply to the wrong thread.... Nonetheless, the absence of getOSlang is an issue.

    I've added it manually to the end of core.js (as suggested in previous posts) and now at least that works, but still an error.

  4. Don't know if anybody still follows this thread or has alerts set or something..

    You all use "NET USE * <SHARE> /USER:<user>" or "NET USE <SHARE> <DRIVELETTER> /USER:<user>" and do stuff to figure out what driveletter was used...

    Did you know: when you use "NET USE <SHARE> /USER:<USER>" you don't get a drive-letter assigned for that UNC, but you CAN access it using the UNC-path?

    So suppose I have a UNC which I have to have specific credentials for that's named \\Server\WPI.

    I could easily connect to that in the following way:

    NET USE \\Server\WPI /USER:install install

    <do stuff>

    NET USE \\Server\WPI /delete

    This way, I connect to the UNC with user install and password install, do some stuff and then disconnect again....

×
×
  • Create New...