I'm getting a crash on startup with v2.1.1 that I am not getting with v2.1. I sent you the crash debug details via a Deviant Note (the email here) so as to not clutter up this thread. Please let me know if you need more details.
I mistakenly used a v2.1 settings file with program v2.2.1. I deleted it and let v2.2.1 create a fresh one. All is fine now.
The version number in my previous post should have said v2.2.1, not v2.1.1. Please see my latest Deviant Note to you with the gory details of my mistake.
I am curious as to whether you could figure out a way to include the most common bottleneck that I encounter - HDD percent utilization - as a third parameter.
I looked way back through the comments here and I have not seen this request. I did see your reason for not including battery status. I also understand you originally wrote this utility for your own needs.
FYI, my idea came up because of a review of the Moo0 system monitor on dottech.org and a commenter's praise of your utility there (dottech.org/142029/windows-rev…).
Actually, that would work out quite well for me. I've got 32GB of RAM (I'm not totally crazy, I have an occasional need for a 16GB RAM disk) so I don't ever come close to running out of that.
Regarding the display of HDD usage, could you implement it so that you monitor each drive individually and have your display indicate the percent utilization of the drive with the highest usage for that refresh? That would best indicate a bottleneck - e.g., if I have three HDDs with one at idle, a second at 10% and the third at 90%, the display should indicate 90% rather than 30% (total average).
Let me make sure I've addressed everything -
1) Disk activity vs. disk space usage?
Yes, I would like percent disk activity for the **most active** disk.
Assume the user can have several disk drives, internally sample all of them, and only graph the one with the highest activity for each refresh.
Note that I don't need to know **which** disk is causing the bottleneck, I only need to know that it is a disk as opposed to the CPU.
2) Any other features?
Nope, I like the elegant simplicity of the program.
3) Bar1, Bar2, and swap?
I'm not sure that disk temperature is useful or meaningful if the user has more than one disk drive.
Worded another way, if percent activity is constantly switching to show the most active disk, which disk's temperature would you show?
Suggestion: If you show a temperature, it might be more useful to know the average of the CPU cores' temperature.
Alternative: Like the disk drives, show the temperature of the **hottest** CPU core for each refresh.
Problem: How will you scale any temperature to show the length of the bar? Everything other measurement is in percentages.
5) Release time frame?
Looking through the comments, even years back, no one has been in a hurry to have you make changes they've requested.
Take as long as you need. We are all very grateful that you've released your program for us to enjoy with you.
I just downloaded version 2.2 and Disk Usage works great. I quickly tested by making various disks and pairs of disk busy and the graph corresponds exactly with other utilities I have that show total utilization numerically. I think you are right - two busy disks is more of a concern than just the busiest disk and is less confusing.
CPU temperature is a big headache to support on different motherboard designs. I've seen utilities that show no temperature at all if the system isn't supported and that looks bad. Unless you want it or someone requests it, I would just leave it out.
Oddly, the swap button doesn't seem to be working. It is a really good idea, but if it's a hassle to fix, just remove it.
RCDT <grin> v2.2 is so much more useful for me and does exactly what I need. It will replace two resource intensive and screen real estate wasting utilities that I was using. Thank you so very much for adding percent disk utilization!
One additional feature thought, not a request: Have you considered an option to hide the taskbar icon to make the program even more subtle? Needing to change settings is rare once it's configured. Running the executable could check to see if an instance of itself is already running and show the settings instead of starting a second instance.