![[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 / BeOS|
Return to README CVS log | Up to [UNIX Amiga Emulator] / uae / docs / BeOS |
1.1 root 1: This file documents the details relevant to the BeOS versions of UAE. General
2: information can be found in the file "README"
3:
4: System requirements
5: ===================
6:
7: UAE will run on any System with BeOS PR2/R3.
8:
9:
10: Compilation
11: ===========
12:
13: If you want to rebuild UAE, unpack the source archive to an appropriate
14: directory (e.g. /boot/home). The simple way to proceed is to type "configure;
15: make". After that has completed you should have a working BeOS version
16: of UAE. Ignore warnings if you get them.
17:
18: However, you should probably have a look at some of the compile-time options
19: found in "config.h" before you do this. There are some things you can change
20: there so that the resulting executable will perform better on your machine.
21: Each of the options in that file has a description. You can edit config.h to
22: suit your needs; and then do "configure; make" afterwards.
23:
24:
25: Graphics
26: ========
27:
28: The BeOS version of UAE currently only supports a color depth of 8 bits.
29: You should set the color depth of the workspace you're running UAE in to
30: 8 bits/pixel for maximum speed.
31:
32:
33: Sound
34: =====
35:
36: The sound currently doesn't work very well. You must start UAE with "-S 2"
37: or "-S 3" to get sound.
38:
39:
40: Keyboard
41: ========
42:
43: Some special keys of the Amiga keyboard are mapped as follows:
44:
45: (Amiga) -> (Be)
46: Help -> Insert
47: Amiga -> Alt
48: Alt -> Wind*ws keys
49: Left Alt -> End
50: Right Alt -> Right Control, Page Down
51: '(' (NP) -> Home
52: ')' (NP) -> Page Up
53:
54:
55: Mouse and joystick emulation
56: ============================
57:
58: The BeOS version has one problem: There are two mouse pointers, the
59: X mouse pointer and the Y mouse pointer. You can work that way, but you get
60: confused quickly.
61:
62: The solution in previous (0.6.8 and before) versions of UAE was a small piece
63: of code that looked at the position of sprite 0 on the screen and tried to
64: generate mouse movements in an emulated hardware port. That worked reasonably
65: well, but had several problems.
66:
67: The new solution is to use a small Amiga program which is called "mousehack".
68: You will find this in the "amiga" subdirectory. Put it into the directory that
69: you use for harddisk emulation so that you can run it from the emulator. Then
70: put the command "run >NIL: mousehack" at the top of your startup-sequence. UAE
71: will detect when this program is running and use the improved mouse pointer
72: positioning method (don't run this program on old versions of UAE).
73:
74: If the program is not running, you get the old behaviour - almost. By default,
75: the emulator will no longer try to keep Amiga and BeOS mouse pointers at the same
76: position, because that led to problems in the past. You can toggle this
77: behaviour with F12.
78:
79: (If you just added "run mousehack" to your startup-sequence, that would have
80: the effect that the initial CLI window would be impossible to close.
81: Unfortunately, redirecting output to >NIL: disables all error messages that
82: mousehack can give you - so if it does not work, try running it by hand
83: without the >NIL: redirection.)
84:
85: If you find a program in which the mouse pointer does not move at all if you
86: use the BeOS version, start that program with mousehack _not_ running
87: (Magnetic Scrolls adventures are known to need this, for example).
88:
89: A joystick in port 1 (the lower port) is supported. UAE calibrates the
90: joystick automatically. Turn it a few times on startup to get the calibration
91: done.
92:
93:
94: Harddisk emulation
95: ==================
96:
97: Please read the appropriate sections in the file "README" on how to use the
98: filesystem emulation. There are a few BeOS-specific things about it, though.
99:
100: If you want to execute files located on a native filesystem, they need to have
101: the x permission bit set. That can be done in the Bash by "chmod +x file" or
102: in AmigaDOS with "protect file rwed".
103:
104: You should set aside a whole directory tree for AmigaOS files, and not use it
105: from BeOS in any way if you can avoid it. Changing permissions/owners,
106: creating symbolic links and doing other stuff that AmigaOS does not know about
107: is a good way to confuse the emulator and the emulated software. E.g. it's
108: possible to have a symlink pointing at a mounted CD-ROM. The emulator would
109: see that as a directory inside which it gets "read only filesystem" errors,
110: and wouldn't know what to do about it. Avoid this sort of thing. It's best to
111: start with an empty harddisk emulation directory and install software there
112: only from within the emulation.
113:
114: The following setup can also lead to problems:
115:
116: -m dh0:/foo -m dh1:/foo/bar
117:
118: Please take care that the filesystems you mount don't overlap each other
119: (another great reason not to use symbolic links within them).
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.