2.2.0 beta3

docs/bsdsocket.txt

@@ -12,7 +12,7 @@ be sufficient to allow you to use most popular AmigaOS network
 clients, such as web browsers and mail readers.
 
 To enable the bsdsocket.library emulation (assuming you are using a
-version of E-UAE with this feature compiled in), add the option
+version of PUAE with this feature compiled in), add the option
 
 bsdsocket_emu=true
 
@@ -28,6 +28,6 @@ emulated Amiga environment. For example, Amiga software will not be
 able to bind to ports already in use by host software, and your host
 operating system may impose access controls on certain ranges of ports.
 
-Older versions of E-UAE required that a bsdsocket.library wrapper file
+Older versions of PUAE required that a bsdsocket.library wrapper file
 be installed somewhere in the LIBS: path in your Amiga environment.
 This is no longer the case, and this file should now be removed.

docs/cmd-line.txt

-Command line options for E-UAE
+Command line options for PUAE
 ==============================
 
-E-UAE supports the following command-line options. Note that, where
+PUAE supports the following command-line options. Note that, where
 applicable, these will over-ride any similar options specified in the
 default configuration file.
 
@@ -28,7 +28,7 @@ This document (like the rest of the documentation) is a work-in-progress.
  
  -s ntsc=true
  
- to start E-UAE in NTSC mode.
+ to start PUAE in NTSC mode.
  
  See configuration.txt for supported options.
  
@@ -60,6 +60,7 @@ This document (like the rest of the documentation) is a work-in-progress.
  2: 68020
  3: 68020/68881
  4: 68040
+ 6: 68060
 
 
 -w<n>
@@ -90,7 +91,7 @@ This document (like the rest of the documentation) is a work-in-progress.
 
  -c4
 
- will cause E-UAE to emulate 2 MB of Chip memory.
+ will cause PUAE to emulate 2 MB of Chip memory.
 
 
 -b<n>
@@ -164,12 +165,12 @@ Options specific to the X11 graphics driver
 
 -L
  Use "low-bandwidth" mode, which may reduce the amount of data transferred
- between E-UAE and the X server. That's particularly an advantage when these
+ between PUAE and the X server. That's particularly an advantage when these
  are running on two different machines in a network.
 
 -T
  Use the MIT-SHM extension. This may not be available on all machines, and
- it will not work if E-UAE and the X server are not running on the same
+ it will not work if PUAE and the X server are not running on the same
  machine. In all other configurations, turning on this option will give you
  a huge speed improvement.
 

docs/compiling.txt

-Compiling E-UAE
+Compiling PUAE
 ===============
 
-E-UAE should be able to compile on any platform with a POSIX-like shell
+PUAE should be able to compile on any platform with a POSIX-like shell
 environment, a C compiler and make. Version 2.95 or newer of the GNU C
 Compiler is recommended as is GNU make, but alternative compilers and
 versions of make may work. Some features may be GCC-specific, however.
@@ -9,15 +9,26 @@ Currently, for example, the JIT - the compiler which dynamically
 translate 68k opcodes to x86 opcodes - does require GCC (and GAS, the
 GNU assembler).
 
-Currently zlib is also required to build E-UAE for all supported
+Currently zlib is also required to build PUAE for all supported
 platforms. This isn't much of hardship since zlib is available
 everywhere, but shout loudly enough and I'll fix this.
 
 
+Required Stuff
+==============
+(for debian based Linux)
+apt-get install build-essential
+apt-get install automake
+apt-get install zlib1g
+apt-get install libsdl1.2-dev
+apt-get install libgtk2.0-dev
+apt-get install xorg-core
+
+
 Configuring
 ===========
 
-The first step to compiling E-UAE is to generate a makefile suitable
+The first step to compiling PUAE is to generate a makefile suitable
 for your intended target system. This is done by running the configure
 script.
 
@@ -85,6 +96,10 @@ selecting what features are built into UAE. Here's a selection:
   bsdsocket.library). This works only on Unix platforms at the moment
   (including Linux, Solaris and OS X).
 
+--enable-gccopt
+  Enable CPU specific optimization parameters. Script will check for your CPU's
+  features and set additional compile flags.
+
 --with-caps
   Build with support for IPF (CAPS) images. This requires the IPF
   development files from http://www.caps-project.org/
@@ -130,22 +145,22 @@ box.
 Building the SCSI emulation
 ---------------------------
 
