• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Aaaaa

Profile Information

  • OS
    Windows 7 x64
  1. Check if issue is in test build: But I guess it falls down to some setting or policy. Is Sleep available in modern ui shudown? Hi, I have the same issue (no sleep button) with build 2.1.2 on Server 2012. I had a look at that link and I couldn't find the test build You can enable the start screen in the "switching" configuration options.
  2. Of course (I know very little English): A small issue with this: the right edge of a window doesn't have a black outline, but the rest of the edges do.
  3. Is that on Windows 8? If so, how did you get the transparent address bar, etc?
  4. It's not actually in its own image. It's part of an image that includes a whole lot of other things (buttons, shadows, etc)
  5. You can also run a command prompt (as administrator) and enter: powercfg -h on
  6. There's a bit of a weird bug on the site when I go to download it. It counts down from 5 and starts downloading at zero, but after that it starts counting down further to negative numbers:
  7. That depends how machine code is generated, it doesn't have to be generated using all components HDD/RAM/CPU/Motherboard. It could be just 2 elements. Eg like Motherboard+CPU .... if so u can swap HDD and RAM everyday . Big Muscle could clarify what Machine Code based on for that. Also once licence been activated on a copy of Windows it doesn't mean it checks it again of hardware is modified. again BigMuscle need to clarify this, dose it check machine code once when activation or every launch ? Anyway, it same as StartIsBack its just 3 Euros =~= 130 Rubles that's a price of a Burger in McDonald's,... I would understand if it was 15 Euros or 20 ... then yeah ... I tested version 1.0 in a virtual machine and changed the BIOS UUID and hard drive UUID, and the machine code for Aero Glass stayed the same.
  8. Using REG ADD is more direct than creating a temporary .reg file: @echo offREG ADD HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows /V "LoadAppInit_DLLs" /T REG_DWORD /D 1 /FREG ADD HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows /V "AppInit_DLLs" /T REG_SZ /D "%systemdrive%\\DWM\\DWMGlass.dll" /FREG ADD HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows /V "RequireSignedAppInit_DLLs" /T REG_DWORD /D 0 /Ftaskkill /f /im dwm.exe /t
  9. But this is what I said many times and people were still shouting. Next time, I will not put message box there and I will ensure that Aero Glass stops working after 1 hour completely, or maybe I will present screenshot only. Maybe, everyone will then realize that this is preview only.A debugging window at least gives information that can be used to find problems. A static message doesn't serve that purpose. It just says one piece of information that people should already know anyway. If you're not even planning on getting money for this, I just don't get why you'd want to have artificial limitations like this given that you don't even gain anything from putting them there. It makes sense to have a limited trial for paid software so people can see how the program functions and decide if they want to buy it. Maybe you should charge for it if you don't think people deserve to get it for free. And so what if some people are incapable of reading that this is a test version? You can't fix stupid. Just let stupid people break their systems (they'll probably find a way to break it even if it's not by using your program). Because bugs are to be expected, and is the reason why there are test versions. Anyone that doesn't understand that deserves to break their system. That's punishment enough, really.
  10. If a debugging window is necessary in some ways to see what's going on, so be it. Although if it were me, I think if anyone wants to use a version where they've removed the debugging window, I'd let them, on the basis that any issues they have is their own responsibility. So if they come and say "I don't like X", just tell them "use the debugging version or I can't/won't help". If people don't like the intended functionality in some way, or a necessary consequence of having it running (it doesn't use zero resources) that's their problem. I just don't think a message box is the right way of dealing with those people. It's kind of a blunt instrument that also annoys people who just want to legitimately test it / are willing to accept any consequences of them running it. A bit like how a lot of DRM annoys people who paid for some software and makes them not want to use it.
  11. Having a debug window isn't the only way of getting debug messages though. The most common way is having log files automatically created (log files stay there even if the system crashes and you can't manually record debug messages). The (il)legality of it doesn't necessarily align with the logic of it. I just don't see (logically) why you'd want to artificially limit what people can do with it as long as they carry the risk. People don't like artificial limitations. That's really all there is to understand about why people do it. It's also why I like the GNU GPL (I'm not particularly knowledgeable about programming, but the things I've made have been licensed under the GNU GPL). As far as testing goes, that's really a separate issue. Just because people don't like artificial limitations, doesn't mean they don't want to test and report bugs (or even fix bugs themselves if it's open source). If anything, limitations just reduce the number of people who want to use the software and by extension people who want to test the software. Just like how I've been considering moving to Linux as a primary OS as a result of Microsoft removing choices in Windows 8 - like not having aero glass. It's an artificial limitation that doesn't really make sense.
  12. I don't think the frequency even matters that much though. I mean, people get annoyed by Windows Update restart popups too, and you can delay them to 4 hours. (yes, you can delay them indefinitely by stopping the WU service, but most people don't know how). And for the tradeoff of having aero glass vs having to deal with any amount of popups at all, most people just won't bother. It's less hassle even to just use Windows 7 instead.
  13. What that obviously means is that people are not using the versions with the popup. Which also means you have fewer people testing it for actual bugs. It just doesn't really make sense why you'd want that.
  14. How is continually clicking "OK" to dismiss a popup nag helping to test the software? How does it aid the testing process? Intentionally annoying people as you describe is a terrible way to build goodwill for your software if and when it does go for sale. No offense but I'm not sure who's worse - Microsoft for removing Aero Glass, or the attitude of the guy trying to add it back in. Anyone who complains that one popup per hour is too annoying to test clearly is not actually testing this software. That is a non-sequitur.
  15. Yes, it solves only one thing - it stops/annoys you using the software if your intention is not the testing/previewing. It also stops people from testing it who do intend to actually test it.