thinBasic is not a compiler but an interpreter.
Bundled EXE are not machine code executable of your source but are a sort of compressed file containing all the modules needed by your script.
Consider a bundled EXE like a ZIP file in which there are all the part of thinBasic needed to execute your script in machines where thinBasic is not installed.
When you execute bundled exe, there is a minimal stub that explode on the disk all needed files (thinBasic.exe, thinCore.dll and other dlls representing the modules you have used in your script) plus a crypted/obfuscated version of your script source code. At that time your script is executed.
When script stop its execution, all exploded files are removed from disk.
You do not see all this process because all files are exploded on disk with system hidden attributes set to on. You can see them if you instruct your shell Explorer to show also system hidden file.
I'm sorry but this process cannot be changed due to the interpretative nature of thinBasic.
This method is used also in other programming language that are not native machine code compiled.
The same .Net framework does something similar but does not need to include the full framework because the framework is a pre-requisite so you have it already installed in your computer. Same is Java code. All of them need the full core and extended classes present in your target machine.
If you have thinBasic installed in all your target machine you can just distribute an obfuscated version of your script and it will work.
Ciao
Eros
Bookmarks