-E-UAE's SCSI emulation may use libscg, the SCSI transport layer from
+PUAE's SCSI emulation may use libscg, the SCSI transport layer from
 the cdrtools project (see http://cdrecord.berlios.de). Note, however,
 due to a license change in the cdrtools project, only versions of
 cdrtools up to 2.01.01a08 inclusive may be used.
 
 If libscg is not available on your build system, download a recent
 version of cdrecord and compile it. Then run the ./src/install_libscg
-script in the E-UAE source archive to move the relevant files from
-cdrecord to the E-UAE source directory.
+script in the PUAE source archive to move the relevant files from
+cdrecord to the PUAE source directory.
 
 If your system has the libscg headers and library installed in a
 non-standard location, you can pass the --with-libscg-prefix option or
 the --with-libscg-includedir and --with-libscg-libdir options to the
 configure script to specify where these are installed.
 
-On Linux systems, if libscg is not available, E-UAE tries to use a
+On Linux systems, if libscg is not available, PUAE tries to use a
 Linux-specific SCSI emulation that is based on some ioctl() commands.
 
 

docs/configuration.txt

-Configuring E-UAE
+Configuring PUAE
 =================
 
-E-UAE may be configured via options supplied in a plain-text configuration
+PUAE may be configured via options supplied in a plain-text configuration
 file. This configuration file contains options of the form <key>=<value> and
 each new option must begin a new line. Blanks lines are ignored, and lines
 beginning with a '#' character are treated as comments and thus also
 ignored.
 
-When E-UAE is started it tries to load a default configuration file. Where
+When PUAE is started it tries to load a default configuration file. Where
 it looks for this file is platform-dependent, but typically it will look for
 a file called '.uaerc' in the current directory and (on multi-user
 platforms) in the user's home directory. On MacOS X, the default is called
 'default.uaerc' instead since 'dot files' are not visible in Finder,
 the OS X file manager.
 
-You may tell E-UAE to load a configuration file in addition to the default by
-passing the '-f' switch to E-UAE on the command line. Any options found in
+You may tell PUAE to load a configuration file in addition to the default by
+passing the '-f' switch to PUAE on the command line. Any options found in
 this file will override the values of the same options in the default file.
 The '-s' switch may also be used to specify a single <key>=<value> option on
 the command line, which, again, will override options found in the default
 file.
 
-The default values for E-UAE's configuration options will cause E-UAE to
+The default values for PUAE's configuration options will cause PUAE to
 emulate a 68000-based ECS system with 512 KB of Chip memory and 512 KB of
 Slow memory. The only option you absolutely need to specify is the path to
-the Kickstart image you want to use (unless you wish to use E-UAE's minimal
+the Kickstart image you want to use (unless you wish to use PUAE's minimal
 Kickstart emulation, in which case you must instead supply the path to a
 floppy disk image to boot from).
 
-In the following descriptions of E-UAE's configuration options, the template
+In the following descriptions of PUAE's configuration options, the template
 <n> refers to an integer value, <boolean> to a value of 'true' or 'false',
 and <path> refers to a file path using whatever conventions the host platform
 uses to specify paths.
@@ -40,7 +40,7 @@ General options
 ===============
 
 The following options all have a prefix of the form <target>. The value of
-<target> corresponds to the host platform on which you are running E-UAE.
+<target> corresponds to the host platform on which you are running PUAE.
 
   Target     Platform
   ------     --------
@@ -79,16 +79,16 @@ use_gui=<boolean> (default=true)
 
   Open a configuration GUI at start-up before starting the emulation proper.
   This option is ignored on platforms without a configuration GUI or if
-  E-UAE has been built without such a GUI.
+  PUAE has been built without such a GUI.
 
 
 use_debugger=<boolean> (default=false)
 
   Open the built-in debugger when the emulation starts. This option is
-  ignored if E-UAE has been built without debugging support or if the
+  ignored if PUAE has been built without debugging support or if the
   debugger cannot be opened due to platform-specific restrictions (at
   the moment the debugger requires a terminal/console window, so it
-  typically only works if you start E-UAE from a shell terminal).
+  typically only works if you start PUAE from a shell terminal).
 
 
 Host CPU-specific options
@@ -97,10 +97,10 @@ Host CPU-specific options
 x86.use_tsc=<boolean> (default=true)
 
   On x86 machines, if this option is true then the processor's timestamp
-  counter will be used for timing in E-UAE. This used to be a problem for
+  counter will be used for timing in PUAE. This used to be a problem for
   machines which did power-saving by scaling down the CPU's clock frequency,
-  but with E-UAE 0.8.28 and above this should no longer be an issue on
-  Linux. If you are running E-UAE on some other x86 platform which
+  but with PUAE 0.8.28 and above this should no longer be an issue on
+  Linux. If you are running PUAE on some other x86 platform which
   does frequency scaling, then set this option to false. Performance
   will suffer, but at least timing won't be affected by changes in CPU
   frequency.
@@ -114,9 +114,9 @@ amd64.use_tsc=<boolean> (default=true)
 ppc.use_tbc=<boolean> (default=true)
 
   On PPC machines, if this option is true then use the processor's timebase
-  register for timing in E-UAE. Since the PPC's TBC isn't affected by
+  register for timing in PUAE. Since the PPC's TBC isn't affected by
   frequency scaling, this option is of little use and is supported only for
-  completeness. It may be useful if E-UAE misdetects or miscalibrates your
+  completeness. It may be useful if PUAE misdetects or miscalibrates your
   machine's timebase frequency (if it does, please let me know).
 
 
@@ -144,13 +144,13 @@ cpu_speed=<speed> (default=real)
   relative to the Amiga chipset. This may have the value 'real', 'max' or
   can be an integer between 1 and 20.
 
-  If set to 'real', E-UAE will try to emulate the performance of an original
+  If set to 'real', PUAE will try to emulate the performance of an original
   7MHz 68000-based Amiga such as an A500. That is, the relative balance of
   time spent emulating the CPU and the Amiga chipset will be similar to the
-  performance of a real Amiga and E-UAE will try do the same amount of CPU
+  performance of a real Amiga and PUAE will try do the same amount of CPU
   work per display frame as a real 68000-based Amiga. Additionally, if
   any time is left over after emulating the A500's CPU and chipset in
-  each display frame, then E-UAE will wait until until the next
+  each display frame, then PUAE will wait until until the next
   display frame is due.
 
   Thus, the setting 'real' is recommended for games designed to run on
@@ -158,7 +158,7 @@ cpu_speed=<speed> (default=real)
   many classic Amiga games.
 
   If set to 'max', the CPU emulation will run at the maximum speed that the
-  host CPU can achieve. E-UAE will spend as much time as it can
+  host CPU can achieve. PUAE will spend as much time as it can
   emulating the 68000 CPU and will not wait at all per frame.
 
   Integer values for <speed> adjust the relative amounts of time devoted to
@@ -180,7 +180,7 @@ finegrain_cpu_speed=<n> (default=N/A)
 
 cpu_compatible=<boolean> (default=false)
 
-  If enabled, E-UAE will use a slower but more compatible version of the CPU
+  If enabled, PUAE will use a slower but more compatible version of the CPU
   emulation. This may be necessary to run some some demos and games
   correctly.
 
@@ -189,7 +189,7 @@ cpu_compatible=<boolean> (default=false)
 
 cpu_cycle_exact=<boolean> (default=false)
 
-  If enabled, E-UAE will employ a CPU emulation which tries to fully
+  If enabled, PUAE will employ a CPU emulation which tries to fully
   emulate the relative timing of CPU and chipset cycles. This is much more
   demanding even than the "compatible" CPU emulation, but more accurate -
   and so may be necessary to correctly run software which aggressively uses
@@ -294,11 +294,11 @@ ROM options
 kickstart_rom_file=<path>
 
   The file path of a Kickstart ROM image to load. <path> may either be an
-  absolute path or a path relative to the current directory when E-UAE was
+  absolute path or a path relative to the current directory when PUAE was
   run. The token '$(FILE_PATH)' at the start of a path will be expanded to
   the path specified by the <target>.rom_path= option.
 
-  If <path> is empty, E-UAE will use its built-in Kickstart emulation rather
+  If <path> is empty, PUAE will use its built-in Kickstart emulation rather
   than a real  Kickstart image. This requires a valid floppy disk to boot
   from mounted in the emulated DF0: drive. The Kickstart emulation is
   sufficient to play many classic Amiga games.
@@ -315,7 +315,7 @@ kickstart_key_file=<path>
   Kickstart ROM images provided by Cloanto in its Amiga Forever
   distribution are encrypted. This option specifies the key file required
   to decrypt such an image. <path> may either be an absolute path to the ROM
-  key file or a path relative to the current directory when E-UAE was run.
+  key file or a path relative to the current directory when PUAE was run.
   The token '$(FILE_PATH)' at the start of a path will be expanded to the
   path specified by the <target>.rom_path= option.
 
@@ -332,11 +332,11 @@ kickstart_ext_rom_file=<path>
 
   This option specifies the file path of an extended ROM image to load.
   <path> may either be an absolute path or a path relative to the current
-  directory when E-UAE was run. The token '$(FILE_PATH)' at the start of a
+  directory when PUAE was run. The token '$(FILE_PATH)' at the start of a
   path will be expanded to the path specified by the <target>.rom_path=
   option.
 
-  If E-UAE has been compiled without support for emulating the CDTV or CD32,
+  If PUAE has been compiled without support for emulating the CDTV or CD32,
   then this option will be ignored.
 
 
@@ -350,7 +350,7 @@ kickshifter=<boolean> (default=false)
 
   If enabled, the Kickstart ROM image will be patched after it is loaded into
   memory to support the running of Shapeshifter, the software-based classic Mac
-  emulation for AmigaOS, within E-UAE.
+  emulation for AmigaOS, within PUAE.
 
 
 RAM options
@@ -362,7 +362,7 @@ chipmem_size=<n> (default=1, that is, 512 KB)
   chipset). The valid range of values for <n> is between 1 and 16, that is,
   from 512 KB to 8 MB.
 
