ROCKNROLL

Updated: https://github.com/MoscaDotTo/Winapp2/commit/870d13336009ac5abef63877ea49a9fe1e6c8437

Yes, but as you can see, none of them are exactly the same: [Aignes Website-Watcher AutoBackup*] LangSecRef=3023 Warning=This will delete your AutoBackup of your site. Detect=HKCU\SOFTWARE\aignes\wswatch Default=False FileKey1=%AppData%\aignes\website-watcher\config\autobackup|*.* [Aignes Website-Watcher Bookmarks*] LangSecRef=3023 Warning=This will delete all of your Bookmarks. Detect=HKCU\Software\aignes\wswatch Default=False FileKey1=%AppData%\aignes\website-watcher\bookmarks|*.* [Aignes Website-Watcher*] LangSecRef=3023 Detect=HKCU\SOFTWARE\aignes\wswatch Default=False FileKey1=%AppData%\aignes\website-watcher\config\log|*.* FileKey2=%AppData%\aignes\website-watcher\config\temp|*.* [WebSite-Watcher*] LangSecRef=3021 Detect=HKCU\Software\aignes\wswatch Default=False FileKey1=%AppData%\aignes\WebSite-Watcher\config\favicons|*.* FileKey2=%AppData%\aignes\WebSite-Watcher\config\settings|*.cfg_bak* The bookmarks and backups should remain separate, in my opinion. The other 2 looks like they could be combined, but you should know that CCleaner is case-sensitive, so if the path is in lower case, then the upper case FileKeys will not work for the lower case directories. Do you know if they should be upper case or lower case? I assume they should be lower case, as the others are all lower case. I have not used this program to know what these entries truly do, but this is just my opinion. I also think FileKey2=%AppData%\aignes\WebSite-Watcher\config\settings|*.cfg_bak* should be thrown into the backup entry instead, since that is a backup copy of a config file.

Perhaps you want to show both the entries that are being duplicated first, so we can compare them and make sure one doesn't have something the other doesn't. Updated the others: https://github.com/MoscaDotTo/Winapp2/commit/caa3d292bc8b21bbef69c1663ab40136790f32ac

Please take a look at these issues: https://github.com/MoscaDotTo/Winapp2/issues/95 Continued here: https://singularlabs.com/forums/topic/ccenhancer-firefox-with-stylus-addon/

Updated: https://github.com/MoscaDotTo/Winapp2/commit/b0810c5e47ba31ef411b39481667402367c69b37

Updates: https://github.com/MoscaDotTo/Winapp2/commit/62140ed6f188c580c0a788cbc8749c5a83688b9b

I can't edit the first post, but Edge is "Save target as". I assume the same for IE. Chrome is most likely "Save link as" like Firefox.

I am alright with adding these if everyone else agrees? Updated the others: https://github.com/MoscaDotTo/Winapp2/commit/14ec735a28a9a71c66f41f5a8aa9ff3cd003cdf3

You mean it has a - at the end of it? If you delete it manually does it regenerate. I have not seen a tmp file with a - at the end like that. Did you try modifying this file at all?

This entry doesn't exist in Winapp2. Did you mean this entry: [Windows Photos*] LangSecRef=3031 Detect=HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\microsoft.windowsphotos_8wekyb3d8bbwe DetectFile=%LocalAppData%\Packages\microsoft.windowsphotos_8wekyb3d8bbwe Default=False FileKey1=%LocalAppData%\Packages\microsoft.windowsphotos_*\AC\AppCache|*.*|RECURSE FileKey2=%LocalAppData%\Packages\microsoft.windowsphotos_*\AC\BackgroundTransferApi|*.down_data FileKey3=%LocalAppData%\Packages\microsoft.windowsphotos_*\AC\BackgroundTransferApi|*.up_meta FileKey4=%LocalAppData%\Packages\microsoft.windowsphotos_*\AC\INetCache|*.*|RECURSE FileKey5=%LocalAppData%\Packages\microsoft.windowsphotos_*\AC\INetCookies|*.*|RECURSE FileKey6=%LocalAppData%\Packages\microsoft.windowsphotos_*\AC\INetHistory|*.*|RECURSE FileKey7=%LocalAppData%\Packages\microsoft.windowsphotos_*\AC\Microsoft\CLR_v4.0\UsageLogs|*.*|RECURSE FileKey8=%LocalAppData%\Packages\microsoft.windowsphotos_*\AC\Microsoft\CryptnetUrlCache\Content|*.* FileKey9=%LocalAppData%\Packages\microsoft.windowsphotos_*\AC\Microsoft\CryptnetUrlCache\MetaData|*.* FileKey10=%LocalAppData%\Packages\microsoft.windowsphotos_*\AC\Microsoft\Internet Explorer\DOMStore|*.*|RECURSE FileKey11=%LocalAppData%\Packages\microsoft.windowsphotos_*\AC\PRICache|*.* FileKey12=%LocalAppData%\Packages\microsoft.windowsphotos_*\AC\Temp|*.* FileKey13=%LocalAppData%\Packages\microsoft.windowsphotos_*\LocalState\bici|*.sqm FileKey14=%LocalAppData%\Packages\microsoft.windowsphotos_*\LocalState|*.log FileKey15=%LocalAppData%\Packages\microsoft.windowsphotos_*\LocalState|*.jpg FileKey16=%LocalAppData%\Packages\microsoft.windowsphotos_*\TempState|*.*|RECURSE RegKey1=HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\microsoft.windowsphotos_8wekyb3d8bbwe\SearchHisto Your entry is not the same as that one, though. Please make sure you are editing the file on GitHub and not a copy on your PC. Updated the rest though: https://github.com/MoscaDotTo/Winapp2/commit/adf18ed324411a2bb1af4d47167613c9c91e373f

