Leaderboard

Just finished testing my fully updated install of Vista Ultimate x64, including build 6003 updates from Aug 2020: It seems that Microsoft fixed the timer issue, as seen above. Unfortunately, there are still random issues, specially with UAC prompts: permissions are not properly granted. Even so, it's clearly much more stable.

(Note: this text is written for and directed at Big Muscle. Just pointing it out in case that the "you"s looks a bit wierd to you (the person reading this text)) Let me first get the most important thing out of the way: You CAN make money with open source software. In many ways actually: You can charge for the convenicance of auto updates You can charge for direct support (for example, via email or via a private discord chat) You can charge for the convenicance of having an already compiled binary version (which is especially true on windows; on linux for example, you usually git clone the repo, cd into it and type `make && sudo make install` and that's it. On Windows though...) You can make (optional) donations Speaking of donations: what you offer on your website, those are NOT donations. Those are payments. It is NOT freeware. You just get a free demo version. A donation is something optional. The point of a donation is not to get something back from it (besides maybe the knowladge of having helped someone/-thing or maybe getting a "Thank you" mail from them), but purely to support someone/-thing. And I want to mention that that is the only reason why I actually paid 5 bucks for it: not because I care about the watermark (if that would be my only reason, I could have just used a cracked version, and yes, I DID have a working one back then, but I didn't use it), but because I want this project to stay alive. In other words: I am pretty shure that a lot of peole donated just for support, or at least partially. Anyways, I of course know that there are not only positive things about open sourceing this software, namely: You may not make the exact same amount of money from "donations"* You may unveal your secrets* However, both of these arguments are very weak. The first one I already talked about above. For the second one: opening this app would mean that a lot more developers could integrate it (as in making their app compatible with it, not as in stealing your code; the only app I know of that supports aero glass is Winstep Nexus, and that one only works when it really wants to, which, as a dev explained to me, is not their fault). It would allow other people to learn about windows from (because, as described on glass8.eu, it uses undocumented windows features). TL;DR both arguments are... bad. Now let's finally get to why I think it should be open sourced: You (Big Muscle) are not able to maintain this on your own, or at least not in a way that I would concider acceptable for a paid app. Often times, this app gets a fix about 1-2 months before the next major update comes out, which will break it again. And again. And again. This app would be accessable to a lot more people. It would improve the user experiance since it will allow updates to be completed much, much faster. You would not have to stem this project all on your own anymore, which, again, you're not able to. Almost the entire forum is just "It doesn't work" posts. As described previosly, third party compatibility could also be improved massively. A concern you may have is others missusing your code to make money on. This is actually not a problem. You can either use the GNU GPL (or similar), which will technically not prevent your code from being commericallized, but since every modification that is being made availably has to also be opensourced under the same license (or a newer version), it is very unrealistic to think that someone would actually do it, exept maybe in those ***** bundles. While some apps (like OpenOffice or 7-zip, see here ) do suffer from this problem, I, again, don't think that such a tool like AeroGlass would really suffer from this. Alternatively, you can also write your own license, for example like this (this is not legal advaise): Of course, the above mentiond "license" is only one of many ways it could be done (and, again, it is not legal advise). I hope that you will change your mind about this program and it's licensing and distribution, as it would gain both you and even more so it's community. Cheers.

We don't need to go back that far for Electron apps. Visual Studio Code 1.46 works and it's based on Chromium 78. If Discord and Steam were x64 native, they'd probably work. We need to get into ntdll (both x86 and x64) for later Chromiums to work. And now that ntoskrnl modification is starting, ntdll modification should be coming soon. And yes, based on recent comments, the current path will be maintained.

Well, with the extended kernel, up to AMD 15.100 drivers work without any modification (Well, you would need to modify the .inf, but other than that, nothing is needed). The AMD 15.6 CCC is missing some powerprof.dll functions, but works anyways. Maybe with the new ntoskrnl, I could try the 16.2.1 drivers, or those modded 16.101 drivers. I think someone would need to mod 372.70 drivers to work better with Vista, because I think the issue is not missing functions. @win32 seems to be the best person to attempt such a thing, unless @blackwingcat decides to try and fix them, but that's highly unlikely. I think I'd rather see the Oct 2nd Steam tricked into running the Windows 7 CEF without issue, or Discord working on Vista before I see the Haswell+ or Ryzen issues fixed. Since Chromium 73 stable and newer don't work on Vista, I think you'd need to modify a older copy of Discord, which Discord still hosts. https://dl.discordapp.net/apps/win/0.0.305/DiscordSetup.exe This is the last(?) copy of Discord that has a Chromium 69 CEF, and should be the easiest to get working on Vista. If you bypass the shortcut, and run Discord directly, it'll update to the latest version of 305, and run. Edit: There might be a Chromium 72 Discord Development build, but I'm not sifting through thousands of versions of Discord Development.

