![[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|
Return to README CVS log | Up to [UNIX Amiga Emulator] / uae / docs |
1.1.1.9 ! root 1: This is version 0.8.9 of UAE, the Un*x Amiga Emulator. 1.1.1.5 root 2: 3: Versions numbered 0.8.x are beta versions, to be used for development only. 4: If you are only a user of UAE, you are better off using the latest 0.7.x 5: version or waiting for 0.9.0. 6: 1.1 root 7: 1.1.1.3 root 8: License 9: ======= 1.1 root 10: 1.1.1.5 root 11: UAE is available under the terms of the GNU General Public License. This means 12: that it is free software: you are welcome to distribute copies of it and/or 13: modify it, under certain conditions. It also means that there is no warranty 14: for UAE. 15: See the file COPYING that is included in the top level directory of this 16: archive for details. 1.1 root 17: 1.1.1.9 ! root 18: The SCSI code distributed with UAE is also available under the terms of the ! 19: GPL and was written by J. Schilling. ! 20: 1.1 root 21: 22: Overview 23: ======== 24: 1.1.1.2 root 25: An emulator is a program which enables you to run software for a machine 26: which has non-native hardware and a non-native operating system, on your 27: computer. UAE allows you to run most of the available Amiga software. It is a 28: software emulation, meaning that no extra or special hardware is needed to do 29: this. The hardware of an Amiga is emulated accurately, so that Amiga software 30: is tricked into thinking it is running on the real thing, with your computer's 31: display, keyboard, harddisk and mouse taking the parts of their emulated 32: counterparts. 1.1 root 33: 34: UAE was developed for Unixoid systems. Meanwhile, it has been ported to the 1.1.1.2 root 35: Mac, DOS, the BeBox, NextStep, the XFree86/OS2 environment and the Amigas (it 36: can run itself by now). You should have received several other files along 37: with this document with details on how to install and use the version for your 38: operating system. 1.1 root 39: 40: This section is just what it says: an overview. Please read _all_ of this 1.1.1.2 root 41: file, especially if you have problems. UAE has many, many features and 42: equally many configuration options. If you don't know about them, it's likely 43: that UAE doesn't work for you, or doesn't work as good as it could. 44: 45: Please read also the file "FAQ" which contains some Frequently Asked 1.1.1.3 root 46: Questions (and even the answers!) You should also look for a document 47: describing the specific port of UAE to the operating system you are using, 48: for example "BeOS/README" or "DOS/README". 1.1.1.2 root 49: 50: People have complained that the UAE documentation contains only "weird jargon". 51: Sorry about this. Despite what MessySoft and Tomato tell you, computer 52: programs aren't always easy to use. UAE does require some assistance from you, 53: and therefore you should at least understand a bit about computers. After all, 54: you are an Amiga fan, so you should know what a Workbench is, don't you think? 1.1 root 55: 56: 1.1.1.2 root 57: Features 58: ======== 59: 60: This version of UAE emulates: 1.1 root 61: 1.1.1.5 root 62: - A 68000, 68010 or 68020 CPU, optionally a 68881 FPU 1.1.1.2 root 63: - OCS Graphics Chipset, plus big blits from the ECS Chipset 1.1.1.5 root 64: - Up to 2MB Chip RAM and up to 8MB Fast RAM, or 8MB Chip RAM without Fast RAM 65: - Up to 64MB Zorro III Fast RAM, independent of Chip RAM setting (68020 only) 1.1.1.3 root 66: - Up to 1MB Slow RAM, for extended compatibility with problem software 67: - Up to 8MB of graphics card memory, usable by software that supports 1.1.1.5 root 68: Picasso 96 compatible graphics cards 69: - 4 x 3.5" floppy disk drives (DF0:, DF1:, DF2: and DF3:). It's not possible to 70: read Amiga disks, so these are emulated with disk files. 71: - A hard-disk: either a harddisk image file or part of the native filesystem 1.1.1.2 root 72: - Joystick support (with option of mapping joystick to numeric keypad) 73: - Mouse support 74: - Ability to run in various screen modes (for better display quality or 75: better speed) 1.1.1.5 root 76: - Full stereo sound support, consisting of 4 x 8bit channels 1.1.1.3 root 77: - Beta parallel and serial port support 1.1.1.2 root 78: - some other things which don't work well enough to mention them here... 79: 80: 81: Requirements (IMPORTANT! READ THIS!)/Limitations 82: ================================================ 83: 84: Not emulated: 1.1.1.3 root 85: - Sprite to playfield collisions (sprite to sprite collisions work) 86: - An MMU (part of 68030/040 CPUs except those that Commodore used). This means 1.1.1.2 root 87: you can't use virtual memory systems or real operating systems like Linux 88: or BSD. 89: - The AGA chipset (A4000/A1200). This chipset has enhanced capabilites for 90: up to 256 colors in all resolutions. 1.1.1.5 root 91: - Serial port emulation exists but doesn't work too well (someone tell me when 92: that's no longer true, I don't use it). 1.1.1.2 root 93: 94: Since the PC floppy controller can't read Amiga disks (yes, that's a fact), 95: floppy access has to be emulated differently: Floppies are emulated by means 96: of disk files that contain a raw image of the floppy disk you want to emulate. 97: A disk file is an image of the raw data on an Amiga floppy disk, it contains 98: 901120 bytes (880K), which is the standard capacity of an Amiga disk. 99: 100: To actually run the program, you'll need to install the ROM image from your 101: Amiga. You can't run UAE if you don't have this image. It is not included 102: because it is copyrighted software. Don't ask me to send you one. I won't. 103: If you don't have an Amiga and still want to use UAE, you'll have to buy an 104: Amiga or at least the system software (ROM + Workbench) first. 105: The Kickstart image can have a size of either 256K or 512K. It must be named 106: "kick.rom" by default. 107: 108: Read the section "tools" below for information how to create ROM images and 109: disk files. 1.1 root 110: 111: If you don't have a Kickstart file, you may still be able to boot some games 112: and demos. The emulator includes some primitive bootstrap code that will try 113: to read and execute the bootblock of the diskfile you are using, and if that 114: bootblock only uses the one or two Kickstart functions that are supported by 115: the "replacement Kickstart", your program will boot. Don't expect too much, 116: though. 117: 1.1.1.2 root 118: You'll also need some other software to run - why else would you want to 119: emulate an Amiga? There are several ways to make the software accessible to 1.1.1.3 root 120: UAE, either with disk image files or with a harddisk emulation. You should 121: make an image of your Amiga's Workbench disk and install it as "df0.adf" 122: (adf = Amiga Disk File) when you use UAE for the first time. More about how 123: to create these files in the chapter "Transferring software" 124: 125: To use Picasso96 emulation, you need the Picasso96 libraries, which are also 126: not included. They can be obtained (e.g.) from Aminet. 1.1 root 127: 128: 129: Invoking UAE 130: ============ 131: 1.1.1.2 root 132: First, read the system-specific documents for information how to set up UAE. 133: You should have an executable program called "uae". You can simply execute it, 1.1.1.7 root 134: but you can also optionally give it one or more of the following parameters: 135: 136: -h : Print out a help text. 137: -f file : Load a configuration file 138: -s opt=val : Set the emulator's option "opt" to value "val". 139: 140: Configuration files consist of several lines of the form "opt=val", just as 141: with the "-s" parameter. You can use the following options with the "-s" 142: option, or in a config file. 143: [Here, "=n" means the option takes a number as value. "=bool" means the option 144: takes a value of either "yes" or "no" (or "true", "false", or abbreviations of 145: any of these). There are other classes as well.] 1.1 root 146: 147: General options: 1.1.1.7 root 148: accuracy=n [default=2] 149: Set emulator accuracy to n. The default is n = 2, which means the 150: emulator will try to be as accurate as possible. This no longer 151: does much in this version, and I'll probably remove it. 152: framerate=n [default=1] 153: Sets the frame rate to 1/n. Only every nth screen will be drawn. Using a 154: higher value can speed up the emulator, at the expense of graphics quality. 155: autoconfig=bool [default=yes] 156: If this is enabled, all expansion devices provided by the emulation will be 157: automounted. You should only disable this if you have a Kickstart ROM 158: earlier than 1.3 which can't cope with this. Some badly written games and 159: demos might also be incompatible with this. 160: kbd_lang=lang [default=us] 161: Set the keyboard language. Currently, the following values can be used: "us" 162: for U.S. keyboard (default), "se" for swedish, "fr" for french, "it" for 163: italian, "es" for spanish, or "de" for german keyboard. 164: This setting only affects the X11 version. 165: floppy0=file [default=df0.adf] 166: Try to use the specified file as diskfile for drive 0 instead of df0.adf. 167: The options floppy1, floppy2, and floppy3 also exist. 168: kickstart_rom_file=file [default=kick.rom] 169: Use the specified file instead of kick.rom as Kickstart image. 170: joyport0=mode [default=mouse] 171: Specify how to emulate joystick port 0. You can use "mouse", "joy0", or 172: "joy1" to use the corresponding input devices of your machine, or you can 173: select several different keyboard replacements for a joystick: "kbd1" for 174: the numeric pad with '0' as fire button, "kbd2" for the cursor keys with 175: right control as fire button and c is T/F/H/B with Alt as fire button. 176: joyport1=mode [default=joy0] 177: Like joyport0, but for the Amiga's joystick port 1. 178: use_gui=bool [default=yes] 179: Show a user-interface that enables changing these options at run-time. 180: 32bit_blits=bool [default=no] 181: If enabled, the blitter emulation will use 32 bit operations where that 182: seems profitable (note that this will cause bus errors on most RISC 183: machines) 184: immediate_blits=bool [default=no] 185: If enabled, all blits will finish immediately, which can be nice for speed, 186: but may cause incompatibilities. 187: cpu_speed=speed [default=4] 188: This can have a value of "real", "max", or an integer between 1 and 20. 189: "real" will try to give the CPU emulation exactly as many cycles, relative 190: to the other chips, as on a real A500. "max" will try to give you the 191: maximum CPU emulation speed achievable on your machine. Numeric values 192: specify a fixed relation between CPU and custom chip emulation, where lower 193: values prioritize CPU emulation, while higher values prioritize custom chip 194: emulation. 195: cpu_type=type [default=68000] 196: Controls which CPU is emulated. This can be "68000", "68010", "68020" or 197: "68020/68881". In some cases, you may need to use "68ec020" or 198: "68ec020/68881" to emulate a crippled variant of the 68020 that has only a 199: 24 bit address bus. Some software, including some Kickstart versions, does 200: not work with a normal 68020 that has a 32 bit address bus. 201: Careful: using an "ec" variant has harmful side effects, and should be 202: disabled unless absolutely needed (you lose Z3 memory and Picasso 203: emulation). 204: cpu_compatible=bool [default=no] 205: If enabled, a slower but slightly more accurate variant of the CPU emulation 206: will be used. This is needed for some types of copy protection, among other 207: things. This is only meaningful for a CPU type of "68000". 1.1 root 208: 1.1.1.3 root 209: Emulating external devices (harddisk, CD-ROM, printer, serial port): 1.1.1.7 root 210: filesystem=access,volume:path [default=no filesystems mounted] 211: Mount the host's file system at "path" as an Amiga filesystem with volume 212: name "VOLUME:". "access" can be either "ro" (for readonly), or "rw" (for 213: read-write). If you want to mount a CD-ROM, you should use a readonly 214: mount. You can mount multiple file systems. 215: See below. 216: hardfile=access,secs,heads,reserved,bsize,file [default=no hardfiles mounted] 217: Mount the hardfile "file" as an emulated harddisk, using a geometry of 218: "secs" sectors per track, "heads" surfaces and "nr" reserved blocks. 219: Each sector should have "bsize" bytes. This can be abused to mount 220: floppy images. You can mount multiple hardfiles. 221: See below. 1.1 root 222: 223: Sound options: 1.1.1.7 root 224: sound_output=type [default=none] 225: The type of sound output can be "none" (no sound at all), "interrupts" 226: (emulated for the internal side effects that can be noticed by programs, 227: but no sound output), "normal" (emulated, and sound output), "exact" (a 228: slightly more accurate emulation that may be necessary in some cases, but 229: can also be slower). 230: sound_channels=type [default=mono] 231: Can be "mono" or "stereo". 232: sound_bits=n [default varies across UAE versions on different OS types] 233: Common values are 8 (low quality) or 16 (high quality) 234: sound_frequency=n [default varies across UAE versions on different OS types] 235: Common values are 22050 or 44100. The quality of sound output increases with 236: the frequency. 237: sound_min_buff=n 238: sound_max_buff=n [default varies across UAE versions on different OS types] 239: You can specify the minimum and maximum size of the sound buffer. 240: Smaller buffers reduce latency. Usually only the minimum size is used. 1.1.1.3 root 241: 1.1 root 242: Memory options: 1.1.1.7 root 243: bogomem_size=n [default=0] 244: Emulate n*256K slow memory at 0xC00000. Some demos/games need this. 245: fastmem_size=n [default=0] 246: Emulate n megabytes of fast memory as an expansion board. 247: z3mem_size=n [default=0] 248: Emulate n megabytes of Zorro III fast memory as an expansion board. 249: chipmem_size=n [default=4] 250: Emulate n*512K chip memory. Some very broken programs need specific amounts 251: of chip mem to work properly. The largest valid value is 16, which means 8MB 252: chip memory. 253: 254: Display options: 255: gfx_width=n [default=800] 256: Use a window that is n pixels wide for displaying the Amiga screen. 257: gfx_height=n [default=300] 258: Use a window that is n pixels high for displaying the Amiga screen. 259: gfx_lores=bool [default=no] 260: Enable this option if you use a very small window width (320 to 400 pixels) 261: to shrink the display horizontally. 262: gfx_linemode=type [default=none] 263: The type can be none (every line is drawn once), "double" (every line is 264: drawn twice), and "scanlines" (every line is drawn once, but the image is 265: stretched vertically by inserting a black line every other line to simulate 266: the display on an old monitor). 267: The "double" mode gives best results, but slows down the emulation quite a 268: lot. Don't use the "none" mode if you want a decent interlace emulation. 269: If you use "double" or "scanlines", your window needs to be twice as high 270: as when using the "none" mode. 271: gfx_correct_aspect=bool [default=none] 272: Try to fit the image into the specified window dimensions by leaving out 273: certain lines. Useful if you want to fit a 640x512 Amiga display in a 274: 640x480 window. 275: gfx_center_vertical=bool [default=no] 276: gfx_center_horizontal=bool [default=no] 277: If you use a smaller window than 800x300 (400x300 with "gfx_lores" option or 278: 800x600 with a gfx_linemode other than "none"), not all parts of the display 279: will fit on the screen. By enabling the necessary centering options, you can 280: ask the emulator to try and move the screen contents so that the relevant 281: parts are displayed. If you are unlucky, this can cause the contents to jump 282: around a bit in certain cases. 283: gfx_fullscreen_amiga=bool [default=no] 284: Enable if you want to use the full screen, not a window on the desktop, for 285: the Amiga display. Some ports (DOS, SVGAlib) always use fullscreen mode. 286: gfx_fullscreen_picasso=bool [default=no] 287: Like gfx_fullscreen_amiga, but for the Picasso graphics card display. 288: gfx_color_mode=mode [default=8bit] 289: Select a color mode to use. 290: Color modes: 8bit (256 colors), 15bit (32768 colors), 16bit (65536 colors), 291: 8bit_dithered (256 colors, with dithering to improve quality), 292: 4bit_dithered (16 colors, dithered); 32bit (16 million colors) 293: gxfcard_size=n [default=0] 294: Emulate a Picasso 96 compatible graphics card with n MB graphics memory. 295: This requires that you use set the CPU type to "68020" or higher, and that 296: you do not use 24 bit addressing. 1.1.1.3 root 297: 298: Debugging options (not interesting for most users): 1.1.1.7 root 299: use_debugger=bool [default=no] 300: If enabled, don't start the emulator at once, use the built-in debugger. 301: log_illegal_mem [default=no] 302: If enabled, print illegal memory accesses 1.1 root 303: 1.1.1.2 root 304: 305: Whew. You'll probably have to experiment a little to get a feeling for it. 1.1.1.3 root 306: 1.1.1.2 root 307: 1.1 root 308: You can also put these options into a configuration file in your home 309: directory. Simply create ~/.uaerc and put some of these options in it. On 310: non-Unix systems, the file is called uae.rc and should be located in the 311: current directory. 312: 313: 314: Choosing color and screen modes 315: =============================== 316: 317: As described in the previous paragraph, UAE can run in many different 318: resolutions and color modes. However, few of the color mode options are 319: available if you use the X11 version of UAE, since the X server determines 320: how many colors are available. If you are running a 256 color X server, you 321: can use "-H3" to tell UAE to dither the colors for better results. 322: 323: You will have to experiment which mode gives the best results for you at a 324: satisfying speed. Note that the dithering process consumes time, so even if 325: 256 colors with dithering look better than 256 colors without, remember that 326: UAE will be slower in that mode. 327: 328: The recommended resolution is 800x600. In the lower resolution modes, some 329: overscan pictures the Amiga tries to display may not fit entirely on the 330: screen, others may be off-center and some graphical effects may look weird. 331: For best results, use 800x600 with at least 32768 colors. 1.1.1.3 root 332: For speed, use 400x300 lores with 256 colors. 333: 334: _Don't_ use 24 bit or 32 bit screen modes, unless you absolutely have to. 335: These are way too slow to be usable. 1.1 root 336: 337: 338: Harddisk emulation 339: ================== 340: 1.1.1.3 root 341: Since using diskfiles is awkward, it is necessary to emulate harddisks. There 342: are two ways how you can use large amounts of data with UAE: harddisk files 343: and mounted directories. 344: 345: 1. Harddisk files 346: 347: Harddisk files are large files that contain the image of an Amiga filesystem. 348: They work much the same way as a disk file. You can simply create a large 349: empty file and tell UAE to use it as a hardfile, but you will need to format 350: it from the emulation before you can actually use it. 1.1 root 351: 1.1.1.3 root 352: Under Unix, You can create a (unformatted) harddisk file with 1.1 root 353: dd if=/dev/zero of=hardfile bs=512 count=16384 1.1.1.3 root 354: That will create an 8MB file. Other ports of UAE may come with a utility 355: called "makedisk" or other ways to create such a file. 1.1.1.2 root 356: 1.1.1.3 root 357: To tell the emulator that you want to use a certain file as a hardfile, use 358: the "-W" option, for example 359: uae -W 32:1:2:hardfile 360: The first three numbers are geometry information which tell the AmigaOS how 361: the file is organized. The first number (32) is the number of sectors per 362: track, the second number (1) is the number of heads or surfaces, the third 363: number (2) is the number of reserved blocks. If you use "normal" sizes 364: (powers of two, like 32MB), then you should be OK using the same numbers as 365: in the above example. Using different numbers can make sense if you transfer 366: the image of a real Amiga harddisk which uses a different geometry. The last 367: field of the argument to the "-W" option is the name of the harddisk file. 368: 369: If you are using Kickstart 1.3 or earlier, hardfiles can't currently be 370: mounted at boot time, and therefore you can't boot from it either. You will 371: have to boot either from a floppy disk image or from a filesystem (see below), 372: and mount the hardfile.device later. To do this, add the following to 373: "DEVS:mountlist": 1.1 root 374: 1.1.1.3 root 375: UAE0: Device = uaehf.device 1.1 root 376: Unit = 0 377: Flags = 0 378: Surfaces = 1 379: BlocksPerTrack = 32 380: Reserved = 1 381: Interleave = 0 382: LowCyl = 0 ; HighCyl = 511 383: Buffers = 5 384: DosType = 0x444F5300 385: BufMemType = 1 386: # 387: 1.1.1.3 root 388: (You may need to adjust the values if you specified a different geometry, 389: and/or your hardfile has a different size than 8MB, and/or the hardfile is not 390: mounted as UAE0: because you mounted other harddisks before it.) 391: 1.1 root 392: Then, type "mount UAE0:" (or put that command in your startup-sequence), and 393: you should be able to access it. Don't forget to format it with the AmigaDOS 394: format command: 395: 396: format drive uae0: name Mister_Willwink 397: 1.1.1.3 root 398: b) Accessing native filesystems from the emulator 1.1 root 399: 400: This has some major advantages: 401: - It has no problems with Kickstart 1.3 402: - It is more convenient. 1.1.1.3 root 403: - It is much faster. 1.1 root 404: 1.1.1.2 root 405: If you specify the -M or -m command line arguments, you your native filesystem 406: from the emulator. If you start UAE with 1.1 root 407: 408: uae -m sound:/usr/amiga/modules 1.1.1.2 root 409: 1.1 root 410: you can access all the files in /usr/amiga/modules by reading from the 411: AmigaDOS volume "SOUND:". 412: (DOS users: try "uae -m dh0:C:\" to mount your drive C:\ as DH0:) 413: 1.1.1.3 root 414: You can mount up to 20 devices, either hardfiles or filesystems, by giving 415: either of these options multiple times. The volumes will be named UAE0:, 416: UAE1:, etc. UAE will boot from UAE0: if no diskfile is found for floppy 417: drive 0. 418: You can also use native filesystems to mount Amiga CD-ROMs, and you can 419: abuse the hardfile emulation to mount floppy disks: "uae -W 11:2:2:wb13.adf" 420: will mount the diskfile "wb13.adf". 1.1 root 421: 422: 423: Tools / Transferring files 424: ========================== 425: 1.1.1.2 root 426: As you should know by now, you need to transfer files between your Amiga and 427: the machine you run UAE on. There are several ways how to do this. 428: 429: - Using a null modem cable, and a terminal package running on each machine, 430: you can transfer the file(s) via Zmodem upload/download. 68000 equipped 431: Amigas can normally attain around 3000cps through the null modem cable, 432: using the standard Commodore serial.device. However, by using the device 433: replacement BaudBandit.device, anything up to 5500cps can be attained. 434: BaudBandit can be obtained from Aminet. A second alternative is to use 435: the BASIC program adfi.bas (included with UAE) to transfer a file from the 436: Amiga to the PC via the null modem cable. 437: 438: - If you're using CrossDOS on your Amiga, you can compress the disk or 439: kickstart image using LhA or similar PC compatible archiver and copy it to 440: a 720KB floppy disk. You can now take the disk over to the PC, copy the 441: compressed file to the UAE directory and uncompress it. 442: If you don't have CrossDOS on the Amiga, there is a similar freeware tool 443: called Msh, which can be found on Aminet or on Fish disk 382 or 327. 444: 445: In either case, you ought to read the documentation for the programs that 446: you use for the transfer. These programs can't be explained here. 1.1 root 447: 1.1.1.2 root 448: In the "amiga" subdirectory you'll find two small Amiga programs that will 449: help you to generate the necessary image files. These are called transrom 1.1 root 450: and transdisk. Copy them to your Amiga and make them executable (by typing 1.1.1.2 root 451: "protect transrom rwed" and "protect transdisk rwed" in the Amiga shell 1.1 root 452: window). 453: transrom will dump the contents of your Kickstart ROM, and transdisk will 454: dump an image of a floppy in one of the drives. Both programs write to the 1.1.1.2 root 455: standard output (read: the screen), so you'll want to redirect that. Do 1.1 root 456: 457: transrom >ram:kick.rom 458: 459: to create a file called "kick.rom" in the RAM disk, and 460: 461: transdisk >ram:df0.adf 462: 463: to create a file called "df0.adf" in the RAM disk. These files are pretty 1.1.1.2 root 464: big, 262144 or 524288 bytes for the ROM image and 901120 bytes for a disk 465: image. 1.1.1.3 root 466: 467: NEVER run either of these programs from the Workbench. Always open a Shell 468: or CLI window to do this. 469: 1.1 root 470: transdisk understands the following arguments: 471: 472: -d device unit: Use this device instead of DF0: 1.1.1.2 root 473: -s n: Begin transfer at track n (default: 0) 474: -e n: End transfer at track n (default: 79) 475: -w file: don't read from the floppy, instead write the contents 476: of "file" to the floppy 477: -h: Treat the disk as high-density disk. HD images aren't 478: supported by UAE yet, though. Note that the resulting 479: file will be twice as big. 1.1 root 480: 481: So, to transfer the disk in drive DF1:, you'd give the command: 482: 483: transdisk >ram:df1.adf -d trackdisk 1 484: 485: If you don't have much RAM and can't fit all of a disk image in the RAM disk, 486: you can split up the transfer into multiple parts with the "-s" and "-e" 487: parameters. To transfer the disk in four parts, you'd use the following 488: commands: 489: 490: transdisk >ram:df0_1.adf -s 0 -e 19 491: transdisk >ram:df0_2.adf -s 20 -e 39 492: transdisk >ram:df0_3.adf -s 40 -e 59 493: transdisk >ram:df0_4.adf -s 60 -e 79 494: 495: Of course, you should save each of the four files to another place before 496: transferring the next one with transdisk to make space in your RAM disk. 497: If you have all the files on your PC, you can do the following under Unix: 498: cat df0_1.adf df0_2.adf df0_3.adf df0_4.adf >df0.adf 499: or, under DOS: 1.1.1.2 root 500: COPY /B df0_1.adf+df0_2.adf+df0_3.adf+df0_4.adf df0.adf 1.1 root 501: I've been told there are the following tools for the Mac to join binaries: 502: "ChunkJoiner 2.1.2" found under Info-Mac's <disk> directory or 503: "JoinFiles 1.0.1" under Info-Mac's <text>. 504: 505: The current transdisk can only read the standard AmigaDOS format. This means 506: that most games that rely on some form of copy-protection cannot be 1.1.1.2 root 507: transferred (more about disk formats in the file "FAQ") 1.1 root 508: 1.1.1.2 root 509: **************************************************************************** 1.1 root 510: If you transfer commercial software, you must not distribute the resulting 511: image files, since that would be a violation of copyright law. The Kickstart 512: ROM has to be considered commercial software. You may only use the Kickstart 513: from your own Amiga, and you may not distribute Kickstart ROM files. 514: Please read the license that came with your software for details. 1.1.1.2 root 515: **************************************************************************** 516: 517: 518: Retrieving files from a disk image 519: ================================== 1.1 root 520: 521: If you have a disk image file, and you want to retrieve the files from it, you 522: can use the "readdisk" tool. It is automatically built by "make". If you have 523: a disk image of a disk called "Workbench1.3D" as df0.adf, and you do 524: readdisk df0.adf 525: the whole directory structure of the disk image will be stored in a newly 526: created subdirectory called "Workbench1.3D". You can optionally give a second 527: parameter to specify a directory where to create the output other than the 528: current directory. 529: readdisk only understands about the OFS right now. FFS disks will cheerfully 530: be regarded as being unreadable. Use the unixfs.device from within the 1.1.1.2 root 531: emulator if you want to transfer files from FFS disks. 1.1 root 532: 533: 1.1.1.3 root 534: Picasso 96 graphics card emulation 535: ================================== 536: 537: To use this feature, you must select 68020 emulation with a 32 bit address 538: space. You also need a Kickstart 3.x ROM. 539: 540: To specify how much graphic memory you want to emulate, use the "-U" option, 541: e.g. "-U 4" for 4 megabytes. Then, you need the Picasso 96 software which 542: is not distributed with UAE (There will be a link to the Picasso 96 home page 543: on the UAE Web page soon). Version 1.31 or higher is recommended. 544: Install the Picasso software, and make sure you enable the "uaegfx" driver. 545: After that is complete, reboot, and you should be able to select the new 546: modes from the ScreenModes program. 547: 548: 1.1.1.9 ! root 549: UAE SCSI device ! 550: =============== ! 551: ! 552: To enable SCSI support, use --enable-scsi-device when running configure. ! 553: The emulator provides a uaescsi.device. This device only supports ! 554: direct SCSI, which is sufficient to run applications like MakeCD. The ! 555: device does not support reading or writing with the normal Exec commands, ! 556: so you cannot mount filesystems on it right now. ! 557: ! 558: The unit numbers of the uaescsi.device follow the Amiga SCSI ! 559: conventions: unit number "xyz" maps to the lun y of target z on bus ! 560: x. Wide SCSI busses can have targets with numbers larger than 9. In ! 561: this case the uaescsi.device pretends that there is another SCSI ! 562: bus. To avoid confusion, all available SCSI targets are listed ! 563: together with their unit number when starting UAE. Devices cannot be ! 564: added while the emulator is running. Reseting it is not sufficient ! 565: either for technical reasons. ! 566: ! 567: The implementation of the uaescsi.device uses cdrecord's libscg as ! 568: interface to the native SCSI system. Many implementations of this ! 569: interface exist, although only the Linux implementation has been ! 570: incorporated into UAE at the moment. Using threads is strongly ! 571: recommended, because some SCSI commands can run for extended periods ! 572: of time and would block the whole emulation during this time without ! 573: threads. Use --enable-threads when starting configure. ! 574: ! 575: Depending on the hosts capabilities the uaescsi.device may be limited ! 576: compared to other Amiga SCSI devices. The Linux kernel by default only ! 577: allows 32KB of data per SCSI command and does not always perform SCSI ! 578: requests in parallel. ! 579: ! 580: Setting the chunk size in MakeCD to 30KB is already too much and ! 581: causes an IO error -4 (IOERR_BADLENGTH), because the setting is only ! 582: used as a guideline. You can work around this by setting the Tooltypes ! 583: BUFFER_CHUNK_XXX to 29. On a Pentium II 350MHz with Adaptec UW SCSI ! 584: controller on board on-the-fly copying was possible from a Philips ! 585: CDD2600 (SCSI) to a Yamaha CRW4416E (IDE) at 4x. ! 586: ! 587: 1.1 root 588: The UAE_CONTROL program 589: ======================= 590: 591: In the "amiga" subdirectory, you will find two programs, uae_control and 592: uaectrl that provide the same functionality as the X11 GUI. uaectrl is 593: shell-based and works with any Kickstart, while uae_control needs the 594: gadtools.library and a recent version of reqtools.library, so it only works 595: with Kick 2.0 and upwards. Copy these two programs to the directory that you 596: use for harddisk emulation. They should be self-explanatory. 597: 598: 1.1.1.9 ! root 599: The timehack ! 600: ============ ! 601: ! 602: Another tool in the "amiga" subdirectory, timehack, synchronizes the ! 603: emulated Amiga's system time with the host's time every second. This ! 604: is useful when the emulation is not done in real-time or is suspended ! 605: completely. ! 606: ! 607: 1.1 root 608: Quick overview of the debugger commands 609: ======================================= 610: 1.1.1.2 root 611: Some (window-system based) ports of UAE have a built-in debugger. You can 612: press ^C at any time to enter this debugger. 1.1 root 613: Each debugger command consists of a single letter and occasionally some 614: parameters. 615: 616: g: Start execution at the current address. 617: c: Dump state of the CIA and custom chips. 618: r: Dump state of the CPU 619: m <address> <lines>: Memory dump starting at <address> 620: d <address> <lines>: Disassembly starting at <address> 621: t: Step one instruction 622: z: Step through one instruction - useful for JSR, DBRA etc. 623: f <address>: Step forward until PC == <address> 624: q: Quit the emulator. You don't want to use this command. 1.1.1.3 root 625: M: hunt for sound modules 626: S <filename> <address> <len>: 627: save a sound module 1.1.1.5 root 628: C <value>: Search for values like energy or lifes in games 629: W <address> <value>: Write into Amiga memory 1.1 root 630: 631: 632: Sound 633: ===== 634: 1.1.1.2 root 635: If your version of UAE supports sound, you can pass parameters like frequency 636: or number of bits to use on the commandline; if you don't specify any, sane 637: defaults will be used. If graphics output is enabled while sound is output, 638: the emulator will be much too slow on most systems. The sound will not be 639: continuous. Therefore, a hack to turn off screen updates is provided: Press 640: ScrollLock to disable graphics, press it again to enable them. 1.1 root 641: 642: The quality of the emulation depends on the setting of the "-S" commandline 643: option. With "-S 3", all of the sound hardware is emulated; and some programs 644: (e.g. AIBB) won't run with other settings. "-S 2" should sound just as good as 645: "-S 3" and will be much faster for some programs. "-S 1" tries to emulate most 646: of the sound hardware, but doesn't actually output sound. "-S 0" completely 647: turns off sound. 648: 649: 1.1.1.2 root 650: Pointers 651: ======== 1.1 root 652: 1.1.1.2 root 653: There are a few sites in the Internet that contain helpful information about 654: UAE. 655: 656: The new "official" UAE page is located at 657: 1.1.1.3 root 658: http://www.freiburg.linux.de/~uae 1.1.1.2 root 659: 660: thanks to Stefan Reinauer who is now maintaining it. 661: 662: There, you will find links to other UAE pages. One which is especially useful 663: is the "UAE Discussion Board" set up by Gustavo Goedert, the address is 664: 1.1.1.3 root 665: http://www.netrunner.com.br/dosuae/uaeboard/index.html 1.1 root 666: 1.1.1.2 root 667: Not quite as good as a newsgroup due to braindamaged reader software 668: (Ratscope), but still a blessing. 669: 1.1.1.3 root 670: There is supposedly a newsgroup named "alt.emulators.amiga", but I don't get 671: it here. 672: The newsgroup "comp.sys.amiga.emulations" appears to be a proper place to 673: discuss Amiga emulation, but, strictly speaking, it is _not_ the right place. 674: More appropriate places are "comp.emulators.misc", and, of course, Gustavo's 675: discussion board. 676: 677: Petter Schau has written another Amiga emulator named "Fellow". It's mostly 678: written in x86 assembly and only runs under DOS. It's quite compatible and 679: generally faster than UAE. The Fellow homepage is at 680: 681: http://www.geocities.com/SiliconValley/Peaks/5244/ 1.1 root 682: 683: 684: Thanks & Acknowledgements 685: ========================= 686: 687: Thanks to all who have written me so far with bugreports and success/failure 688: reports when trying to run the emulator on various hardware with different 689: Kickstart versions. A list of everyone who has contributed to the source code 690: can be found in the CREDITS file (this was getting too big to keep it here). 691: 692: Special thanks to: 693: - Jay Miner, Dale Luck, R.J. Mical and all the others who built the Amiga. 694: - Felix Bardos, whose HRM I "borrowed". 695: - Hetz Ben Hamo mailed Peter Kittel from Commodore asking for permission to 696: give Kick 1.3 away. Unfortunately, the response was negative :-( 1.1.1.5 root 697: - Stefan Reinauer, for hosting the UAE Web page after the RWTH decided it's 698: too dangerous to let students have their own Web pages. 699: - Bruno Coste, Ed Hanway, Alessandro Soldo and Marko Nippula provided useful 700: documentation about the Amiga 1.1 root 701: - Fabio Ciucci gets the "Best bug reports" award for his help with the 702: blitter line emulation and other problem areas. 1.1.1.3 root 703: - Michael C. Battilana and Cloanto Software, for all their support. 1.1.1.5 root 704: - Julian Eggebrecht of Factor 5, for providing several F5 games and a lot 705: of valuable input. 706: Factor 5 has made Katakis, one of their classic Amiga games, freely 707: available for download. There are still some good people left in the 708: world... 709: - Jens Sch�nfeld, inventor of the Catweasel controller, donated one 710: controller card. 1.1 root 711: 712: 1.1.1.2 root 713: Authors/Maintainers 714: =================== 1.1 root 715: 1.1.1.3 root 716: My address is (please read the section "Before you send email" below): 1.1 root 717: 718: [email protected] 719: 720: or, via snailmail 721: 722: Bernd Schmidt 723: Schlossweiherstrasse 14 724: 52072 Aachen 725: Germany 726: 727: Email is more likely to be answered, and will definitely be answered much 728: faster. Please avoid phonecalls if you can. 1.1.1.3 root 729: I won't distribute software, neither PD or commercial. Don't send me floppy 730: disks without at least asking first, you will not get them back. 1.1.1.2 root 731: 732: The following people have ported UAE to different platforms; you should 733: direct system-specific questions to them: 734: 735: DOS port: 1.1.1.3 root 736: Gustavo Goedert <[email protected]> 737: Available: http://www.netrunner.com.br/dosuae 738: Sourecode: available on the above Web page, most of it included in the 739: main source (with some delay) 1.1.1.2 root 740: 741: Mac port: 1.1.1.3 root 742: Originally: Ernesto Corvi <[email protected]> 743: Currently: Arnaud Blanchard <[email protected]> 744: Available: http://www.pratique.fr/~jblancha/ 745: Sourcecode: extra package available. Bits and pieces in the main source, 746: but nothing you could get to compile. 1.1.1.2 root 747: 748: BeBox port: 749: Christian Bauer <[email protected]> 750: Available: The main UAE web page (use the Unix sources) 1.1.1.3 root 751: Sourcecode: Included in the main source. Should compile OK. 752: Notes: Christian says he doesn't have much time to spend on UAE, so if 753: anyone is willing to help maintain this port, please speak up. 1.1.1.2 root 754: 755: NextStep port: 756: Ian Stephenson <[email protected]> 757: Available: The main UAE web page (use the Unix sources) 1.1.1.3 root 758: Sourcecode: Included in the main source. Should compile OK. 759: Notes: Ian says he doesn't have much time to spend on UAE, so if 760: anyone is willing to help maintain this port, please speak up. 1.1.1.2 root 761: 762: Amiga port: 763: Originally: Olaf 'Olsen' Barthel <[email protected]> 764: Currently: Samuel Devulder <[email protected]> 765: Available: Not quite sure yet. Paul Liss' Web page has binaries. 1.1.1.3 root 766: Sourcecode: Included in the main source. Should compile OK. 1.1.1.2 root 767: 1.1.1.3 root 768: pOS port: 769: Samuel Devulder <[email protected]> 770: Available: Not quite sure yet. 771: Sourcecode: Included in the main source. Should compile OK. 1.1.1.7 root 772: 1.1.1.2 root 773: XFree86/OS2 port: 774: Krister Bergman <[email protected]> 1.1.1.3 root 775: Available: http://www.kuai.se/~bellman/html/xfreeapps.html 776: Sourcecode: nothing special, apparently the Unix stuff compiles cleanly (?) 1.1.1.2 root 777: 1.1.1.3 root 778: Win32 port: 1.1.1.7 root 779: Originally: Mathias Ortmann <[email protected]> 780: Currently: Brian King <[email protected]> 781: Available: http://www.codepoet.com/uae 782: Sourcecode: bits merged into the main source, the rest available from the 783: URL above. Still trying to merge more of it... 1.1.1.3 root 784: 785: Acorn RISC PC port: 786: Peter Teichmann <[email protected]> 787: Available: http://www.wh1.tu-dresden.de/~sol/acorn.shtml 788: http://www.wh1.tu-dresden.de/~sol/acorne.shtml 789: Sourcecode: Some of it is included in the main source, but since Acorn's OS 790: apparently doesn't have decent file handling, you can't even 791: use the same source layout. Also needs lots of additional files. 792: 1.1.1.2 root 793: Since I generally don't have the possibility to test or improve these ports, 794: it is a good idea to contact their respective authors if you have questions. 795: 796: 1.1.1.3 root 797: Before you send email... 798: ======================== 1.1.1.2 root 799: 800: Before you contact me with a problem that you have, make sure you have read 801: _all_ of the above. Please read also the file "FAQ", which contains a lot of 1.1.1.3 root 802: helpful information, and the README file for your specific system. 1.1.1.2 root 803: 1.1 root 804: I can't answer _every_ question. If you have trouble understanding this 805: README, either because you don't speak English very well or because you have 1.1.1.2 root 806: no clue at all about computers, please try to find some friend of yours who 807: does understand this file and who can translate/explain it for you. I simply 808: can't explain (for example) how to use terminal programs or CrossDOS because 809: I don't use either, and it would be much too time-consuming anyway. This file 810: and the file FAQ contains about every piece of information I can give you. I 811: try to help people who have questions, but sometimes it takes too much time. 812: 813: Please don't ask for Kickstart ROM files or other copyrighted software. Don't 814: _send_ me stuff like this either. If you want to send me something else which 815: is big (>= 50K), ask me before or put it somewhere in Webspace. 1.1.1.3 root 816: If I get 3MB of screen shots or a core dump ("it doesn't work, it generates 817: this file"), I'm very likely to get extremely angry, I might complain to your 818: sysadmin, and you might lose your account. Think twice. 819: 820: I'm also going to be extremely annoyed if you send email in HTML format. 821: Fight this disease! 1.1 root 822: 823: Oh, and another thing: If I promise to do things (like implement new 824: features), and forget about them, pester me. That happens occasionally, it's 825: a known bug in my brain. I'll have it replaced.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.