Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is there a maintained fork of this? #449

Open
mightyiam opened this issue Jun 1, 2024 · 3 comments
Open

Is there a maintained fork of this? #449

mightyiam opened this issue Jun 1, 2024 · 3 comments

Comments

@mightyiam
Copy link

Does anyone know?

@thewriteway
Copy link

thewriteway commented Jun 29, 2024

Does anyone know?

I have a fork that I created just to include the latest internal build dependencies and LibreHardwareMonitor commit 1b11816 for the standalone version.

You can find it in here: https://github.com/ArcadeRenegade/SidebarDiagnostics/forks

I'm not planning support or any other changes at this stage. However its there if anyone needs it until ArcadeRenegage returns.

@thewriteway
Copy link

thewriteway commented Aug 30, 2024

Updated my fork to target "newer" .NET framework V4.8.1 and updated LibreHardwareMonitor commit to 437c4d3
Find it in the releases under tag 3.6.3b

@MNLierman
Copy link

@thewriteway I am looking for a fork or a fix that leaves LibreHardwareMonitor library in the application folder that it's in and doesn't download/write a new DLL to the temp folder every second. I wasn't aware that it was doing this, but on cheaper SSD's this amount of write and delete for absolutely no reason can seriously degrade an SSDs life. I've used this sidebar for 7 years and had no idea it was doing this, and I leave my computers on all the time.

Would love to see a fix for this, even keeping the DLL in memory is a significantly better option. Load the DLL, and then use the refresh option within the library. If that fails to work, the DLL can be removed from the embedding during compilation and instead included with, then loaded every second, if that's actually necessary. I assume it's extracting it and then deleting it, and I don't see a reason for that, I just don't.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants