Thanks. Is this the only dependency or are there other perhaps too?v7.73-5675 required Windows 10 dependices dcomp.dll and can't start on Win7 SP1 x64 then this DLL avalibaly only for Windows 10:
I am still seeing some strange behavior.
Test 1 - Enabled Auto Start in HWINFO main settings. Saw HWiNFO64Launcher.exe appear in the HWINFO v7.73-5375 directory. Double-clicked on HWiNFO64Launcher.exe, I saw what I think is a command line window quickly open and close, then a few seconds later HWINFO started.
Test 2 - Changed the target to HWiNFO64Launcher.exe in the old task that I made. The task did run, and I again saw the brief command line window open and close, but it closed much faster, and HWINFO did not start.
Test 3 - Ended and Disabled my old task. Ran the new task that HWINFO created when I enabled Auto Start in HWINFO main settings. I again saw what I think is a command line window quickly open and close, then a few seconds later HWINFO started (same as Test 1).
So for some reason, the task HWINFO created runs HWiNFO64Launcher.exe and HWINFO starts, but the task I created which also runs HWiNFO64Launcher.exe runs, but the launcher window closes very quickly and HWINFO does not start. I think the noticeably faster closing of the command line window is indicating that the launcher did not work. There is no error for the task because the task did run. I think something is stopping the launcher. All of the settings in the 2 tasks are identical. The only difference is the task created by HWINFO says the author is HWiNFO. The task I made says the author is Administrator. Both tasks were configured for Windows Vista, Windows Server 2008 (don't know why). I changed them both to Windows 10 but it did not make any difference.
I will just use the task that HWINFO created, but I cannot figure out why the launcher does not work when it is started from my task, which is identical to the task HWINFO created. Could this be a permissions issues, or a dependency?
I'm not positive if it's an issue with InfoPanel or HWiNFO but they no longer work together for me. I get a SHM error despite it being checked/shared. Old version still working fine.
Yes. Same folder, same target, same task settings. Here is a snip showing the directory with the HWINFO64.exe file and the HWinfo64Launcher.exe file. Both tasks (the one created by HWINFO and the old task file that I have used to start HWINFO for years) start HWinfo64Launcher.exe in this folder. The only differences I see are 1 - the Author of the tasks are different, and 2 - the amount of time I see the Command Line window is much shorter when started with my task than when started with the HWINFO created task. When I run the HWINFO created task, I see the command line window on the screen for almost 1 second, and then HWINFO starts a few seconds later. When I run my task, I see the command line window for a much shorter time, and HWINFO does not run.Was HWiNFO64Launcher.exe also present in the same folder as HWiNFO64.exe ? HWiNFO now automatically creates the file when it creates the new (or modifies the old) task.
Yes. Same folder, same target, same task settings. Here is a snip showing the directory with the HWINFO64.exe file and the HWinfo64Launcher.exe file. Both tasks (the one created by HWINFO and the old task file that I have used to start HWINFO for years) start HWinfo64Launcher.exe in this folder. The only differences I see are 1 - the Author of the tasks are different, and 2 - the amount of time I see the Command Line window is much shorter when started with my task than when started with the HWINFO created task. When I run the HWINFO created task, I see the command line window on the screen for almost 1 second, and then HWINFO starts a few seconds later. When I run my task, I see the command line window for a much shorter time, and HWINFO does not run.
Edit to add - I just tested this on my other rig which is set up the same way (dedicated Program drive where current and past versions of HWINFO are located, same task that I made long ago to start the latest version of HWINFO). I enabled Auto Start in HWINFO settings, the HWinfo64Launcher.exe file appeared in the HWINFO v7.73-5375 directory on the Program drive. I changed the target in my task to the launcher file. Task runs, command line window very briefly appears, HWINFO does not start. I then ran the HWINFO-created task (also with the launcher as the target file). Task runs, command line window appears for a longer time (~1-second), HWINFO starts.
View attachment 10811
If you mean a start delay on the Trigger, I did not catch that when I compared the tasks (oops). The HWINFO-created task has a Delay task for 5 seconds. My task did not have that set. Also, the HWINFO task has "Run with highest privileges" checked and my task did not (oops again). I added the Delay task for 5 seconds and checked "Run with highest privileges" in my task but it did not make any difference on both computers.Is "Start in (optional)" set same for both tasks?
Thanks Martin. I really appreciate it.Support of Aquacomputer Vision will be added in the next (Beta) build.
Hi Sir,
For the OSD, I wish you can extend this functionality to portable version, and not necessarily to be installed to Program Files. I'd imagine a lot of users would appreciate this. I'll definitely buy the license for fully licensed app