View Full Version : Free program to convert .bat or .vbs to .exe
PhoenixTekBC
February 5th, 2007, 11:35 PM
Anyone know of a free program that will convert VB or batch file scripts to .exe files? EXEScript will do it but it costs money. I'm looking for something free. Anyone know of anything?
Colmaca
February 5th, 2007, 11:41 PM
Read this and see if its what you require, it looks like xp already has it so its free.
I'v never used it so I don't know if its what you want
http://renegadetech.blogspot.com/2006/07/how-to-convert-bat-file-or-vbs-file.html
PhoenixTekBC
February 6th, 2007, 12:39 AM
Nope, I tried that and it's basically a glorified .zip file... I need something that completely converts scripts (.vbs, .js, or .bat) to .exe's.
oracle128
February 6th, 2007, 10:52 AM
Why would you need to? They're scripting languages for reason - because they're not compiled programming languages. It's a niche market with little real-world requirement, which is why you're only likely to come across paid applications, or resorting to "glorified .zip files" like IExpress makes.
That said, I did manage to find a couple free apps for you, one for .bat, one for .vbs, both by the same author.
http://www.f2ko.de/b2e.html
http://www.f2ko.de/v2e.html
PhoenixTekBC
February 6th, 2007, 02:38 PM
BECAUSE, our new managed services platform can only run .exe scheduled scripts, so I have to convert what I got to .exe
smurfy
February 7th, 2007, 09:58 AM
http://www.autoitscript.com/autoit3/
scripts can also be compiled into stand-alone executables with Aut2Exe.
You may be able to write a simple autiIT script to call your existing .bats or .vbs files and this may work in the environment, otherwise you may have to re-write your scripts in the AutoIT language - which is better than you'll get in a BAT, but less featured than VBs.
oracle128
February 7th, 2007, 10:16 AM
BECAUSE, our new managed services platform can only run .exe scheduled scripts, so I have to convert what I got to .exeIn that case, cmd.exe, the command-line interpreter, and cscript.exe, the command-line-based VBScript interpreter (or wscript, the GUI-based VBS interpreter) should be called instead, passing the name of your script for each one as a parameter.