ROCKNROLL

I wonder if any Windows malware can work on ReactOS? I don't see any AVs on that list and I am wondering what people would do if a certain piece of malware worked in ReactOS but no AVs can load on it. I assume it isn't a big issue now because of its low population use. I wonder if anyone has ever attempted it. By the way, since it seems like some people are interested in this, is it OK if I post when ReactOS updates are released here? I see other topics that do this with other software, so...

Updated with my own addition: https://github.com/MoscaDotTo/Winapp2/commit/4f976b760291e20ef718d836db54a5e483d90c0a

Corrected them: https://github.com/MoscaDotTo/Winapp2/commit/5c39e23c891371091d2b2340808fef2264b2e310 https://github.com/MoscaDotTo/Winapp2/commit/891f0075c97777e8deea9f1465fe31e448bfbe11 https://github.com/MoscaDotTo/Winapp2/commit/6b628404bce7569c3bbc0fbc5abe9f50f3ac4c4b Ill try harder not to make these mistakes in the future.

If you are going to use OpenOffice, be careful. There are a lot of unfixed security holes/vulnerabilities in it. Read here: https://forum.openoffice.org/en/forum/viewtopic.php?f=49&t=84952 Also, a lot of other posts around their forums with similar conclusions. Too bad though, OpenOffice was always more lightweight then LibreOffice. maybe when OpenOffice is officially EOL, LibreOffice can make a lightweight version, suitable for weak/older systems. Anyways, this topic is about ReactOS, so let's not get too off topic here.

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

I don't know what Robert is planning on doing to his website. I don't have control over it, so I can't do anything on my end. To get the most up-to-date copy, you should grab them off GitHub.

"I wasn't able to get it to actually do much, can't get onto the 'net, doesn't have much in the way of softwares." It is designed to be lightweight, so it won't have any unnecessary stuff like what you would see in Windows 8/10. I hope they also keep it lightweight as well, even when they try getting vista/7/8/10 compatibility going. Or if they do decide to copy some of it, that they offer them as separate add-ons rather then pre-installing them. "Also, some of the "alternate" office suites are getting very compatible with the microsoft office." I use LibreOffice since OpenOffice is dead and most of the developers have moved to LibreOffice. LibreOffice, as far as I am concerned, should have full compatibility with Microsoft Office and its extensions. "I want an OS that will just work, and won't leak my every mouse click to somebody." Well if you are on a Linux, make sure you have telemetry disable then, lol.

I usually don't recommend Linux system as a replacement to Windows because there is just too much command line/tech savy stuff you have to do to get it to run the way you want it to. Most Windows users are use to just having everything the way it is. Even Zorin OS is like that. Also, currently ReactOS only runs on Fat32 filesystems, because they used that to have something to write on while making this and it was the simplest approach. The next major update (0.5.0) is suppose to add NTFS and possibly ext 2. Anyways, it is alpha, so bugs and crashes are expected. Maybe try one of the daily builds and see if it solves the issue.

Runs fine for me. Maybe try one of the daily builds? Also, try it on a VM first.

Updated and reverted changes: https://github.com/MoscaDotTo/Winapp2/commit/8acb847e7067b3c768822bd4c53001272bbbefec Sorry about that everyone.

His previous name on GitHub was winapp2, he deleted his account so people wouldn't think he was winapp2 owner. I felt like he was a user here who got banned (tho I was thinking of a different user who got banned). Anyways, there is no revert button, so can you tell me which and where needs to be fixed? Also, you can't rely on just me know to know everything works. I posted the log here 2 days ago to make sure everyone was OK and I didn't include the ones that everyone disagreed with.

If so, maybe you want check of operating system called ReactOS. ReactOS is a operating system designed to look, feel, and act like Windows. It is design to be NT compatible. Currently, it is in alpha stage, so I recommend using it on a VM or a drive you don't use. Here it is if anyone wants to check it out: https://www.reactos.org/ Incase anyone is wondering why it has been in development since 1998, it technically hasn't. The original development team designed the first version to be a Windows 98 clone, but after a few development switches, the project was kind of rebooted and turned into more of a Windows XP/2003 focus now. Future versions will focus on Vista/7/etc. Also, no this isn't a Linux system, yes CCleaner runs just find on it (I haven't tried the other tools, but I assume they should as well), and also no there isn't anything illegal about this because they are not de-compiling NT. If anything, it is more of a guessing game. I have tried it myself and it is really nice, but remember it is still alpha stage. I plan on, myself, making a permenate switch to it once it comes out of alpha.

By the way, if anyone wanted to clean the windows.old files, you can do this in Windows built in cleaner. Just select your drive, click properties, click disk cleanup, click clean up system files, then check Windows Old I believe it's called.

Updated: https://github.com/MoscaDotTo/Winapp2/commit/5fd04a149f1e764d9ccf72677095515ccfe0aef5

What about the Windows System Volume Tracking.log*? I think it's safe, but is there anyway a wildcard could be used instead of making all those FileKeys?

A user posted this over at GitHub: https://github.com/MoscaDotTo/Winapp2/issues/42 What does everyone think? Some of them look a little too risky maybe?

Thanks for fixing these. Shane reported this on GitHub, but I wasn't aware of what was wrong with them. https://github.com/MoscaDotTo/Winapp2/commit/00a0098a7f98bacc46f28cbd4dec195771291b26 @dvdbane: Temp Files* and SyncBackFree* are from the removed entries section (just saying cause it took me awhile to find these, lol), but thanks I corrected them, too. https://github.com/MoscaDotTo/Winapp2/commit/efcfedc542d1b19e77f195efe4596588978ce43f

@Augeas: You might want to read some of those comments. That article looks like what someone thinks about Defragging and SSDs and not actual facts about it.

Don't mean to step in the way here, but Defraggler most likely ran a TRIM anyways, if it only took 2 minutes to do that, because traditional defrags usually take much longer as they move the whole drive, where as TRIM only shrinks (not moves) parts of the SSD (the most important parts). What kind of SSD do you have (Intel, Samsung, etc?). IF you have a Samsung, you should download Samsungs tool called Samsung Magician and run some of the performance optimizations for it. You can also read the amount of write data on your system with this tool, as well. Also, you should into your bios and enable ACHI mode for your controller, as this will help with performance as well.

Well actually, you should TRIM your SSD, as it can help expand it's lifespan and everything. It also does give it a minor performance boost. I have been using a SSD for over 2 years now, and I run a trimmer at least once for my SSD. Consider reading up on what TRIM actually does before running it so you understand what it can do for you. But NEVER defrag a SSD as it does nothing for a SSD and can only cause harmful large amounts of write data on your SSD.

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

Unfortunately, I have already tried converting it to ANSI, as well as some other formats, and they all still reproduce the same issue. The files seem to be OK when viewing them in Wordpad or Notepad++, so I just recommend using one of those. I think this issue is caused because everyone is using a different editor to edit Winapp2 entries that notepad can't recognize the format anymore, so it either produces a giant wall fo text, or it will bundle certain parts with no spaces between them.

[IObit Advanced SystemCare V8 Logs*] and [Foxit Reader 8.0*] were not in there already, so I added them. https://github.com/MoscaDotTo/Winapp2/commit/49b1775a1a4d86e1594315e4c1172de36175a81c

Haha, good point. Oh well, just a idea I had.

Good points. However, I think speeding up Trim.bat in anyway is important since you have to execute it every time you update Winapp2, unless you plan on manually merging each entry.