Why doesn’t Desktop Info (DTI) find the environment variable I set?
When a Windows process is started, it inherits a snapshot of the parent environment as it exists at that time. So, opening a command window and changing environment variables after DTI has started will not change the environment of the DTI process. To give DTI specific environment values, you would need to start a command process, set the environment and spawn DTI from that same command process.
Why doesn’t the Cpu Temperature work on my computer?
Hardware sensors are problematic. The problem is manufacturers don’t expose them to the operating system in a standard way. Windows provides standard WMI properties to be used by manufacturers but almost nobody implements them.
The only other approach is to laboriously study each manufacturer’s hardware sensor implementation and write specific code for each one. This is not a path I wish to follow, better to leave that to a dedicated team of experts. There are a number of tools available to read hardware sensor information such as CoreTemp, Open Hardware Monitor, HWMonitor, Speedfan, Real Temp, Hardware Sensors Monitor, OCCT. I have implemented the CORETEMP item and hopefully I’ll find another more complete tool that exposes an API.
Why does it show “<n/a>” for my WMI query?
The “<n/a>” is the English string for “not available”. It’s there in the sample ini file. You can change this to anything you like. The reason this string appears is because your WMI query either has a problem or it worked and there was no result set. That is to say nothing matches your request so there is nothing to display.
This can happen for other items as well. For example, PROCESSMEM where no processes match your criteria, CPUTEMP where the sensor information is not available in WMI.
BGR? Whoever heard of bgr? What’s wrong with regular rgb?
I agree. However, that’s how the Delphi compiler does colours. At the time I first started writing DTI (2005), it seemed pragmatic to go with that. It was probably not a wise choice but there’s no turning back now.
How Do I Make It Start When I Log In?
The simplest solution is to create a shortcut in your Startup folder. Right click on DesktopInfo.exe and select “Create shortcut”. Now copy this shortcut to one of the following directories:
On Windows 7 and later, the user path is:
On Windows 7 and later, the All Users path is:
On Windows XP, the user path is:
C:\Documents and Settings\<username>\Start Menu\Programs\Startup
On Windows XP, the All Users path is:
C:\Documents and Settings\All Users\Start Menu\Programs\Startup
The problem is some items won’t display properly unless you “Run as Admin”. In this case modify your Startup shortcut and check the Privilege Level option.
You can also add it to the registry Run key:
This doesn’t give you the Admin level though.
Another option is using Task Scheduler to run the application at log in. You also have the option to “Run with the highest privileges”.