Author Topic: A Bug in Environment Checking  (Read 6392 times)

0 Members and 1 Guest are viewing this topic.

Offline mylogon

  • Newbie
  • *
  • Join Date: Oct 2016
  • Posts: 1
  • Karma: 0
    • View Profile
A Bug in Environment Checking
« on: October 22, 2016, 08:33:43 pm »
This folder in the 'Path' variable doesn't exist: "C:\Program Files (x86)\Grep"

When it certainly does.

Not a critical error for me, as I know better, but it might effect someone else.

Thanks.

Windows 10 Home Edition, 64 bit
« Last Edit: October 22, 2016, 08:38:38 pm by mylogon »

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
Re: A Bug in Environment Checking
« Reply #1 on: October 23, 2016, 01:56:38 pm »
Passed onto Shane.

Offline Shane

  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9281
  • Location: USA
  • Karma: 137
  • "Knowledge should be shared not hidden."
    • View Profile
Re: A Bug in Environment Checking
« Reply #2 on: October 24, 2016, 09:28:48 am »
The program pulls the path variable from the registry, in the program is that path at the bottom of the list?

When the program pulls it from the registry it then calls the findfile api (It finds folders as well) and if it comes back as false then windows is telling it it doesnt exist. But I have had it to where the path registry key had extera chars in it and so when the program pulls it and breaks each path part those extra chars cause the program to look for the wrong path string, normally this happens at the end of the list since that is where the chars are.

Shane