too long to submit for analysis ??? NOD32 64bit @ win 7 64bit

what sort of nonsense is that? and what is too long, path name, file name, ... ?

 

Poor wording, it means the file is too large.

 

gotta be kidding! what is the limit then?

 

What is the size? If only few MB then it is more likely to be path name. If it is massive file (don't know what limit that is) upload it somewhere and just send them the link to it when submitting

 

13 MB

would be nice if some knowledgeable Eset mod could comment, whether it is a silly wording or what the limit actually reads.

the file is non-malicious for sure, but produced an error during in-depth scan and since Eset mentioned to be interested to learn about such files/archives I was trying to get it through via the submit feature.

 

I'm sure they do want to learn about it and are grateful for submission; as I said while you wait for some clarification, upload it somewhere and send them link to it via submit feature
see similar
https://www.wilderssecurity.com/showthread.php?t=275569

 

so, nobody knowledgeable around from Eset then?

 

Be patient

 

no, you misunderstood, I am not in hospital

 

No I hope you're not in a hospital.
But you need to be patient with Eset sometimes

patient, forbearance, patience, understand the word (patient) better now?

 

back from hospital, still no explanation from Eset?

 

Hehe good for you

No not a word yet

 

Cudni has already replied, I cannot add anything more. Follow these instructions to submit a file or report FP to ESET. If the file is too large to be sent by email, just enclose a link to the file.

 

neither Cudni nor you clarified the matter. Nor was email mentioned but the NOD reporting system - that email? Did not ask anywhere for any sort of instructions.

The question remaining:

What is the actual limit?
And 'too long' just funny wording?

Why is it so difficult to get a straight answer?

 

I assume the limit for submitting filles via ThreatSense.Net is 3 MB. As for the wording of the message, it's quite old and hence it slipped my attention. It will be amended in the next build.

 

not fixed in 4.2.58.3

 

message wording fixed in 4.2.64.12


yet still not indicating the user what the max. file size might be ...