aboutsummaryrefslogtreecommitdiff
path: root/games/colem/README
diff options
context:
space:
mode:
authorB. Watson <yalhcru@gmail.com>2014-08-26 07:31:11 +0700
committerWilly Sudiarto Raharjo <willysr@slackbuilds.org>2014-08-30 14:19:21 +0700
commit9d3f8a34b2df42f3ff8df18524e3c7b288a5db71 (patch)
tree7ef7dc6dde6d8438842453ddb7c2b8f7a703564d /games/colem/README
parent3f99f3cb074121d14670ace3b8b4e6fd057eca06 (diff)
games/colem: Updated for version 2.9.
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'games/colem/README')
-rw-r--r--games/colem/README50
1 files changed, 25 insertions, 25 deletions
diff --git a/games/colem/README b/games/colem/README
index 47668260fc470..93f7a565277cd 100644
--- a/games/colem/README
+++ b/games/colem/README
@@ -1,33 +1,33 @@
+colem (ColecoVision emulator)
+
ColEm is a portable emulator of the old ColecoVision videogame console.
It should run most ColecoVision games and supports Coleco's SuperAction
controllers with spin wheels.
-In order to run ColecoVision games, you will need a copy of the system
-ROM image, but for copyright reasons, no ROM image is included. The
-file is generally called "coleco.rom" or "coleco.zip" (which contains
-"coleco.rom"). If you own a ColecoVision console, depending on the laws
-where you live, it may or may not be legal for you to use a copy of the
-ROM. If it's legal, you can either crack open your console, remove the
-ROM chip, and read the data from it... or use google-fu to find an
-already-dumped image file. Legal issues aside, you have 2 ways to
-provide the ROM image for the emulator to use:
+ColEm uses OSS for audio, so you'll have to either load the OSS
+emulation modules (via /etc/rc.d/rc.alsa-oss), run it as "aoss colem"
+from the command line, or launch it from your desktop by opening a .cv
+or .col file.
+
+In order to run ColecoVision games, you will need a copy of the system
+ROM image, but for copyright reasons, no ROM image is included.
+The file is generally called "coleco.rom" or "coleco.zip" (which
+contains "coleco.rom"). If you own a ColecoVision console, depending
+on the laws where you live, it may or may not be legal for you to use a
+copy of the ROM. If it's legal, you can either crack open your console,
+remove the ROM chip, and read the data from it... or use google-fu to
+find an already-dumped image file. Legal issues aside, you have 2 ways
+to provide the ROM image for the emulator to use:
-1. Place either "coleco.rom" or "coleco.zip" (containing "coleco.rom") in
-the directory with the SlackBuild script. The resulting package will
-include the ROM image in "usr/share/colem/coleco.rom". If you do this,
-DO NOT give anyone a copy of the package! Using the ROM might possibly
-be legal, but bundling it with ColEm is against the ColEm license.
+1. Buld the package with the ROM image:
-2. Build the package without the ROM image. After installing the
-package, manually place a copy of "coleco.rom" in "/usr/share/colem/"
-or "~/.colem/".
+ Place either "coleco.rom" or "coleco.zip" (containing "coleco.rom")
+ in the directory with the SlackBuild script. The resulting package will
+ include the ROM image in "usr/share/colem/coleco.rom". If you do this,
+ DO NOT give anyone a copy of the package! Using the ROM might possibly
+ be legal, but bundling it with ColEm is against the ColEm license.
-Note about the sources: It appears that every time upstream releases a
-new version, the download link for the previous version is removed. If
-you are unable to download the source, try visiting the home page and
-look for a new version of ColEm. If this is the case, please contact
-the maintainer of this script (see the .info file)
+2. Build the package without the ROM image:
-By default, ColEm is built for 24- and 32-bit color depth X11 displays.
-If you intend to run ColEm on an 8- or 16-bpp display, set either
-DISPLAY_BPP=8 or DISPLAY_BPP=16 in the script's environment.
+ After installing the package, manually place a copy of "coleco.rom" in
+ "/usr/share/colem/" or "~/.colem/".