Archive for the 'VistaGlazz' Category

VistaGlazz 1.1 is on it’s way

We are working hard on some small bug fixes and features to make VistaGlazz 1.1 more stable and easier to use. After that we have to fix our new installer and we’re ready to release. Expect the new (full) version soon.

Update 2008-09-17
VistaGlazz is currently in the approval process of a third party. We can release it as soon as it is approved. We’ll keep you up to date.

Not only VistaGlazz is getting an update, PixelCryptor as well! The new version is blazing fast and memory management is greatly improved. Prepare for version 1.2.

VistaGlazz SP1 beta3

Good, it is still Saturday. We’ve modified some code and everything seems to work like it should. Beta3 will be able to fix 32bit SP1 systems that have been patched with VistaGlazz 1. VistaGlazz should identify your system as “patchable” (as opposed to “original” for untouched systems). If VistaGlazz identifies your system as corrupt or if you encounter any other problem, please let us know.

We do not have a solution for 64bit SP1 systems that are patched with VistaGlazz 1 yet, since that problem is a little bit more complex.

Download VistaGlazz SP1 beta3 now!
(Remember download it to disk first, do not run it from your browser)

RunDll32 Update

So far we’ve only seen rundll32 problems after patching a VistaSP1 system with the original VistaGlazz, using the “patch anyway” option. It seems somewhat unlikely that anybody did in fact use the “patch anyway” option from the old VG on their SP1 system, but we want to be sure that this is not the cause of the rundll32 problems. You can expect a new beta release in the next few days that’ll address that specific point.

Update 2008/05/21:
We ran into some problems while creating a fix for the 64bit systems suffering from the problem described above. Yvo patched his 64bit Vista with VG 1.0 using the patch anyway option, so we could see firsthand what that would lead to. Apparently Vista didn’t like it. While Vista32 just throws some rundll32 errors, Vista64 will no longer boot in normal mode. A trip to safe mode and some file copying via the command prompt is what it took to restore things. We’ve not decided yet on what the best way is to help those of you running Vista64 and suffering from these kind of problems.

Long story short: It’s taking a little bit longer than expected. Though we will probably have a new version ready by Friday, we really want to perform some tests before uploading it to our site. Expect a new release somewhere Saturday.

In the meanwhile: If there is anyone with rundll32-problems that didn’t use the patch anyway of VG 1.0, please let us know exactly what steps you took that led to your problems. This way you will help us in identifying what went wrong and may lead to a fix for this problem.

RunDll32 errors after VistaGlazz beta 2

We’ve received numerous reports on RunDll32 errors after patching your system with VistaGlazz beta 2. We are looking into the problem, until then we advice (the brave among you) to await beta 3 or our next well tested release version of VistaGlazz.

Read the forum and comments in the VistaGlazz beta 2 post for more information. This issue seems to occur on SP1 systems only.

Update 2008/05/10:
We like to note that VistaGlazz isn’t compatible with Vista Home Basic. Microsoft has deliberately removed Aero from Vista Home Basic, and we would violate probably 10 pages of Terms of Use if we were to make it Vista Home Basic compatible.

Also make sure that you are using Beta 2. Unfortunately the link on our download page linked to Beta 1. Beta 2 should fix any errors caused to you by Beta 1 after patching.

Some more work ahead

Though beta2 seems to work for most of you, there are still people suffering from some rundll32 related problems. So far we still haven’t been able to reproduce the described problem, but hopefully we will be able to do so.
There are some other issues we want to address in the upcoming release, being:
->  Version information in the app - Currently not available and it would definitely help you to identify which version of VG you’re using
->  Liability waiver at app startup - Apparently it is deemed a little aggressive and annoying, so we might remove it altogether or make it a onetime only thing
->  Restore points - Some people, especially those using beta1, had some “Vista kind of like died on me, now what?” moments, so we’re considering to add a ‘Create Restore Point before playing with VG’ option
You might also have noticed a slight, erm, “change” in the look and feel of our site. WordPress released an update and our skin is not yet compatible with this update. Currently we’re waiting for our friends at K2 to release their new WordPress 2.5 compatible skin. Please bear with us as that release is due in the near future.