--- uae/docs/README 2018/04/24 16:40:41 1.1.1.4 +++ uae/docs/README 2018/04/24 17:19:47 1.1.1.28 @@ -1,11 +1,21 @@ -This is version 0.7.6 of UAE, the Un*x Amiga Emulator. +This is version 0.8.28 of UAE-core, the UAE Amiga Emulator. + +This package used to be the master copy of UAE; it has somewhat lagged in +development since. It is now intended to be a stable emulator core with a +focus on running old A500 games and demos. Certain extra features, such as +a JIT compiler, will not be added - other packages such as WinUAE or E-UAE +are available which include these patches. + License ======= -UAE is available under the terms of the GNU General Public License. See the -file COPYING that is included in the top level directory of this archive for -details. +UAE is available under the terms of the GNU General Public License. This means +that it is free software: you are welcome to distribute copies of it and/or +modify it, under certain conditions. It also means that there is no warranty +for UAE. +See the file COPYING that is included in the top level directory of this +archive for details. Overview @@ -21,10 +31,10 @@ display, keyboard, harddisk and mouse ta counterparts. UAE was developed for Unixoid systems. Meanwhile, it has been ported to the -Mac, DOS, the BeBox, NextStep, the XFree86/OS2 environment and the Amigas (it -can run itself by now). You should have received several other files along -with this document with details on how to install and use the version for your -operating system. +Mac, DOS, Windows, the BeBox, NextStep, the XFree86/OS2 environment and the +Amigas (it can run itself by now). You should have received several other +files along with this document with details on how to install and use the +version for your operating system. This section is just what it says: an overview. Please read _all_ of this file, especially if you have problems. UAE has many, many features and @@ -48,21 +58,21 @@ Features This version of UAE emulates: -- An Amiga 500 Computer, with 68000 or 68020 CPU (68020 includes 68881 FPU) +- A 68000, 68010 or 68020 CPU, optionally a 68881 FPU - OCS Graphics Chipset, plus big blits from the ECS Chipset -- Up to 2MB Chip RAM and up to 8MB Fast RAM, or 8MB Chip RAM without Fast RAM. -- Up to 64MB Zorro III Fast RAM, independent of Chip RAM setting. +- Up to 2MB Chip RAM and up to 8MB Fast RAM, or 8MB Chip RAM without Fast RAM +- Up to 64MB Zorro III Fast RAM, independent of Chip RAM setting (68020 only) - Up to 1MB Slow RAM, for extended compatibility with problem software - Up to 8MB of graphics card memory, usable by software that supports - Picasso 96 compatible graphics cards. -- 4 x 3.5" floppy disk drives (DF0:, DF1:, DF2: and DF3:) -- Hard-disk emulation + Picasso 96 compatible graphics cards +- 4 x 3.5" floppy disk drives (DF0:, DF1:, DF2: and DF3:). It's not possible to + read Amiga disks, so these are emulated with disk files. +- A hard-disk: either a harddisk image file or part of the native filesystem - Joystick support (with option of mapping joystick to numeric keypad) - Mouse support - Ability to run in various screen modes (for better display quality or better speed) -- Full sound support, consisting of 4 x 8bit channels (mixed into one, so - output is mono for now). +- Full stereo sound support, consisting of 4 x 8bit channels - Beta parallel and serial port support - some other things which don't work well enough to mention them here... @@ -75,8 +85,6 @@ Not emulated: - An MMU (part of 68030/040 CPUs except those that Commodore used). This means you can't use virtual memory systems or real operating systems like Linux or BSD. -- The AGA chipset (A4000/A1200). This chipset has enhanced capabilites for - up to 256 colors in all resolutions. - Serial port emulation exists but doesn't work too well. Since the PC floppy controller can't read Amiga disks (yes, that's a fact), @@ -119,152 +127,230 @@ Invoking UAE First, read the system-specific documents for information how to set up UAE. You should have an executable program called "uae". You can simply execute it, -but you can also optionally give it one or more of the following options: +but you can also optionally give it one or more of the following parameters: + + -h : Print out a help text. + -f file : Load a configuration file + -s opt=val : Set the emulator's option "opt" to value "val". + +Configuration files consist of several lines of the form "opt=val", just as +with the "-s" parameter. You can use the following options with the "-s" +option, or in a config file. +[Here, "=n" means the option takes a number as value. "=bool" means the option +takes a value of either "yes" or "no" (or "true", "false", or abbreviations of +any of these). There are other classes as well.] General options: - -h : Give help on the options. - -A n : Set emulator accuracy to n. The default is n = 2, which means the - emulator will try to be as accurate as possible. This no longer - does much in this version, and I'll probably remove it. - -f n : Sets the frame rate to 1/n. Only every nth screen will be drawn. - -a : Add no expansion devices. This will disable fastmem and harddisk - emulation, but some extremely badly-written games may need this. - (Kickstart 1.2 needs it, too) - -l lang : Set the keyboard language. Currently, the following values can be - used for lang: "us" for U.S. keyboard (default), "se" for swedish, - "fr" for french, "it" for italian, "es" for spanish, or "de" for - german keyboard. - This setting only affects the X11 version. - -0 file : Try to use file as diskfile for drive 0 instead of df0.adf. - The options -1, -2 and -3 also exist for the other drives. - -r file : Use file instead of kick.rom as Kickstart image. - -J xy : Specify how to emulate joystick port 0 (x) and 1 (y). Both x and y - can be one of the following characters: 0 = joystick 0, 1 = - joystick 1, M for mouse, and a, b or c stand for various keyboard - replacements (a is the numeric pad with '0' as fire button, b the - cursor keys with right control as fire button and c is T/F/H/B with - Alt as fire button. - The default is "-J M0" (mouse and joystick as usual) - -G : Disable the user interface (if present). - -n specs: Set blitter emulation. "specs" is a string of characters. If it - contains a "3", the blitter will use 32 bit operations where that - seems profitable (note that this will cause bus errors on most - RISC machines). If you specify "i", all blits will finish - immediately, which can be nice for speed. To enable both options, - say "-n 3i" - -w n : Set CPU emulation speed to n. The default value is 4; higher values - will give the custom chip emulation a higher priority over the CPU, - but some programs crash if this is higher than 4. Setting it to 1 - is a good way to make the emulator run slower on machines which are - too fast. - -C specs: Controls how the CPU is emulated. The first letter must be '0' for - 68000 emulation, '1' for 68010, '2' for 68020 or '3' for - 68020 + 68881. It can be followed by a 'c', which enables a slower - but more compatible version of 68000 emulation, or by an 'a', which - enables a 24 bit address space for 68020 emulation. Normally you - don't want either; use the more compatible emulation if some game or - demo does not work. The 24 bit address space option appears to be - necessary for some Kickstart ROMs, so try that if things don't work - at all. +accuracy=n [default=2] + Set emulator accuracy to n. The default is n = 2, which means the + emulator will try to be as accurate as possible. This no longer + does much in this version, and I'll probably remove it. +framerate=n [default=1] + Sets the frame rate to 1/n. Only every nth screen will be drawn. Using a + higher value can speed up the emulator, at the expense of graphics quality. +autoconfig=bool [default=yes] + If this is enabled, all expansion devices provided by the emulation will be + automounted. You should only disable this if you have a Kickstart ROM + earlier than 1.3 which can't cope with this. Some badly written games and + demos might also be incompatible with this. +kbd_lang=lang [default=us] + Set the keyboard language. Currently, the following values can be used: "us" + for U.S. keyboard (default), "se" for swedish, "fr" for french, "it" for + italian, "es" for spanish, "dk" for danish, or "de" for german keyboard. + This setting only affects the X11 version. +floppy0=file [default=df0.adf] + Try to use the specified file as diskfile for drive 0 instead of df0.adf. + The options floppy1, floppy2, and floppy3 also exist. +kickstart_rom_file=file [default=kick.rom] + Use the specified file instead of kick.rom as Kickstart image. + You can also use an 8k sized A1000 boot ROM. The emulator will detect it + by its small size and behave like an A1000. +kickstart_key_file=file [default=none] + For some strange licensing reasons, Cloanto had to encrypt the ROM images + they ship with the Amiga Forever package. This option lets you select the + key file; this is only necessary if you are using one of the ROMs from + Amiga Forever. +joyport0=mode [default=mouse] + Specify how to emulate joystick port 0. You can use "mouse", "joy0", or + "joy1" to use the corresponding input devices of your machine, or you can + select several different keyboard replacements for a joystick: + "kbd1" for the numeric pad. '0' is the fire button. Three keys on the + numeric pad act as autofire toggle: '.' (or ',' depending on your + keyboard language), Enter and the division key. + "kbd2" for the cursor keys with right control key as fire button and the + right shift key as autofire toggle + "kbd3" for T/F/H/B with the left Alt key as fire button and the left Shift + key as autofire toggle. + The autofire toggle keys will turn on autofire (25 shots per second), it + will stay enabled until you hit the autofire toggle again. +joyport1=mode [default=joy0] + Like joyport0, but for the Amiga's joystick port 1. +use_gui=state [default=yes] + If enabled, show a user-interface that enables changing these options at + run-time. Possible settings are "no", "yes" and "nowait". If "nowait" is + used, the GUI will be shown at program startup, but the emulator will also + start immediately without waiting for the user to change any of the + settings. +immediate_blits=bool [default=no] + If enabled, all blits will finish immediately, which can be nice for speed, + but may cause incompatibilities. +collision_level=level [default=sprites] + This can have a value of "none", "sprites", "playfields", or "full". If + set to "sprites", the emulator will only compute collisions between sprites. + If set to "playfields", it will additionally compute collisions between + sprites and the background. This is much slower and used only rarely. When + "full" level is selected, collisions of the background with itself are also + computed. This is also used very rarely, and makes the emulator even slower. + Using "sprites" or "none" will almost always be enough. +cpu_speed=speed [default=4] + This can have a value of "real", "max", or an integer between 1 and 20. + "real" will try to give the CPU emulation exactly as many cycles, relative + to the other chips, as on a real A500. "max" will try to give you the + maximum CPU emulation speed achievable on your machine. Numeric values + specify a fixed relation between CPU and custom chip emulation, where lower + values prioritize CPU emulation, while higher values prioritize custom chip + emulation. +finegrain_cpu_speed=speed + Like cpu_speed, but only accepts numeric values. These numeric values are + equivalent to the ones given to cpu_speed multiplied by 512. This means + that "cpu_speed=2" and "finegrain_cpu_speed=1024" have the same effect. + Using this option you can give the CPU emulation a much higher priority by + using small values. +cpu_type=type [default=68000] + Controls which CPU is emulated. This can be "68000", "68010", "68020" or + "68020/68881". In some cases, you may need to use "68ec020" or + "68ec020/68881" to emulate a crippled variant of the 68020 that has only a + 24 bit address bus. Some software, including some Kickstart versions, does + not work with a normal 68020 that has a 32 bit address bus. + Careful: using an "ec" variant has harmful side effects, and should be + disabled unless absolutely needed (you lose Z3 memory and Picasso + emulation). +cpu_compatible=bool [default=no] + If enabled, a slower but slightly more accurate variant of the CPU emulation + will be used. This is needed for some types of copy protection, among other + things. This is only meaningful for a CPU type of "68000". +nr_floppies=n [default=4] + The emulator will emulate this many external floppy drives. Some very old + games apparently have problems if this is larger than 1, but for all normal + programs the default is good enough. Emulating external devices (harddisk, CD-ROM, printer, serial port): - -M VOLUME:path - -m VOLUME:path - Mount the unix file system at "path" as an Amiga filesystem with - volume name "VOLUME:". For example, "-M sound:/usr/amiga/modules" - If you use -M instead of -m, the volume will be read only. Use this - for mounting CD-ROMs. See below. - -W secs:heads:nr:file - Mount the hardfile "file" as an emulated harddisk, using a geometry - of "secs" sectors per track, "heads" surfaces and "nr" reserved - blocks. Can be abused to mount floppy images. See below. - -p cmd : Enable printing. See below. - -I dev : Use "dev" as serial device (e.g. /dev/ttyS1 on Linux). +filesystem=access,volume:path [default=no filesystems mounted] + Mount the host's file system at "path" as an Amiga filesystem with volume + name "VOLUME:". "access" can be either "ro" (for readonly), or "rw" (for + read-write). If you want to mount a CD-ROM, you should use a readonly + mount. You can mount multiple file systems. + See below. +hardfile=access,secs,heads,reserved,bsize,file [default=no hardfiles mounted] + Mount the hardfile "file" as an emulated harddisk, using a geometry of + "secs" sectors per track, "heads" surfaces and "nr" reserved blocks. + Each sector should have "bsize" bytes. This can be abused to mount + floppy images. You can mount multiple hardfiles. + See below. Sound options: - -S specs: If your version of UAE supports sound, this option allows you to - tell the emulator how to produce sound. The specs parameter is - made up as follows: - n:stereo:bits:frequency:minimum buffer size:maximum buffer size - You can use one of the following values for "n": - n = 0: No proper sound emulation at all. May be incompatible - (unlikely). This is the default. - n = 1: Emulate the sound hardware, but don't output sound. May be - needed for compatibility, but can be much slower - n = 2: Emulate the sound hardware and output sound. Recommended. - n = 3: Emulate the sound hardware _exactly_. I don't think you'll - hear a difference. SIDmon modules will be emulated - correctly, but painfully slow with this setting. - Unfortunately, this may also be needed to get some programs - to work (AIBB, for example). - Use either 's' or 'm' to set the "stereo" value. - For "bits", common values are 8 (low quality) or 16 (high quality). - For "frequency", common values are 22050 or 44100. The quality of - sound output increases with the frequency. - You can specify the minimum and maximum size of the sound buffer. - Smaller buffers reduce latency. - You don't need to specify all of the options, you can stop after - each subpart. Examples: "-S0" (sound off), "-S2:s" (sound on, - stereo), "-S3:m:16:44100" (complete emulation, mono, 16 bits, - 44100 Hz). - Note: high quality sound requires a lot of computing power, so try - with different settings if your machine is not fast enough. +sound_output=type [default=none] + The type of sound output can be "none" (no sound at all), "interrupts" + (emulated for the internal side effects that can be noticed by programs, + but no sound output), "normal" (emulated, and sound output), "exact" (a + slightly more accurate emulation that may be necessary in some cases, but + can also be slower). +sound_channels=type [default=mono] + Can be "mono", "stereo", or "mixed". If set to "stereo", the left and right + channels produce the same output as on a real Amiga - two of the four audio + channels are audible on the left, and the other two on the right. This is + exactly what you want, except if you're using headphones - having the sound + split so strictly can lead to a strange listening experience at times. This + is what "mixed" is trying to solve: it mixes the left channel with a low + volume into the right channel and vice versa. (This mixing operation loses + a bit of precision in the output). +sound_bits=n [default varies across UAE versions on different OS types] + Common values are 8 (low quality) or 16 (high quality) +sound_frequency=n [default varies across UAE versions on different OS types] + Common values are 22050 or 44100. The quality of sound output increases with + the frequency. +sound_min_buff=n +sound_max_buff=n [default varies across UAE versions on different OS types] + You can specify the minimum and maximum size of the sound buffer. + Smaller buffers reduce latency. Usually only the minimum size is used. +sound_interpol=type [default none] + Normally, sound samples are output exactly as they are computed, without + any post-processing. This can generate errors in the sound output when the + output frequency isn't an even multiple of the input frequency. These + errors are usuable perceived as a high-frequency noise. + There are currently two types of interpolation available, both under + experimentation. You can use either "rh" or "crux" as value for this + option. Note that no interpolation is supported for 8 bit output; you need + to use 16 bit output to hear a difference. If you have any comments about + the effects of either method on audio quality, I'd be very interested to + hear them. Memory options: - -s n : Emulate n*256K slow memory at 0xC00000. Some demos/games need this. - -F n : Emulate n megabytes of fast memory as an expansion board. - -Z n : Emulate n megabytes of Zorro III fast memory as an expansion board. - -c n : Emulate n*512K chip memory. The default is 2MB chipram. Some very - broken programs need "-c 1" to work properly. The largest legal - value is "-c 16", which means 8MB chip memory. - -4 n : Usually, UAE uses a 24 bit address space when it emulates a 68000, - and a 32 bit address space when it emulates a 68020. If n is 1, - this option turns on a 24 bit address space in 68020 emulation. It - appears to be necessary for some Kickstart images. Careful: this - option has harmful side effects, and should be disabled by default. +bogomem_size=n [default=0] + Emulate n*256K slow memory at 0xC00000. Some demos/games need this. +fastmem_size=n [default=0] + Emulate n megabytes of fast memory as an expansion board. +z3mem_size=n [default=0] + Emulate n megabytes of Zorro III fast memory as an expansion board. +chipmem_size=n [default=4] + Emulate n*512K chip memory. Some very broken programs need specific amounts + of chip mem to work properly. The largest valid value is 16, which means 8MB + chip memory. + +Display options: +gfx_width=n [default=800] + Use a window that is n pixels wide for displaying the Amiga screen. +gfx_height=n [default=300] + Use a window that is n pixels high for displaying the Amiga screen. +gfx_lores=bool [default=no] + Enable this option if you use a very small window width (320 to 400 pixels) + to shrink the display horizontally. +gfx_linemode=type [default=scanlines] + The type can be none (every line is drawn once), "double" (every line is + drawn twice), and "scanlines" (every line is drawn once, but the image is + stretched vertically by inserting a black line every other line to simulate + the display on an old monitor). + The "double" mode gives best results, but slows down the emulation quite a + lot. Don't use the "none" mode if you want a decent interlace emulation. + If you use "double" or "scanlines", your window needs to be twice as high + as when using the "none" mode. +gfx_correct_aspect=bool [default=none] + Try to fit the image into the specified window dimensions by leaving out + certain lines. Useful if you want to fit a 640x512 Amiga display in a + 640x480 window. +gfx_center_vertical=bool [default=no] +gfx_center_horizontal=bool [default=no] + If you use a smaller window than 800x300 (400x300 with "gfx_lores" option or + 800x600 with a gfx_linemode other than "none"), not all parts of the display + will fit on the screen. By enabling the necessary centering options, you can + ask the emulator to try and move the screen contents so that the relevant + parts are displayed. If you are unlucky, this can cause the contents to jump + around a bit in certain cases. +gfx_fullscreen_amiga=bool [default=no] + Enable if you want to use the full screen, not a window on the desktop, for + the Amiga display. Some ports (DOS, SVGAlib) always use fullscreen mode. +gfx_fullscreen_picasso=bool [default=no] + Like gfx_fullscreen_amiga, but for the Picasso graphics card display. +gfx_color_mode=mode [default=8bit] + Select a color mode to use. + Color modes: 8bit (256 colors), 15bit (32768 colors), 16bit (65536 colors), + 8bit_dithered (256 colors, with dithering to improve quality), + 4bit_dithered (16 colors, dithered); 32bit (16 million colors) +gfxcard_size=n [default=0] + Emulate a Picasso 96 compatible graphics card with n MB graphics memory. + This requires that you use set the CPU type to "68020" or higher, and that + you do not use 24 bit addressing. Debugging options (not interesting for most users): - -D : Don't start the emulator at once, use the built-in debugger. - -i : Print illegal memory accesses +use_debugger=bool [default=no] + If enabled, don't start the emulator at once, use the built-in debugger. +log_illegal_mem [default=no] + If enabled, print illegal memory accesses -Display options: - -H mode : Select a color mode to use. - -O specs: Select a display mode, see below how the specs parameter is - interpreted. - -U n : Emulate a Picasso 96 compatible graphics card with n MB graphics - memory. - -Color modes: 0 (256 colors, default); 1 (32768 colors); 2 (65536 colors) - 3 (256 colors, with dithering to improve color quality) - 4 (16 colors, dithered); 5 (16 million colors) - -About the "-O" display specs. These consist of the width and height of the -mode, plus optional modifiers. One valid option to pass to UAE would be -"-O 640:300:" which means use a display 640 pixels wide and 300 pixels high, -with no modifiers (nothing after the second ":"). You may specify the -following modifiers: - l: Tell UAE to omit drawing every second pixel horizontally (for "lores" - modes). Example: "-O 320:200:l" - x: Tell UAE to try to fit the image horizontally into the displayed - window. For example, if you have a mode that is 640 pixels wide, and the - displayed image is also 640 pixels wide, the picture may still be - partially invisible because it is displayed too wide to the left or to - the right. With the "x" modifier, UAE tries to prevent this. - You can also specify a capital "X", in that case, UAE tries to be - extremely clever when doing this. - y: The same thing in green, for fitting the image vertically into the - window. (Y also exists) - d: Draw every line twice. This allows interlace mode to be emulated nicely, - but of course you also need a display that is twice as high - c: Correct the aspect. This will omit certain lines of the display to make - it fit better into the screen. Whew. You'll probably have to experiment a little to get a feeling for it. -UAE may choose to ignore and/or refuse some combinations of these two -parameters. Some of these modes may also fail to work on your system. - You can also put these options into a configuration file in your home directory. Simply create ~/.uaerc and put some of these options in it. On non-Unix systems, the file is called uae.rc and should be located in the @@ -446,7 +532,7 @@ If you don't have much RAM and can't fit you can split up the transfer into multiple parts with the "-s" and "-e" parameters. To transfer the disk in four parts, you'd use the following commands: - + transdisk >ram:df0_1.adf -s 0 -e 19 transdisk >ram:df0_2.adf -s 20 -e 39 transdisk >ram:df0_3.adf -s 40 -e 59 @@ -495,7 +581,7 @@ Picasso 96 graphics card emulation ================================== To use this feature, you must select 68020 emulation with a 32 bit address -space. You also need a Kickstart 3.x ROM. +space (i.e. _not_ 68ec020). You also need a Kickstart 3.x ROM. To specify how much graphic memory you want to emulate, use the "-U" option, e.g. "-U 4" for 4 megabytes. Then, you need the Picasso 96 software which @@ -506,6 +592,84 @@ After that is complete, reboot, and you modes from the ScreenModes program. +AHI sound card emulation +======================== + +In the "amiga" subdirectory of the UAE distribution, you will find a "Devs" +directory that contains the necessary files for AHI sound support. This is +at an early stage and will not work very well in this release. It is +included mainly in the hope that someone with a clue about AHI will pick up +this work and finish it properly. + + +Saving and restoring snapshots +============================== + +From version 0.8.17 onwards, the emulator has the capability to save the +current state of the emulation into a "snapshot" file that can be restored +later on. This functionality is available through the GUI on some ports. +It is mainly useful for computer games that either have no save game +feature, or whose save game feature does not work on UAE (often, games try +to save in a non-standard disk format, this can be tricky to emulate). + +There are several restrictions that apply to the save state feature: + + - It is at the moment experimental. It is not guaranteed that the + emulator can correctly restore every snapshot. It is not guaranteed + that future versions of the emulator will be able to restore snapshots + saved by this version. + - The state of the harddisk emulation cannot be saved. This makes it + essentially useless for applications, but remember it's designed for + games. Be careful with games that have been installed to the harddisk. + - Neither ROM contents nor floppy disk contents are saved right now. + + +UAE SCSI device +=============== + +To enable SCSI support, use --enable-scsi-device when running configure. +The emulator provides a uaescsi.device. This device only supports +direct SCSI, which is sufficient to run applications like MakeCD. The +device does not support reading or writing with the normal Exec commands, +so you cannot mount filesystems on it right now. + +The unit numbers of the uaescsi.device follow the Amiga SCSI +conventions: unit number "xyz" maps to the lun y of target z on bus +x. Wide SCSI busses can have targets with numbers larger than 9. In +this case the uaescsi.device pretends that there is another SCSI +bus. To avoid confusion, all available SCSI targets are listed +together with their unit number when starting UAE. Devices cannot be +added while the emulator is running. Reseting it is not sufficient +either for technical reasons. + +The implementation of the uaescsi.device uses cdrecord's libscg as +interface to the native SCSI system. The Linux implementation of this +library used to be included into UAE, but now the library as generated +by the cdrecord source package (ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/) +is used. As the library is not distributed seperately, you will have +to get the whole cdrecord sources, compile it and then make several +header and lib files available to the compiler if (and only if) building +UAE with SCSI support. The script "src/install_libscg" copies the files +required for the libscg in cdrecord 1.8.1. + +Using threads is strongly recommended, because some SCSI commands can +run for extended periods of time and would block the whole emulation +during this time without threads. Use --enable-threads when starting +configure. + +Depending on the hosts capabilities the uaescsi.device may be limited +compared to other Amiga SCSI devices. The Linux kernel by default only +allows 32KB of data per SCSI command and does not always perform SCSI +requests in parallel. + +Setting the chunk size in MakeCD to 30KB is already too much and +causes an IO error -4 (IOERR_BADLENGTH), because the setting is only +used as a guideline. You can work around this by setting the Tooltypes +BUFFER_CHUNK_XXX to 29. On a Pentium II 350MHz with Adaptec UW SCSI +controller on board on-the-fly copying was possible from a Philips +CDD2600 (SCSI) to a Yamaha CRW4416E (IDE) at 4x. + + The UAE_CONTROL program ======================= @@ -517,6 +681,15 @@ with Kick 2.0 and upwards. Copy these tw use for harddisk emulation. They should be self-explanatory. +The timehack +============ + +Another tool in the "amiga" subdirectory, timehack, synchronizes the +emulated Amiga's system time with the host's time every second. This +is useful when the emulation is not done in real-time or is suspended +completely. + + Quick overview of the debugger commands ======================================= @@ -525,18 +698,38 @@ press ^C at any time to enter this debug Each debugger command consists of a single letter and occasionally some parameters. -g: Start execution at the current address. -c: Dump state of the CIA and custom chips. -r: Dump state of the CPU -m
: Memory dump starting at
-d
: Disassembly starting at
-t: Step one instruction -z: Step through one instruction - useful for JSR, DBRA etc. -f
: Step forward until PC ==
-q: Quit the emulator. You don't want to use this command. -M: hunt for sound modules -S
: - save a sound module +g [
] Start execution at the current address or
+c Dump state of the CIA, disk drives and custom registers +r Dump state of the CPU +m
[] Memory dump starting at
+d
[] Disassembly starting at
+t [instructions] Step one or more instructions +z Step through one instruction - useful for JSR, DBRA etc +f Step forward until PC in RAM +f
Add/remove breakpoint +fi Step forward until PC points to RTS/RTD or RTE +fi Step forward until PC points to +fl List breakpoints +fd Remove all breakpoints +f Step forward until <= PC <= +e Dump contents of all custom registers +i Dump contents of interrupt and trap vectors +o <1|2|addr> []View memory as Copper instructions +O Display bitplane offsets +O Offset a bitplane +H Show PC history instructions +M Search for *Tracker sound modules +C Search for values like energy or lifes in games +W
Write into Amiga memory +w
[] + Add/remove memory watchpoints +wd Enable illegal access logger +S Save a block of Amiga memory +s / [] [] + Search for string/bytes +T Show exec tasks and their PCs +h,? Show this help page +q Quit the emulator. You don't want to use this command. Sound @@ -565,17 +758,14 @@ UAE. The new "official" UAE page is located at -http://www.freiburg.linux.de/~uae + http://www.freiburg.linux.de/~uae thanks to Stefan Reinauer who is now maintaining it. There, you will find links to other UAE pages. One which is especially useful is the "UAE Discussion Board" set up by Gustavo Goedert, the address is -http://www.netrunner.com.br/dosuae/uaeboard/index.html - -Not quite as good as a newsgroup due to braindamaged reader software -(Ratscope), but still a blessing. + http://amiga.nvg.org/uaeboard There is supposedly a newsgroup named "alt.emulators.amiga", but I don't get it here. @@ -588,7 +778,12 @@ Petter Schau has written another Amiga e written in x86 assembly and only runs under DOS. It's quite compatible and generally faster than UAE. The Fellow homepage is at -http://www.geocities.com/SiliconValley/Peaks/5244/ + http://www.geocities.com/SiliconValley/Peaks/5244/ + +The homepage of the Disk2FDI project, which allows you to read Amiga floppies +if you have two PC drives, is + + http://fast.emuunlim.com/disk2fdi/ Thanks & Acknowledgements @@ -604,30 +799,44 @@ Special thanks to: - Felix Bardos, whose HRM I "borrowed". - Hetz Ben Hamo mailed Peter Kittel from Commodore asking for permission to give Kick 1.3 away. Unfortunately, the response was negative :-( - - Bruno Coste, Ed Hanway, Alessandro Soldo and Marko Nippula provided - documentation + - Stefan Reinauer, for hosting the UAE Web page after the RWTH decided it's + too dangerous to let students have their own Web pages. + - Bruno Coste, Ed Hanway, Alessandro Soldo and Marko Nippula provided useful + documentation about the Amiga - Fabio Ciucci gets the "Best bug reports" award for his help with the blitter line emulation and other problem areas. - Michael C. Battilana and Cloanto Software, for all their support. - - Julian Eggebrecht of Factor 5, for providing several F5 games. + - Julian Eggebrecht of Factor 5, for providing several F5 games and a lot + of valuable input. + Factor 5 has made several of their classic Amiga games freely + available for download. There are still some good people left in the + world... + - Jens Schönfeld, inventor of the Catweasel controller, donated one + controller card. + - Jürgen Beck and Ralf Steines, maintainers of the Amiga emulation web + site "Back to the Roots" (http://www.back2roots.org) and everyone else + who spends time writing to software companies asking for permission to + distribute old Amiga games. + - all the software companies who allow distribution of their Amiga games on + sites like "Back to the Roots". Authors/Maintainers =================== -My address is (please read the section "Before you send email" below): +My email address is (please read the section "Before you send email" below): -crux@pool.informatik.rwth-aachen.de +bernds_cb1@t-online.de or, via snailmail Bernd Schmidt -Schlossweiherstrasse 14 -52072 Aachen +Toelzer Strasse 27a +81379 Muenchen Germany Email is more likely to be answered, and will definitely be answered much -faster. Please avoid phonecalls if you can. +faster. I won't distribute software, neither PD or commercial. Don't send me floppy disks without at least asking first, you will not get them back. @@ -671,18 +880,23 @@ pOS port: Samuel Devulder Available: Not quite sure yet. Sourcecode: Included in the main source. Should compile OK. - + +OS/2 port: + Pressenna Sockalingasamy + Available: ftp://hobbes.nmsu.edu/pub/os2/apps/emulator/uae2_0810_a1.zip + Sourcecode: working on including it + XFree86/OS2 port: Krister Bergman Available: http://www.kuai.se/~bellman/html/xfreeapps.html Sourcecode: nothing special, apparently the Unix stuff compiles cleanly (?) Win32 port: - Mathias Ortmann - Brian King - Available: http://www.informatik.tu-muenchen.de/~ortmann - http://www.codepoet.com/uae - Sourcecode: we're working on it + Originally: Mathias Ortmann + Currently: Brian King + Available: http://www.codepoet.com/uae + Sourcecode: bits merged into the main source, the rest available from the + URL above. Still trying to merge more of it... Acorn RISC PC port: Peter Teichmann @@ -713,14 +927,8 @@ and the file FAQ contains about every pi try to help people who have questions, but sometimes it takes too much time. Please don't ask for Kickstart ROM files or other copyrighted software. Don't -_send_ me stuff like this either. If you want to send me something else which -is big (>= 50K), ask me before or put it somewhere in Webspace. -If I get 3MB of screen shots or a core dump ("it doesn't work, it generates -this file"), I'm very likely to get extremely angry, I might complain to your -sysadmin, and you might lose your account. Think twice. - -I'm also going to be extremely annoyed if you send email in HTML format. -Fight this disease! +_send_ me stuff like this either. Don't send large attachments, at least not +without asking first. Oh, and another thing: If I promise to do things (like implement new features), and forget about them, pester me. That happens occasionally, it's