starflakeprj wrote:planetearth wrote:vasyan wrote:planetearth wrote:I'm not trying to convince anyone; I'm just saying that deleting the 32-bit DLL doesn't affect the synth at all.
In archive two DLL are available PolyGAS_v2.0.rar intended for installation manually:
- PolyGAS32.dll - 32 bit DLL
- PolyGAS64.dll - 64 bit DLL
Use necessary to DLL in dependence with your requests (digit capacity of OS, DAW)
Unclaimed DLL can be deleted.
Right. That was my point to the user who said he was going to avoid the synth until the 32-bit version was "clean" from a virus it didn't have in the first place.
Since you don't need the 32-bit version, just delete it. Problem solved.
I'm pretty sure I have read somewhere in this forum that Layzer is running a 32-bit host though.
I, myself, is pretty confident to run a software which only 1 of 60 anti-malware engines marks as possible malware. I would be confident to run a software which 10 out of 60 engines mark as possible malware as well, because I know false positives are quite usual.
On the other hand, a part of me understands a person who are just trying to be safe. I know a few producers/musicians who wouldn't even connect their DAW computer to the internet, because they fear for any re-installations of the system in case of a malware or hacking attack. Because re-installing a system takes hours, a lot of hours, to get to the same state again. Unless you are not regularly taking 1:1 images of your system of course. But I guess most people are just backing up the important files (and sometimes not even those).
Yep, I agree with your points. There's absolutely nothing wrong with trying to keep your DAW safe from infection. No point in taking unnecessary risks.
Now that PolyGAS is "live" on KVR, more people will be trying it (and hopefully donating to the devloper!). And if some of them get a false-positive reading, they may want to know what to do. That's why I mentioned that simply deleting the 32-bit .DLL (if you don't need it) basically solves the problem.
For those using 32-bit DAWs, I personally would still side with the overwhelming majority of anti-virus scanner reports, and accept that the .DLL isn't infected. But that's just me, of course.