Installing MESS - Revision history

Mizapf: /* Insert or change a cartridge at runtime */

2020-09-28T11:03:19Z

Insert or change a cartridge at runtime

← Older revision		Revision as of 11:03, 28 September 2020
Line 78:		Line 78:
	[[File:messosd.png\|thumb\|left\|200px\|The MESS OSD menu]]		[[File:messosd.png\|thumb\|left\|200px\|The MESS OSD menu]]

	You can make the OSD menu pop up by pressing the '''TAB''' key within the keyboard [[partial emulation mode]]. You can toggle between the [[full emulation mode]] and the partial emulation mode using the Scrl-Lock key (default). In case the Scrl-Lock key is not available you can put the [~~[Change_MESS_menu_mode_key \|~~ mode switch on any other key]].		You can make the OSD menu pop up by pressing the '''TAB''' key within the keyboard [[partial emulation mode]]. You can toggle between the [[full emulation mode]] and the partial emulation mode using the Scrl-Lock key (default). In case the Scrl-Lock key is not available you can put the [https://www.mizapf.de/en/ti99/mame mode switch on any other key].

	The OSD menu allows you to change the configuration of the TI emulation, like activating or deactivating peripheral cards (Driver Configuration) or setting DIP switches on cards (Dip Switches).		The OSD menu allows you to change the configuration of the TI emulation, like activating or deactivating peripheral cards (Driver Configuration) or setting DIP switches on cards (Dip Switches).
Line 86:		Line 86:
	In the '''File Manager''' you will find again the slots and drives you already noticed in the MESS UI under Device View. Here, the navigation is not quite so comfortable, although the mouse is also supported. You can change inserted media just by selecting a new entry, but you can also remove the cartridge or disk by selecting '''Empty slot'''.		In the '''File Manager''' you will find again the slots and drives you already noticed in the MESS UI under Device View. Here, the navigation is not quite so comfortable, although the mouse is also supported. You can change inserted media just by selecting a new entry, but you can also remove the cartridge or disk by selecting '''Empty slot'''.

	Notice that when you insert a new cartridge, the emulation will automatically reset. This is partly intentional (as it happens with the real console as well), partly a requirement of the current implementation (as inserting the cartridge changes the device tree within the emulation, which is currently updated by a reset). That is, at this time there is no way of sticking tape over the reset line.		Notice that when you insert a new cartridge, the emulation will automatically reset. This is partly intentional (as it happens with the real console as well), partly a requirement of the current implementation (as inserting the cartridge changes the device tree within the emulation, which is currently updated by a reset). That is, at this time there is no way of sticking tape over the reset line.

	== Installing the Linux version ==		== Installing the Linux version ==

Mizapf: /* Install the ROMs */

2019-08-28T18:59:57Z

Install the ROMs

← Older revision		Revision as of 18:59, 28 August 2019
Line 31:		Line 31:
	Now where do you get the ROMs from? The problem is that almost all ROMs have '''not been released into public domain''' and are therefore subject to licensing. Due to the giant number of emulated systems, MESS simply cannot afford to license the ROMs.		Now where do you get the ROMs from? The problem is that almost all ROMs have '''not been released into public domain''' and are therefore subject to licensing. Due to the giant number of emulated systems, MESS simply cannot afford to license the ROMs.

	System ROM files are ZIP files containing the dumps of the various memory chips in the system. For the different TI systems, we need a ~~[[TI ROM dumps for MESS \|~~ set of ROM contents]] specific to the respective system.		System ROM files are ZIP files containing the dumps of the various memory chips in the system. For the different TI systems, we need a set of ROM contents specific to the respective system.

	Let's assume you have found the '''ti99_4ae.zip''' file somewhere; next, you drop this file into the roms folder that you previously created.		Let's assume you have found the '''ti99_4ae.zip''' file somewhere; next, you drop this file into the roms folder that you previously created.

Mizapf: /* Launching MESS */

2019-08-26T16:56:22Z

Launching MESS

← Older revision		Revision as of 16:56, 26 August 2019
Line 181:		Line 181:
	You are certainly already familiar to Linux, and you should not be surprised that the prefered way of starting MESS is by command line in a terminal. You can, of course, create an icon in your favorite window system (like GNOME or KDE) that launches MESS with some appropriate switches. Maybe you want to create a small script file that launches mess with your favorite options.		You are certainly already familiar to Linux, and you should not be surprised that the prefered way of starting MESS is by command line in a terminal. You can, of course, create an icon in your favorite window system (like GNOME or KDE) that launches MESS with some appropriate switches. Maybe you want to create a small script file that launches mess with your favorite options.

	You will need some libraries against which the binary file has been linked. These libraries are automatically installed when you install the development packages as described in [~~[Building_MESS \|~~ Building ~~MESS]~~]. If you use a pre-built package please check with your Linux distribution whether you already have the libraries.		You will need some libraries against which the binary file has been linked. These libraries are automatically installed when you install the development packages as described in [https://www.mizapf.de/en/ti99/mame/buildmame Building MAME]. If you use a pre-built package please check with your Linux distribution whether you already have the libraries.

	If the executable is in your PATH, just start it by name, else put the path to the executable before.		If the executable is in your PATH, just start it by name, else put the path to the executable before.

Mizapf: /* Build the sources and install */

2019-08-26T16:14:46Z

Build the sources and install

← Older revision		Revision as of 16:14, 26 August 2019
Line 98:		Line 98:
	=== Build the sources and install ===		=== Build the sources and install ===

	Make sure you have a proper build environment. You need the GCC C and C++ compilers. The source package contains a makefile, so building is no rocket science. Have a look at our detailed [~~[Building MESS\|~~building instructions]].		Make sure you have a proper build environment. You need the GCC C and C++ compilers. The source package contains a makefile, so building is no rocket science. Have a look at our detailed [https://www.mizapf.de/en/ti99/mame/buildmame building instructions].

	After building the MESS executable you have one of the following files:		After building the MESS executable you have one of the following files:

Mizapf at 16:13, 26 August 2019

2019-08-26T16:13:36Z

← Older revision		Revision as of 16:13, 26 August 2019
Line 92:		Line 92:
	=== Download ===		=== Download ===

	As said above, on the [http://www.mess.org/download.php MESS download page] you will find the most recent version of MESS. However, for Linux there is no pre-built version here. You have to ~~[[Building MESS \|~~ build the version]] on your system.		As said above, on the [http://www.mess.org/download.php MESS download page] you will find the most recent version of MESS. However, for Linux there is no pre-built version here. You have to build the version on your system.

	One notice here: The MESS download page only contains the source code for the MESS-specific parts. This will not suffice to build the system. You have to download the MAME base of the same version number, unpack it in your filesystem, and unpack the MESS sources directly over them. See the [http://mamedev.org/release.html MAME download page] for downloading MAME.		One notice here: The MESS download page only contains the source code for the MESS-specific parts. This will not suffice to build the system. You have to download the MAME base of the same version number, unpack it in your filesystem, and unpack the MESS sources directly over them. See the [http://mamedev.org/release.html MAME download page] for downloading MAME.

Mizapf: /* Launching MESS */

2013-05-14T19:33:18Z

Launching MESS

← Older revision		Revision as of 19:33, 14 May 2013
Line 179:		Line 179:
	=== Launching MESS ===		=== Launching MESS ===

	You are certainly already familiar to Linux, and you should not be surprised that the prefered way of starting MESS is by command line in a terminal. You can, of course, create an icon in your favorite window system (like GNOME or KDE) that launches MESS with some appropriate switches. ~~We'll now discuss those switches~~.		You are certainly already familiar to Linux, and you should not be surprised that the prefered way of starting MESS is by command line in a terminal. You can, of course, create an icon in your favorite window system (like GNOME or KDE) that launches MESS with some appropriate switches. Maybe you want to create a small script file that launches mess with your favorite options.

			You will need some libraries against which the binary file has been linked. These libraries are automatically installed when you install the development packages as described in [[Building_MESS \| Building MESS]]. If you use a pre-built package please check with your Linux distribution whether you already have the libraries.

	If the executable is in your PATH, just start it by name, else put the path to the executable before.		If the executable is in your PATH, just start it by name, else put the path to the executable before.
Line 186:		Line 188:
	This will give you a selection of systems as available by the ROM files in your roms directory. If you already know that you want to start the TI emulation, type		This will give you a selection of systems as available by the ROM files in your roms directory. If you already know that you want to start the TI emulation, type

	user@host:~/mess> mess64 ~~ti99_4ae~~		user@host:~/mess> mess64 ti99_4a

	MESS has a set of drive emulations, so you might want to start the emulator with an inserted disk.		MESS has a set of drive emulations, so you might want to start the emulator with an inserted disk.

	user@host:~/mess> mess64 ~~ti99_4ae~~ -peb:slot8 hfdc -flop1 mydisk.dsk -flop2 anotherdisk.dsk		user@host:~/mess> mess64 ti99_4a -peb:slot8 hfdc -flop1 mydisk.dsk -flop2 anotherdisk.dsk

	This will mount the image files to DSK1 and DSK2. Also, since version 0.145, you have to define the controllers plugged into your emulated PEB, like the HFDC in slot 8. If you forget this parameter you will not be able to use the floppy, just as if you fail to plug in the controller in the real system.		This will mount the image files to DSK1 and DSK2. Also, since version 0.145, you have to define the controllers plugged into your emulated PEB, like the HFDC in slot 8. If you forget this parameter you will not be able to use the floppy, just as if you fail to plug in the controller in the real system.
Line 196:		Line 198:
	Of course, you may also start with a module inserted:		Of course, you may also start with a module inserted:

	user@host:~/mess> mess64 ~~ti99_4ae~~ -cart1 editor_assembler.rpk -peb:slot8 hfdc -flop1 eadisk.dsk		user@host:~/mess> mess64 ti99_4a -cart1 editor_assembler.rpk -peb:slot8 hfdc -flop1 eadisk.dsk

	If Editor/Asembler complains about a missing 32K expansion you should either turn on the "console 32K" mod, or you plug in the 32K expansion in another slot. Check the slot options with		If Editor/Asembler complains about a missing 32K expansion you should either turn on the "console 32K" mod, or you plug in the 32K expansion in another slot. Check the slot options with

	user@host:~/mess> mess64 ~~ti99_4ae~~ -listslots		user@host:~/mess> mess64 ti99_4a -listslots

	You can insert, change, and remove all media from the On-Screen Display - the same one as in the Windows version as shown above.		You can insert, change, and remove all media from the On-Screen Display - the same one as in the Windows version as shown above.

Mizapf: /* Launching MESS */

2013-05-14T19:27:14Z

Launching MESS

← Older revision		Revision as of 19:27, 14 May 2013
Line 190:		Line 190:
	MESS has a set of drive emulations, so you might want to start the emulator with an inserted disk.		MESS has a set of drive emulations, so you might want to start the emulator with an inserted disk.

	user@host:~/mess> mess64 ti99_4ae -flop1 mydisk.dsk -flop2 anotherdisk.dsk		user@host:~/mess> mess64 ti99_4ae -peb:slot8 hfdc -flop1 mydisk.dsk -flop2 anotherdisk.dsk

	This will mount the image files to DSK1 and DSK2. ~~Of course~~, you ~~may also start with a module inserted:~~		This will mount the image files to DSK1 and DSK2. Also, since version 0.145, you have to define the controllers plugged into your emulated PEB, like the HFDC in slot 8. If you forget this parameter you will not be able to use the floppy, just as if you fail to plug in the controller in the real system.

	user@host:~/mess> mess64 ti99_4ae -cart1 editor_assembler.rpk -flop1 eadisk.dsk		Of course, you may also start with a module inserted:

			user@host:~/mess> mess64 ti99_4ae -cart1 editor_assembler.rpk -peb:slot8 hfdc -flop1 eadisk.dsk

			If Editor/Asembler complains about a missing 32K expansion you should either turn on the "console 32K" mod, or you plug in the 32K expansion in another slot. Check the slot options with

			user@host:~/mess> mess64 ti99_4ae -listslots

	You can insert, change, and remove all media from the On-Screen Display - the same one as in the Windows version as shown above.		You can insert, change, and remove all media from the On-Screen Display - the same one as in the Windows version as shown above.
Line 200:		Line 206:
	Your Geneve emulation may be started with		Your Geneve emulation may be started with

	user@host:~/mess> mess64 geneve -hard1 mfmdisk.hd -flop1 working.dsk		user@host:~/mess> mess64 geneve -peb:slot8 hfdc -hard1 mfmdisk.hd -flop1 working.dsk

	if you have put the contents of your hard disk into the mfmdisk.hd file before. This can be done with the ''chdman'' tool (part of the MESS distribution).		if you have put the contents of your hard disk into the mfmdisk.hd file before. This can be done with the ''chdman'' tool (part of the MESS distribution).

Mizapf at 17:29, 20 October 2011

2011-10-20T17:29:05Z

← Older revision		Revision as of 17:29, 20 October 2011
Line 212:		Line 212:

	which allows me to add some switches to the invocation of this file, as, for instance, to mount disks or cartridges.		which allows me to add some switches to the invocation of this file, as, for instance, to mount disks or cartridges.
			[[Category:MESS]]

Mizapf: /* Additional configurations */

2011-06-08T20:16:59Z

Additional configurations

← Older revision		Revision as of 20:16, 8 June 2011
Line 211:		Line 211:
	./mess64 ti99_4ae -keymap -keymap_file keymaps/km_de_LINUX.map $*		./mess64 ti99_4ae -keymap -keymap_file keymaps/km_de_LINUX.map $*

	which allows me to add some switches to the invocation of this file, as, for instance, disks or cartridges.		which allows me to add some switches to the invocation of this file, as, for instance, to mount disks or cartridges.

Mizapf at 20:15, 8 June 2011

2011-06-08T20:15:36Z

← Older revision		Revision as of 20:15, 8 June 2011
Line 96:		Line 96:
	One notice here: The MESS download page only contains the source code for the MESS-specific parts. This will not suffice to build the system. You have to download the MAME base of the same version number, unpack it in your filesystem, and unpack the MESS sources directly over them. See the [http://mamedev.org/release.html MAME download page] for downloading MAME.		One notice here: The MESS download page only contains the source code for the MESS-specific parts. This will not suffice to build the system. You have to download the MAME base of the same version number, unpack it in your filesystem, and unpack the MESS sources directly over them. See the [http://mamedev.org/release.html MAME download page] for downloading MAME.

	'''~~TO BE COMPLETED~~'''		=== Build the sources and install ===

			Make sure you have a proper build environment. You need the GCC C and C++ compilers. The source package contains a makefile, so building is no rocket science. Have a look at our detailed [[Building MESS\|building instructions]].

			After building the MESS executable you have one of the following files:

			{\|
			\| style="width:10em" \| mess
			\| mess 32-bit standard build
			\|-
			\| messd
			\| mess 32-bit debug build
			\|-
			\| mess64
			\| mess 64-bit standard build
			\|-
			\| mess64d
			\| mess 64-bit debug build
			\|}

			The debug builds are much larger than the standard builds, and you may experience bad performance. For a normal usage, the standard builds are clearly recommended. However, the debug builds are quite useful for debugging MESS, especially within the GNU debugging tool gdb.

			The executables are all statically linked. Thus you can copy the executable file into some part of your PATH; if you want to provide it to all users on the system you may want to copy it to ''/usr/local/bin'' or similar locations.

			For the following descriptions we assume you have copied the mess executable into '''$HOME/mess'''.

			=== Install the ROMs ===

			Create a '''roms''' directory in your mess installation directory. Copy the '''ti99_4ae.zip''' file (or '''ti99_4a.zip''', '''geneve.zip''', '''ti99_8.zip''' etc.) into this directory.

			user@host:~/mess> mkdir roms
			user@host:~/mess> cp ti99_4ae.zip roms

			=== Create a config file ===

			You may want to create a configuration file first in order to adjust some setttings. If the executable is called mess64, type

			user@host:~/mess> mess64 -createconfig

			Check the contents. We want to make sure that writeconfig is 0, since a 1 causes all changes of inserted media to become saved in this file, which is most likely not what you prefer.

			#
			# CORE CONFIGURATION OPTIONS
			#
			readconfig 1
			writeconfig 0

			Check the paths. It is important that the rompath cites the directory where you put the ROM zip files. Hashes are not important for the TI emulations.

			#
			# CORE SEARCH PATH OPTIONS
			#
			rompath roms
			hashpath hash
			samplepath samples
			artpath artwork
			ctrlrpath ctrlr
			inipath $HOME/.mess;.;ini
			fontpath .
			cheatpath cheat
			crosshairpath crosshair

			If you have OpenGL support in your system you should make use of it, since it ensures best video performance. Linux distributions should offer the '''glxgears''' test program, and if you can see spinning gears in a window, OpenGL is available. Also, I don't like fullscreen display, so I set window to 1 and maximize to 0.

			#
			# VIDEO OPTIONS
			#
			video opengl
			numscreens 1
			window 1
			maximize 0

			And finally you want to have a comfortable window size.

			#
			# PER-WINDOW VIDEO OPTIONS
			#
			screen auto
			aspect auto
			resolution 640x480

			=== Launching MESS ===

			You are certainly already familiar to Linux, and you should not be surprised that the prefered way of starting MESS is by command line in a terminal. You can, of course, create an icon in your favorite window system (like GNOME or KDE) that launches MESS with some appropriate switches. We'll now discuss those switches.

			If the executable is in your PATH, just start it by name, else put the path to the executable before.
			user@host:~/mess> mess64

			This will give you a selection of systems as available by the ROM files in your roms directory. If you already know that you want to start the TI emulation, type

			user@host:~/mess> mess64 ti99_4ae

			MESS has a set of drive emulations, so you might want to start the emulator with an inserted disk.

			user@host:~/mess> mess64 ti99_4ae -flop1 mydisk.dsk -flop2 anotherdisk.dsk

			This will mount the image files to DSK1 and DSK2. Of course, you may also start with a module inserted:

			user@host:~/mess> mess64 ti99_4ae -cart1 editor_assembler.rpk -flop1 eadisk.dsk

			You can insert, change, and remove all media from the On-Screen Display - the same one as in the Windows version as shown above.

			Your Geneve emulation may be started with

			user@host:~/mess> mess64 geneve -hard1 mfmdisk.hd -flop1 working.dsk

			if you have put the contents of your hard disk into the mfmdisk.hd file before. This can be done with the ''chdman'' tool (part of the MESS distribution).

			=== Additional configurations ===

			If you have an international keyboard you may encounter some dead keys. This can be fixed by using a ''keymap''. The keymap files are part of the source distribution. You may want to copy them into your mess directory. Therefore, my usual script file to start MESS looks like this:

			#!/bin/bash
			./mess64 ti99_4ae -keymap -keymap_file keymaps/km_de_LINUX.map $*

			which allows me to add some switches to the invocation of this file, as, for instance, disks or cartridges.