Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
In this Discussion
- KevinWorkman May 2015
- PhiLho May 2015
How to create an executable that will not be stopped by anti-virus software
I've written a simple Java Script game. I used Processing 2.2.1 to export the program into a Windows 64 executable. It runs well on my PC. I used the "Embed Java for Windows (64-bit)" option.
I uploaded the executable file to my website. The link is
http://planegames.me/downloads/games/keepup/KeepUp64.exe
When I downloaded the program to a Windows 7 64-bit PC, its installation of Avast anti-virus would not allow the executable to run. When I transferred the file from my PC to the other PC's public folder (the two PC's share a homegroup), the same problem occurred.
How can I use Processing 2.2.1 to create .exe files that other people can trust?
Answers
If it's a JavaScript game, why don't you just deploy as JavaScript?
I think spitfire mixed up Java and JavaScript, like many people...
Perhaps try this on the downloaded file: go to properties, see at the bottom, there might be an Unlock button. Click it and click OK. Maybe it can work now.
Or just tell Avast the file is safe...