Well, it appears that MS got around to improving Haswell, though there are still some issues. I haven't been able to test it due to issues with Windows Update on my Kaby Lake though. Now I'm thinking; do I rebase the extended kernel on the September 2020 versions of files, thus abandoning the April 2017 versions? Or do I still work on LoadLibraryExW from build 6519 since that is flawless, while this one is not (mind you, the UAC permission issues may lie elsewhere).

You can import the .csv file into windowspatchloader. Then it will only download what is in the list.

Yes. Hoping there are no issues that may arise once the appropriate functions are added.

I get a score of 21910 with XFX 7800GS 256MB. I believe I have the same drivers as you installed for mobo and gpu. nVidia control panel shows OS AGP 2x and fast write is Yes. Mobo has 3GB of RAM of which 2 are currently enabled in 9x.

Most are from RTM SP2, but I'm pretty sure I posted some dumps from the 2017 EOS point, and the 2020 EOS point. I'll try to get some more with the custom kernel tomorrow.

I used windowspatchloader http://www.satloader.net/WindowsPatchLoader_v1.1.3.zip to make a list of download links from Vista Starter which had just been installed, then updated via WU. Might be useful to somebody. There is file listed in the csv and the text with a .psf extension ( windowspatchloader gets stuck trying to download that one ) http://www.download.windowsupdate.com/msdownload/update/software/updt/2008/04/windows6.0-kb937286-x86-en-us_3b802969583d81edab326fcb29273d4416d4beb6.psf starter-final.zip

Your Vista is UEFI? That changes everything. osloader.exe is a modified version of winload.exe which is intended only for MBR/BIOS systems, though you will be able to use the same ntkrnlmp as everyone else. So I checked out winload.efi and it's indeed very similar to the MBR version. So hopefully the patched osloader.efi works. So for UEFI users, just follow this instruction as opposed to the similar one for BIOS users: bcdedit /set {91274567-89ab-cdef-00ff-nca000ffffff} path \Windows\system32\osloader.efi

For Starter, some updates won't install, as some features are not supported, such as Dreamscene and other Ultimate extras.

there is no "release" schedule since all "releases" are just actually "pre-release". and no, I don't want to make any point-release builds for continuing develop product. 45ESR builds are different as upstream only drops few commits per month for bug-fixing.

Not trying to advertise or anything, but, there is a new windows blinds theme out which includes ALL the themes from windows 7 aswell as Vista. The startmenu looks pretty identical but start10 is required! The only thing that throws me off is the tray corners, only the arrow has the glassy look to it with the little white drop reflection. Also the jumplist of windows 7 (like the feature from Startisback++) isn't on there due to limitations, though i'm in a stardock server and they said thats on a list for a future update. Surprisingly aeroglass does work, but the shine doesn't move (if that makes sense, just it's transparent with blurred background). Also the min,max, and close buttons glow~ Anyways, here is the link:: Aero7: https://www.deviantart.com/newinfinitepro/art/Aero7X-Reset-for-Windowblinds-10-836337064 Vista: https://www.deviantart.com/newinfinitepro/art/AeroVistaX-Reset-for-WindowBlinds-10-844912103 Basic Theme Preview: https://www.deviantart.com/newinfinitepro/art/Aero7X-Reset-Sneak-Peak-Basic-Theme-849338619

@bigmuscle Yes, please consider this for the future development of Aero Glass. If you want to keep it paid, at least provide a bit more communication.

All versions Adobe Flash Player newer than 32.0.0.371 contain a time-bomb. After 12-Jan-2021 local SWF-files does not playback. The latest working version is 32.0.0.371. Use a virtual machine to check. Install the Adobe Flash Player and set the clock to January 2021.

I have that board sitting on my benchtable at the moment. I can confirm what Feamane said. After all is said and done, it is a matter of preference, both choices are ok. That is not happening very often with W9x ... :-D