-  Note that E-UAE must emulate an ECS ("Fat") Agnus to be able to use 1 MB
+  Note that PUAE must emulate an ECS ("Fat") Agnus to be able to use 1 MB
   of Chip memory or more. Also note that Fast memory cannot be used if you
   select more than 2MB of Chip memory.
 
@@ -384,7 +384,7 @@ bogomem_size=<n> (default=2, that is, 512 KB)
   Fast memory, this memory cannot be accessed by the CPU when the custom
   chipset is busy - hence the term "Slow".
 
-  Some old games and demos may require this type of memory. If E-UAE
+  Some old games and demos may require this type of memory. If PUAE
   reports strange exceptions occuring when booting a floppy or weird
   accesses to custom chip registers, then try adding some "Slow" memory.
   Really old games may fail when "Slow" memory is added.
@@ -400,7 +400,7 @@ z3mem_size=<n> (default=0)
 
   Emulate <n> MB of Zorro III Fast memory.
 
-  E-UAE must emulate a 32-bit CPU (a 68020 or better, not an 68ec020) to
+  PUAE must emulate a 32-bit CPU (a 68020 or better, not an 68ec020) to
   support the emulation of Zorro III memory.
 
 
@@ -410,7 +410,7 @@ gfxcard_size=<n> (default=0)
   greater than 0, enables the graphics card or so-called 'Picasso96'
   emulation. A maximum of 32 MB of graphics card memory may be emulated.
 
-  E-UAE must emulate a 32-bit CPU (a 68020 or better, not an 68ec020) to
+  PUAE must emulate a 32-bit CPU (a 68020 or better, not an 68ec020) to
   support the graphics card emulation.
 
 
@@ -423,7 +423,7 @@ corresponding to the AmigaDOS devices DF0: to DF3:, respectively. Drive 0 is
 the first drive, and drive in which you would typically insert a floppy disk
 to boot from.
 
-E-UAE supports file-based images of Amiga floppy disks in a number of
+PUAE supports file-based images of Amiga floppy disks in a number of
 different file formats (see floppies.txt).
 
 
@@ -431,7 +431,7 @@ floppy<drive>=<path>
 
   Specifies the path of a floppy disk image to mount in drive DF<drive>:.
   <path> may either be an absolute path or a path relative to the current
-  directory when E-UAE was run. The token '$(FILE_PATH)/' at the start of a
+  directory when PUAE was run. The token '$(FILE_PATH)/' at the start of a
   path will be expanded to the path specified by the <target>.floppy_path=
   option.
 
@@ -457,7 +457,7 @@ floppy<drive>type=<type> (default=0 for drives 0 and 1, -1 for drives 2 and 3)
 
 floppy_speed=<speed> (default=100)
 
-  E-UAE's floppy drive emulation will work at <speed> per cent of a real
+  PUAE's floppy drive emulation will work at <speed> per cent of a real
   Amiga floppy drive (relative to the speed of the rest of the emulation).
   Valid values are from '100' to '800', that is 1x to 8x the speed of a
   standard Amiga floppy drive.
