GFA-BASIC for Windows 32-bits  GFA-BASIC 32 runs on all Windows versions.

Essentially, you have two options. Download the binary updates  or download the entire package containing all binaries, documentation, help files, and samples.

Updates of September 25 2017

Follow this link to my OneDrive\Public folder. It contains the latest GFA-BASIC 32 downloads. 

1. 2.33 Build 1202 
The latest update of the GfaWin23.Ocx (Runtime DLL).
-> Unpack and replace the GfaWin23.ocx in your GFABASIC32's Bin directory.
-> Read the rtf file for the latest comments.

The latest updates of binaries and related files.
This includes: GfaWin23.Ocx (, GfaWin32.Exe IDE/Compiler (2.4.03), GfaWin32.Gll, manifest file, and a readme RTF.
-> Unpack and replace these files in your GFABASIC32's Bin directory.
-> Read the rtf file for the latest comments.

The complete (and up-to-date) package separated into different folders.
-> The zip contains a folder named 'gb32' so that you can drag (unpack) the package in one action to any location.
-> Read the rtf file for the latest comments.
Note - The Help file needs a proper installation of winhlp32.exe, which isn't supported by recent versions of Windows. You need to install it manually using the 4th download.

This zip-file contains a script to manually install winhlp32.exe.
-> Unzip and run install.cmd, but first read the readme.txt.
-> Save the zip somewhere, because after each major update of Windows the winhlp32 installation is destroyed.

About gfawin32.gll:
When you choose to use GfaWin32.exe version 2.4 you must unpack gfawin32.gll into the same directory. To work properly the IDE needs this GLL! More and more fixes are put in this Gll, rather than through poking patches in the binary file.
In addition gfawin32.gll extends the functionality of the IDE.

This version of gfawin32.gll is a bit rudimentary and misses a lot of features that are now ready for production. The problem with this kind of GLL is the heavy intrusion and hacking of the IDE that for a long time brought me fatal problems. For instance, some functions rely on the use of Try/Catch handlers that - when used in a GLL - erase the Err object's properties. When a program raised a Runtime exception, or used Err.Raise, the editor never got a chance to display a proper message box. Fortunately, that's one of those problems that is now solved.

More on GFA-BASIC (32)
Go to the Links page for additional downloads and samples.