Classic TPS is untouched. New driver: DRIVER('TopSpeedW'), .tpsw files, USTRING fields + UNICODE blobs, keys that work, and clean version rejects instead of silent mojibake. TopSpeedW files use the new 512 GB big file format — the classic 2 GB limit is now a guarded error, never a corrupted file, and SEND('BIGFILE=ON') upgrades an adopted classic file in place.
yeah quite a lot happening in this space. The new Clarion 12 (currently in beta) has a new TPS driver (TPSW) which supports USTRING, and allows TPS files to be (much larger).
I just tried downloading from here (I have ESET Security Ultimate) and it didn’t complain, so this is going to be an issue with your AV rather than the ZIP.
Another option is to clone or fork the repository rather than downloading it. This will allow you to pull the code directly to your computer without downloading a ZIP at all.
As Bruce said, he isn’t responsible for the ZIP; GitHub creates that automatically from the repository.
If your AV is actually detecting one of the files contained in the repository, rather than the ZIP itself, it may still complain when you clone it.
I only have Windows Security, and I can download it without problems using Git Desktop. However, I don’t think the .exe file should be in that repository if the source code that generates it already exists there.
I think there’s probably a practical reason the EXE is there.
This repository is the free version of Bruce’s DriverKit, and looking at the documentation, ObdPatch is supplied as a utility, with its source code also included. My guess is Bruce has included the compiled EXE deliberately so that someone using the free DriverKit doesn’t first have to open the project and compile the patch utility themselves.
Certainly, if this were purely a source repository then excluding generated binaries would make sense, but in this case the repository is intended as something developers can download and use directly.
Also, antivirus software doesn’t normally flag a file simply because it is an EXE. Executables may receive more scrutiny, particularly unsigned or uncommon ones, but if antivirus software treated every EXE as malicious we’d have a rather difficult time running Windows
The fact that GitHub Desktop cloned the same repository, including the EXE, without Windows Security complaining also suggests there’s something different about how the downloaded ZIP is being scanned, rather than Windows Security simply objecting to ObdPatch.exe being present.