@@ -470,7 +470,7 @@ floppy_speed=<speed> (default=100)
 Hard disk options
 =================
 
-  E-UAE may emulate hard drive partitions (AmigaOS volumes) or full,
+  PUAE may emulate hard drive partitions (AmigaOS volumes) or full,
   partitionable hard disks. Two basic types of emulation are supported: the
   virtual filesystem and the hard file.
 
@@ -586,8 +586,8 @@ gfx_framerate=<n> (default=1)
   do), but decreases the quality of the display output.
 
   For example, when emulating a PAL display (50 Hz), for full-quality output
-  (gfx_framerate=1), E-UAE must update its display 50 times a
-  second. Setting gfx_framerate=4 will cause E-UAE to draw only 1
+  (gfx_framerate=1), PUAE must update its display 50 times a
+  second. Setting gfx_framerate=4 will cause PUAE to draw only 1
   frame in 4 and thus its display will updated only 12.5 times a second.
 
 
@@ -596,19 +596,19 @@ gfx_height_windowed=<n> (default=568)
 gfx_width_fullscreen=<n> (default=800)
 gfx_height_fullscreen=<n> (defaullt=600)
 
-  Specify the dimensions of the E-UAE display for graphical output from the
+  Specify the dimensions of the PUAE display for graphical output from the
   Amiga chipset.
 
   Ideally, the gfx_*_windowed options should specify the dimensions when
-  E-UAE is running in a window on your desktop and the gfx_*_fullscreen
+  PUAE is running in a window on your desktop and the gfx_*_fullscreen
   options will apply when running full-screen. However, this is not supported
-  yet, and E-UAE will use the gfx_*_windowed dimensions in both windowed and
+  yet, and PUAE will use the gfx_*_windowed dimensions in both windowed and
   full-screen modes.
 
   To emulate a high-resolution, fully overscanned PAL screen - either
   non-interlaced with line-doubling, or interlaced - you need to use a
   display of at least 720 by 568 pixels. If you specify a smaller size,
-  E-UAE's display will be clipped to fit (and you can use the gfx_center_*
+  PUAE's display will be clipped to fit (and you can use the gfx_center_*
   options - see below - to centre the clipped region of the display).
   Similarly, to fully display an over-scanned lo-res PAL screen, you need a
   display of 360 by 284 pixels.
@@ -623,7 +623,7 @@ gfx_height=<n>
 
 gfx_fullscreen_amiga=<bool> (default=false)
 
-  E-UAE will open it's display for Amiga screens in full-screen mode by
+  PUAE will open it's display for Amiga screens in full-screen mode by
   default - not as a window on the desktop.
 
   This option is not supported on all platforms.
@@ -632,9 +632,9 @@ gfx_fullscreen_amiga=<bool> (default=false)
 gfx_lores=<boolean> (default=false)
 
   Determines the fundamental horizontal resolution of output. If true, then
-  E-UAE will emulate a low-resolution output; high-res Amiga screens will
+  PUAE will emulate a low-resolution output; high-res Amiga screens will
   have their horizontal resolution halved (only every other horizontal pixel
-  will be drawn). If false, E-UAE will emulate a high-resolution output;
+  will be drawn). If false, PUAE will emulate a high-resolution output;
   low-resolution Amiga screens will have their horizontal resolution doubled.
 
   Most classic games employ low-resolution screens; Workbench uses a
@@ -656,7 +656,7 @@ gfx_linemode=<type> (default=double)
 gfx_correct_aspect=<boolean> (default=false)
 
   If set to true and the emulated Amiga screen has a larger vertical size
-  than the display window, E-UAE will fit the screen to the display by
+  than the display window, PUAE will fit the screen to the display by
   leaving out certain lines. This is useful, for example, if you wish
   to fit a 640x512 Amiga screen into a 640x480 window.
 
@@ -665,7 +665,7 @@ gfx_correct_aspect=<boolean> (default=false)
 
 gfx_center_horizontal=<type> (default=none)
 
-  If the Amiga screen emulated is wider than the E-UAE display, then this
+  If the Amiga screen emulated is wider than the PUAE display, then this
   option will try to cause the screen to be rendered centred on the display.
 
   Type           Description
@@ -678,18 +678,18 @@ gfx_center_horizontal=<type> (default=none)
 gfx_center_vertical=<type> (default=none)
 
   Similar to gfx_center_horizontal, but centres the screen vertically within
-  the E-UAE display.
+  the PUAE display.
 
 
 show_leds=<bool> (default=false)
 
   If true, show drive activity and power LEDs at the bottom right corner of
-  the E-UAE display.
+  the PUAE display.
 
 
 hide_cursor=<bool> (default=true)
 
-  If this option is set to true and E-UAE is displaying in windowed mode,
+  If this option is set to true and PUAE is displaying in windowed mode,
   then the host window manager's cursor is hidden; otherwise it is shown.
   This option may not be implemented on all platforms yet.
 
@@ -752,7 +752,7 @@ sound_latency=<t> (default=100)
 
 sound_max_buff=<n>
 
-  From E-UAE 0.8.29, this option is obsolete and has been replaced by the
+  From PUAE 0.8.29, this option is obsolete and has been replaced by the
   option sound_latency.
 
 
@@ -760,7 +760,7 @@ sound_interpol=<type> (default=none)
 
   Selects the sound interpolation mode used for audio output (only supported
   when audio output is in 16-bit resolution). Interpolation is a technique
-  which "smoothes out" the audio waveform generated by E-UAE and thus may
+  which "smoothes out" the audio waveform generated by PUAE and thus may
   lead to higher quality audio output. Supported values for <type> are:
 
   none - no interpolation.
@@ -805,7 +805,7 @@ joyport1=<mode>
 SCSI emulation options
 ======================
 
