I just read a fairly interesting blog post about a very technical aspect of Windows Vista that I feel has a lot of potential for causing serious problems for Windower, and possibly breaking Windower for good. Keep this in mind when you're planning to upgrade your OS to Vista. A link to the blog article is here:
http://blogs.msdn.com/michael_howard/ar ... 08315.aspx
In summary, when you run a program (e.g. click an Icon in Windows) that corresponds to a single file. This file doesn't contain the entire code for the program, the code is split up among many files. So, the first file calls upon the services of the code that exists in many other files. When this happens, the Operating System loads all this other code and data into memory so that it may execute it.
In current versions of the operating system, Windows uses a deterministic method of figuring out WHERE in memory to put this other code and data. Thus, for something like Windower which relies on offsets hardcoded into the program, there is no problem. Since all the code and data is loaded into the same places every time the application is run, these tools like Windower, etc can be guaranteed that their hardcoded "offsets" or "memlocs" will work every time the application is launched.
With Vista, this will change, and this load order is "seeded" at the time you boot the operating system. So, each time you reboot, memlocs will change. Not because the application itself changed, but because the OS is relocating the memory transparently.
Something to think about for Windower fans.