I have 0.43 vanilla working on Windows Vista.
To get it working with ASIO4all it is best to find your registry settings with a current working version before installing. To do this go to audio settings in pd or pdx and set your input and output devices. then click on save all settings. Then go to the registry editor and look at these audioindev1 and audiooutdev1 make note of these. The keys are in \HKEY_LOCAL_MACHINE\SOFTWARE\Pd or pdx. also make a note of the rest of the keys. If you want to use GEM with Vanilla you will also have to copy MSVCR71.dll to your new pd/bin/directory. I'm not sure if the ASIO4all thing was only with my machine or if it is common for all windows installs as I have a creative labs ASIO driver stuck in my system that loads and tells me there are no creative devices installed then ASIO4all loads. Before I set the devices in the registry ASIO4All would not load. I also use the -asio startup flag. Of course you will have to add your ext paths and libraries. MSVCR71.dll can be found in your /pd/bin directory if you have a previous version of GEM installed. I have a registry entry each for pd and pdx. I'm not sure if this is the norm. Anyways 0.43 seems to be working good so far. I have only tested it with externals GEM and ggee/~moog.
geo_ker, is there a similar thing as the registry on a mac? If not you might want to look into using the startup flags to get the audio working. I'm not sure but I'm guessing the audio problems are a pulseaudio problem it has been updated since the previous version the flags you probably want to look at are audioapi, audiobuf, audioindev1, audiooutdev1, blocksize, callback, noaudioout, noaudioin. If you can somehow get the values of those from a working version of pd I would imagine that your audio might work if it is of course the same problem. It's worth a try anyways.
. The sound doesn't work, so it's obviously buggy at the moment.