Not quite.

"c:/Program Files" is visible to the 32-bit applications.
The issue is environment variables.

The difference is that, for 32 bit applications
getenv("ProgamFiles")
is evaluated to "c:/Program Files (x86)",
and for 64-bit applications
getenv("ProgamFiles")
is evaluated to "c:/Program Files".


See the comments in ess-site.el lines 531-557 for the glorious details.
This all works correctly in 32bit emacs running on the 64-bit machine.
Opening 64-bit R inside an *R* window in the 32-bit emacs works correctly.



The comment about putting a .lnk file is completely consistent with Paul's
suggestion.
The .lnk (shortcut) file is a native Windows way of doing something similar
to a soft link in
Unix terminology.




On Thu, Feb 3, 2011 at 2:26 PM, Rodney Sparapani <rsparapa@mcw.edu> wrote:

> On 02/ 3/11 12:06 PM, RICHARD M. HEIBERGER wrote:
>
>> I think it is easy.  The Windows R installation puts a shortcut "R
>> 2.12.1.lnk" on the desktop.
>> That might be sufficient as is.
>>
>> That shortcut could also be copied to any arbitrary place, say c:/program
>> files/R.lnk, and
>> on 64-bit machines, we could also have R32.lnk and R64.lnk, with R.lnk
>> pointing to
>> the 32-bit system as Martin suggested earlier in this thread.  The
>> shortcut
>> can be
>> programmatically executed from the MSDOS cmd window, and from the shell
>> exec
>> mechanism.
>>
>>
> Ok, but this is an entirely different suggestion, correct?  There's
> no way that a 32-bit application can do anything with the real
> C:\Program Files since it is hidden from them, right?  Only 64-bit
> applications see the true C:\Program Files; of course, they can also
> see C:\Program Files (x86).  Maybe the R installer needs to be a
> 64-bit application for 7 and 32-bit application for XP.
> What a f*cking mess!
>
>
> Rodney
>
> ______________________________________________
> ESS-help@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/ess-help
>

	[[alternative HTML version deleted]]

