If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

You have three account in play here, the Administrator account, an account for Michel that has administrator rights, and a user (limited) acount for Amis.
In an earlier post you said

In my administrator profiles, I only have an "hostperm.1" file of 957 ko....

In my limited rights profiles, I only have "permissions.sqlite" file (0 ko)

The first thing you need to do is to close any open browsers, and also make sure SpybotSD is also closed

Do NOT reopen Spybot until the steps below have been done.

Next delete the "permissions.sqlite file in the limited account.
Now log on in to the limited account (Amis), and start Firefox.
Goto Tools/Options then open the Privacy Tab. In the cookie area click on the exceptions button, then add a site. It's not important what that site is, so for example you could use www.google.com and give it "allow" status.
Click on close, OK, then exit Firefox. This will have created a Hostperm.1 file for the user (limited) account and importantly will also have primed it.

Now log off of the restricted account and log onto the Michel account which has admin rights.

Now start Spybot. Go to the immunise screen and first undo all immunisations. This may take some time to complete as removal of immunisations from Firefox is fairly slow - be patient.
Once the undo has completed, re-immunise. This should be somewhat faster.

Hopefully this will fix the problems.

I suspect the number 20 that appears through the immunisation entries is new entries that had not yet been immunised when the screen shots were taken.

If you change to Firefox 3.4, make sure you completely uninstall Firefox 2.0.18first. The suggestion I provided for piranha does not really apply to Firefox 3 so if the upgrading doesn't fix your problem, don't apply that suggestion.

If you want to stay with Firefox 2.0.18 then you need to look at the profile for every account and determine which ones have hostperm.1 and which ones have permissions.sqlite, then follow the procedure I suggested to piranha. If they all have a hostperm.1 file, make sure spybot is not running then open the Firefox browser from each account in turn and prime its hostperm.1 file by adding a cookie as detailed in my previous post. When that has been done for each account, then do the immunisation from an account that has administrator rights.