sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

Public bug reported:

*** How to avoid:
- do not use the jar's but the provided command files, which only add to path locally in the run context - no access to registry

- if you need to use the jars (e.g. when programming with Eclipse …)
directly, then add the path to the libs folder yourself to the
environment before using the jars the first time. REMEMBER: log
out/login after changes or even restart Windows.

*** reported by bjoernklose on github:
Context: Windows 7 x64
Version: SikuliX Setup Build: 1.0.1 12NOV2013120000

Unfortunately, i noticed that during setup it overwrites my PATH
variable, leaving only the ../Sikuli/libs entry.

This makes every other app (such as command line utilities like grunt-
cli) on the system not usable anymore.

Temporary Solution:
In case somebody else coming across this problem, and has Windows' System Backups properly setup, there's a way to restore PATH values.

Otherwise, the SikuliX-1.0.1-SetupLog.txt file itself seems to also list
all previous entries, starting lines with RunSetup: syspath: C:\...

** Affects: sikuli
     Importance: Undecided
         Status: New

** Summary changed:

- [1.0.1] first use of Sikuli ready-to-use jars after setup might override the user path entry in system settings 
+ [1.0.1] Windows: first use of Sikuli ready-to-use jars after setup might override the user path entry in system settings

** Description changed:

+ *** How to avoid:
+ - do not use the jar's but the provided command files, which only add to path locally in the run context - no access to registry
+ 
+ - if you need to use the jars (e.g. when programming with Eclipse …)
+ directly, then add the path to the libs folder yourself to the
+ environment before using the jars the first time. REMEMBER: log
+ out/login after changes or even restart Windows.
+ 
+ *** reported by bjoernklose on github:
  Context: Windows 7 x64
  Version: SikuliX Setup Build: 1.0.1 12NOV2013120000
  
  Unfortunately, i noticed that during setup it overwrites my PATH
  variable, leaving only the ../Sikuli/libs entry.
  
  This makes every other app (such as command line utilities like grunt-
  cli) on the system not usable anymore.
  
  Temporary Solution:
  In case somebody else coming across this problem, and has Windows' System Backups properly setup, there's a way to restore PATH values.
  
  Otherwise, the SikuliX-1.0.1-SetupLog.txt file itself seems to also list
  all previous entries, starting lines with RunSetup: syspath: C:\...

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1277177

Title:
  [1.0.1] Windows: first use of Sikuli ready-to-use jars after setup
  might override the user path entry in system settings

Status in Sikuli:
  New

Bug description:
  *** How to avoid:
  - do not use the jar's but the provided command files, which only add to path locally in the run context - no access to registry

  - if you need to use the jars (e.g. when programming with Eclipse …)
  directly, then add the path to the libs folder yourself to the
  environment before using the jars the first time. REMEMBER: log
  out/login after changes or even restart Windows.

  *** reported by bjoernklose on github:
  Context: Windows 7 x64
  Version: SikuliX Setup Build: 1.0.1 12NOV2013120000

  Unfortunately, i noticed that during setup it overwrites my PATH
  variable, leaving only the ../Sikuli/libs entry.

  This makes every other app (such as command line utilities like grunt-
  cli) on the system not usable anymore.

  Temporary Solution:
  In case somebody else coming across this problem, and has Windows' System Backups properly setup, there's a way to restore PATH values.

  Otherwise, the SikuliX-1.0.1-SetupLog.txt file itself seems to also
  list all previous entries, starting lines with RunSetup: syspath:
  C:\...

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1277177/+subscriptions