Tarzikaf

TESTing windows 8.1 "alpha" version. Did I misunderstand "Install like the windows 8 version" or is it just not working on my setup? (I installed and replaced files) I forgot/Don't know how to get the exact version of windows including updates and all. All I can get is the same for every RTM install.

I'm not But making it possible to run on more machines will give more informations to work on from different setups, eventually leading to better compatibility.

100$ is cheap for a signature that runs on every machine you put the thing on. there's some decoders that are 1500$ per year. Given bigmuscle's knowledge, I'm sure he can manage to afford it, given the time he's been working on this project, 10 bucks a month would do it. While I like the efforts put into this, and the promising results, I struggle to understand why someone can think about releasing a product using appInit_DLL... Especially if the said product might be a paid one. As far as I know, Stardock did it too, and they're using signed binaries. But eh. I'm just saying what I think. this is a forum, right? Forums are made to talk and share opinions.

I think that more people would be interested and/or able to use your mod if you used another method than AppInit_DLL... Is there a reason why you stick to this frowned upon method? Last I checked, a signature by Microsoft is only 100 USD.

Could you be kind enough to point me to that 1.3.3 version? I can't find it on the official thread...

1.3.2 (latest)... AGT works fine usually... But the latest doesn't for me

I wonder what's wrong with my AGTweaker then.. Because the transparency disappears when I apply. Also, DosProbie, your quoteblock is misformed

Interesting.

I actually reset to factory install, and it still wasn't working, it has been confirmed already that there is a problem. Okay, let's review all this: it won't work on systems with SecureBoot enabledDon't use AGTweaker (see my post above)I'd recommend disabling Hybrid sleep, or sleep at all. (it gives me the unfixable "black screen" when I use sleep and aero glass)Sometimes, it breaks. Please provide logs if it does.

I had the same problem. Here's how to fix it: Don't use the AGTweaker to load the DLL. Disable DWMGlass with the tweaker, reboot, go delete C:\Windows\DWMGlass.dll and C:\Windows\DWMGlass.png and use the "LoadGlass__AppInit_DLLs.reg" file from the 0.94RC3 archive (edit and fix the path, mine's ""AppInit_DLLs"="C:\\AeroGlass\\DWMGlass.dll"") to load it. Mine: Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows]"LoadAppInit_DLLs"=dword:00000001"AppInit_DLLs"="C:\\AeroGlass\\DWMGlass.dll""RequireSignedAppInit_DLLs"=dword:00000000[HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM]CustomThemeResource"="C:\\AeroGlass\\CustomDefault.png" After I did that and rebooted, I got the command prompt that downloaded the symbols, and it worked. On a side note, AGTweaker seems broken for the 0.95RC4 release. It doesn't start the transparency when pressing apply. I guess I'll start using the custom resources with the registry tweak.

But it does, i am testing server 2012 (not R2) since the start and i am using aero glass since about one month. Funny to see by the way a server edition with aero Interesting, so it is just side effect that 2012 server has the same DWM as Win8 RTM has :-) However, if anyone is interested to make this work on R2 too, he can provide dwmcore.dll and udwm.dll and I can see what could be done with that :-) It would be great if I managed to get my Intel network card to work witn server 2012 R2. I'm fighting with it since yesterday, lol. I can provide the DLLs, though. WinServ2012R2DWMDLL.zip

In such case, post your debug.log (unless you've already post it and I overlooked it) and possibly minidump.dmp (for RC3 only). Maybe something causes crash or deadlock in your DWM. Sorry BM, I've been out of it lately. Will try RC3 and post the relevant stuff soon. EDIT: So far, it worked on the first try! I'm going to go stare at the changelog very hard...

re @ "What hardware used" Maybe, that is the cause: http://support.micro...b/2850674/en-us? I don't think it's related. My windows does not freeze (I can hear skype/etc logging in, and power button works just fine to shut it down. pressing random keys gives the familiar bell. I just can't see what's happening since the screen is black. I also don't use sleep at all, my computer either run, or is restarting. or powered down. re-enabling UEFI secure boot makes windows boot just fine. it only happens when the DWMGlass DLL is loaded. I don't use custom theme (regular windows 8 theme, no uXpatch) (is it required?)

Noone has a clue about fixing this black screen issue? re-installing again without knowing what causes it is out of question.

I have an UEFI bios with disable-able secure boot, so I can turn that on and negate any DLL inject. but yeah. Not everyone can do that.

I still can't use this piece of wonder again. I get a black screen on boot. Is there anything kind of info I can provide to help getting it fixed/sorted? Windows is up to date. (9200.16581.amd64fre.win8_gdr.130410-1505) nVidia driver is up to date-ish. (314.07, I downgraded from 320 since it nearly killed one of my cards.) Motherboard: ASUS Crosshair V Formula-Z BIOS version : 1403 Video card: ASUS GTX660 (non-Ti, no SLI, single card) Processor (AMD FX-8350 @4.7GHz) RAM Crucial ballistix Tactical (Micron D9 chips) - 16GB .. not sure what else could be relevant.

I have these too.

I don't even understand how this is possible to set this to 0x10000000 ??? Makes no sense.

Being a developer too (or on my way to be), I understand BigMuscle. I can't talk for him, but I can talk for me; There's generally a few types of feedback when I release something and I explicitely tell them "it's a testing software. It may crash, it may not work as you want, and it may even kill your kittens": Nothing work! *whine* It keeps crashing. This is the most useless piece of ****** I have ever installed It crashed when I did [manipulation]. I looked at the program log and the error it gives me is [insert error here]. The first definitely is useless, aside from letting the developer know that it failed at some point. The second is worse, because it shows a lack of control and civility. The third one is good, and the correct way to report problems in testing software. The developer can't fix a problem without knowing what happened, during which operation. Every hint helps. I don't want to beat a dead horse, but this is testing software. it /will/ improve, but it is easier for everyone when problems and disagreements are explained maturely and with calm. If you don't like a feature/behavior, ask nicely and describe your opinion in a civilized way. Don't moan/whine/cuss/diss. The only world where being mad and mean at someone to get it done is when it's coming from who gives you the money for your bread. That being said... The fact that it works already that well at version 0.7 for many people is a great thing, considering that glass was called as "Gone". I personally chose to use it in my production environment, because it is my choice and I accept to deal with the consequences, even if it goes as far as destroying my whole data storage. Because everything I currently do already risks such things, one more can't really make a difference.

Maybe it is problem that you have UEFI secure boot enabled? No solution for it yet :-( I had the same behavior. I needed to disable Secureboot manually in the bios.

Correct. I use the 0.5 loader to load the 0.7. I will look into the logs... However due to a technical problem I will be re-installing windows 7 today. Windows 8 is so fragile it keeps breaking on me. The only thing I can see in the log viewer is a warning confirming that I indeed am loading custom libraries. That is all.

So after poking a bit... 1: The GUI tool resets the DLL path. Bad. 2: Without touching the tool and being sure that the registry setting survives, glass still refuses to work in any other way than by running the loader included in older versions. 3: I'm out of ideas.

Interesting. The path to the DLL was right the first time, and seems to have been reset. (was D:\DWMGlass.dll) https://dl.dropboxusercontent.com/u/7425443/reg.JPG

Interesting. There might be a problem with my setup, because I noticed that the 0.5 version contained a loader, so I used it. It works with loader, both with 0.5 and the DLL from 0.7. So... The DLL doesn't seem to be loaded right at boot. https://dl.dropboxusercontent.com/u/7425443/HoTS_glass.png

I also tried to lower color intensity, to no avail.