-E-UAE can provide direct access to a host optical drive like a CD-ROM drive
+PUAE can provide direct access to a host optical drive like a CD-ROM drive
 to AmigaOS via an Exec device wrapper called uaescsi.device. The SCSI device
 emulation is not supported on all platforms. See the SCSI emulation section
 of the documentation for more details.
@@ -824,9 +824,9 @@ scsi_device=<config>
 Network emulation
 =================
 
-E-UAE can provide network access to AmigaOS applications via an emulated
+PUAE can provide network access to AmigaOS applications via an emulated
 bsdsocket.library. This emulated bsdsocket.library is simply a wrapper
-around the host's networking stack. The AmigaOS environment within E-UAE
+around the host's networking stack. The AmigaOS environment within PUAE
 will share the same IP address as the host. The bsdsocket.library emulation
 is not supported on all platforms. See the bsdsocket emulation section of
 the documentation for more details.
@@ -839,7 +839,7 @@ bsdsocket_emu=<bool> (default=false)
 X11-specific options
 ====================
 
-The following options apply when E-UAE has been built with the X11 graphics
+The following options apply when PUAE has been built with the X11 graphics
 driver.
 
 x11.map_raw_keys=<bool> (default=false)
@@ -857,16 +857,16 @@ x11.map_raw_keys=<bool> (default=false)
 
 x11.low_bandwidth=<bool> (default=false)
 
-  If this option is set to true, then E-UAE will try to minimize the amount
+  If this option is set to true, then PUAE will try to minimize the amount
   of data sent to the X server by only redrawing areas of the amiga screen
   that have changed. This may increase frame rate on slow machines or when
-  running E-UAE on a separate host from the X server.
+  running PUAE on a separate host from the X server.
 
 
 x11.use_mitshm=<bool> (default=true)
 
   If this option is set to true, your X server supports the MITSHM extension
-  and E-UAE is running on the same host as the server, then E-UAE will use
+  and PUAE is running on the same host as the server, then PUAE will use
   memory shared between itself and the server for display buffers. This will
   increase display refresh speed.
 
@@ -879,7 +879,7 @@ x11.hide_cursor=<bool>
 SDL-specific options
 ====================
 
-The following options apply when E-UAE has been built with the SDL graphics
+The following options apply when PUAE has been built with the SDL graphics
 driver.
 
 sdl.map_raw_keys=<bool> (default=false)
@@ -899,22 +899,22 @@ sdl.use_gl=<bool> (default=false)
 AmigaOS-specific options
 ========================
 
-The following options apply when E-UAE has been built for AmigaOS (or
+The following options apply when PUAE has been built for AmigaOS (or
 similar platform) with the AmigaOS graphics driver.
 
 amiga.screen_type=<type> (default=public)
 
-  Specifies the type of screen that E-UAE will open it's display on. Valid
+  Specifies the type of screen that PUAE will open it's display on. Valid
   values for <type> are:
 
   Type     Description
   ----     -----------
   public   The display will be a window on the default or named public
            screen.
-  custom   E-UAE will open a custom screen for its display. The best
+  custom   PUAE will open a custom screen for its display. The best
            screenmode matching the configured dimensions will be used.
-  ask      E-UAE will present you with a requester to select the screenmode
-           to use for display. If this requester is cancelled, E-UAE will
+  ask      PUAE will present you with a requester to select the screenmode
+           to use for display. If this requester is cancelled, PUAE will
            use a window on the default or named public screen.
 
 
@@ -940,7 +940,7 @@ amiga.use_grey=<bool> (default=false)
 ALSA-specific options
 =====================
 
-The following options apply when E-UAE has been built with the ALSA audio
+The following options apply when PUAE has been built with the ALSA audio
 driver.
 
 alsa.device=<device> (default=default)

docs/floppies.txt

 Floppy drive emulation
 ======================
 
-E-UAE emulates up to four floppy drives. Standard PC floppy drives cannot
+PUAE emulates up to four floppy drives. Standard PC floppy drives cannot
 read Amiga floppies, so floppy disks are currently supported as image files
 (support for Catweasel hardware, a floppy controller which can read Amiga
 floppies - and other unusual disk formats - will be added in a future
 version).
 
-E-UAE supports a number of floppy image formats, optionally compressed by
+PUAE supports a number of floppy image formats, optionally compressed by
 gzip or packed inside a Zip archive.
 
 ADF
@@ -20,7 +20,7 @@ formatted contents.
 DMS
 ---
 
-DMS was a popular disk image cruncher. E-UAE can transparently read DMS
+DMS was a popular disk image cruncher. PUAE can transparently read DMS
 images.
 
 

docs/joystick.txt

@@ -3,13 +3,13 @@ Joystick port emulation
 
 An Amiga has two joystick ports. Port 0 typically has a mouse attached to it
 and port 1 may have a digital joystick, joypad or some other device
-connected. E-UAE can emulate Amiga mice and joysticks using either input
+connected. PUAE can emulate Amiga mice and joysticks using either input
 from a physical mouse or joystick or by using specific key presses on the
 keyboard to synthesize mouse and joystick movements or button clicks.
 
 The device connected to port 0 can be configured with the joyport0=<mode>
 configuration file option and the device at port 1 with joyport1=<mode>.
-Additionally, some versions of E-UAE may supply a GUI controls to configure
+Additionally, some versions of PUAE may supply a GUI controls to configure
 the joystick.
 
 Here <mode> can be one of:
@@ -19,7 +19,7 @@ none    - no device is connected to this port.
 mouse   - a mouse will be emulated on this port using the host's default
           mouse (usually the device you use to move the mouse pointer on your
           desktop). Up to three mouse buttons are supported and a scroll
-          wheel is currently supported when using E-UAE's X11 or SDL
+          wheel is currently supported when using PUAE's X11 or SDL
           graphics drivers.
 
 joy0    - a digital joystick will be emulated on this port using input from
@@ -78,7 +78,7 @@ joystick input - they will not produce normal key presses.
 Emulating a CD32 controller
 ===========================
 
-When emulating a CD32 (to do this, E-UAE must be booted with CD32 ROMs) the
+When emulating a CD32 (to do this, PUAE must be booted with CD32 ROMs) the
 joystick configured to port 1 may emulate a CD32 controller. The buttons on
 the joystick will be mapped to CD32 controller buttons as follows:
 

docs/keyboard.txt

 Keyboard emulation
 ==================
 
-E-UAE emulates an Amiga keyboard layout by a straightforward mapping - where
+PUAE emulates an Amiga keyboard layout by a straightforward mapping - where
 possible - of host keys to Amiga keys. In general, the alphanumeric keys,
 function keys, numbers, punctuation, cursor keys, numeric keypad, etc.
 should work as expected (that is, the symbol on the key cap should be
@@ -23,14 +23,14 @@ keyboard, Amiga keys on an Amiga keyboard, etc. Note that most Mac keyboards
 don't differentiate between left and right Option keys, and both will
 produce a Left Amiga.
 
-Currently, E-UAE's keyboard mapping is not user-configurable. This will be
+Currently, PUAE's keyboard mapping is not user-configurable. This will be
 addressed in a future release.
 
 
 International keyboards
 =======================
 
-If you are using E-UAE built with the X11 or SDL graphics drivers then you
+If you are using PUAE built with the X11 or SDL graphics drivers then you
 may set the kbd_lang= option to specify your keyboard layout (you also need
 to pick an appropriate keyboard driver in AmigaOS).
 
@@ -51,7 +51,7 @@ Support for some layouts is currently poor - for example, numeric and
 punctuation keys are interchanged on the French layout - and SDL poorly
 supports international keys.
 
-A partial solution is to use E-UAE's raw key mapping (see below).
+A partial solution is to use PUAE's raw key mapping (see below).
 
 
 Command key sequences
@@ -126,10 +126,10 @@ your keymap settings to produce (if your keymap is correct) a value which
 actually does correspond to the symbol painted on the physical key on your
 keyboard.
 
-If E-UAE tries to work with this translated key symbol, it then has to
+If PUAE tries to work with this translated key symbol, it then has to
 somehow convert that back into a raw keycode appropriate to if that key
 were pressed on an Amiga keyboard (and then AmigaOS will use its keymap
-settings to translate it into a key symbol again). This requires that E-UAE
+settings to translate it into a key symbol again). This requires that PUAE
 know about international keyboard layouts, and requires the graphics system
 to report unique events for all host keys (SDL does not completely support
 some international layouts, for example).
@@ -148,14 +148,14 @@ logically or even physically identical keys.
 The upshot of all this is that raw key-mapping is currently (optionally)
 supported when:
 
-a) E-UAE is built with the X11 graphics driver, your X server supports the
+a) PUAE is built with the X11 graphics driver, your X server supports the
    XKB extension and you are using a keyboard which produces xfree86
    keycodes (e.g., PC and Mac keyboards with XFree86 on Linux do);
