Posts: 3.205
Threads: 68
Joined: Mar 2010
Reputation:
109
Location: Netherlands
12-12-2015, 12:49 AM
(This post was last modified: 12-12-2015, 12:50 AM by Ryudo.)
Again? First it was with padnull and now this lol.
Welp, report to avast again, it should get fixed with an update to the definitions.
AMD Ryzen 5 3600 @ 3.60~4.20 GHz | Corsair Vengeance LPX 16 GB (2x8GB) DDR4-3200
MSI GeForce GTX 1660 Super @ 6 GB | Kingston A400 480GB SSD | Windows 10 Pro x64 (b19043.1288)
Posts: 8.030
Threads: 278
Joined: Feb 2009
Reputation:
343
12-12-2015, 12:56 AM
(This post was last modified: 12-12-2015, 12:59 AM by vsub.)
I just find it strange...no change to the file(according to github)but there is some change(according to avast)
Edit:The file size is different
Posts: 21.719
Threads: 401
Joined: Sep 2013
Reputation:
475
Location: 私の夢の中
It's because of the change to VS2015 that the file is different. That's also what triggered padnull to be detected.
Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD
Posts: 8.030
Threads: 278
Joined: Feb 2009
Reputation:
343
Hmm,yes.
On exactly that rev(1416),CDVDnull have totally different imports and one of the files tells me that it need vc2015
Posts: 21.719
Threads: 401
Joined: Sep 2013
Reputation:
475
Location: 私の夢の中
Yeah 1416 was the first version we compiled with VS2015.
Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD