Logged In: NO 

I am in fact not using the wrong version of win32all, the 
problem occurs prior to the install of the extensions. And 
it is correct that the 2.0 dll's are not installed and 
python2.1.1 (or 2.1) is complaining about it. I originaly 
thought the same thing so I removed win32all and 
python2.1.1 unloaded the dll's and re-installed 2.1.1 prior 
to re-installing win32all I got the same errors.