• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
ORelio

Aero Glass Tweaker GUI for Win8 v1.3.2

319 posts in this topic

Ok, as I copied & pasted the regitry path from bigmuscle's post, that's probably due to a compatibility feature of Windows itself for 32-bits apps.

... but as the libraries used are 32-bits only I can't just recompile the app as 64-bits, this would not work :}

0

Share this post


Link to post
Share on other sites

try to search how to disable key virtualization... as I remember correctly there is some article at MSDN

0

Share this post


Link to post
Share on other sites

Thanks for the hint, found the article ! http://msdn.microsoft.com/en-us/library/windows/desktop/aa965884%28v=vs.85%29.aspx

But I read this in the article :

"Registry virtualization is disabled for the following: [...] - Processes that have requestedExecutionLevel specified in their manifests."

AGTweaker contains a manifest, with the following statement : <requestedExecutionLevel level="requireAdministrator" uiAccess="false" />

So Registry Virtualization should be disabled according to the article ... :huh:

Googling for Wow6432Node, found a stackoverflow question that gave an interesting answer :

http://stackoverflow.com/questions/11808462/avoid-registry-wow6432node-redirection - http://msdn.microsoft.com/en-us/library/microsoft.win32.registrykey.openbasekey%28v=vs.100%29.aspx

So using RegistryKey.OpenBaseKey(RegistryHive.LocalMachine, RegistryView.Registry64); should bypass the Wow6432Node key virtualization :)

Could someone that did have the Wow6432Node issue try this *TEST* build of AGTweaker ? : AGTweaker-1.1.5b.zip

0

Share this post


Link to post
Share on other sites

1.1.5b correcttly reading and writing to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM and if that "folder" is missing, it is created.

Note:- Don't know if it's intentional but if the "Use Direct2D" box is selected in AGTweaker 1.1.5b, the HLKM\....\Windows\DWM\UseDirect2DRendering key is deleted rather than its value being set to "1" (double-checked and the key is totally absent - it's not being created elsewhere in the registry). Aero Glass does switch to D2D and without that key present, it remains in D2D after being stopped and restarted - which suggests that it's running in D2D by default (so anyone who doesn't have the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\DWM is not running D3D even if they think they are).

0

Share this post


Link to post
Share on other sites

Glad to see that the registry issue is solved, thanks bigmuscle for the hint and pengipete for the feedback!

Yes, AGTweaker deletes useless keys, eg if the UseDirect2DRendering key is missing, D2D is used by default so AGTweaker deletes the key rather than setting it to 1.

This is designed to leave in the registry only the necessary keys, ie when you want to use values that are not the default ones :)

EDIT: Released 1.1.6, which includes the key virtualization registry fix.

Edited by ORelio
0

Share this post


Link to post
Share on other sites

Nice one.

Just a suggestion though - might be best to leave the D2D key and just set it as required by BM's app - apart from anything else, there will be people who created the key manually and it's "bad manners" to delete their keys :)

I like the way you think though - cleaning up as you go along is admirable ;)

0

Share this post


Link to post
Share on other sites

In version 0.5 was restored registry key "Disable logging", i think it must be in gui. Interest thing, that for leave logging enabled the key in registry must be "1".

0

Share this post


Link to post
Share on other sites

ouch, this seems to be the bug in my application. When DisableLogging is set to 1 then the logging should be disabled. However, it is not a big deal because it is not recommended to touch this settings.

0

Share this post


Link to post
Share on other sites

ouch, this seems to be the bug in my application. When DisableLogging is set to 1 then the logging should be disabled. However, it is not a big deal because it is not recommended to touch this settings.

Agreed )))) And because of it i not report a bug ))))

Edited by CKyHC
0

Share this post


Link to post
Share on other sites
Nice one.

Just a suggestion though - might be best to leave the D2D key and just set it as required by BM's app - apart from anything else, there will be people who created the key manually and it's "bad manners" to delete their keys :)

I like the way you think though - cleaning up as you go along is admirable ;)

Both approaches are valid, I think the average user does not care about whether the key is there or not - he does not use the registry editor - so I chose to clean keys when they are unused. Your point of view is just as well, though.

ouch, this seems to be the bug in my application. When DisableLogging is set to 1 then the logging should be disabled. However, it is not a big deal because it is not recommended to touch this settings.

Oh, so it was a bug. I thought you removed the ability to disable the log, but don't worry, AGTweaker automatically cleans the file on each startup when the "disable log" box is checked so the file does not grow indefinitely ... (I am decidedly a bit obsessed with cleanliness. lol.)

