Take Command v10 beta build 34 uploaded

[rconn]

I've uploaded the v10 public beta build 34 to the ftp beta area:

ftp://jpsoft.com/beta/tcmd.exe

This build has some help updates, a fix for an occasional FTP directory read error, and a fix for an offset problem with @LINES.

 

[dcantor]

I downloaded it, installed it, and tried to run TCC.EXE from a desktop icon that I constructed for the purpose.

I got an error from AVG Free Edition as follows:

File name: C:\Program Files\JPSoft\TCMD10\TakeCmd.dll
Threat name: Virus found Win32/Heur
Detected on open.


So I downloaded another copy, removed the original installation, and reinstalled, and got the same result.

However, scanning the installation file TCMD.EXE with AVG yields no error.

Needless to say (though I'm saying it anyway) is that this didn't happen with builds 30, 31, nor 32.

 

[rconn]

I downloaded it, installed it, and tried to run TCC.EXE from a desktop icon that I constructed for the purpose.

I got an error from AVG Free Edition as follows:

File name: C:\Program Files\JPSoft\TCMD10\TakeCmd.dll
Threat name: Virus found Win32/Heur
Detected on open.


So I downloaded another copy, removed the original installation, and reinstalled, and got the same result.

However, scanning the installation file TCMD.EXE with AVG yields no error.

Needless to say (though I'm saying it anyway) is that this didn't happen with builds 30, 31, nor 32.

It's a false report (we've had occasional problems with AVG previously).

You might want to notify the AVG developers of the problem.

 

[Glennbo51]

It's a false report (we've had occasional problems with AVG previously).

You might want to notify the AVG developers of the problem.

Why does it always have to be the other guy. I know it is a false positive, but, should you as a developer ensure that it doesn't exhibit characteristics that and popular antivirus program might interpet as a virus?

 

[vefatica]

Why does it always have to be the other guy. I know it is a false positive, but, should you as a developer ensure that it doesn't exhibit characteristics that and popular antivirus program might interpet as a virus?

On the contrary (!) this should **not** be the developer's concern. It couldn't be more clear. AVG does not work correctly.

 

[rconn]

Why does it always have to be the other guy. I know it is a false positive, but, should you as a developer ensure that it doesn't exhibit characteristics that and popular antivirus program might interpet as a virus?

Because I have no way to know what they might interpret as a virus -- the antivirus developers keep their algorithms secret. In this case, it isn't even a real virus signature, just something that their code (and only their code; the other antivirus apps have no problem) mistakenly identifies as "virus-like".

 

[rconn]

Why does it always have to be the other guy. I know it is a false positive, but, should you as a developer ensure that it doesn't exhibit characteristics that and popular antivirus program might interpet as a virus?

An additional note: I tried to contact AVG to tell them about their problem, but I was told that they only provide technical support to paid customers. I'm disinclined to pay them in order to tell them that their product doesn't work ...

 

[Steve Fabian]

dcantor wrote:
| I downloaded it, installed it, and tried to run TCC.EXE from a
| desktop icon that I constructed for the purpose.
|
| I got an error from AVG Free Edition as follows:
|
| File name: C:\Program Files\JPSoft\TCMD10\TakeCmd.dll
| Threat name: Virus found Win32/Heur
| Detected on open.
|
|
| So I downloaded another copy, removed the original installation, and
| reinstalled, and got the same result.
|
| However, scanning the installation file TCMD.EXE with AVG yields no
| error.
|
| Needless to say (though I'm saying it anyway) is that this didn't
| happen with builds 30, 31, nor 32.

I had the same result from AVG free: TakeCmd.dll is claimed to contain a
threat, as had an earlier build as well. I had used AVG's help to find out
how to put my whole C:\JPSOFT directory tree "off-limit" for "resident
shield". No more messages. I'll see what the overnight virus scan will do.
--
Steve

 

[Jay Sage]

I, too, get a message -- in my case from the pro version of AVG -- that
tcmd.dll contains a virus. It's probably a false alarm, but I'm not
going to try running it until there is confirmation that it's OK.

-- Jay

 

[vefatica]

On Thu, 15 Jan 2009 21:52:24 -0600, dcantor <> wrote:

>I got an error from AVG Free Edition as follows:
>
>File name: C:\Program Files\JPSoft\TCMD10\TakeCmd.dll
>Threat name: Virus found Win32/Heur
>Detected on open.

Having used JPSoft products for over 15 years, I'm comfortable saying that Rex
is on the level. Googling for [Win32/Heur AVG "false positive"] turns up quite
a few hits. I didn't read carefully but I saw a couple of tips ... turn off
heuristic scanning, for one ... get a real AV, for another.

I'm not being opinionated. I don't use AV at all and I know nothing of AVG or
any other AV system. I hope no one thinks the developer bears the
responsibility to make sure his software doesn't set off alarms.

 

[Glennbo51]

Why does it have to be the other guy? This is a new release of your
software. Why don't you investigate what is causing it to exhibit behavior
that AVG interprets as a Virus? I am sure it is a false positive but does
it not behoove us to create software that does not exhibit these behaviors?

--Glenn Bowes

----- Original Message -----
From: "rconn" <>
To: <glennbo51@gmail.com>
Sent: Friday, January 16, 2009 04:50
Subject: RE: [Support-t-803] Re: Take Command v10 beta build 34 uploaded


---Quote (Originally by dcantor)---
I downloaded it, installed it, and tried to run TCC.EXE from a desktop icon
that I constructed for the purpose.

I got an error from AVG Free Edition as follows:

File name: C:\Program Files\JPSoft\TCMD10\TakeCmd.dll
Threat name: Virus found Win32/Heur
Detected on open.


So I downloaded another copy, removed the original installation, and
reinstalled, and got the same result.

However, scanning the installation file TCMD.EXE with AVG yields no error.

Needless to say (though I'm saying it anyway) is that this didn't happen
with builds 30, 31, nor 32.
---End Quote---

It's a false report (we've had occasional problems with AVG previously).

You might want to notify the AVG developers of the problem.

 

[vefatica]

On Fri, 16 Jan 2009 10:16:48 -0600, GlennBo51 <> wrote:

>Why does it always have to be the other guy. I know it is a false positive, but, should you as a developer ensure that it doesn't exhibit characteristics that and popular antivirus program might interpet as a virus?

On the contrary, this should definitely **not** be the responsibility of the
developer. That would prevent the developer from using the very best, small,
fast code just because it resembled code in some virus, or prevent him from
including a range of features in his product because that collection of
features, all in one place, heuristically resembles a virus.

If someone claims "my software detects viruses", then it's his obligation to see
that his program works well.

 

[dim]

On 2009-01-16 17:15, GlennBo51 wrote:

> Why does it always have to be the other guy. I know it is a false positive, but, should you as a developer ensure that it doesn't exhibit characteristics that and popular antivirus program might interpet as a virus?

Come on, it is well known that antivirus vendors screw up now and again.
AVG is one of the worse ones, they even managed to quarantine some
essential Windows system files, rendering numerous systems unbootable.

That said, AVG will probably have triggered on the executable obfuscator
that is being used for takecmd.dll. This used to be ASPack, but it
looks like Rex is using something else now.

 

[Jim Cook]

> It's a false report (we've had occasional problems with AVG previously).
> You might want to notify the AVG developers of the problem.
> ---End Quote---
> Why does it always have to be the other guy. I know it is a false positive, but, should you as a

I think developers have the responsibility to make their software as
bug free as possible. I do not think developers have any
responsibility to ensure no other buggy software will cause trouble.

If the AVG developers have buggy software, that's their problem alone.

