halcyon
February 9th, 2004, 10:11 AM
Ok, you may remember that I reported Desert Combat 0.5L as being improperly tagged with "Positive identication" by TDS 3.21.
Well, past weekend Desert Combat 0.7 was released.
Can you already guess what happens with it? :)
Yes, exact same false positive identification:
Alarm: Positive Identification
Name: (empty)
File: desert_combat_full-0.7.exe
You can download the 605 MBYTE DC 0.7 file from:
http://www.gamershell.com/news_BF1942BDesertCombatBv0.7.shtml
...and verify it for yourself.
Again, if I disable exec protection, disable tds, install DC 0.7, re-start TDS, re-start exec protection, re-scan the folder where I installed DC 0.7, then I get nothing. Not even a single warning.
Best regards,
Halcyon
Well, past weekend Desert Combat 0.7 was released.
Can you already guess what happens with it? :)
Yes, exact same false positive identification:
Alarm: Positive Identification
Name: (empty)
File: desert_combat_full-0.7.exe
You can download the 605 MBYTE DC 0.7 file from:
http://www.gamershell.com/news_BF1942BDesertCombatBv0.7.shtml
...and verify it for yourself.
Again, if I disable exec protection, disable tds, install DC 0.7, re-start TDS, re-start exec protection, re-scan the folder where I installed DC 0.7, then I get nothing. Not even a single warning.
Best regards,
Halcyon