Updates: https://github.com/MoscaDotTo/Winapp2/commit/15f7b097fe63f99b2784d1e8bc3c867aa94c81fe

That's true. Though one has to jump through hoops. I suppose it doesn't hurt to leave them.

Updated: https://github.com/MoscaDotTo/Winapp2/commit/c5a746d2efb3140f6dbf0ce4afa7db26ed612ba9

Updated: https://github.com/MoscaDotTo/Winapp2/commit/8643bf7db8549e7bb11da04b1f37e9f56ae72bcf

Hello everyone. Good news my PC is back online. I have already updated the non-ccleaner with the regular Winapp2 file. Unfortunately I have lost track as to what was added and what hasn't. If anything got missed, please re post it.

Well, the FCC wants to make 100mbps a standard by 2020, so I don't think it will be much of a issue. Also, ISPs can sell user data now, so they can make higher speeds more affordable or even make free internet, since they have a alternative making money method. Spectrum has already made 60mbps a standard with their internet and that can handle 8K 60fps streaming. Anyways, 2020 is a good year to upgrade your gear. A lot of new stuff will be releasing around there: HBM 3.0, GDDR6, AM5 platform, PCI-E 5.0, and by the time, HDMI 2.2/3.0 will be out, which will probably double the bandwidth again, probably allowing 10K at 180hz.

So, HDMI 2.1 is coming in the future, which is targeting 10K at 120hz through display stream compression, with possible 16-bit color, HDR/dynamic HDR, as well as Game mode VRR for tvs, which is similar to g-sync/freesync. I personally don't think it is worth going beyond 10K. I plan on getting a 10K myself, but not anytime soon. Maybe when like 144hz+ 10K tvs with a 1ms response and +16-bit color support are a thing, I will get one. It also looks like HDMI is taking the high-end road again as 2.1 is targeting 48gb/s bandwidth, while display port 1.5/2.0/next version is only targeting 40gb/s. It also seems like monitors will be a thing of the past, too. I mean if tvs are getting all this good stuff, who needs monitors anymore. You can watch tv and game on tvs now. I mean, I highly doubt they will only just keep increasing frame rates, color bits and resolution when it seems like all that is reaching it's max points. I assume they will come out with more eye candy stuff, similar to HDR. What are your opinions? Do you think it is worth going beyond 10K or going beyond 144hz or going beyond 16bit colors? What do you think tv companies have planned to sell future tvs?

We could probably use 1 detect on that, too. This should work: Detect=HKCU\Software\Foxit Software\Foxit PhantomPDF Today is now 15 days since my motherboard is at the RMA at MSI. I haven't heard anything back. They said it will take 15-35 days, depending on stockage, problem, etc. I hope I will receive a email of the status this week, but no guarantee. I still can't load up the GitHub files on this laptop, so you will have to patient on my return. EDIT: Just got a email. Looks like they shipping my motherboard. It will probably be here at the latest of Monday, assuming they don't ship weekends. I didn't get a notice if my motherboard was bad, though. Will have to call them tomorrow. If my motherboard isn't the issue, then I will try to fix this laptop so it can load GitHub so I can still work on Winapp2 at least.

I have my process count on my PC set to 8, but I think I may increase it more. The autofill looks nice and will come in handy for people who do a lot of online shipping or whatever, especially since lots of people don't like saving information on a website. I think soon I will go back to using Firefox beta and would even be willing to enable telemetry data for them to help development.

Maybe we could just use 1 detect for them both? Adobe Photoshop Elements could be Detect=HKCU\Software\Adobe\Photoshop Elements Adobe Premiere Elements could be: Detect=HKCU\Software\Adobe\Premiere Elements

Well, looks like my motherboard is fried on my PC. I am currently on a really bad laptop. This laptop cannot load github or any large websites for some reason. I am afraid I have to put Winapp2 on hole for awhile until my new motherboard is here, which won't be for another 2-3 weeks. I am sorry to have to do this. I can still communicate through the forums, though.

We are planning on licensing Winapp2, as we have had some requests from other programs to use Winapp2. This shouldn't change much for most people. Please read and discuss here: https://github.com/MoscaDotTo/Winapp2/issues/86

I tried 3.1, which was released recently. It actually runs really well and a lot better and faster then the previous version. I wonder what is wrong with software today, I thought it was just gaming that was unoptimized, but it seems like even software are too. I wonder if it's a problem with the programming languages themself. Maybe that's why Mozilla made Rust and Google made Go.

Thank you. It is OK, as I enjoyed doing it (though I don't think I will be doing that again anytime soon lol), but knowing that I was helping everyone who uses Winapp2, really helped with morale.

Guess again. Vivaldi already dropped XP/Vista support. The only other browser that I know of that works on XP/Vista (and also 2000 if it's any consolation) is Midori. It is still in early development and I don't know if they have any plans to drop support for those old systems, but the current versions runs on them. Well, Waterfox also managed to get XP/Vista working, while keeping updates with Firefox releases, but only 64-bit versions and some features have been disabled.