This error means: you are driving (at least) this signal from more than 
(at least) one process. Or you are driving this signal from a process 
and a concurrent statement...

The problem in your code is addresss, its driven from 2 processes.

But there are al lot of more problems to come!!!
Lots of them are reported in the warnings. This are at least highest 
warning level, maybe this should be an error:

1

WARNING:Xst:737 - Found 1-bit latch for signal <s1>. Latches may be generated from incomplete case or if statements. We do not recommend the use of latches in FPGA/CPLD designs, as they may lead to timing problems.

2

WARNING:Xst:737 - Found 1-bit latch for signal <s2>. Latches may be generated from incomplete case or if statements. We do not recommend the use of latches in FPGA/CPLD designs, as they may lead to timing problems.

3

WARNING:Xst:737 - Found 1-bit latch for signal <done>. Latches may be generated from incomplete case or if statements. We do not recommend the use of latches in FPGA/CPLD designs, as they may lead to timing problems.

4

WARNING:Xst:737 - Found 4-bit latch for signal <addresss>. Latches may be generated from incomplete case or if statements. We do not recommend the use of latches in FPGA/CPLD designs, as they may lead to timing problems.

BTW:

1

process (done) -- sensitivity list is incomplete: clk is missing

2

  begin

3

    if done='1' then

4

       if (clk'event and clk='1') then

5

         if (en = '1' and rd='1' and wr='1' and s2='1' and count1="111" and s1='0' ) then ...

Due to the incomplete sensitivity list your simnulation ist totally 
crap.
And the description of an asynchronous clock enable is very unusual... 
:-/

This warning is also a very high level warning:

1

 Index value(s) does not match array range, simulation mismatch.

It simply says: you're not simulating the actual hardware...

hi, thanks for suggestion.
i have used the clk in sensitivity list and also checked with other 
signals
s2,wr,en,rd but getting same warnings.
Please suggest me what to do for that multiple error.

> i have used the clk in sensitivity list and also checked with other
> signals s2,wr,en,rd but getting same warnings.
This incomplete sensitivity list does not cause your problems!
Its just another problem.

> Please suggest me what to do for that multiple error.
Don't assign values from more than 1 process to a signal. I already said 
tis:
>>> This error means: you are driving (at least) this signal from more
>>> than (at least) one process.
>>> The problem in your code is addresss, its driven from 2 processes.