Raspberry support for FireCapture v2.6 and ZWO cameras !
| Compatibility |  FC v2.7.15 (x64) |
 FC v2.7.15 (x64) |
 FC v2.7.15 (x64) |
FC v2.7.15 (aarch64) |
|
|---|---|---|---|---|---|
 Altair |
 |
 |
|
|
|
 ASCOM |
 |
|
|||
 Basler |
|
|
|||
 FLIR/FlyCap |
 |
|
|||
| FLIR/Spinnaker |
|
|
|||
 LUCID |
|
|
|||
 NexImage |
|
|
|||
 OGMA |
|
|
|
|
|
 PlayerOne |
|
|
|
|
|
 QHY |
|
|
|
|
|
 Skyris |
|
|
|||
 SVBony |
|
|
|
|
|
TIS |
|
|
|||
 Touptek/Omegon |
|
|
|
|
|
 ZWO ASI |
 |
|
|
|
|
Older Versions
Developing software is mostly fun, but it also takes up nearly all of my spare time. If you find FireCapture useful and would like to support me in continuing development you're welcome to donate a small amount of your choice.
: If you receive an error that the file is in use, you may need to boot your computer into Safe Mode to delete it [5†L11-L12].
Vsut64exe appears to be a specialized command-line tool for managing — the hardware identification information stored in a computer's BIOS. Based on available references, it is specifically designed for use with Intel-based BIOS systems , particularly in HP computers. It is likely part of a larger suite of diagnostic and configuration utilities used by HP for maintenance tasks.
Understanding vsut64.exe: A Guide for Developers and Power Users If you have been scouring your Task Manager and spotted vsut64.exe
The file name typically represents the 64-bit version of Intel's support tool, used for scanning and gathering detailed hardware and software information from a computer. It is often used by support engineers to diagnose issues related to processors, motherboards, or network adapters.
Before removing anything, it is wise to ensure your system is clean. Run a full scan with your installed antivirus or Windows Security (Microsoft Defender).
What prompted you to look into this file? Did you manually download an Intel support tool recently?
Legitimate Intel files are generally located in C:\Program Files\Intel\ or a subfolder therein.
Is it a critical Windows system file? A driver for a piece of hardware? Or something more sinister, like a cryptocurrency miner or a trojan?
: If you receive an error that the file is in use, you may need to boot your computer into Safe Mode to delete it [5†L11-L12].
Vsut64exe appears to be a specialized command-line tool for managing — the hardware identification information stored in a computer's BIOS. Based on available references, it is specifically designed for use with Intel-based BIOS systems , particularly in HP computers. It is likely part of a larger suite of diagnostic and configuration utilities used by HP for maintenance tasks.
Understanding vsut64.exe: A Guide for Developers and Power Users If you have been scouring your Task Manager and spotted vsut64.exe
The file name typically represents the 64-bit version of Intel's support tool, used for scanning and gathering detailed hardware and software information from a computer. It is often used by support engineers to diagnose issues related to processors, motherboards, or network adapters.
Before removing anything, it is wise to ensure your system is clean. Run a full scan with your installed antivirus or Windows Security (Microsoft Defender).
What prompted you to look into this file? Did you manually download an Intel support tool recently?
Legitimate Intel files are generally located in C:\Program Files\Intel\ or a subfolder therein.
Is it a critical Windows system file? A driver for a piece of hardware? Or something more sinister, like a cryptocurrency miner or a trojan?
It was back in 2008 when I got hold of a SONY newsletter announcing a new CCD sensor (ICX618) which promised fantastic sensitivity. Still working with an old webcam those days I instantly had the idea of replacing the webcam sensor with the new SONY sensor. It took weeks and dozens of emails to get the confidential spec of the new sensor. When I saw the sensitivity values it was clear: I had to have this sensor! The Basler Scout scA640 was the first machine vision camera on the market using this sensor and when I bought it the nightmare began: the included software was useless for planetary imaging and running the camera with the VRecord webcam tool was a complete PITA. Bugged by the inability to store even the basic camera settings I decided developing my own capture software.
What started as a solely private project soon turned into higher gear when fellow astronomers saw the software and insisted on getting it. I decided to make it public, included new camera interfaces and after years of continuous development FireCapture has evolved to one of the leading planetary capture tools. Developing the thing is only one part of the story: with a supportive community of users behind me I always had the feeling of someone 'looking over my shoulder' during the countless hours of programming. I can't mention all but just want to say:
Thank you guys !