-b) E-UAE is built with the SDL graphics driver and you are running it on
+b) PUAE is built with the SDL graphics driver and you are running it on
    Linux on XFree86 with a PC or Mac keyboard, on MacOS X, on BeOS or on
    AmigaOS (or an AmigaOS clone);
-c) E-UAE is built with the BeOS graphics driver; or
-d) E-UAE is built with the AmigaOS graphics driver.
+c) PUAE is built with the BeOS graphics driver; or
+d) PUAE is built with the AmigaOS graphics driver.
 
 As I said above, raw key-mapping better supports international keyboards, so
 is recommended for most users, although its not terribly well tested and
@@ -175,7 +175,7 @@ x11.map_raw_keys=true
 Both the SDL and X11 graphics driver will try to enable raw key-mapping by
 default if they can support it on your host platform.
 
-Note that the AmigaOS version of E-UAE when built with native AmigaOS
+Note that the AmigaOS version of PUAE when built with native AmigaOS
 graphic support and the BeOS version when built with native BeOS graphics
 support both always do raw key mapping, so no comparable config options is
 supported or required in these situations. Note also, however, that the

docs/make_hdf.txt

@@ -2,7 +2,7 @@ make_hdf
 ========
 
 make_hdf is a command-line tool for creating unformatted hard disk
-images (hard files) for E-UAE (and other versions of UAE). It will
+images (hard files) for PUAE (and other versions of UAE). It will
 also print a config option that can be added to a UAE config file to
 mount the created disk image.
 

docs/scsi.txt

 SCSI emulation
 ==============
 
-E-UAE's SCSI emulation allows any CD-ROM drives on the host machine to be
+PUAE's SCSI emulation allows any CD-ROM drives on the host machine to be
 used as Amiga SCSI devices within the emulation. You can use this to fully
 support CD-ROMs, audio discs, CD-writing, etc. in AmigaOS. SCSI emulation is
 also required to emulate a CD-TV or CD32.
 
 In general, to enable SCSI emulation simply add the 'scsi=true' option to
-your config file. Any useable CD or DVD devices that E-UAE finds will be
+your config file. Any useable CD or DVD devices that PUAE finds will be
 available to AmigaOS via the device driver 'uaescsi.device' on consecutive
 unit numbers starting at unit 0. However, depending on your host platform,
 there may a number of host configuration issues which can make using the
 SCSI emulation problematic.
 
