I did replace the image, you just need to hit F5 or CTRL + R. I also see the typo, seems like everyone missed it, how evasive. I'll fix it and release an update soon. As for the text file, I'll work on that too as I want it to display the base score. Don't worry about the updater.
As I decided to release the updater version had to be corrected, this way it wouldn't show an incorrect update. If you check Xiret later a newer version will be available to correct the typo and change the way scores are exported via text.
Sorry, can't find any more bugs. For me to find some more I'll have to test Xiret on another machine, which I currently don't have. So until then- I'd say it's perfect
I would say the only thing now is get a .lng-file ready and tell F-Secure to pi$$ off with the warnings.
Xiret v1.3.3 has a clean VT, including F-Secure. Just add an exception. F-Secure's heuristics engine is probably acting up as I use methods similar to malware to protect and obfuscate my work. And yes, the core is ready for language files.
I have a few small changes in mind for Xiret. First of all I plan to re-develop the memory management system, although the application has a small footprint, the system can cause Xiret to work twice as hard. Since I noticed this potential bottleneck I've redesigned how my software deals with keeping unused resources down where it can. Second, I'm changing how text files are structured, again. This time they will include a notice of how the base core was determined. Third, language files are a go. I'm just typing up all the strings I need translated again since the application has evolved quite a bit. If you'd like to get involved with translations please send me a message. Also, If anyone would like to see a feature please mention it here. For now I'm taking a few days off. P.S. If someone could make an instructional video on how to use Xiret, I'd appreciate it. Thanks will be given in the about section including a link of your choice.
I checked Xiret 1.3.3 (1.3.1 was flagged by Avast!) against a failing system (Celeron, Win7 32bit, 1GiB RAM). Unfortunately, it doesn't work at all. No WinSAT process ever appears. Checked earlier versions of Xiret (down to 1.0.2). All failed. Seems that system cannot run any Xiret version to success. As if it cannot ramp up enough resources to launch WinSAT successfully. Yet, running WinSAT.exe formal -v works every time. Would it be possible to do a build with extensive logging (calls, return codes, possible .NET errors etc.)?
I have an idea, I'll build a specific version for you and send it tomorrow, I know what it is. And yes Xiret 1.3.1 came and went in a flash, even I don't have a version, could you send it to me please?
Version 1.3.6 (preliminary) is nearly ready to go, WinSAT will now execute via the preferences Windows gives to it rather than being controlled via the application itself. I've also made some enhancements and fixed a potential bottleneck. Right now I'm working on some minor UI additions. Here is the preliminary changelog: 1. Core code enhancements 2. Changes applied to the memory manage system (may be removed) 3. WinSAT now chooses the best execution method automatically via Windows Regards, QB.
Hey guys, The update is postponed as I've completely switched the way XML files are read, now I'm testing. Here is the preliminary changelog (not final): 1. Changed the way system scores are read 2. Fixed incorrect path formatting 3. Memory management system removed 4. WinSAT now chooses the best execution method automatically 5. Application multiple instance messagebox removed 6. Messagebox changes to follow the UI 7. Core enhancements
The memory management system is not only unnecessary for Xiret but also caused a slight bottleneck and degraded performance. Now I've removed it, analysis shows a performance increase with the addition of using up to an extra 30MB ram, which doesn't really matter. As for the multiple instance messagebox, it was removed as it doesn't follow the UI, Xiret is now brought to the front if you try to execute a second instance. I also encountered an issue reading scores on my friends computer so I rewrote the XML parser with a newer and cleaner method. This method does not cache data to read, instead it reads straight from the file. I'll send you a test version soon as it's ready.
Test version is ready to be sent out (EDIT: sent to testers on 02.08.2016), getting server ready now. We're at version 1.4.0. Sorry about the delay, I changed the XML parsing method twice. Preliminary changelog: (May change before release) 1. New XML parsing method added 2. Fixed a bug in path formatting 3. Memory management system removed 4. Added an auto repair option for corrupted scores 5. WinSAT now chooses the best execution method automatically 6. Application multiple instance messagebox removed 7. Messagebox changes to follow the UI 8. Core enhancements 9. UI and Control enhancements EDIT 2: Virus total has one FP - AV vendor messaged (Avira)