I just wrote another script just to confirm the problem, and, well instead I did the opposite. This script seems to have upset my previous thoughts, so I'll keep trying to figure out what the problem is, it may be my own fault.

<?php
setcookie( "one", "uno", time()+10000 );
setcookie( "two", "dos", time()+10000 );
echo $_COOKIE['one'], '=1<br>', $_COOKIE['two'], '=2<br>', 

setcookie( "three", "tres", time()+10000 );
setcookie( "four", "quatro", time()+10000 );
echo $_COOKIE['three'], '=3<br>', $_COOKIE['four'], '=4<br>';
?>

That previous script I wrote behaves strangely.

I erased my cookies, then loaded the page. As expected, no cookies were sent from my web browser, and the script simply said "=1 =2 =3 =4" with the BR tags between them.

I hit reload, and only 1 and 2 showed the appropriate cookies, Uno and Dos. I hit reload again, and now Tres and Quatro show up.

I did this process 3 times to make sure it was consistent, and it happens the same way every time.

Please try using this CVS snapshot:

  http://snaps.php.net/php4-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-latest.zip

Using the CVS version Sniper asked me to use, NONE of the cookies were set using the before-mentioned script.

I beleive the problem is in the PHP.INI file, I retardedly copied over the suggested ini file that came with php 4.2.3 as soon as i installed it, and no longer have my old ini file.

I just downgraded to php 4.1.2 and I'm having similar problems! Though the before-mentioned php script actually only sends the client one cookie per execution in my current setup. Additionally, my other scripts do not work under the current ini file even while using php 4.1.2.

I don't know if this information will actually help, but I suspect it should narrow it down at least a little bit.

RTFM:

"setcookie() defines a cookie to be sent along with the rest 
of the HTTP headers. Like other headers, cookies must be 
sent before any output from your script (this is a protocol 
restriction)."

You have gotta be kidding me sniper, haven't you been paying attention? Output buffering is enabled. And if it weren't, Tres and Quatro would NEVER be set, and I'd get an HTTP HEADER error printed out on the page.

Yes, this was some bug which now seems to be fixed in 4.3.0-dev (as I can not reproduce this)

I stumbled into one other bug here, #20887, that's why I
got confused, sorry about that.