The argument, taken to the extreme, is that Rex should predict all
possible bugs that may exhibit, now or in the future, when his
software is scanned by all possible broken anti-virus software. My
position is that AVG's stated goal is to trigger on viruses but not
clean programs and they are responsible for errors in their own code.

--
Jim Cook
2009 Saturdays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
Next year they're Sunday.

 

[Steve Fabian]

GlennBo51 wrote:
| ---Quote (Originally by rconn)---
| It's a false report (we've had occasional problems with AVG
| previously).
|
| You might want to notify the AVG developers of the problem.
| ---End Quote---
|
| Why does it always have to be the other guy. I know it is a false
| positive, but, should you as a developer ensure that it doesn't
| exhibit characteristics that and popular antivirus program might
| interpet as a virus?

I would agree with Glenn if this were a released version. However, for test
builds that may come several times a day it would require an inordinate
amount of work, resulting in longer delays to fix problems. I am not
familiar with other AV products, but AVG allows you to exclude files and
directories from scanning. I did that for the whole JPsoft work and download
trees, though this is excessive, I could have just excluded the V10 work and
download trees.

 

[dim]

On 2009-01-18 00:04, Jay Sage wrote:

> I, too, get a message -- in my case from the pro version of AVG -- that
> tcmd.dll contains a virus. It's probably a false alarm, but I'm not
> going to try running it until there is confirmation that it's OK.

The SHA256 hash of your takecmd.dll (version 10.0.34) should be:

DD66CEE0951A1258D97DC1FDB05B994DED572733E674F9CD0CA0AA6620E0A18D

You can verify this by running %@SHA256[takecmd.dll] from your known
good version of Take Command.

If the hash matches, you have the correct file, and you can ignore the
virus warning. Better yet, if you have the Pro version of AVG, report
it to them as a false positive! :)

 

[dcantor]

The problem didn't recur with build 35, so I'm happy. If it does recur in a later build, I'll raise it again, and report it to AVG.

 

[rconn]

dcantor wrote:

> The problem didn't recur with build 35, so I'm happy. If it does recur in a later build, I'll raise it again, and report it to AVG.

Since it's happened in at least two builds thus far, I'm certain it will
happen again until AVG fixes their app.

Rex Conn
JP Software

 

[dcantor]

dcantor wrote:



Since it's happened in at least two builds thus far, I'm certain it will
happen again until AVG fixes their app.

Rex Conn
JP Software

You're probably right, Rex. May I have your permission to submit the file to the AVG people the next time it happens?

 

[rconn]

dcantor wrote:

> ---Quote (Originally by rconn)---
> dcantor wrote:
>
>
>
> Since it's happened in at least two builds thus far, I'm certain it will
> happen again until AVG fixes their app.
>
> Rex Conn
> JP Software
> ---End Quote---
>
>
> You're probably right, Rex. May I have your permission to submit the file to the AVG people the next time it happens?

Yes.

Rex Conn
JP Software

 

[dcantor]

Excellent. Will do. Maybe we'll get lucky and there'll be no need.

 

[Jay Sage]

Re: AVG False Virus Report

It seems that AVG fixed the problem very quickly, and I no longer have
the problem.

-- Jay

P.S. Like many others, I'm having lots of problems with the forum. I
never saw my own message and know that it went out only because there
have been responses.

 

[Steve Fabian]

Re: AVG False Virus Report

Jay Sage wrote:
| It seems that AVG fixed the problem very quickly, and I no longer have
| the problem.
|
| -- Jay
|
| P.S. Like many others, I'm having lots of problems with the forum. I
| never saw my own message and know that it went out only because there
| have been responses.

I seemed to be cut off most of the time. I did NOT receive any message you
posted in the last few weeks.
--
Steve

 

[rconn]

Re: AVG False Virus Report

Jay Sage wrote:

> It seems that AVG fixed the problem very quickly, and I no longer have
> the problem.

The AVG problem only shows up every two or three builds. You'll
probably see it again.

Rex Conn
JP Software