This example shows how to use the various BITMAP and TILEMAP resolutions. After each command, the screen will be configured at the best allowed. If a given parameter is omitted, this means that we have no particular interest in that component. The BITMAP ENABLE and TILEMAP ENABLE commands wait for up to three parameters: the width, the height and the number of colors. Width and height are measured in pixels (if BITMAP mode) or in tiles (if TILEMAP mode). Colors are always individual – i.e. the maximum number of different colors allowed.

 
   BITMAP ENABLE (320,200,16)
   BITMAP ENABLE (320,,4)
   BITMAP ENABLE (,256,2)
   BITMAP ENABLE (320,200)
   BITMAP ENABLE (320,)
   BITMAP ENABLE ()
   BITMAP ENABLE (,)
   BITMAP ENABLE (,,)
   
   TILEMAP ENABLE (40,25,16)
   TILEMAP ENABLE (32,,2)
 

• screens_resolution_01.bas

The instructions here refer to compiling the example from the command line. For Microsoft Windows users we suggest using UGBASIC-IDE, which allows you to compile the example with just one click.

In order to compile and run the example, you need to have the Altirra emulator, and in particular that the altirra executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.atari screens_resolution_01.bas -o example.xex
 altirra example.xex
 
 # Windows 
 ugbc.atari.exe screens_resolution_01.bas -o example.xex
 altirra example.xex

In order to compile and run the example, you need to have the Altirra emulator, and in particular that the altirra executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.atarixl screens_resolution_01.bas -o example.xex
 altirra example.xex
 
 # Windows 
 ugbc.atarixl.exe screens_resolution_01.bas -o example.xex
 altirra example.xex

In order to compile and run the example, you need to have the VICE emulator, and in particular that the x64sc executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.c64 screens_resolution_01.bas -o example.prg
 x64sc example.prg
 
 # Windows 
 ugbc.c64.exe screens_resolution_01.bas -o example.prg
 x64sc example.prg

In order to compile and run the example, you need to have the VICE emulator, and in particular that the x64sc executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.c64reu screens_resolution_01.bas -o example.prg
 x64sc -reu example.prg
 
 # Windows 
 ugbc.c64reu.exe screens_resolution_01.bas -o example.prg
 x64sc -reu example.prg

In order to run the example, you need to have the YAPE emulator. In particular that the yape executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.plus4 screens_resolution_01.bas -o example.prg
 yape example.prg
 
 # Windows 
 ugbc.plus4.exe screens_resolution_01.bas -o example.prg
 yape example.prg

In order to run the example, you need to have the VICE emulator. In particular that the xplus4 executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.plus4 screens_resolution_01.bas -o example.prg
 xplus4 example.prg
 
 # Windows 
 ugbc.plus4.exe screens_resolution_01.bas -o example.prg
 xplus4 example.prg

In order to compile and run the example, you need to have the XROAR emulator, and in particular that the xroar executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.d32 screens_resolution_01.bas -o example.bin
 xroar -rompath (your rom path) example.bin
 
 # Windows 
 ugbc.d32.exe screens_resolution_01.bas -o example.bin
 xroar.exe -rompath (your rom path) example.bin

In order to compile and run the example, you need to have the XROAR emulator, and in particular that the xroar executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.d64 screens_resolution_01.bas -o example.bin
 xroar -rompath (your rom path) example.bin
 
 # Windows 
 ugbc.d64.exe screens_resolution_01.bas -o example.bin
 xroar.exe -rompath (your rom path) example.bin

In order to compile and run the example, you need to have the DCMOTO emulator, and in particular that the dcmoto executable is accessible.

Then, type this command on the command line and on the emulator:

 # Linux 
 ugbc.pc128op screens_resolution_01.bas -o example.k7
 dcmoto
 (choose BASIC 128)
 CLEAR,&H2FFF: LOADM"CASS:",R: EXEC
 
 # Windows 
 ugbc.pc128op.exe screens_resolution_01.bas -o example.k7
 dcmoto
 (choose example.k7)
 (choose BASIC 128)
 CLEAR,&H2FFF: LOADM"CASS:",R: EXEC

In order to compile and run the example, you need to have the DCMOTO emulator, and in particular that the dcmoto executable is accessible.

Then, type this command on the command line and on the emulator:

 # Linux 
 ugbc.pc128op screens_resolution_01.bas -o example.k7
 dcmoto
 (choose BASIC 128)
 CLEAR,&H2FFF: LOADM"CASS:",R: EXEC
 
 # Windows 
 ugbc.pc128op.exe screens_resolution_01.bas -o example.k7
 dcmoto
 (choose example.k7)
 (choose BASIC 128)
 CLEAR,&H2FFF: LOADM"CASS:",R: EXEC

In order to compile and run the example, you need to have the VICE emulator, and in particular that the xvic executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.vic20 screens_resolution_01.bas -o example.prg
 xvic --memory 24k example.prg
 
 # Windows 
 ugbc.vic20.exe screens_resolution_01.bas -o example.prg
 xvic --memory 24k example.prg

In order to compile and run the example, you need to have the Speccy emulator, and in particular that the speccy executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.zx screens_resolution_01.bas -o example.tap
 Speccy example.tap
 
 # Windows 
 ugbc.zx.exe screens_resolution_01.bas -o example.tap
 Speccy example.tap

In order to compile and run the example, you need to have the openMsx or the BlueMSX emulator, and in particular that its executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.msx1 screens_resolution_01.bas -o example.rom
 openmsx -cart example.rom
 
 # Windows 
 ugbc.msx1.exe screens_resolution_01.bas -o example.rom
 openmsx -cart example.rom

 # Linux 
 ugbc.msx1 screens_resolution_01.bas -o example.rom
 bluemsx example.rom
 
 # Windows 
 ugbc.msx1.exe screens_resolution_01.bas -o example.rom
 bluemsx example.rom

In order to compile and run the example, you need to have the openMsx or the BlueMSX emulator, and in particular that its executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.coleco screens_resolution_01.bas -o example.rom
 openmsx -machine \"COL - ColecoVision\" -cart example.rom
 
 # Windows 
 ugbc.coleco.exe screens_resolution_01.bas -o example.rom
 bluemsx -machine \"COL - ColecoVision\" example.rom

 # Linux 
 ugbc.coleco screens_resolution_01.bas -o example.rom
 bluemsx /machine \"COL - ColecoVision\" /rom1 example.rom
 
 # Windows 
 ugbc.coleco.exe screens_resolution_01.bas -o example.rom
 bluemsx  /machine \"COL - ColecoVision\" /rom1 example.rom

In order to compile and run the example, you need to have the BlueMSX emulator, and in particular that its executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.sc3000 screens_resolution_01.bas -o example.rom
 bluemsx /machine \"SEGA - SC-3000\" /rom1 example.rom
 
 # Windows 
 ugbc.sc3000.exe screens_resolution_01.bas -o example.rom
 bluemsx  /machine \"SEGA - SC-3000\" /rom1 example.rom

In order to compile and run the example, you need to have the BlueMSX emulator, and in particular that its executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.sg1000 screens_resolution_01.bas -o example.rom
 bluemsx /machine \"SEGA - SG-1000\" /rom1 example.rom
 
 # Windows 
 ugbc.sg1000.exe screens_resolution_01.bas -o example.rom
 bluemsx  /machine \"SEGA - SG-1000\" /rom1 example.rom

If you have found a problem trying to run this example, if you think there is a bug or, more simply, you would like it to be improved, open an issue for this example on GitHub. Thank you!