similar to: Local library on Windoze.

Displaying 20 results from an estimated 20000 matches similar to: "Local library on Windoze."

2004 Jul 16
3
rd2dvi bug on windoze?
hi, can anyone confirm the following problem? when i do dos> rcmd rd2dvi --pdf my-package-name i get dos> Can't open perl script "c:\PROGRA~1\r\rw1091/bin/rd2dvi": No such file or directory might the problem be in (double back slashes rather than forward slashes) R-1.9.1\src\gnuwin32\front-ends\rcmdfn.c(251): strcat(cmd, RHome); strcat(cmd, "/bin/Rd2dvi.sh");
2005 Nov 05
1
Problem with installing home-made package under Windoze.
I am using/trying to use R 2.2.0. I have created a package of ``supplementary'' time series functions for use by my students in a time series course. The package involves only raw R code; no dynamic loading to complicate matters. I need to install this package in a location on a local area network where the students can access it under Windoze. In the past I learned that I could do
2006 Sep 01
2
Local library under Windoze.
Continuing to try to customize my environment for using R under Windoze, I experimented with installing a package from CRAN in a local library ``Lib''. I created the directory ``Lib'' in the folder in which R starts, and then executed > install.packages("abind",lib="Lib") Everything went according to form (I got prompted to choose a mirror, etc.) until
2006 Sep 01
1
Summary --- Local library under Windoze.
Prof. Brian Ripley solved the problem. He wrote: > I was not aware that this works with relative paths for any version > of R. Try using a full path, which always works for me. I tried it using a full path, and bingo! It worked like a charm. Under Unix the relative path also works, but. Prof. Ripley also remarked: > If indeed your filesystem is readonly, you will have problems
2006 Aug 30
10
.Rprofile under Windoze.
I am (for my sins) having to do some work using R under Windoze. I wanted to set up a .Rprofile to control my set-up. The docs on .Rprofile say that it can/should be placed in ``the user's home directory''. ``An Introduction to R'' observes lucidly that this concept needs to be clarified under Windoze. Following the suggestions in An Introduction to R, I tried putting a
2006 Aug 31
0
Summary and thanks: .Rprofile under Windoze.
Many thanks to all who responded to my cri de coeur: Charles Annis, John Bollinger, Petr Pikal, Brian Ripley, Duncan Murdoch, Dan Nordlund, and Richard Heiberger. (I don't think --- I hope --- I haven't missed anyone.) The essential solution to my problem was indeed to eliminate that @#@$#@$^#@ ``.txt'' extension from the filename. I.e. the file must be called
2005 Feb 17
2
How to upgrade library from R 1.9.1 to R 2.0.1
Dear All: I have a library for R 1.9.1, it is very easy to setup a library in R 1.9.1. For example: I want to setup a library "test" for R1.9.1. 1. Create a folder "test" in the direct X:\ R\ rw1091\ library \. 2. Create a file "DESCRIPTION" in the direct X:\ R\ rw1091\ library\ test\. 3. Modify the "Package:" and "Title:"
2004 Aug 11
2
Xemacs do not want to execute help.start() with R1.9.1
Hi all, I 've just reinstalled from the scratch my Windows 2000 (Italian version) on a formatted HD, because I like to clean the environment from time to time (say once a year). I'm currently using XEmacs-21.4.13 and R (rw1091) and Xemacs is configured as described in http://socserv.socsci.mcmaster.ca/jfox/Books/Companion/ESS/ess-xemacs.pdf The problem is that the command help.start()
2004 Sep 22
2
Facing problems with C code compilation - Please help.
Hello, I started using R a month ago - so I am a novice in this area. I am stuck with a problem and need some help urgently. I am using windows version of R 1.9.1. I am trying to compile C code in it. I have my C code - "hello.c" is lying in C:\Program Files\R\rw1091 This code is - #include <R.h> void hello(int *n) { int i; for(i=0;i< *n; i++) {
2004 Jul 03
1
Installation of R in Windows
I tried to install R (V 1.9.1) on an XP Home Edition box with loads of disk space and 256 MB of RAM. During installation, I get messages stating that some files are corrupted. I used two copies of the install exe downloaded from different sites and still get the same messages at the same spots in the install. What do I need to do to get around this? I ran md5sum on the downloaded exe file:
2001 Aug 28
1
wine and windoze me
I have tried codeweavers wine and now the latest cvs version of wine dated 2001-08-24. In no case am I able to run anything but notepad from windoze ME. The doze media player...nope, internet exploder? nope. Here is what I get trying to run windoze media player: wine --managed --winver win98 /mnt/win_c/Program\ Files/Windows\ Media\ Player/wmplayer.exe fixme:shell:SHRegGetUSValueW
2001 Dec 20
2
library()
I've just installed version 1.4.0 of R, and am experiencing a puzzling phenomenon with the library() function. I have .lib.loc set as follows: > .lib.loc [1] "/usr/local/lib/R/library" "/home/faculty/rolf/Rlib" If I invoke > library(melvin) I get the error message Error in library(melvin) : There is no package called `melvin' but if I invoke >
2004 Aug 27
2
about passing parameter to '.R' script file (PR#7201)
Hi, I am trying the 'R' application for generating the data for the uploaded '.gpr' file. I have written script file named 'test.R'. Currently i have hardcoded the path of uploaded '.gpr' file in the script itself. I would like to know how to pass a command line parameter to the 'test.R' script file, so that i dont have to hardcode the path and filename
2004 Aug 27
3
About passing parameter to '.R' script file
Hi, I am trying the 'R' application for generating the data for the uploaded '.gpr' file. I have written script file named 'test.R'. Currently i have hardcoded the path of uploaded '.gpr' file in the script itself. I would like to know how to pass a command line parameter to the 'test.R' script file, so that i dont have to hardcode the path and filename
2004 Mar 22
5
detach()
I got bitten recently by the following behaviour of detach(); > save(file="Junk") > attach("Junk") > search() [1] ".GlobalEnv" "file:Junk" "package:methods" "package:ctest" [5] "package:mva" "package:modreg" "package:nls" "package:ts" [9]
2004 Sep 10
2
loading Sjava
I'm excited about SJava, and I'ld love to get it working, but can't get past loading the package. .First.lib fails on this statement: > library.dynam("SJava", "SJava", "C:/PROGRA~1/R/rw1091/library") Error in dyn.load(x, as.logical(local), as.logical(now)) : unable to load shared library
2004 Dec 04
9
Excel *.xls files, RODBC
I gather from reading the back-issues of r-help that it should be possible (modulo a number of caveats) to read an excel (yuck!) file into R using RODBC. I have obtained and installed ODBC and the RODBC package, but cannot for the life of me figure out how to go about it. Can anyone give me a simple recipe? I have an excel file on cdrom, say: /mnt/cdrom/melvin.xls I have started R and loaded
2004 Jul 14
1
RCMD fails in Windows XP
I have setup R 1.9.1 on my Dell laptop running windows XP. I have installed it to C:\R\rw1091. Rgui runs fine, but Rcmd fails if run with parameters (i.e. install). The windows dialog box cheerfully says "R for Windows front-end has encountered a problem and needs to close. We are sorry for the inconvenience." Running the visual C++ debugger informs me that there is an unhandled
2012 Aug 24
3
misc subdirectory
The utils package has a misc folder, and some other packages have folders that are not listed in the R-extensions documentation (?data?, ? demo?, ?exec?, ?inst?, ?man?, ?po?, ?src?, and ?tests?). I'd like to be able to put some ancillary data into a misc folder, but it's mere presence in the source folder or source tarball (created with R CMD build) does not mean that it gets put into
2004 Jul 07
2
Win32 & C code
Hi, I'm trying to get C code working with R. This is my first time writing C on Windows and I'm making a mess of it. Help! I'm following the example in Roger Peng's "An Introduction to the .C interface to R". The C code is: #include <R.h> void hello(int *n){ int i; for(i=0; i < *n; i++) { Rprintf("Hello, world!\n"); } } I seem to be unable