Hi Mark,

it seems that the PATH environment variable on that particular laptop may be 
too large!

Researching a bit the maximum size of an environment variable seems to indicate 
that by default
there is a Windows limit of 1024 (which includes \0) bytes!

The Lenovo Thinkpad's PATH environment variable is polluted by Intel' paths for 
whatever
(unorganized) utilities they (or Lenovo) have installed on that laptop, such 
that its PATH
environment variable value is larger than 1024 bytes!

After removing entries on the PATH environment variables, such that the length 
dropped well under
1024, I became able to install the 32 and 64 bit versions of ooRexx without a 
problem!

----

Here is one link where a possible solution (setting the Path registry entry) 
for enlarging the size:
<http://superuser.com/questions/387619/overcoming-the-1024-character-limit-with-setx>,
 which I found
via googling "windows 7 path environment variable exceeds the maximum".

Although a KB article (<http://support.microsoft.com/kb/830473>) talks about a 
limit of 2048 or
8192, depending on the system, this seems to not apply to this scenario.

HTH,

---rony

P.S.: There is yet another problem I have stumbled over which I will report in 
a separate e-mail.




On 02.04.2013 23:01, Rony G Flatscher wrote:
> Hi Mark,
>
> thank you very much for this hint. Will look at it tomorrow (when back in the 
> office) and repot back.
>
> ---rony
>
> Rony G. Flatscher (mobil/e)
>
> Am 02.04.2013 um 22:42 schrieb Mark Miesfeld <miesf...@gmail.com 
> <mailto:miesf...@gmail.com>>:
>
>> On Tue, Apr 2, 2013 at 1:19 PM, Rony G. Flatscher <rony.flatsc...@wu.ac.at
>> <mailto:rony.flatsc...@wu.ac.at>> wrote:
>>
>>
>>     just wondering if anyone else got problems installing ooRexx 4.1.2 in 32 
>> or 64 bits on a
>>     German Windows 7 Professional version with Service Pack 1 applied:
>>
>>
>> There have not been any reports of this.
>>  
>>
>>       * The installer is not able to set the value of the PATH environment 
>> variable ("There was a
>>         problem reading the current value of PATH. You will need to set the 
>> PATH environment
>>         variable manually."
>>
>>
>> There is a limit to the length of a string in the NSIS installer.  If your 
>> current path is longer
>> than this length, then you can get this message.  If the installer were to 
>> attempt to update the
>> path, it would truncate it.  Resulting in havoc on your system.
>>
>> Redirect your path into a file and check the length.
>>
>> set path > myPath.tx
>>
>> I forget the length off the top of my head but it is probably 1024 or maybe 
>> 2048.
>>
>> --
>> Mark Miesfeld

------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users

Reply via email to