Hi, thanks for this nice application. This is my first post.
XPSP3, ZU 2.5 Beta here.
I have read the Admin point of view about Vista. I am not Vista fanboy either. But there is Windows 7 coming out: Vista in a better shape. This will certainly be the move from 32 to 64, or at least it will boost the move, and it will also put an term to XP (which is very-very-very old), or at least create a big gap.
So what's the point of this message? I have read ZU is "vista compatible", i.e. it should run (and it probably runs) on Vista. I would rather ZU to be fully "compatible/designed" for Vista and forthcoming new OS. That's a wish. But not only. There s been quite a transition in the manner programs install in Vista vs. XP and that will probably be the same in W7. I speak for myself here, but when I will move to Vista - or W7, sooner or later, I will probably only use vista ready software. Unless I completely disable the UAC feature (and I guess I will - but that's a user choice). So I hope ZU will keep being developed and it will be developed on newer platforms, and very soon.
Here is some general information about what' a Manifest and the difference between XP/Vista (excerpt of the article below).
(why? because the explanation is easy to understand)
[...]Microsoft introduced the User Account Control (UAC) in Windows Vista, and so far it is also in the upcoming Windows 7. Among other components it also contains a feature called filesystem virtualization. Essentially it remaps reads/writes for certain files to other paths. The most important protected path we have to deal with is Program Files.
Let's assume the protected path is C:\Program Files.
Older versions of Filezilla and other programs not explicitely Vista-aware lack a so called manifest. A manifest basically tells Windows how aware the program is about the recent Windows versions. And it tells Windows about the privileges the application requires.
A program without manifest is run in the context of a standard user (NOT the currently logged on user). Filesystem virtualization is applied to such a program.
If the program is installed in C:\Program Files\Program, and tries to write a file into it's directory, the file will not go into that directory, but into another, in this case C:\Users\<username>\AppData\Local\VirtualStore\Program Files\Program.
This is totally transparent to the older program and the user.
The problem starts if you now want to access this file with a Vista-aware program, such as Filezilla. As Filezilla includes a manifest, it doesn't use the VirtualStore, but the real paths. It will of course not be able to find your file there.[...]
Thanks for reading.