bigmuscle

This info is already there. But I will not put there exact steps to get the symbols, because automatic symbol procedure is specific bonus of full version. If user does not want to support the development, then he must help on its own, e.g. by reading the forum ;-)

Look, I have no problem to help anyone with any problem, especially when information is lost in many page. However, I will not repeat something which has been discussed milliontimes here (so not only one or two posts, but almost every second post). We are here to help people but not to solve the user's laziness. Then you are probably using different software, because this software: a.) has never been called commercial b.) has never been called donation-ware If anyone wants to use this file, he can. It is not crack, it just autoclicks "Cancel" button on "DWM incompatibility error" which ignores the symbols and correct occlusion data will not be loaded = you will often see invalid content in transparent regions.

Try to remove BlurDeviation settings. Your value is too high and if it is not the cause of your problem, it can cause performance degradation.

Specular: layered windows are often set by some 3rd party hack such as WinAeroGlass utility or similar. Maybe you could provide the screenshots of your registry keys: HKLM\SOFTWARE\Microsoft\Windows\DWM and HKCU\SOFTWARE\Microsoft\Windows\DWM so I can check whether there is not some incompatible setup. simonking: it has already been discussed here countless-times, so no need to ask and answer it again.

Specular: I could not find any problem about this. If it happens too often for you then it is really weird because I doubt that noone else would notice this either. However, there is one thing which you could check - layered windows. If some window is marked as layered (transparency is set for it), DWM does not provide occlusion data for it, so you can see titlebar blur artefacts when moving windows over them. This thing happens since original implementation in WinVista. About the key not working - give me some time, I need to fix something :-)

I will try it and will contact you back. EDIT: so it is my mistake. I'm fixing it as soon as possible but my internet connection is real s*it, so it can take some time.

The password thing is implemented. Since now, every new donator receives e-mail with the password which he can use to log in. Old method (postal code / ZIP) still works now. The password cannot be changed yet. The password is sent on the first donation only (i.e. if you donate twice, the password will not be sent again in the second e-mail).

badmojo: send me your PayPal info via PM and I'll check it. Maybe, you are just entering wrong data.

JohnVB: what is your graphic card and screen setup?

It would good to know the exact scenario, it could be the problem with computing the occlusion data but it is impossible to be fixed without being able to reproduce the problem. + maybe the screen image (it will probably be necessary to take the shot by camera, because this kind of artefacts are not visible in PrintScreen shots)

djborek: have you read my post above? I will put this info on the first page.

Well, I find this understandable , the guy that cracked it somehow lost credibility all of a sudden and they are frustrated by this. jaclaz The most funny thing is that it was me who stated the following as a reaction to the crack:

This is wrong behaviour which should not happen and if it is bug then it should be fixed. However, the most common reason is that user installed some 3d party tweaks in the past, so symbols are downloaded but they cannot be stored/loaded etc. It is important to know that Aero Glass folder must be writable by Everyone (or at least by Windows Manager group). Also, dbghelp.dll and symsrv.dll files must be present in this folder. The another reason for "DWM incompatibility error" is that donation key is not present in Aero Glass folder, e.g. Jonny5isalivetm's log: ------------------- And the last one, there are also some users who complain that my application is buggy because their cracked version does not download symbols correctly:

This is correct behaviour. Symbols were downloaded and window stays opened until you close it - just to inform you that something happened. Next time, it will open only when symbols need to be downloaded again.

Nope, you just need to update the symbols. Donated version does it automatically, otherwise you must help on your own, it has been discussed many times in this topic.

The procedure to manually update the symbols has already been discussed several times in this topic.

If you don't have filled the postal code, you should contact me via PM with your PayPal details and I will set the password for you. I'm going to switch to password only completely (where you receive the password via e-mail, but it is not ready yet).

It seems interesting. I hope it works for remote debugging, because regular VS profiler does not :-(

daveo76: if you hover the mouse pointer over the "Key deactivated on ..." text, you will see how many days are remaining.

I will check it, maybe some bug

The upcoming version will enable glass efect by default even on battery, but it solves only the consequence but not the cause.

Hold the CTRL key during whole booting procedure. It is not enough to press it continuously, it must be hit exactly when DLL is loaded into DWM.exe which happens some time between the bootlogo is hidden and login screen is displayed (thus it is better to hold it all the time :-)). If it does not help, then the problem is not caused by Aero Glass. If it help, then send us minidump file and debug.log.

NoelC: I must admit that I don't know the answer. But I think it should not cause any problem because Aero Glass works completely transparently regardless the used device driver/settings. So if DWM runs correctly, then Aero Glass should work correctly too. guzoku: it seems that DWM process does not running at your PC at all and thus Aero Glass cannot work.

In very short... when some API returns success (e.g. TRUE or whatever it should return) then you should not rely on GetLastError() unless you manually called SetLastError before calling the API function.

For me, it seems happen everytime the display is turned off on inactivity and I turn it on again. I will try to find a place where this thing is logged. Maybe it is some performance thing in DWM which I could fix.