0

Share this post


Link to post
Share on other sites

I was only thinking of it with AG being in the development stage - so people testing it are more likely to be entering settings manually.

0

Share this post


Link to post
Share on other sites

Working Good! Thanks for the update thumbup.gif

0

Share this post


Link to post
Share on other sites

Hum, Okay but with the content of the "Details" Box it would be better... Could you copy and paste the contents of the "Details" box? ^^"

0

Share this post


Link to post
Share on other sites

Hum, Okay but with the content of the "Details" Box it would be better... Could you copy and paste the contents of the "Details" box? ^^"

I'm sorry for the late reply but I didn't see that you answered. :hello:

Here it is:

at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)

at System.Windows.Forms.Control.CreateControl()

at System.Windows.Forms.Control.WmShowWindow(Message& m)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

at System.Windows.Forms.ContainerControl.WndProc(Message& m)

at System.Windows.Forms.Form.WmShowWindow(Message& m)

at System.Windows.Forms.Form.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************

mscorlib

Assembly Version: 4.0.0.0

Win32 Version: 4.0.30319.18033 built by: FX45RTMGDR

CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

----------------------------------------

AGTweaker

Assembly Version: 1.0.0.0

Win32 Version: 1.0.0.0

CodeBase: file:///C:/Users/Danny/Desktop/AGTweaker/AGTweaker.exe

----------------------------------------

System.Windows.Forms

Assembly Version: 4.0.0.0

Win32 Version: 4.0.30319.18037 built by: FX45RTMGDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System.Drawing

Assembly Version: 4.0.0.0

Win32 Version: 4.0.30319.18022 built by: FX45RTMGDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

System

Assembly Version: 4.0.0.0

Win32 Version: 4.0.30319.18033 built by: FX45RTMGDR

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

For example:

<configuration>

<system.windows.forms jitDebugging="true" />

</configuration>

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

0

Share this post


Link to post
Share on other sites

Ah, lol! Your registry value for Transparency or Opacity is wrong, it should be between 0 and 255, so starting the app with a registry value of 304 crash it.

I'll fix that in the next release. While waiting, delete or modify the registry keys with a wrong value.

Thanks for the full crash report :)

0

Share this post


Link to post
Share on other sites

Ah, lol! Your registry value for Transparency or Opacity is wrong, it should be between 0 and 255, so starting the app with a registry value of 304 crash it.

I'll fix that in the next release. While waiting, delete or modify the registry keys with a wrong value.

Thanks for the full crash report :)

Oh ok thanks for your help it is much appreciated ps: I noticed your profile pic was from a game called " Radiant" I just got that game/app yesterday lol

0

Share this post


Link to post
Share on other sites

One question where do I find the registry values?

0

Share this post


Link to post
Share on other sites

Yeah, that's from Radiant :rolleyes:

Registry paths are detailed here:

0

Share this post


Link to post
Share on other sites

Yeah, that's from Radiant :rolleyes:

Registry paths are detailed here:

All right thank you SO much for your help :D:thumbup

0

Share this post


Link to post
Share on other sites

My pleasure, if you have any further question don't hesitate ;)

0

Share this post


Link to post
Share on other sites

1.1.6 not working with AG v0.6 - I believe it's cos BM changed the name of the exe.

0

Share this post


Link to post
Share on other sites

just rename the exe - that seemed to work for me but 0.6 does not work for me - aero is too dark and i dont seem to be able to cure that - plus taskbar is wrong - not bothered to play as 0.5 works well

0

Share this post


Link to post
Share on other sites

An update is coming soon, don't worry :)

Try lowering color intensity for window borders in Personalization panel.

0

Share this post


Link to post
Share on other sites

Thank you for your great proggy!

I have however the problem that I installed Windows 8 at drive D:! :wacko: And now Aero Glass Tweaker GUI for Win8 v1.1.6 doesn't work: it says: Cannot find ... at C:\DWM...

Is it possible to customize the HD to which it must be addressed to? Something like an .ini-file in which it is possible to change the default C-drive to D-drive? That would be great! :rolleyes:

Hope that is possible!

EDIT:

Meanwhile I found a workaround: I just copied the DWM-folder to my C-drive, and that works! But it would be nice, of course, to have the opportunity to choose the drive at which Windows 8 is installed on. :w00t:

Edited by palbertsma
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.