HWInfo Pro Auto Log

[wutishwinfo]

Hello,
I recently got HWInfo Pro to use command line auto-logging feature.
I went through following threads - Supported Command-line parameters in HWiNFO64 Pro, Auto Logging to a specific Drive and CSV,
I have the following questions. Really appreciate if you can help me with it.

1. "C:\Program Files\HWiNFO64\HWiNFO64.exe" -l"S:\HWInfo Logs\" When I use this command. A log file is generated in S:\ however the timestamp used makes no sense since it generates a file of name "HWiNFO_LOG_201686765.CSV". Note: Sensor settings says Date/Time Format: Default. But I can't convert this timestamp to match the current date.
2. hostname or {comp_name} doesnt work with -l. Is it possible to create a file name as "hostname_datetime.CSV"? If yes, please guide how can we do it?
3. I want to know the command to be used in command prompt to stop/terminate auto-logging

Thank you so much.

 

[Martin]

The "Date/Time Format" in sensor settings refers to format inside the CSV log file (the date/time column), not the file name.
The time-stamp used in log file name is just to make the name unique and it's using the "tick count" which is the number of milliseconds since the computer started.

{comp_name} currently works for report files only, not the sensor log file name. The next Beta build will support it for sensor log too.

Use "taskkill.exe /im hwinfo64.exe" to gracefully terminate HWiNFO64.

 

[wutishwinfo]

"C:\Program Files\HWiNFO64\HWiNFO64.exe" -l"C:\Users\HWInfo Logs\" - I can generate log file and launch HWiNFO64 application by using this command in the command prompt of the product I am testing.
But when I use a powershell script from host computer that controls the server, powershell script is not able to generate log file on the same server.
Is the syntax different for using in Powershell script? Very confused because it works in command prompt but not in powershell script.
I have 4 products connected to host computer. I don't want to manually login and use command prompt on 4 units.
Can you please help or suggest an alternate method?

 

[Martin]

Syntax should be same. Try to create a batch file (bat or cmd) and execute that one from PS.