*Paul,
I didn't understood your problem with tinn-r.
I don't work at a lab, so i have no idea how it can be your specific
problem. I think it has a problem with R + Win 7 that is about the changes
in the permissions at Program Files folder. What am i doing to cheat this
problem.
1) Install R and Tinn-R at c:/MyProgs
2) Change the security permissions and give all full control to all users in
the machine and apply the new settings.
3) Open Tinn-R and configure the Rprofile.site file. **(R >> Configure
>>
Permanent) If it necessary you can change some parameters or put some
packages to load by default and you can change the default Cran mirror.
4) Open R inside tinn-r and wait to install all packages
What version of tinn-r and R are you using? I'm using R version 2.13.1
(2011-07-08) in 32bits and 64bits at the same machine with Tinn-R 2.3.7.1
Yep, you have to configure TINN-R when you install a new release of R.
**
In the Option >> Application >> R you have an option to use i384 or
x64. I
didn't understood the problem of the changes in the R path.
*Atenciosamente,
Leandro Marino
http://www.leandromarino.com.br (Fotógrafo)
http://est.leandromarino.com.br/Blog (EstatÃstico)
Cel.: + 55 21 9845-7707
Cel.: + 55 21 8777-7907
2011/10/7 Paul Johnson <pauljohn32@gmail.com>
> On Wed, Oct 5, 2011 at 12:45 PM, Leandro Marino
> <leandromarino@leandromarino.com.br> wrote:
> > Paul,
> >
> > I use Tinn-r and i didn't see anything hard to configure it. You
have to
> > install the R, then the Tinn-r. After you have to open Tinn-r go to R
>>
> > Configure >> Permanent . This procedure will open the
Rprofile.site file,
> if
> > you want you can change some parameters and save. After that you have
> only
> > to open tinn-r and inside it open the R or the Rterm (i prefer this
one
> > because consumes less memory).
> >
> > Regards,
> > Leandro
> >
>
> You don't mention which version of windows or R. Setting thus up for
> all users on a Windows 7 system has been more trouble for me after R
> re-organized their install so that Rterm.exe is no longer in the
> path. It is in that subdirectory i386 or such.
>
> My notes say "Even if you change the paths, TINN-R will not save what
> you do because it always looks at R again and tries to guess the path
> when TINN-R starts, and IT ALWAYS GUESSES Wrong. That's why, under the
> menu where you set those 2 paths (for rterm and rgui), you also TURN
> OFF the option to always use newest R. "
>
> And Tinn-R has to be reconfigured whenever R gets updated.
>
> But if y ou have tinn-r working, I don't mean to stop you. The
> problem is that a seemingly endless stream of new users can't make it
> work. Maybe you post your install recipe on the Tinn-R website, it
> would help people out.
>
> --
> Paul E. Johnson
> Professor, Political Science
> 1541 Lilac Lane, Room 504
> University of Kansas
>
[[alternative HTML version deleted]]