Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Paul Bottin
    @fresc81
    :)
    Stephanie Hobbs
    @RX14
    It's probably easier for you to edit the readme now
    Paul Bottin
    @fresc81
    yeah I'll just edit it inline
    Paul Bottin
    @fresc81
    what do you think about #30 (switching to semver 1.0.0)? @mikeyoon , @justinmchase
    Stephanie Hobbs
    @RX14
    @fresc81 I think that this package is mature enough to be called 1.0.0
    Paul Bottin
    @fresc81
    I might just rewrite the API docs and regenerate the github.io page http://fresc81.github.io/node-winreg/
    the readme file isn't really fancy right now
    Paul Bottin
    @fresc81
    I would feel more comfortable releasing 1.0 if there were proper docs.
    Stephanie Hobbs
    @RX14
    lol i didn't even know the github.io page existed
    Paul Bottin
    @fresc81
    just pushed out the documentation and updated the github.io page. I guess we're good for releasing 1.0.0 :clap:
    Stephanie Hobbs
    @RX14
    @fresc81 the docs look good to me
    Paul Bottin
    @fresc81
    yeah looks cool, doesn't it? Also wasn't a big deal. I just updated the stuff from the other branch and removed the tests for now.
    Stephanie Hobbs
    @RX14
    Hmmn, it would be nice to set up appveyor CI to test it with
    afaik they are the only free CI who does windows
    Paul Bottin
    @fresc81
    wow, I wasn't aware of that there is any CI that supports Windows right now. Looks like I have my bed lecture for tonight :smile:
    Stephanie Hobbs
    @RX14
    heh
    i've used them for C# projects before
    i'm sure you can work out how to test node on there
    Paul Bottin
    @fresc81
    yeah I'll definitely have a look on that, thanks for the advice
    Stephanie Hobbs
    @RX14
    no problem
    Paul Bottin
    @fresc81
    allright, lets see if this appveyor thing works out. I hope I configured it right
    LohithBlaze
    @LohithBlaze
    Hi, We are using winreg to access the registry, but if we enable the group policy to disable access to the registry, the node module is throwing an error for saying "process exited with error code 1"
    @fresc81 is this as designed or anything can be done, because , we are writing and reading information from HKCU
    Stephanie Hobbs
    @RX14
    @LohithBlaze node-winreg uses the reg commandline tool to access the registry. If this is disabled the tool doesn't work.
    Paul Bottin
    @fresc81
    @LohithBlaze I guess this policy setting controls the access for certain groups to the actual Registry Editor Application and REG.EXE commandline utility. It does only prevent users from starting mentioned registry fronends. This module uses the REG.EXE commandline utility, so unfortunatly there's nothing I can do. You need a native module that uses the WinAPI to access the registry. That might bypass this group policy.
    Hi chris btw. long time no see xD
    Stephanie Hobbs
    @RX14
    @fresc81 nice to see you too!
    LohithBlaze
    @LohithBlaze
    @fresc81 @RX14 there is nothing we can do to enable read/write access to HKCU?? usually without admin privileges HKCU must have read and write access.
    http://blog.codeinside.eu/2015/08/11/reg-exe-or-how-to-import-reg-files-without-admin-privileges/
    Paul Bottin
    @fresc81
    It's not the HKCU key that is blocked by the policy setting you've mentioned - it's the actual regedit.exe and reg.exe applications that are blocked. Due this module uses reg.exe, there's really nothing we can do here.
    Paul Bottin
    @fresc81
    Did you try using reg.exe on it's own to access the key in HKCU? It might give you a more detailed error message.
    Paul Bottin
    @fresc81
    if you need a node module that uses the windows api for registry access you could give this one a try:
    but you need to compile a native module for using it. don't know if that is an option for you.
    Jason Wills
    @jasonwills_twitter
    Hi All, hopefully in the right place - starting out with this, and i am reading the registry fine on my local machine - however, i was wondering if winreg is able to read the registry of a remote machine at all - is this possible?
    Paul Bottin
    @fresc81
    oh sorry, I missed your message. It should be possible (see host parameter http://fresc81.github.io/node-winreg/Registry.html ) but this functionality is not yet covered by the test. Would be great if you could give some feedback how it performs in the wild.
    Paul Bottin
    @fresc81
    @all This brings me to another issue: the test coverage of various functions is, best said, lousy at the moment (see https://npmtest.github.io/node-npmtest-winreg/build/coverage.html/node-npmtest-winreg/node_modules/winreg/lib/registry.js.html ). Any volounteers? I provide a bounty ( 25 € Steam prepaid card ) in exchange for 95+ % test coverage :sparkles: Thoughts?
    There's sombody with nickname ALL :smile: sorry for mentioning you^^
    Deafwave
    @Deafwave
    @fresc81 Any possibility for me to change the process spawner to change based on OS? e.g. for linux I'd like to prefix all of the reg statements with "wine"