![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to README CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [UNIX Amiga Emulator] / uae / docs / unix|
Return to README CVS log | Up to [UNIX Amiga Emulator] / uae / docs / unix |
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: - 8MB RAM (better 16MB) + some swap
15: - The 386 is the only CPU that UAE will not run on. You need a 486 or
16: higher if you want to use an Intel CPU.
17: - an ANSI C compiler. Do not use a K&R compiler, otherwise you risk getting
18: incorrect code. GCC is _strongly_ recommended. Don't use versions of GCC
1.1.1.2 root 19: older than 2.7.2. I wouldn't recommend 2.7.2 either.
1.1 root 20: - Optionally, the gtk library, available from ftp.gimp.org, and a pthreads
21: library.
22:
23: For reference, this is my system configuration:
1.1.1.3 ! root 24: OS: Linux 2.2.13
1.1 root 25: CPU: AMD-K6-233
1.1.1.2 root 26: RAM: 64MB
1.1.1.3 ! root 27: X11: version 3.3.4
! 28: Compiler: gcc-2.95.1
! 29: Libraries: glibc-2.1.1 (includes libpthread), gtk-1.2.3
! 30: binutils: 2.9.1
1.1 root 31: If you have the same configuration, and it doesn't run, you're doing something
32: wrong ;)
33:
34:
35: Compilation
36: ===========
37:
38: To build UAE, first unpack it to an appropriate directory (e.g. /usr/src/uae
39: on a Linux system). The simple way to proceed is to type "configure; make",
40: after that has completed you should have a working X11 version of UAE. Ignore
41: warnings if you get them.
42:
43: However, you should probably have a look at some of the compile-time options
44: found in "config.h" before you do this. There are some things you can change
45: there so that the resulting executable will perform better on your machine.
46: Each of the options in that file has a description. You can edit config.h to
47: suit your needs; and then do "configure; make" afterwards.
48:
49: When running configure, there are a few options that you can use to
50: influence configure's decision as to what kind of display should be used.
51: The following displays are available:
52: - Standard X11, in a window. This is the default.
53: - X11/DGA. This runs full-screen and is somewhat faster than the normal X11
54: code. You need a recent (>= version 3.2) XFree86 X server.
55: - SVGAlib. This is only available on Linux systems. It is the default if X11
56: is not found by configure.
57: - ncurses character output. This is the last resort.
58:
59: Type "configure --help" to get a list of options that configure understands.
60: The following are likely to be useful:
61: --without-x : Don't use X11 as target.
62: --with-svgalib : Build a version that uses SVGAlib (Linux only)
63: --with-ggi : Build a version that uses GGI (Linux only)
64: --with-asciiart : Build a version that uses ASCII "graphics"
65: --enable-sound : If a sound system is found that UAE knows about, sound
66: emulation will be compiled in.
67: --enable-profiling : Build a much slower version of the emulator (if you
68: don't know what it's for, you don't want it)
69: --enable-dga : If your X server supports the DGA extension, use it
70: --enable-vidmode : If your X server supports the VidMode extension, use
71: it. This enables the emulator to switch to low
72: resolutions such as 320x256 or 400x300 if you have
73: defined ModeLines for them.
74: --enable-ui : Build a user interface if possible (enabled by default)
75: --enable-threads : Build UAE multithreaded on systems that support it.
76: Note that there is very little thread support in UAE at
77: the moment.
78: --enable-penguins : Enable some additional threads which only make sense on
79: SMP (symmetric multi penguin) machines. If you have a
80: single-CPU machine, you don't want to use this option.
81: Note that there is a corresponding "--disable-xxx" for each "--enable-xxx"
82: option, and a "--without-yyy" for each "--with-yyy".
83:
84: Both the SVGAlib and the DGA version run full-screen, i.e. you can't run other
85: programs at the same time very well. You also need to be root to run either of
86: these two versions.
87: Making UAE suid root is _not_ a particularly good idea if you care about the
88: security of your system.
89:
90: If you are not sure whether you have an SMP machine, you don't have one.
91:
92:
93: Run-time options
94: ================
95:
96: The X11 version (without DGA) of UAE understands these special command-line
97: options:
98: -L : Use "low-bandwidth" mode, which can reduce the amount of data
99: transferred between UAE and the X server. That's particularly an
100: advantage when these are running on two different machines in a
101: network.
102: -T : Use the MIT-SHM extension. This may not be available on all
103: machines, and it will not work if UAE and the X server are not
104: running on the same machine.
105: In all other configurations, turning on this option will give you
106: a huge speed improvement.
107: -x : Turn off the X11 mouse cursor for the UAE window. Personally, I
108: find that seeing the X cursor helps, but that's a matter of taste.
109:
110: The SVGAlib version understands the following command-line option:
111: -x : Turn off linear frame buffer support, even if it is available.
112: Unless linear mode doesn't work properly, you don't want to disable
113: it, because UAE is much faster if it can draw into a linear
114: frame buffer.
115:
116:
117: Keyboard mappings
118: =================
119:
1.1.1.3 ! root 120:
! 121: You can exit the SVGAlib version by pressing the F12 key.
1.1 root 122: PgUp/PgDn emulate the right/left Amiga keys. In the SVGAlib version, F11 will
123: bring you back to the user interface screen so you can change disks during the
124: emulation.
125:
126: The X11 version needs some help to figure out how to map keys: You'll have to
127: tell it the keyboard language with the "-l" commandline option. Several
128: languages ("us", "se", "de", "fr", "es", "it") are supported. If you have
129: a different keyboard, patches to make UAE work with it are appreciated.
130:
1.1.1.3 ! root 131: In the X11 version, there are several key combinations that invoke some
! 132: behaviour:
! 133: F12+'q': Quit the emulation.
! 134: F12+'g': "Grab" the mouse, so it won't leave the UAE window. Use the same
! 135: combination to ungrab the mouse.
! 136: F12+'i': Toggle graphics updates on/off. Same as ScrollLock.
! 137: F12+'p': Toggle sound interpolation method. This is useful for determining
! 138: the differences between interpolation methods.
! 139: F12+'m': Toggle between alternative mouse pointer emulation methods; either
! 140: follow-mouse or dont-care.
! 141: F12+'+' (keypad plus sign): Increase frame rate (fewer frames displayed).
! 142: F12+'-' (keypad minus sign): Decrease frame rate (more frames displayed).
! 143:
1.1 root 144:
145: Mouse and joystick emulation
146: ============================
147:
148: The X11 (non-DGA) version has one problem: There are two mouse pointers, the
149: X11 mouse pointer and the mouse pointer in the emulator window. You can work
150: that way, but you get confused quickly.
151: The solution in previous (0.6.8 and before) versions of UAE was a small piece
152: of code that looked at the position of sprite 0 on the screen and tried to
153: generate mouse movements in an emulated hardware port. That worked reasonably
154: well, but had several problems.
155: The new solution is to use a small Amiga program which is called "mousehack".
156: You will find this in the "amiga" subdirectory. Put it into the directory that
157: you use for harddisk emulation so that you can run it from the emulator. Then
158: put the command "run >NIL: mousehack" at the top of your startup-sequence. UAE
159: will detect when this program is running and use the improved mouse pointer
160: positioning method. (Don't run this program on old versions of UAE)
161: If the program is not running, you get the old behaviour - almost. By default,
162: the emulator will no longer try to keep Amiga and X mouse pointers at the same
163: position, because that led to problems in the past. You can toggle this
164: behaviour with F12.
165: (If you just added "run mousehack" to your startup-sequence, that would have
166: the effect that the initial CLI window would be impossible to close.
167: Unfortunately, redirecting output to >NIL: disables all error messages that
168: mousehack can give you - so if it does not work, try running it by hand
169: without the >NIL: redirection.)
170:
171: If you find a program in which the mouse pointer does not move at all if you
172: use the X11 version, start that program with mousehack _not_ running
173: (Magnetic Scrolls adventures are known to need this, for example).
174:
175: The SVGAlib and DGA versions are not affected by any of this (and pressing F12
176: exits those versions).
177:
178: If you use Linux and have the joystick driver kernel module, "configure"
179: should automatically enable support for it. UAE calibrates the joystick
180: automatically. Turn it a few times on startup to get the calibration done.
181:
182:
183: Harddisk emulation
184: ==================
185:
186: Please read the appropriate sections in the file "README" on how to use the
187: filesystem emulation. There are a few Unix-specific things about it, though.
188:
189: If you want to execute files located on a native filesystem, they need to have
190: the x permission bit set. That can be done in Unix by "chmod +x file" or in
191: AmigaDOS with "protect file rwed".
192: You should set aside a whole directory tree for AmigaOS files, and not use it
193: from Unix in any way if you can avoid it. Changing permissions/owners,
194: creating symbolic links and doing other stuff that AmigaOS does not know about
195: is a good way to confuse the emulator and the emulated software. E.g. it's
196: possible to have a symlink pointing at a mounted CD-ROM. The emulator would
197: see that as a directory inside which it gets "read only filesystem" errors,
198: and wouldn't know what to do about it. Avoid this sort of thing. It's best to
199: start with an empty harddisk emulation directory and install software there
200: only from within the emulation.
201: The following setup can also lead to problems:
202: -m dh0:/foo -m dh1:/foo/bar
203: Please take care that the filesystems you mount don't overlap each other
204: (another great reason not to use symbolic links within them).
205:
206:
207: Printing
208: ========
209:
210: If you give UAE the "-p lpr" option, output for the parallel port will be
211: piped to lpr, which will in turn print it. You should use the Postscript
212: printer driver on the Amiga side (since UAE relies on the ^D character at
213: the end of the Postscript output).
214: Note that I never tried this myself, so you're on your own.
215:
216:
217: Transferring things over the serial port
218: ========================================
219:
220: There's an easy way to use a null-modem cable without terminal software if
221: you use Linux (and probably other Unices). You can do
222:
223: transdisk >SER: <options>
224:
225: on the Amiga to copy the data directly to the serial port. Before that, do
226:
227: cat /dev/ttyS1 >df0.adf
228:
229: on your Linux box to receive the data (it may be ttyS0 on your system, or
230: another number, depending on which serial port you are using). When the Amiga
231: is done transferring, hit ^C on the PC to interrupt the cat program. To make
232: this work, you need to use the same settings for the serial port on both
233: sides. This is done with the Preferences program on the Amiga (this is split
234: into several programs from Kickstart 2.0 upwards, you'll find a program called
235: "serial" in the Prefs directory of your Workbench disk). On the Linux side,
236: use the stty program. "man stty" will give you the manpage describing how to
237: use it.
238: To be on the safe side, set the speed to a low value (2400 baud). Turn off
239: Xon/Xoff, but enable RTS/CTS.
240: I use the following command myself:
241:
242: stty 19200 parenb -cstopb cread clocal crtscts -istrip -inlcr -icrnl -opost
243: -onlcr -parodd -isig -icanon -iexten raw cs8 </dev/ttyS1
244:
245: which is probably overkill, but you never know :)
246: This maps to 19200 baud, 8 bits, even parity, one stop bit, which you have to
247: set in the Amiga preferences.
248:
249:
250: Using the Linux AFFS filesystem
251: ===============================
252:
253: If you use Linux with a kernel version >= 2.0.7 and version 2.5k of the mount
254: program, you can do
255: mount df0.adf /mnt -t affs -o loop
256: to mount disk image df0.adf at the mount point /mnt. This is much more
257: convenient than using the "readdisk" program.
258:
259: You'll need to enable support for the Amiga filesystem and the loop device
260: when configuring and compiling the kernel (say yes to the "Ask about
261: experimental drivers" question at the start).
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.