[R] help with updating to R2.7

[ravi]

Hi,
Ouch! That really hurt. But I get the point.
Here's what I did now. I copied all the package folders from R2.6, except for the R.css file, and copied them into the R2.7 folder. 
In the process, I overwrote the common files that came with the installation of R2.7.
Here's the output that I obtained in R2.7 :
> library()
Error in unique.default(ans) : 
  2 arguments passed to .Internal(unique) which requires 3
> update.packages(checkBuilt=TRUE, ask=FALSE)
Error: could not find function "update.packages"

My intention with my previous mail was to check and obtain confirmation on details like what I should do with the R.css file.
But I realise that I should have then restricted myself to that single question. 
That way, I would not be wasting the valuable time of the R list experts, from whom I have received a lot of help previously.
After reading the FAQ once again, I am guessing that the problem could be a case of the internet downloading functions failing.
As suggested in the FAQ, I tried the following commands :
> "path_to_R\bin\Rgui.exe" http_proxy=http://gannet/ http_proxy_user=ask
Error: unexpected symbol in ""path_to_R\bin\Rgui.exe" http_proxy"
> "path_to_R\bin\Rgui.exe" http_proxy=http://user:pass@gannet:80/
Error: unexpected symbol in ""path_to_R\bin\Rgui.exe" http_proxy"
Should I run the above commands in R, or in the windows command window?

Thanking You,
Ravi

----- Original Message ----
From: Duncan Murdoch <murdoch at stats.uwo.ca>
To: ravi <rv15i at yahoo.se>
Cc: r-help at r-project.org
Sent: Thursday, 8 May, 2008 2:57:07 PM
Subject: Re: [R] help with updating to R2.7

On 5/8/2008 8:30 AM, ravi wrote:
> I know that it would be best if I reproduced the exact error messages, but I have tried so many different things now 
> and have lost track of the exact error messages at each stage.

This is not a reasonable request.  Rather than trying those two methods 
one more time, and recording what goes wrong, you expect someone on the 
list to do it for you?  If the advice was in the FAQ, presumably it 
works for others, so the reason it didn't work for you is likely that 
you misinterpreted part of it, or your system has a unique problem, etc. 
  The *only* way someone could diagnose that would be to see the error 
messages.

You need to use some common sense when you're asking for help.

Duncan Murdoch