WindowBlinds 4.51 supports 64 bit XP for example.
Yes some parts are 32 bit (wbconfig for example), but it doesn't need access to more than 4GB of RAM and would gain little from the added registers so why would we port it to 64 bit?
Our policy is to reuse the 32 bit parts of the apps as much as possible as this reduces testing overhead, development time & is unlikely to have any impact on the speed of the apps. Any parts which need to be 64 bit (wblind64.dll for example) are 64 bit. If something is 32 bit then there is probably a good reason for it.
There is no point making something 64 bit just for the sake of it.
Taking Multiplicity as an example, the service & winlogon dll are both 64 bit on XP 64 bit, but the system tray icon & config UI remain 32 bit. This reduces the size of the downloads & has no impact on the user.
