I'm working on final adjustments to ready for a release. If anyone has encountered any issues, now is the time to report them. Thank you. A time frame is not set, however it will be soon™. Some changes so far include: - Windows 11 is now reported correctly when the build number >= 22000 - Some menu items under "Options" are now disabled when a system is not rated
Seems to run good so far (Win7). Missing that table flip ASCII in the log. Only thing I can't find anymore are the acknowledgements, I mention it just in case it was forgotten. _____ Bonus picture: "The gang":
Thanks Carlos, the table flip is incoming. I did forget about acknowledgements, it will be there for release. The gang pic is cool, as you can see I'm not a fan of whitespace.
It didn't complete Log attached if it can shed some light on the problem. It could just be my pc being awkward, although it has run ok before
It did complete, you received an exit code of 0. The message that winsat unexpectidly quit is probably an issue in my watchdog code. I'll look into the issue of why it gave an error after the watchdog has exited as it shouldn't happen. In the meantime, could you post your log from %SystemDrive%\Windows\Performance\WinSAT\winsat.log? If you are having an issue, it may shed some light.
Okay, I found an oversight in the code. However, analyzing your log and the code, it seems your winsat instance may not have exited in a timely fashion (5000ms). It did write an exit code of 0 to the log, which is good and means the test completed, however winsat needs to exit before flushing old config data. So my guess, your PC may possibly be playing up somehow. My suggestion is you use "Options > Reset WinSAT" in the application, backing up your old score files if necessary. I also appreciate you coming here for this, it will solve another problem in the BETA.
Your welcome, i know how long it can be to weed out glitches, some are easy to spot and others can take ages to fix and the grey hair grows faster! Attached as requested the log from '\Windows\Performance\WinSAT' folder. Had to add .txt to be able to attach the file. As for my PC/OS playing silly beggars that is quite possible as i just swapped motherboards (same chipset) to a ATX version as the previous mATX was a bit tight on space for the M2 drive being too near the Gfx card and overheating the drive. Will try the reset Winsat option and re-try. Thanks for getting back to me.
Reset Winsat and re-run.. Code: > Total Run Time 00:01:49.97 Entering function D3DCommon::DX9Shutdown > Composition restarted Shutting down Watchdog... Watchdog shutdown successful Waiting for WinSAT to exit... Validity: VALID Exit Code: 0 Message: The assesssment completed successfully. No errors this time. An extra 's' in assesssment , just noticed. The app looks awesome - wish i could design a GUI as sweet..
Excellent, that's good news. Thanks for pointing that out, I've fixed the typo, and the bug from your log will be patched soon by adding the missing conditions based on whether winsat has exited in 5000ms. It's nice to know the UI is pleasing
Now that Mac EFI Toolkit is in a good place, I've started cleaning WinEI up, and re-designing the UI. I expect it won't take too long, possibly January we'll be good for a release. @Carlos Detweiller The table flip will be added. @mxman2k The bug you encountered has been fixed, spelling mistake fixed. I'm considering re-adding metrics, not 100% decided yet.