GoAsm install notes

The GoAsm support for RadASM uses a predefined directory structure in order to get everything up and functioning correctly. The following directory structure is expected out-of-the-box, this can be changed to suit your specific situation :

            GFL.txt    - GFL is a text file that contains a list of DLLs
            Windows ANSI include files
            Windows UNICODE include files
            Win32.hlp    - This file is an API reference see the  page

The Windows ANSI and UNICODE include files can be obtained form the url in the page.

Because of the fixed nature of command lines in RadASM the GFL.txt file is used to list the API DLLs that a program will be using. Generally you would include all of the DLLs that are available in the order that they are most used. The GoAsm assembler uses this file as a reference when searching for API commands. The default command line is based on project type and can be modified on a project by project basis using .

The ANSI and UNICODE include files are a group of equates that convert the API name from character set specific wrappers to a more generic form e.g. MessageBoxA and MessageBoxW are both changed to MessageBox, pick the include folder that supports the character set you wish to use. All of the API names that require an ANSI or UNICODE suffix have been consolidated in a file called all_api.inc, there is copy of the file in each of the include folders that is specific to the selected character set.

#include "C:\GoAsm\IncludeA\all_api.inc" will include the ANSI version of API calls
#include "C:\GoAsm\IncludeW\all_api.inc"
will include the UNICODE version of API calls

Limitations (v2.0.3.7):
Because the entry point must be specified on the command line the following defaults have been chosen:

Win32 (all types) : Start
DLLs : DllEntryPoint

New to v2.0.3.7, for FRAME to collapse correctly you must not specify the procedure name in the ENDF statement . Earlier implementations required that the ENDF statement be preceded by the procedure name, that is no longer the case. The USEDATA statement is now collapsible as well. These changes were made to conform more closely to the specifications in the GoAsm documentation.