how can solve these problems in bf2 ?

[[mahdi]

i usually have these problem in bf2 :
1- when i want drop c4 or something else sometimes donot droped and sometimes drop suddenly more than one.
2- when i right click for explosive c4 its donot explosive and also drop another c4.
3- when right click for aim on enemy its suddenly back from aim even i didnot click on any button.
4- when try to lie down and click on z button i suddenly stand up again without click on any button.
5- when i am gunner of chopper and want to right click for tv missle , its take more than 3 secs that is more than usuall.(i saw kind of lag or something like that when want to change weapon of gunner)

i want know anyone esle have these problems or not and also what are solutions?

i think these problems can Related to one or some of these : ping - hardware - windows - gamefiles
 i have :
ping about : 140 ms
hardware :
 processor : Dual-core cpu E5200 @2.5GHz
 RAM : 2 GB
 Graphics : NVIDIA GeForce 9400 GT
i know that this hardware is old and i want to update it but even this hardware must be enough for play bf2 i think.
windows : 7 - 32 bits
gamefiles : i downloaded the version 1.0 game first and installed it then used patch 1.41 and 1.5

[[ Pekii]

1. Happens to me sometimes too, so it's script problem maybe.
2. Sometimes you have to click twice to make C4 explode, sometimes happens to me
3. It's because of lagg, happens to me too
4. Maybe because of lag or if you do it while jumping because it's not allowed
5. I don't get this question

[[NRNS]Xenalite]

It's purely network connection related. The server sometimes does not register that you've dropped something.

[[ Pekii]

I don't think it's all about network hm ,  but 90% is

[[NRNS]-(Fight-Men)-75-]

It's purely network connection related. The server sometimes does not register that you've dropped something.

Exactly.

Its why BF2 is know for the "dusting effect".

[[mahdi]

Thanks everybody for answers.
there is another question for me : there is not any more update of bf2 after 1.5 for solve some of these or any other bugs ?
 if yes why battelog donot use it ?