![[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 / pOS|
Return to README CVS log | Up to [UNIX Amiga Emulator] / uae / docs / pOS |
1.1 root 1: UAE-0.6.9f
2: pOS version
3:
4: by Samuel Devulder
5: ([email protected])
6:
7: Oct. 1997
8:
9:
10: INTRODUCTION
11: ============
12:
13: This the Amiga port of UAE v0.6.9. UAE is the Un*x Amiga Emulator
14: written by Bernd Schmidt.
15:
16: You should read the README file before this one to know more about uae.
17: (how to use it, command-line options, what is emulated, and so on...).
18:
19: This port features many things. It is build with the help of Geekgadget:
20: GCC, ixemul, ... Thus allowing an easy port of the original unix version
21: to pOS without a lot of modification. It is also based in part on
22: examples of the pOS developer package. I am very gratefull to proDAD for
23: providing me (and other developers) that package.
24:
25:
26: REQUIREMENTS
27: ============
28:
29: This version will work on any machine running at least pOS r26. That
30: version needs ixemul v47.1. UAE needs roughly 6-8Mb of free ram and a
31: fast processor. It has been tested successfully on a A500 OCS with
32: 8Mb of fast ram with a 68030 processor (gvp A530 board) running pOS r27.
33:
34:
35: QUICKSTART
36: ==========
37:
38: To try quickly UAE, insert a bootable disk in df0 that runs on a standard
39: A500 (a demo for example), and type in a pOS shell:
40:
41: > Stack 32000
42: > UAE -L -H2 -S2 -c2 -s2 -f2 -O320:256:XYl -0/dev/df0
43:
44: Then you should see a window open on you pOS workbench with the demo
45: running inside.
46:
47: The emulated amiga with that setup is a standard A500: 512kb chip,
48: 512kb slow fast, sound and full color display.
49:
50:
51: FEATURES
52: ========
53:
54: UAE can display in 8 bits or in truecolor (24 bits). In 8bits, UAE
55: can use a grayscale palette (-H0) or a color palette (-H1). Thoses
56: two modes does not use the dither and thus gives the maximum rendering
57: speed but you loose some colors. You can also activate the truecolor
58: mode (-H2) that will make UAE use all of the 4096 colors ECS can give.
59: In that case, UAE will automatically dither the output if necessary
60: thanks to pOS RTG drivers.
61:
62: If you use the -L option, UAE will try to only update the needed part
63: of the window. That will propably speed up things a little bit
64: especially in truecolor mode.
65:
66: The sound can be emulated in this version. But Amigas Hardware is too
67: slow for it to be really usefull. On my amiga, UAE produces one second
68: of sound every twenty seconds in Sanity's Interference demo. Thus, An
69: amiga which is around 20 times faster as an A4000 would be nice. I
70: wonder what will this version of UAE give when recompiled for a PPC
71: running pOS (please tell me if you succed to produce such an executable).
72:
73: The CPU emulation is speed up by using ASM code to compute flags
74: directly from the native CPU on m68K and x86 targets. For risc machines
75: as the PPC, it seems that asm hacks are not usefull, so the generic
76: C code is used.
77:
78: You can insert disks by pressing CTRL-LALT-F1, CTRL-LALT-F2,
79: CTRL-LALT-F3, or CTRL-LALT-F4. F1 corresponds to drive DF0, F2 to DF1,
80: and so on. Alternatively you can simply eject a disk by pressing
81: LSHIFT in addition of the above keys.
82:
83: You can mount native partitions using the -m option. Be sure to use unix
84: convention when giving a path to UAE. For exemple do not do
85:
86: CLI> uae -m boot:dh0:path -0 /disks/df0.adf
87:
88: but rather
89:
90: CLI> uae -m boot:/dh0/path -0 ../disks/df0.adf
91:
92: This is not a bug, but an ixemul.library feature. You can access native
93: disks by specifying /dev/<device-name>[.device]/unit or /dev/df<num>
94: after -0. For example you can do "uae -0 /dev/df0" or "uae -0
95: /dev/pTrackdisk.device/0" to use the internal floppy drive as drive 0
96: under UAE. Under the file requester, select the DEV: assign to access
97: disk-devices.
98:
99: You can reset the emulator by pressing CTRL-ALT-DEL in UAE's window. I
100: guess it reminds you about something :^) You can enter debug mode by
101: pressing ^C or ^D in the cli/shell window or by pressing the close-gadget
102: of UAE's window.
103:
104: The F12 key of the X11 version of uae is simulated by pressing
105: CTRL-SHIFT-ALT-F10 simultanemously. This toggles the mouse emulation
106: mode and is needed for some games or demos when you find that the
107: mouse emulation does not work well.
108:
109: You can toggle on/off the screen rendering to speed up the sound
110: processing by pressing CTRL-SHIFT-ALT-F9. You can also "iconify" UAE
111: by pressing on the gagdet next to the depth-gadget. When uae is
112: iconified, the display is automatically switch off, speeding the
113: emulation a little bit (be you won't be able to see it as the window
114: is shrinked :-)
115:
116: If UAE does not find a rom-file, it'll use the ROM located at address
117: $F80000 - $FFFFFF. Thus, you need not grab it and that will spare you
118: some disk space. You can disable this feature by creating the
119: environment variable "USE_UAE_ERSATZ", in which case UAE will try to
120: emulate rom calls using a built'in pseudo kickstart. That feature will
121: probably disappear when pOS will be able to run on other hardwares than
122: amiga machines.
123:
124: If you setenv AUDIONAME <filename>, then uae will put the sound-samples
125: into <filename>. Using that you can grab soundtracks very easily :-).
126: Notice that <filename> can have two "%d". The first one will be replaced
127: by the frequency (see the -R flag for UAE) and the second one will be
128: replaced by the buffer size (-B option).
129:
130: *NEW*: If under uae you run "amiga/uae_rcli", then you'll be able to
131: run AmigaOS commands in UAE just by dropping the icon of the executable
132: on UAE's window.
133:
134:
135: MISSING FEATURES
136: ================
137:
138: The joystick can't be used: use the -J flag instead.
139:
140: No AREXX port available to use an external GUI: use the built-in
141: pseudo GUI (did you see the leds in the dragbar ? :-)
142:
143: No mouse-pointer masking.
144:
145:
146: HOW TO (RE-)BUILD UAE
147: =====================
148:
149: You should be familiar with unix programming to build UAE. For the
150: moment it can only be cross-compiled under AmigaOS as apparently
151: there is no "ln -s" or "Makelink" support in pOS r27 (That will
152: probably change in future releases).
153:
154: If you wish to (re-)build uae, you need to have GeekGadget correctly
155: installed (see ftp://ftp.ninemoons.com/pub/gg/). Not all part of
156: Geek Gadget are needed, but be sure to have gcc2.7.2.1, binutils,
157: autoconf, awk, ...
158:
159: To compile for pOS you should setenv CFLAGS "-D__POS__" as it is
160: that define that is used to find the target system. Alternatively,
161: you can simply add "--target=p.os" when launching ./configure.
162:
163: The default Makefile provided is for a MC68030 microprocessor. If you
164: wish to have a Makefile tuned for your CPU (and fpu), just type "sh -c
165: configure". If the configure script is correcly written (or with some
166: extra tuning in Makefiles), UAE should also compile for a x86 or PPC
167: architecture if you are using a special version of GCC tuned to
168: cross-compilation (the cpu specific parts of uae are dissociated from
169: OS specific things). I can't wait trying UAE for pOS on x86 or PPC
170: plateforms :-)
171:
172: Once your Makefile is generated (if needed), you can modify the file
173: "config.h" to suit your needs. I suggest you to define DONT_WANT_SOUND
174: in "config.h". That will speed up the emulation (sound emulation slows
175: down the speed by roughly 10%).
176:
177: When you'll have configured uae correctly, type "make" in a shell. Then
178: one hour and a half later you'll get the uae executable (it might be less
179: if you have a *real fast* m68k machine, but don't expect less that 15
180: minutes). I know it's slow, but Amigas are slow (even those with 68060
181: are not that fast, by today's standards ;-).
182:
183: NOTE: I had reports that gcc complains and fail to compile cpu_f?.s.
184: This is caused by a problem with perl5 and src/md-amiga/cpuopti.
185: To avoid this you can try to use perl4 instead of perl5, or uncomment
186: the lines in the beginning of src/md-68k/cpuopti. Unfortunately, UAE
187: will run slower as the asm files won't have an extra optimization pass.
188:
189: NOTE 2: With some fiddling, you can succeed in compiling UAE with the
190: nixpos link-library. That library will give you an executable that can
191: run without ixemul. But then you'll loose the ability of uae to produce
192: statistics when you enter 'c' in its debugger. You'll also have to enter
193: a mandatory space between flags and arguments in the makefile.
194:
195:
196: REMARKS OR BUG-REPORTS
197: ======================
198:
199: You can send me your remarks and bug-report to:
200:
201: [email protected]
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.