When I use any ASCOM device with trace option enable with SharpCap version 3.3 I get an error from ASCOM saying that access to the file ..\Administrator\Documents\ASCOM\log 2020-12-29\ASCOM.DriverAccess.1843.198220.txt is Denied.
In the same PC SharpCap version 3.2 works perfectly , When I disable my Avast (Free edition) it works. Other software that use the same ASCOM drivers (MaximDL for instance) also works. I don't understand why is only with version 3.3 that I have ASCOM problems with Avast writing the ASCOM driver logs.
My windows version is: Microsoft Windows [Version 6.1.7601]
I have the trace option enabled in the drivers because I'm developing an ASCOM application, by disabling the trace option in the driver the problem, obviously. disappear. Any idea about why this only happen with 3.3?
Thanks
SharpCap 3.3 + Avast AV prevent ASCOM device to work
Forum rules
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
Please also read about Troubleshooting USB Issues before posting.
*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***
Please include the following details in any bug report:
* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
Please also read about Troubleshooting USB Issues before posting.
*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***
Please include the following details in any bug report:
* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
-
admin
- Site Admin
- Posts: 13344
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: SharpCap 3.3 + Avast AV prevent ASCOM device to work
Hi,
I think the difference is that the I have now moved to a new code signing certificate for SharpCap 3.3 (the old one expired). Unless you pay through the nose for these, they take time to build up 'trust' with the various AV companies, which means that AV software will be more annoying than usual
I expect that there is a way to tell Avast to not apply its rules to SharpCap, but I'm not sure exactly how.
cheers,
Robin
PS. I have to admit that Avast seems to be the biggest cause of AV related problems by a long way - it just seems to be very agressive with the way it works.
I think the difference is that the I have now moved to a new code signing certificate for SharpCap 3.3 (the old one expired). Unless you pay through the nose for these, they take time to build up 'trust' with the various AV companies, which means that AV software will be more annoying than usual
I expect that there is a way to tell Avast to not apply its rules to SharpCap, but I'm not sure exactly how.
cheers,
Robin
PS. I have to admit that Avast seems to be the biggest cause of AV related problems by a long way - it just seems to be very agressive with the way it works.
Re: SharpCap 3.3 + Avast AV prevent ASCOM device to work
Good point! Thanks.turfpit wrote: ↑Wed Dec 30, 2020 7:46 pm Add an exception in Avast https://support.avast.com/en-gb/article ... xclusions/
Dave
Re: SharpCap 3.3 + Avast AV prevent ASCOM device to work
Given that the log files are created in folders containing the date, you may have to exclude the ASCOM folder. This might need some experimentation to get right. Test during the day rather than on a clear night!ASCOM saying that access to the file ..\Administrator\Documents\ASCOM\log 2020-12-29\ASCOM.DriverAccess.1843.198220.txt is Denied
Dave