-I'll start with the easy stuff. If you're running E-UAE on AmigaOS (or a
+I'll start with the easy stuff. If you're running PUAE on AmigaOS (or a
 clone) or BeOS, then don't worry. The SCSI emulation works transparently.
 Just set the 'scsi=true' config option and away you go.
 
@@ -21,7 +21,7 @@ Just set the 'scsi=true' config option and away you go.
 Linux
 -----
 
-Starting with version 0.8.29, E-UAE's SCSI emulation can directly
+Starting with version 0.8.29, PUAE's SCSI emulation can directly
 communicate with the Linux kernel's CD-ROM driver to access a single
 CD/DVD drive (it currently doesn't support multiple drives, unlike the
 libscg back-end).
@@ -31,13 +31,13 @@ option 'scsi_device=' (as well as, obviously, 'scsi=true'. For example:
 
 scsi_device=/dev/hdc
 
-You should ensure that the account you use to run E-UAE has permission
+You should ensure that the account you use to run PUAE has permission
 to access this device file.
 
 You may run into problems if your Linux distribution has the HAL
 daemon installed. This software continually polls your removable media
 drives to detect insertion/removal of discs, and this activity may
-interfere with E-UAE's SCSI emulation. A solution to this problem
+interfere with PUAE's SCSI emulation. A solution to this problem
 needs to be investigated.
 
 This Linux-native SCSI back-end is less well-tested than the libscg
@@ -64,9 +64,9 @@ we'll come to that in a minute.)
 
 If you're using sg or ide-scsi and sg, then your devices are accessed via
 device nodes of the form /dev/sg0, /dev/sg1, etc. You need read and write
-permission on all of these for SCSI emulation in E-UAE to work (Note that
+permission on all of these for SCSI emulation in PUAE to work (Note that
 cdrecord is typically installed SUID root, so typically the default
-permissions on the /dev/sgx nodes will not be sufficient. Installing E-UAE as
+permissions on the /dev/sgx nodes will not be sufficient. Installing PUAE as
 SUID root is one possibility, but not a terribly good idea security-wise.
 One solution to this is to set the owner of the /dev/sgx nodes as the group
 'cdrom' and add you own user account to that group. For example, as root, do
@@ -80,9 +80,9 @@ If your system doesn't have the adduser command, you can always manually
 edit the /etc/group file or use some whizz-bang, GUI-based user/group
 configuration utility to do the job.
 
-If you log in as yourself again and start E-UAE (remember to add 'scsi=true'
+If you log in as yourself again and start PUAE (remember to add 'scsi=true'
 to your config file first), then the SCSI emulation should work. If so you'll
-see something like this logged to the console when E-UAE starts up.
+see something like this logged to the console when PUAE starts up.
 
 scsibus0:
   0,0,0  0 'BTC     ' 'BCE1610IM       ' 'A.20' CD-ROM
@@ -96,7 +96,7 @@ scsibus0:
 SCSIDEV: 1 devices found
 support_scsi = 1 support_ioctl = 0
 
-If you're using a 2.6 kernel, E-UAE can access ATAPI devices on the host
+If you're using a 2.6 kernel, PUAE can access ATAPI devices on the host
 directly via the kernel ide-cd driver without the sg kernel module. To do
 this on older 2.6 kernels, add the config option
 
@@ -116,7 +116,7 @@ scsi_device=/dev/hdc
 MacOS X
 -------
 
-Now we get to the real problems. SCSI emulation with E-UAE on OS X is
+Now we get to the real problems. SCSI emulation with PUAE on OS X is
 currently a real pig, due to some features and limitations of OS X. The big
 problem is that you need a writable device - a CD or DVD burner - for SCSI
 emulation to work at all. This is because the OS X kernel will only let you

src/cfgfile.c

@@ -2049,7 +2049,7 @@ empty_fs:
 #ifdef FILESYS
 		add_filesys_config (p, -1, dname, aname, str, ro, secs, heads, reserved, bs, bp, fs, hdcv, 0);
 #endif
-	    free (str);
+		free (str);
 		return 1;
 
 invalid_fs:

src/include/autoconf.h

@@ -47,8 +47,8 @@ extern uaecptr need_uae_boot_rom (void);
 struct mountedinfo
 {
     uae_u64 size;
-    int ismounted;
-    int ismedia;
+    bool ismounted;
+    bool ismedia;
     int nrcyls;
 };
 
@@ -59,7 +59,7 @@ struct mountedinfo
 extern char *validatedevicename (char *s);
 extern char *validatevolumename (char *s);
 
-int filesys_insert(int nr, char *volume, const char *rootdir, int readonly, int flags);
+int filesys_insert (int nr, TCHAR *volume, const TCHAR *rootdir, bool readonly, int flags);
 int filesys_eject(int nr);
 int filesys_media_change (const char *rootdir, int inserted, struct uaedev_config_info *uci);
 

src/include/commpipe.h

@@ -9,7 +9,7 @@
 typedef union {
     int i;
     uae_u32 u32;
-    const void *pv;
+    void *pv;
 } uae_pt;
 
 /* These currently require the maximum size to be known at initialization
@@ -55,8 +55,8 @@ STATIC_INLINE void maybe_wake_reader (smp_comm_pipe *p, int no_buffer)
     if (p->reader_waiting
 	&& (no_buffer || ((p->wrp - p->rdp + p->size) % p->size) >= p->chunks))
     {
-	p->reader_waiting = 0;
-	uae_sem_post (&p->reader_wait);
+		p->reader_waiting = 0;
+		uae_sem_post (&p->reader_wait);
     }
 }
 
@@ -65,23 +65,23 @@ STATIC_INLINE void write_comm_pipe_pt (smp_comm_pipe *p, uae_pt data, int no_buf
     int nxwrp = (p->wrp + 1) % p->size;
 
     if (p->reader_waiting) {
-	/* No need to do all the locking */
-	p->data[p->wrp] = data;
-	p->wrp = nxwrp;
-	maybe_wake_reader (p, no_buffer);
-	return;
+		/* No need to do all the locking */
+		p->data[p->wrp] = data;
+		p->wrp = nxwrp;
+		maybe_wake_reader (p, no_buffer);
+		return;
     }
 
     uae_sem_wait (&p->lock);
     if (nxwrp == p->rdp) {
-	/* Pipe full! */
-	p->writer_waiting = 1;
-	uae_sem_post (&p->lock);
-	/* Note that the reader could get in between here and do a
-	 * sem_post on writer_wait before we wait on it. That's harmless.
-	 * There's a similar case in read_comm_pipe_int_blocking. */
-	uae_sem_wait (&p->writer_wait);
-	uae_sem_wait (&p->lock);
+		/* Pipe full! */
+		p->writer_waiting = 1;
+		uae_sem_post (&p->lock);
+		/* Note that the reader could get in between here and do a
+		 * sem_post on writer_wait before we wait on it. That's harmless.
+		 * There's a similar case in read_comm_pipe_int_blocking. */
+		uae_sem_wait (&p->writer_wait);
+		uae_sem_wait (&p->lock);
     }
     p->data[p->wrp] = data;
     p->wrp = nxwrp;
@@ -95,18 +95,18 @@ STATIC_INLINE uae_pt read_comm_pipe_pt_blocking (smp_comm_pipe *p)
 
     uae_sem_wait (&p->lock);
     if (p->rdp == p->wrp) {
-	p->reader_waiting = 1;
-	uae_sem_post (&p->lock);
-	uae_sem_wait (&p->reader_wait);
-	uae_sem_wait (&p->lock);
+		p->reader_waiting = 1;
+		uae_sem_post (&p->lock);
+		uae_sem_wait (&p->reader_wait);
+		uae_sem_wait (&p->lock);
     }
     data = p->data[p->rdp];
     p->rdp = (p->rdp + 1) % p->size;
 
     /* We ignore chunks here. If this is a problem, make the size bigger in the init call. */
     if (p->writer_waiting) {
-	p->writer_waiting = 0;
-	uae_sem_post (&p->writer_wait);
+		p->writer_waiting = 0;
+		uae_sem_post (&p->writer_wait);
     }
     uae_sem_post (&p->lock);
     return data;
@@ -128,7 +128,7 @@ STATIC_INLINE uae_u32 read_comm_pipe_u32_blocking (smp_comm_pipe *p)
     return foo.u32;
 }
 
-STATIC_INLINE const void *read_comm_pipe_pvoid_blocking (smp_comm_pipe *p)
+STATIC_INLINE void *read_comm_pipe_pvoid_blocking (smp_comm_pipe *p)
 {
     uae_pt foo = read_comm_pipe_pt_blocking (p);
     return foo.pv;
@@ -148,7 +148,7 @@ STATIC_INLINE void write_comm_pipe_u32 (smp_comm_pipe *p, int data, int no_buffe
     write_comm_pipe_pt (p, foo, no_buffer);
 }
 
-STATIC_INLINE void write_comm_pipe_pvoid (smp_comm_pipe *p, const void *data, int no_buffer)
+STATIC_INLINE void write_comm_pipe_pvoid (smp_comm_pipe *p, void *data, int no_buffer)
 {
     uae_pt foo;
     foo.pv = data;

src/include/uae_string.h

@@ -13,14 +13,14 @@
 #define UAE_STRING_H
 
 #ifdef HAVE_STRINGS_H
-# include <strings.h>
+#include <strings.h>
 #endif
 #ifdef HAVE_STRING_H
-# include <string.h>
+#include <string.h>
 #endif
 
 #ifdef HAVE_STRDUP
-# define my_strdup strdup
+#define my_strdup strdup
 #else
 extern char *my_strdup (const char *s);
 #endif

src/misc.c

@@ -486,7 +486,7 @@ void setmouseactive (int active)
 
 char *au_fs_copy (char *dst, int maxlen, const char *src)
 {
-        int i;
+        unsigned int i;
 
         for (i = 0; src[i] && i < maxlen - 1; i++)
                 dst[i] = src[i];
@@ -496,13 +496,13 @@ char *au_fs_copy (char *dst, int maxlen, const char *src)
 
 int my_existsfile (const char *name)
 {
-		struct stat sonuc;
-		if (lstat (name, &sonuc) == -1) {
-			return 0;
-		} else {
-			if (!S_ISDIR(sonuc.st_mode))
-				return 1;
-		}
+	struct stat sonuc;
+	if (lstat (name, &sonuc) == -1) {
+		return 0;
+	} else {
+		if (!S_ISDIR(sonuc.st_mode))
+			return 1;
+	}
         return 0;
 }
 

src/tools/config.log

@@ -445,7 +445,7 @@ configure:4344: $? = 0
 configure:4344: result: yes
 configure:4350: checking for _doprnt
 configure:4350: gcc -o conftest -g -O2 -Wall -W -Wno-unused   conftest.c  >&5
-/tmp/cc9SecbZ.o: In function `main':
+/tmp/ccBiDfLi.o: In function `main':
 /home/gnostic/puaex/src/tools/conftest.c:67: undefined reference to `_doprnt'
 collect2: ld returned 1 exit status
 configure:4350: $? = 1
@@ -533,7 +533,7 @@ configure:4364: $? = 0
 configure:4364: result: yes
 configure:4364: checking for strcmpi
 configure:4364: gcc -o conftest -g -O2 -Wall -W -Wno-unused   conftest.c  >&5
-/tmp/ccXI8Zie.o: In function `main':
+/tmp/ccpI9QLu.o: In function `main':
 /home/gnostic/puaex/src/tools/conftest.c:69: undefined reference to `strcmpi'
 collect2: ld returned 1 exit status
 configure:4364: $? = 1
@@ -613,7 +613,7 @@ configure: failed program was:
 configure:4364: result: no
 configure:4364: checking for stricmp
 configure:4364: gcc -o conftest -g -O2 -Wall -W -Wno-unused   conftest.c  >&5
-/tmp/ccaQV0Wi.o: In function `main':
+/tmp/cc94CjOB.o: In function `main':
 /home/gnostic/puaex/src/tools/conftest.c:69: undefined reference to `stricmp'
 collect2: ld returned 1 exit status
 configure:4364: $? = 1