![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to README.UNIX CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [UNIX Amiga Emulator] / uae / docs|
Return to README.UNIX CVS log | Up to [UNIX Amiga Emulator] / uae / docs |
1.1 root 1: This file documents the details relevant to the Unix versions of UAE. General
2: information can be found in the file "README"
3:
4: System requirements
5: ===================
6:
7: UAE will run on most Unix systems, and by now most of the portability issues
8: have been sorted out. However, since I am developing UAE using Linux, you may
9: encounter problems from time to time. If this happens, let me know as soon as
10: possible so these can be fixed in the next release.
11:
12: These are the requirements for getting the Unix version to run:
13: - X11, or SVGAlib if you are using Linux.
14: - The 386 is the only CPU that UAE will not run on. You need a 486 or
15: higher if you want to use an Intel CPU.
16: - an ANSI C compiler. Do not use a K&R compiler, otherwise you risk getting
17: incorrect code. GCC is _strongly_ recommended.
18: - 8MB RAM (better 16MB) + some swap
19: - Optionally, tcl7.4/tk4.0 or the X Forms library (version 0.80 or higher)
20:
21:
22: Compilation
23: ===========
24:
25: To build UAE, first unpack it to an appropriate directory (e.g. /usr/src/uae
26: on a Linux system). The simple way to proceed is to type "configure; make",
27: after that has completed you should have a working X11 version of UAE. Ignore
28: warnings if you get them.
29:
30: However, you should probably have a look at some of the compile-time options
31: found in "config.h" before you do this. There are some things you can change
32: there so that the resulting executable will perform better on your machine.
33: Each of the options in that file has a description. You can edit config.h to
34: suit your needs; and then do "configure; make" afterwards.
35:
36: If you are running Linux, you can say "configure --without-x" as an
37: alternative. If you do this, UAE will be configured to use the SVGA library.
38: If you use SVGAlib, be warned that SVGAlib is not too stable and using it is
39: inherently a little dangerous, you might want to have a way to log in from a
40: remote terminal if things go horribly wrong. If you are very unfortunate, you
41: might lock up your machine otherwise.
42: Note that you must be root to run SVGAlib programs. Making UAE suid root is
43: _not_ a particularly good idea if you care about the security of your system.
44:
45: If you use a recent XFree86 server (such as XFree86 3.2, or one of the betas
46: before that), you can configure UAE to use the DGA extension for speed. This
47: will make UAE access the framebuffer directly. It also means that you'll have
48: to exit UAE if you want to use another X program in between, because it
49: completely takes over the control. The mouse will be emulated slightly better
50: if you use DGA mode. To enable it, pass the "--enable-dga" option to
51: configure.
52:
53: If you configure UAE for building the X11 version (which is the default if you
54: simply say "configure"), the configure script will try to find the program
55: "wish4.0" in the path. You can disable the UAE user-interface by passing the
56: "--disable-gui" option to configure. By default, the X11 version of UAE
57: tries to use a GUI written in Tcl. This requires Tk version 4.0.
58: The SVGAlib version uses a ncurses-based user interface.
59:
60: If you are a daring person, you can edit custom.c before compiling and enable
61: the "EMULATE_AGA" define. UAE will then try to emulate some AGA features. I'd
62: like to hear feedback as to how well it works (expect it not to work at all
63: for a start).
64:
65:
66: Keyboard mappings
67: =================
68:
69: You can exit the SVGAlib (and the DGA) version by pressing the F12 key.
70: PgUp/PgDn emulate the right/left Amiga keys.
71:
72: The X11 version needs some help to figure out how to map keys: You'll have to
73: tell it the keyboard language with the "-l" commandline option. Several
74: languages ("us", "se", "de", "fr", "es", "it") are supported. If you have
75: a different keyboard, patches to make UAE work with it are appreciated.
76:
77:
78: Mouse and joystick emulation
79: ============================
80:
81: The X11 version will try to keep the Amiga mouse pointer at the same location
82: as the X mouse pointer. You can turn off this mode if it does not work with
83: your program by pressing F12. This is needed (for example) for Lemmings, the
84: Magnetic Scrolls adventures and ProTracker; these programs don't use sprite 0
85: as a mouse pointer. The SVGAlib and DGA versions do not have this problem.
86:
87: If you use Linux and have the joystick driver kernel module, "configure"
88: should automatically enable support for it. UAE calibrates the joystick
89: automatically. Turn it a few times on startup to get the calibration done.
90:
91:
92: Harddisk emulation
93: ==================
94:
95: If you want to execute files located on a native filesystem, they need to have
96: the x permission bit set. That can be done in Unix by "chmod +x file" or in
97: AmigaDOS with "protect file rwed".
98:
99:
100: Printing
101: ========
102:
103: If you give UAE the "-p lpr" option, output for the parallel port will be
104: piped to lpr, which will in turn print it. You should use the Postscript
105: printer driver on the Amiga side (since UAE relies on the ^D character at
106: the end of the Postscript output).
107: Note that I never tried this myself, so you're on your own.
108:
109:
110: Transferring things over the serial port
111: ========================================
112:
113: There's an easy way to use a null-modem cable without terminal software if
114: you use Linux (and probably other Unices). You can do
115:
116: transdisk >SER: <options>
117:
118: on the Amiga to copy the data directly to the serial port. Before that, do
119:
120: cat /dev/ttyS1 >df0.adf
121:
122: on your Linux box to receive the data (it may be ttyS0 on your system, or
123: another number, depending on which serial port you are using). When the Amiga
124: is done transferring, hit ^C on the PC to interrupt the cat program. To make
125: this work, you need to use the same settings for the serial port on both
126: sides. This is done with the Preferences program on the Amiga (this is split
127: into several programs from Kickstart 2.0 upwards, you'll find a program called
128: "serial" in the Prefs directory of your Workbench disk). On the Linux side,
129: use the stty program. "man stty" will give you the manpage describing how to
130: use it.
131: To be on the safe side, set the speed to a low value (2400 baud). Turn off
132: Xon/Xoff, but enable RTS/CTS.
133: I use the following command myself:
134:
135: stty 19200 parenb -cstopb cread clocal crtscts -istrip -inlcr -icrnl -opost
136: -onlcr -parodd -isig -icanon -iexten raw cs8 </dev/ttyS1
137:
138: which is probably overkill, but you never know :)
139: This maps to 19200 baud, 8 bits, even parity, one stop bit, which you have to
140: set in the Amiga preferences.
141:
142:
143: Using the Linux AFFS filesystem
144: ===============================
145:
146: If you use Linux with a kernel version >= 2.0.7 and version 2.5k of the mount
147: program, you can do
148: mount df0.adf /mnt -t affs -o loop
149: to mount disk image df0.adf at the mount point /mnt.
150:
151: You'll need to enable support for the Amiga filesystem and the loop device
152: when configuring and compiling the kernel (say yes to the "Ask about
153: experimental drivers" question at the start).
154:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.