My previously used Xiret 2 RC was from 2020-01-21 and seems to be almost identical to the new one. To folks: The SHA256 given is for the EXE, not for the ZIP! It still seems to be longing out for auto update, maybe should be disabled once it's really final.
@Carlos Detweiller It pretty much is, just UI and stability improvements. Plus a few other changes like the donation dialog and removing the score editor code. I've corrected the checksums in my previous post. The updater will be removed fully soon, and the resources removed from the server, it all depends how the next few months project, but thanks to everyone here the application is pretty stable. But now I will move all my time to NVR and give Xiret some peace. EDIT: Oh, and an Easter egg, there's a few which I don't think have been found.
Purrrrrrrrr? Edit: Also, the @EFA11 reference and link is very nice. I hope the topic will be on that URL forever.
No bugs reported, getting ready for release. Expect server resources to be offline, and issues may occur in v2.0.2 for the next few hours. BETA and RC versions are offline. 1. Quick edit of of how the main form title bar UI is laid out. 2. Server resource updates 3. Check updater 4. v2.1.0 release 5. Source code upload All completed.
Some updates: - New settings system nearly completed and portability mode in settings has been removed. - Switchable form graphics added into the settings system and has been completed. - Support to allow a user to disable automatic update checks has been implemented and the setting resides in the new settings INI. - Support to allow Windows Server execution has been implemented and the setting resides in the new settings INI (this may end up being removed). - All images in Base64 have been moved back into the resources file, this only happened as VS2019 was giving me issues with too many images in the resx, which I have resolved. - Fixed the error reporter output text stating the digest was SHA512 instead of the correct SHA256. - More stuff that isn't noteworthy. Estimated release date of mid-april is on track.
Yes, the only change is settings are stored with Xiret just like Compatibility.ini. My apps are always portable until there is no choice but to deviate.
More changes finalized: Code: · Portability enhancements >> ‘Appdata/xiret.log’ is now stored at ‘AppPath/Data/Assessments.log’ >> ‘Appdata/imgurlinks.log’ is now stored ‘AppPath/Data/Imgur.log’ >> Previous files will be migrated automatically Appdata will not be used anymore, only the executable path. This way if the target machine has .NET4 it's entirely portable. Image attached.
More changes finalized: - @Carlos Detweiller - The application will no longer automatically phone home to check for an update on start-up. However, this can be re-enabled in the settings INI (Settings.ini > Overrides > AutoCheckUpdate="false/true") and in Settings itself. - Notification badge removed and replaced with a simple colour change of the 'Help' menu button text to grab the users attention. Anything that doesn't work to a complete standard has to come out (See attachment) - Fixed missing handles that stopped the 'Off/On' background changing colour when 'Show Hardware' switch is hovered. I'm on track for mid-April. A test version will run before release. If I need to push back I will. Again, if you like what I've done with Xiret please show support on GitHub by following and liking the project as I've more system tools coming. I've gained a bit of traffic and it's nice to see. https:// github . com /0x43616c/Xiret (Remove spaces. Had to be formatted like this so MDL doesn't hide it)
Because the application is designed to be non-dependant on settings.ini and compatibility.ini I have added "Create Compatibility.ini" and "Create Settings.ini" to the Options menu. I also may have to create some sort of device fingerprinting system to identify each PC it is running on (for the logging system). However this will NOT be saved or sent via the network. Remember this software is FOSS and never collects data, however anyone can see that for themselves by studying the code. The font installer is also getting a change at some point so a user can choose to install missing fonts, exit, or do it manually. I'm also looking at adding language support now I have the knowledge, this is a 'just looking' scenario right now. I will most certainly need help from the community, but I see on French and Spanish forums they like Xiret but it's English only. I guess the support will be extended as I don't want to leave this on a 'should have' note.
Report 21337.1000 (VM): Code: New Test Started on Friday, Mar 19 2021 12:45 AM (╯°□°）╯︵ ┻━┻ Xiret v2.1.0 Release (1JA12) SystemOS: Windows 10 Pro (Kernel: 10.0.21337.1000) Bitness: x64 Culture: en-US INI: Present Winsat EXE v10.0.21337.1000 Winsat API v10.0.21337.1000 Tests: DWM (DX9), Processor, Memory, Disk Mode: Verbose Validity Int: 1 Windows System Assessment Tool > Command Line '"winsat" formal -v' > Running the Formal Assessment > DWM running... turnning DWM off > Running: Feature Enumeration '' > Gathering System Information > Operating System : 10.0 Build-21337 > Run Time 00:00:00.00 > Running: WinSAT Direct3D Assessment '-aname DWM -time 10 -fbc 10 -disp off -normalw 1 -alphaw 2 -width 1280 -height 1024 -winwidth C(1144) -winheight C(915) -rendertotex 6 -rtdelta 3 -nolock' > Processor : AMD FX-8370 Eight-Core Processor > TSC Frequency : 0 > Assessing Desktop Graphics Performance Entering function SimpleDWM::SimpleDWMState::ProcessCommandLine > Number of Processors : 1 > Number of Cores : 1 Entering function D3DCommon::DX9Init Entering function D3DCommon::CreateQueries > Number of CPUs : 1 > Number of Cores per Processor : 1 Entering function D3DCommon::FreeQueries Entering function `anonymous-namespace'::OnCreateDeviceToTexture > Number of CPUs Per Core : 1 > Cores have logical CPUs : NO > L1 Cache and line Size : 16384 64 > L2 Cache and line Size : 2097152 64 > L3 Cache and line Size : 8388608 64 > Total physical mem available to the OS : 3.99 GB (4,294,496,256 bytes) > Adapter Description : Microsoft Basic Render Driver > Adapter Manufacturer : Oracle Corporation > Adapter Driver Provider : Oracle Corporation > Adapter Driver Version : 5.2.45.0 > Adapter Driver Date (yy/mm/dd) : 2020\7\31 > Has DX9 or better : Yes > Has Pixel shader 2.0 or better : Yes > Has LDDM Driver : Yes > Dedicated (local) video memory : 0MB > System memory dedicated as video memory : 0MB > System memory shared as video memory : 2047.78MB > Primary Monitor Size : 3840 X 2070 (7948800 total pixels) > WinSAT is Official : Yes Entering function `anonymous-namespace'::OnCreateDevice Entering function D3DCommon::CreateQueries Entering function `anonymous-namespace'::OnResetDeviceToTexture Entering function `anonymous-namespace'::OnResetDevice Entering function `anonymous-namespace'::OnLostDeviceToTexture Entering function `anonymous-namespace'::OnLostDevice Entering function D3DCommon::FreeQueries Entering function D3DCommon::CreateQueries Entering function `anonymous-namespace'::OnResetDeviceToTexture Entering function `anonymous-namespace'::OnResetDevice Entering function `anonymous-namespace'::OnLostDeviceToTexture Entering function `anonymous-namespace'::OnLostDevice Entering function D3DCommon::FreeQueries Entering function `anonymous-namespace'::OnDestroyDeviceToTexture Entering function `anonymous-namespace'::OnDestroyDevice Entering function D3DCommon::DX9Shutdown Entering function D3DCommon::ProcessLog > Run Time 00:00:14.44 > Running: WinSAT Direct3D Assessment '-aname Batch -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(10) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)' Entering function D3DCommon::StartKernelTracing > Assessing DirectX Batch Performance Entering function D3DCommon::ProcessLog > Run Time 00:00:00.30 > Running: WinSAT Direct3D Assessment '-aname Alpha -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(75) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)' Entering function D3DCommon::StartKernelTracing > Assessing DirectX Alpha blend Performance Entering function D3DCommon::ProcessLog > Run Time 00:00:00.25 > Running: WinSAT Direct3D Assessment '-aname Tex -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -texshader -totaltex 10 -texpobj C(4) -rendertotex 6 -rtdelta 3' Entering function D3DCommon::StartKernelTracing > Assessing DirectX Texture load Performance Entering function D3DCommon::ProcessLog > Run Time 00:00:00.30 > Running: WinSAT Direct3D Assessment '-aname ALU -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -alushader -totaltex 10 -texpobj C(1) -rendertotex 6 -rtdelta 3' Entering function D3DCommon::StartKernelTracing > Assessing DirectX ALU Performance Entering function D3DCommon::ProcessLog > Run Time 00:00:00.27 > Running: WinSAT Direct3D Assessment '-dx10 -aname Batch -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(10) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)' > Run Time 00:00:00.05 > Running: WinSAT Direct3D Assessment '-dx10 -aname Alpha -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(75) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)' > Run Time 00:00:00.00 > Running: WinSAT Direct3D Assessment '-dx10 -aname Tex -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -texshader -totaltex 10 -texpobj C(4) -rendertotex 6 -rtdelta 3' > Run Time 00:00:00.05 > Running: WinSAT Direct3D Assessment '-dx10 -aname ALU -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -alushader -totaltex 10 -texpobj C(1) -rendertotex 6 -rtdelta 3' > Run Time 00:00:00.03 > Running: WinSAT Direct3D Assessment '-dx10 -aname GeomF4 -time 7 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 150;200;241 -batchcnt C(50);C(200);C(300) -objs C(12);C(26);C(45) -noalpha -geomf4shader -texpobj C(0) -rendertotex 6 -rtdelta 3 -tierframes 60 -tiertime 1' > Run Time 00:00:00.03 > Running: WinSAT Direct3D Assessment '-dx10 -aname GeomV8 -time 7 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 75;100;120 -batchcnt C(25);C(100);C(150) -objs C(8);C(17);C(29) -noalpha -geomv8shader -texpobj C(0) -rendertotex 6 -rtdelta 3 -tierframes 60 -tiertime 1' > Run Time 00:00:00.02 > Running: WinSAT Direct3D Assessment '-dx10 -aname CBuffer -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 75 -batchcnt C(25) -objs C(8) -rendertotex 6 -rtdelta 3 -texpobj C(1) -cbuffershader -cbufa 2 -cbuff 5 -cbufp 6' > Run Time 00:00:00.00 > Gathering System Information > Run Time 00:00:00.00 Entering function D3DCommon::DX9Init Entering function D3DCommon::DX9Init Entering function D3DCommon::DX9Shutdown Entering function D3DCommon::DX9Shutdown > CPU LZW Compression 94.23 MB/s > CPU AES256 Encryption 404.51 MB/s > CPU Vista Compression 248.94 MB/s > CPU SHA1 Hash 335.63 MB/s > Uniproc CPU LZW Compression 94.39 MB/s > Uniproc CPU AES256 Encryption 409.09 MB/s > Uniproc CPU Vista Compression 249.92 MB/s > Uniproc CPU SHA1 Hash 334.74 MB/s > Memory Performance 7252.63 MB/s > Direct3D Batch Performance 42.00 F/s > Direct3D Alpha Blend Performance 42.00 F/s > Direct3D ALU Performance 42.00 F/s > Direct3D Texture Load Performance 42.00 F/s > Direct3D Batch Performance 42.00 F/s > Direct3D Alpha Blend Performance 42.00 F/s > Direct3D ALU Performance 42.00 F/s > Direct3D Texture Load Performance 42.00 F/s > Direct3D Geometry Performance 42.00 F/s > Direct3D Geometry Performance 42.00 F/s > Direct3D Constant Buffer Performance 42.00 F/s > Video Memory Throughput 497.43 MB/s > Dshow Video Encode Time 0.00000 s > Dshow Video Decode Time 0.00000 s > Media Foundation Decode Time 0.00000 s > Disk Sequential 64.0 Read 108.96 MB/s 6.7 > Disk Random 16.0 Read 3.31 MB/s 4.7 > Total Run Time 00:00:18.11 Entering function D3DCommon::DX9Shutdown > Composition restarted Stopping ProcessWatcher... ProcessWatcher stopped The assessment ran with no warnings or errors Exit Code W: 0 Exit Code X: 0 Validity Int: 1 Process finished (ヘ･_･)ヘ┳━┳ The wrong branch reported is because it is stored wrong in the Registry. QueryTool and MRP from @mxman2k have the same problem.
@Carlos Detweiller I've looked into this. The issue is MS keep f**king moving stuff they don't need to touch and there's no point chasing a fix; mine still says Branch: VB. As of now I'm unsure if it stays in a specific static location. They have created a new key in "HKLM\Software\Microsoft\Windows NT\CurrentVersion" called "DisplayVersion", I'll switch to that in the new version (Done: See image).
An update on other stuff: I found the Spartan Toolkit source code some time back. I ripped Secret Agent apart, and merged it with Spartan Toolkit and WinTK into my 'unmentioned until now' RRG Toolset to a standard of where I'd have wanted Spartan Toolkit to end up (See Image). RRG is turning into an extremely useful tool, however it was made for me only as a personal tool; then I changed my mind so it's being stabilised for public release. As for a timeframe for first release, this hasn't been set, yet... But I'm only one person with a busy life. With the RRG UI, I wanted to follow a somewhat simple 'folder tab' design, which is coming on well. Some info about RRG: Everything is loaded at runtime in the Splash screen and executed again if needed Beautiful UI with as low a footprint as possible for the system and user Easy to use with many tools from the years of WinTK, Spartan Toolkit and Secret Agent Fonts loaded into memory Portable (.NET Framework 4.5) High standard of code Full DPI support Asynchronous tasking so not to block long threads Exploring the possibility of powering system details with a driver Low profile underlying system designed for stability Automatically hides sensitive data with quick toggles to unhide There is no update regarding NVReform, it's very much on the way but on the back-burner for now until I finish the NVAPI system.
The update is on track and coming on well. RRG is also coming on well, more options added every day. When an Alpha is available I'll make a new forum post, however Alpha versions will be closed to specific people. Looking back through all the positive feedback regarding WinTK, even though it was written so badly, will make me glad to share RRG. It's like experiencing WinTK in 2021 with so much more stability and function. When Xiret goes to rest, RRG will take over whilst I develop the NVReform API further. All the best parts of Spartan Toolkit and WinTK will return with a completely fresh approach and completely rewritten tools into a minimalist UI designed for a max of two open forms; the main form and one tool to keep flow and low memory. Remember, I'm one person achieving quite the task, so please be patient. I'd like to personally thank @Alphawaves. When I joined here I wanted to be as good with .NET as you were and it was you who taught me to do better. Now I understand what it takes to make a good application and how much work is needed.