Retro video games delivered to your door every month!
Click above to get retro games delivered to your door ever month!
X-Hacker.org- Blinker 5.10 Online Reference - <b> force</b> http://www.X-Hacker.org [<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]
 Force
------------------------------------------------------------------------------
 Blinker supports versions 2.1 through 4.0 of Force to create DOS real mode
 programs. Protected mode and Windows applications can also be created, but
 with some restrictions, so please refer to the file README.FRC in the FRC
 subdirectory of the Blinker installation directory for more details.
 When overlayed with Blinker version 3.2 and later, the runtime system of
 Force version 4.00 and prior presents an anomaly which may result in a
 system crash, so please also refer to this file for details of how to
 resolve this.
 The following sample programs written in Force 4.0 will be used throughout
 this section to illustrate the basics of linking Force programs with
 Blinker.

 TEST.PRG:
 proc Limerick extern
 proc main
 Limerick()
 endproc
 LIMERICK.PRG:
 proc Limerick
 ? "There was a young fellow from Forceland..."
 endproc

 The two modules are compiled as follows:

 FORCE test
 FORCE limerick

 To execute Blinker from the command line :

 BLINKER FILE test,limerick LIB force OUTPUT t

 This causes Blinker to link the two object modules specified in the FILE
 command (test.obj and limerick.obj) to create an executable program with the
 name t.exe, as specified in the OUTPUT command.

 Non-overlaid program

 The following link script file produces the same result as the above
 execution of Blinker from the command line:

 # TEST.LNK (This is a comment)
 FILE test
 FILE limerick
 LIB force         # FORCE compiler library
 OUTPUT t          # Output .EXE name

 To execute Blinker when using the above sample link script file use the
 following command :

 BLINKER @test

 The `@' character informs Blinker that what follows is the name of a link
 script file. Blinker will assume the extension `.LNK' unless one is given on
 the command line.

 Overlaid program with additional commands

 # TESTOVL.LNK
 # 50kb overlay area
 BLINKER OVERLAY OPSIZE 50
 # Run overlays in the EMS page frame
 BLINKER OVERLAY PAGEFRAME ON
 BLINKER MESSAGE WINK    # Only wink one eye
 BEGINAREA               # Start of overlays
    FILE test            # This file is overlaid
    FILE limerick        # This file is overlaid
 ENDAREA                 # End of overlays
 LIB force               # FORCE library not overlaid
 OUTPUT t                # Output .EXE name
 STACK 4096              # Stack size of 4 kb
 MAP A,S                 # Create MAP file

 For more information on using Blinker with Force compilers, please refer to
 the file README.FRC in the FRC subdirectory of the Blinker installation
 directory

Online resources provided by: http://www.X-Hacker.org --- NG 2 HTML conversion by Dave Pearson