$ startx
 
[: ==: unknown operand
kdeinit: launch -> dcopserver --nosid
kdeinit: Launched DCOPServer, pid = 1612 result = 0
_KDE_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root
iceauth:  creating new authority file /home/Administrateur/.ICEauthority
DCOP: register 'anonymous-1560' -> number of clients is now 1
DCOP: register 'anonymous-1612' -> number of clients is now 2
DCOPServer up and running.
kdeinit: launch -> klauncher (null)
DCOP: unregister 'anonymous-1560'
DCOP: unregister 'anonymous-1612'
DCOP: register 'ksplash' -> number of clients is now 1
kdeinit: Launched KLauncher, pid = 1676 result = 0
DCOP: register 'klauncher' -> number of clients is now 2
DCOP: unregister 'klauncher'
DCOP: register 'klauncher' -> number of clients is now 2
kdecore (KSocket): Trying to listen on Unix /tmp/ksocket-Administrateur/klaunche
rHavrMb.slave-socket
kdecore (KSocket): Socket bound: 7
DCOP: new daemon klauncher
DCOP: register 'anonymous-1676' -> number of clients is now 2
DCOP: unregister 'ksplash'

Why doesn't KDE get past the splash screen?
If you get DCOP errors like this:  
 
kdeinit: launch -> dcopserver --nosid  
kdeinit: Launched DCOPServer, pid = 1912 result = 0  
_KDE_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root  
DCOPClient::attachInternal. Attach failed Could not open network socket  
DCOPClient::attachInternal. Attach failed Could not open network socket  
DCOPClient::attachInternal. Attach failed Could not open network socket  
DCOPClient::attachInternal. Attach failed Could not open network socket  
DCOPServer self-test failed.
Please make sure your paths are mounted in binmode.  
The cygwin default is to mount all paths in textmode which causes an error with the dcop client.  
 
To set all paths to binmode mounting you can change the following registry key (tested ONLY under Windows NT 4.0):
 
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2  
 
Set the key "cygdrive flags" to the value "0x0a" (dec: 10).