Jump to content

AlexKven

Member
  • Posts

    92
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by AlexKven

  1. you could try also different values - e.g. 0x9100 or 0x9200. 0x9100 works for me - other 2 values do not It finally works. Using version 0.4 (without the 2 files you posted) it works fine by setting DeviceFeatureLevel to 0x9100 That is also my configuration, 0.4 with 0x9100. So, Bigmuscle, what does setting it to 0x9300, 0x9200, 0x9100 even do, and would setting it to 0x9000, 0x8900, and 0x9400 be something to recommend to those that still have problems?
  2. This still doesn't work for WPF applications, and based on my knowledge of WPF, I don't think this will ever work until you can ditch layered windows. Until then, could you make this program detect if a particular window is a WPF window, and if it is, render it normally?
  3. For me, 9300 doesn't work, 9200 doesn't work, but 9100 works great! I am loving this new version (Preview 4, not the private build, which I will refer to as "preview 4.1'). Performance is the same as the Windows 7 OS I had previously on my computer. Thank you!
  4. Kind of. You still need to patch your system since this is considered a customized theme. I recommend either UxTheme (http://www.softpedia...tiPatcher.shtml), or UxStyle (http://uxstyle.com/b...mental_bits.zip). Actually, you don't even need to patch your system. The actual theme file used in the release preview is in the same file format as the current build. Since the theme for Release Preview was digitally signed by Microsoft, that means you can use the real .msstyles file from Windows 8 Release Preview in Windows 8 RTM without patching of any kind. Note, this only works in the release preview.
  5. I am having the same problem as everyone else. Here is my debug file. debug.txt
  6. But it's a bigger deal now because Windows RT is supposed to not be able to run non-microsoft apps. Thus, people who activate this hack are vulnerable to threats from the mainstream Windows 8 that the author could have ported to ARM.
  7. You can try playing with DeviceFeatureLevel registry settings. It allows achieving glass effect also on non-supported drivers (and even when no graphics drivers are installed). Can you tell me how to do this? I am having this same problem, and it is driving me crazy.
  8. Don't get your hopes up. Microsoft said somewhere that it will patch away the jailbreak.
  9. Why isn't there any sort of freeware visual style maker?
  10. Oh, that would be tough. I guess he could implement the program to not blend the corners, but then he would have to create a bunch of new visual style files (.msstyles files) for rounded windows.
  11. Windows Store apps can't take screenshots.
  12. This kind of thing is simply not possible on Windows RT, and it would be pointless to do so. This is because a program would have to be compiled for the ARM processor to work, which Microsoft doesn't allow nor support for desktop apps, so both creating a DWM hacker like this and a DWM.exe replacement would even be able to be made. And you can't hack the DWM from a metro app, because the secure model doesn't allow it. Short story, if you use Windows RT, you are stuck without transparency (Which shouldn't be much of a problem because you will spend relatively little time in the desktop).
  13. This is very good. I made an account on this site just because of this. But there is one issue: It is incompatible with all wpf apps that use the system frame. Thank you for working so hard on this! I am glad we don't need to replace dwm.exe to get glass back.
×
×
  • Create New...