


I've also tried the R CMD (and Rcmd) commands with the following paths included (note that these paths don't lead to anything on my computer, so I tried doing R CMD / Rcmd with and without them specified): C:\Rtools\perl\bin C:\Rtools\MinGW\bin I updated the path variables on my computer, where the below paths were used: C:\Rtools\bin C:\Program Files\R\R-2.15.0\bin\圆4 Originally I let Rtools specify the path variables (turning that option on during installation).Install Rtools215 to match R version 2.15.0.Install the latest version of R (2.15.0).For reference, below are the steps I have taken already to try to resolve this issue: I realize this is a complex issue to remotely diagnose, but any advice and suggestions on resolving this trouble is appreciated. For example, I have triple-checked the paths to ensure they are correct, including for the R version number, that 圆4 in the path name is accurate, etc.

The most immediate thing that came to mind was that the path variables in Windows were not set right, but this also has not (yet) led to the answer. I have examined the following guides without success in identifying the trouble: ) Note that even if I type in just R in Command Prompt and hit enter, I get the same error, so I'm not even able to bring up R here, though it opens perfectly fine in its stand-alone interface. (If I try the Rcmd install pkgName command, then the error starts out as 'Rcmd' is not. I've tried R CMD install pkgName, R cmd install pkgName, Rcmd install pkgName, where pkgName is a place-holder for an actual package that has been R CMD checked on OS X and also posted on CRAN, where I have the unzipped source in the current working directory), I get the following error message: 'R' is not recognized as an internal or external command, The problem: whenever I try an R CMD command in Command Prompt (e.g. The following thread appears to be on the same topic that I'm having trouble with, but the question remains unresolved: I'm exploring package building on Windows 7 but have been running into trouble after reaching the Command Prompt stage.
