This is useful for variables which should be set for all users and all usages of this R installation. Their values can be overridden in a. Renviron file or on the command line. Startup for more details of environment files. For all applications via Windows. How you set an environment variable is system-specific: The order of precedence for environmental variables is the order in which these options are listed, that is the command line then.
Renviron then the inherited environment. How did you specify it? You can make life easier for yourself by using forward slashes as path separators: You should include the file extension e. A simple way to avoid these problems is to use the function file. If you select a file there, the name will be passed to R in the correct format.
Another possible source of grief is spaces in folder names. We have tried to make R work on paths with spaces in, but many people writing packages for Unix do not bother. Not when R itself is running.
If you tick the first option, the following string entries are added to the Windows registry: After installation you can add the Registry entries by running RSetReg. We have had several reports of this, although they do work for us on all of our machines. There are two known possible causes. This has not been reported for a few years, but used to happen regularly.
This is a warning which indicates that R has taken action to correct the action of some non-R DLL which has just been loaded and has changed the floating point control word in its initialization code to a setting incompatible with that needed for R. This is not good practice on the part of the DLL, and often indicates that it needs to be updated. Some users have found that Rgui. This error may also happen in the middle of a session.
In some cases where we have tracked this down, it was due to bugs in the video driver on the system in question: Good practice would restore the control word to the state it was in when the driver code was called, and R tries hard to correct this before running its own code.
For example, one user reported that the virtual screen manager JSP2 caused this crash. These errors are essentially impossible for us to fix or work around beyond the measures already taken. The only solution we know of is for the user to replace the buggy system component that is causing the error.
What the task manager shows is not the usage in CPUs but the usage as a percentage of the apparent total number of CPUs. A few issues have been reported that are related to the way accounts and file permissions work. These are not specifically R issues, but changes in user experiences.
Earlier versions of Windows had user and Administrator accounts, and user accounts could be give administrative privileges by being added to the local Administrators group and so write permission over system areas such as c: R would be installed either by a user in his own file space or by an account with administrator privileges into a system area. The Administrator account by default has it turned off. Unlike say Windows XP, such accounts do not run programs with full administrator privileges, and this is where the issues arise.
System administrators can disable installing applications from non-trusted sources, in which case you will have to persuade them that R is trustworthy, or digitally sign the R installer yourself, or unless this is also disabled run the installer from a standard account and install into your own file area. The same issues apply to the.
If you install R as a standard user into your own file space and use it under the same account, there are no known permission issues. You will run into problems if you try installing including updating packages in the main R library. It would be nice if at that point R could use over-the-shoulder credentials, but they apply to processes as a whole. Vista and later disallow creating. There are several ways around this. Run R with Administrator privileges in sessions where you want to install packages.
Transfer ownership of the R installation to the user which installed R. Install packages into a different library tree owned by the account used to install R.
See I don't have permission to write to the R There is a standard location for a site library, the site-library directory in the top-level R folder which you would need to create with full control for the R installation account.
This will be used for installation in preference to the main library folder if it exists. R runs correctly with DEP enabled. R may make use of directional quotes that are not always rendered correctly by Windows: There are two potential problems with rendering directional quotes.
The first is with running Rterm: The other is that the default raster fonts only include directional single quotes and not directional double quotes which will probably be rendered as a filled rectangle.
They are also used in HTML help, where most browsers use fonts which render them correctly. The font used can affect whether quotes are rendered correctly. The default font in the Rgui console and internal pager is Courier New, which has directional quotes on all the systems we tried.
Lucida Console which has elegant glyphs for directional quotes but seems rather light unless ClearType is in use: Consolas is another font which we often select when ClearType is in use. Non-TrueType fonts such as Courier and FixedSys lack directional double quotes on the systems we tried. There is a related problem with using Sweave output in Rgui, for LaTeX needs to be told about the encoding of directional quotes by including in the LaTeX preamble e.
Where tilde does not appear on the main keyboard, it can normally be accessed by pressing AltGr the right Alt key plus some other key. On all Windows versions you should be able to get tilde by holding the down the left Alt key and typing on the numeric keypad if you have one , then releasing the Alt key. The bit build of R for Windows will run on both bit and bit 2 versions of Windows.