BBC BASIC for Windows
« Virus reported in my compiled program »

Welcome Guest. Please Login or Register.
Apr 5th, 2018, 10:13pm



ATTENTION MEMBERS: Conforums will be closing it doors and discontinuing its service on April 15, 2018.
Ad-Free has been deactivated. Outstanding Ad-Free credits will be reimbursed to respective payment methods.

If you require a dump of the post on your message board, please come to the support board and request it.


Thank you Conforums members.

BBC BASIC for Windows Resources
Online BBC BASIC for Windows documentation
BBC BASIC for Windows Beginners' Tutorial
BBC BASIC Home Page
BBC BASIC on Rosetta Code
BBC BASIC discussion group
BBC BASIC for Windows Programmers' Reference

« Previous Topic | Next Topic »
Pages: 1  Notify Send Topic Print
 thread  Author  Topic: Virus reported in my compiled program  (Read 762 times)
BigJoeKelley
New Member
Image


member is offline

Avatar




PM

Gender: Male
Posts: 2
xx Virus reported in my compiled program
« Thread started on: Sep 29th, 2011, 04:58am »

I am just an old TRRS-80 programmer trying this new stuff after 30 years persueing a different career. My first try at compiling a program and sending it to my wife's laptop went awry when McCaffee quarantined it as having a virus called Win32dll. Has anyone else come across this problem? shocked
User IP Logged

BigJoe
admin
Administrator
ImageImageImageImageImage


member is offline

Avatar




PM


Posts: 1145
xx Re: Virus reported in my compiled program
« Reply #1 on: Sep 29th, 2011, 09:21am »

on Sep 29th, 2011, 04:58am, BigJoeKelley wrote:
My first try at compiling a program and sending it to my wife's laptop went awry when McCaffee quarantined it as having a virus called Win32dll. Has anyone else come across this problem?

This is a much-discussed issue, which results from the widespread use of 'heuristic' techniques by Virus Scanners in an attempt to detect as-yet-undiscovered viruses. If you check out the detail of the McAfee report, you will almost certainly find that the 'virus' is described as a heuristic detection, which means that it isn't actually a known virus at all, but simply the result of what the scanner considers to be 'suspicious' behaviour.

Since it isn't really a virus, the simplest solution is to ignore it, and to add the program to McAfee's 'white list' of programs which it will accept without generating an alert. If you prefer not to do that, there are some other things you can try:

  • Make sure that you have enabled the 'encrypt and compress' option in the Compile dialogue.
  • Create a VERSIONINFO resource for the program using the Version Info add-in (Utilities menu).
  • Ideally, 'digitally sign' your program with a code-signing certificate (but that costs money if you haven't already got one).

Unfortunately these 'false alarms' are the price we pay for increased vigilance. You might want to consider changing to a different virus scanner; I use AVG here and have not been troubled by false alarms from compiled BB4W programs.

Richard.
User IP Logged

BigJoeKelley
New Member
Image


member is offline

Avatar




PM

Gender: Male
Posts: 2
xx Re: Virus reported in my compiled program
« Reply #2 on: Sep 30th, 2011, 05:02am »

Thanks Richard, cheesy
Adding the Version Info did the trick. I wonder if you would point me in the right direction to find out more about the error I am receiving from the Sockets Lib. 10035 seems to be connected to WSAEWOULDBLOCK which means nothing to me. I am just trying to set-up some communication between 2 computers using the Listen - Connect - Check Conection Processes
Thanks Again,
Joe huh
User IP Logged

BigJoe
admin
Administrator
ImageImageImageImageImage


member is offline

Avatar




PM


Posts: 1145
xx Re: Virus reported in my compiled program
« Reply #3 on: Sep 30th, 2011, 09:34am »

on Sep 30th, 2011, 05:02am, BigJoeKelley wrote:
I wonder if you would point me in the right direction to find out more about the error I am receiving from the Sockets Lib. 10035 seems to be connected to WSAEWOULDBLOCK which means nothing to me.

Normally your program won't see that error, because it is trapped in SOCKLIB and converted to something else. For example in both FN_readsocket and FN_writesocket you will find this code:

Code:
IF E%=10035 THEN = 0 

In other words if Windows returns the WSAEWOULDBLOCK error what you see is simply a value of zero returned from the function (signifying that no data was available, or the data couldn't be sent, depending on the function called).

So WSAEWOULDBLOCK doesn't normally represent an 'error' at all, but simply indicates that you need to re-try a call because it couldn't be completed immediately. If you call the string functions FN_readlinesocket and FN_writelinesocket the 'retrying' is done automatically for you.

Have you tried running these programs in the Files area of the Yahoo group:

http://tech.groups.yahoo.com/group/bb4w/files/Miscellaneous/socksend.bbc
http://tech.groups.yahoo.com/group/bb4w/files/Miscellaneous/sockrecv.bbc
http://tech.groups.yahoo.com/group/bb4w/files/Miscellaneous/socktest.bbc

Richard.
User IP Logged

Pages: 1  Notify Send Topic Print
« Previous Topic | Next Topic »

| |

This forum powered for FREE by Conforums ©
Terms of Service | Privacy Policy | Conforums Support | Parental Controls