logo
Free, unlimited AI code reviews that run on commit
git-lrc git-lrc GitHub Install Now We'd appreciate a star git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt

fuse — Sinclair ZX Spectrum emulator

Contents

+D Emulation

       Fuse supports emulating the +D disk and printer interface. See the DISKFILEFORMATS  section  for  more
       details  on  supported  disk  file formats. The +D's printer port is emulated. (See the PRINTEREMULATION
       section for more details.) The +D may only be used with 48K, 128K and +2 (not +2A) emulation.  To  access
       disks, you will first need to load G+DOS, by inserting a disk containing the DOS file (+SYS) and entering
       “RUN”.   Once  DOS is loaded, you can load to/from +D disks by prefixing filenames with `dn' where `n' is
       the number of the drive in use.  For example, `LOADd1"myfile"' would load the file named  `myfile'  from
       the emulated drive 1.  Microdrive syntax may also be used.

       To  save  a  snapshot, choose the Machine,NMI menu option, and then press `4' to save a 48K snapshot, or
       `5' to save a 128K snapshot.  When saving a 128K snapshot, you must then press Y or N to indicate whether
       the screen changed while saving the snapshot, to finish saving.  You  can  also  choose  `3'  to  save  a
       screenshot  to  disk.  Holding Caps Shift together with any of these options will cause the +D to save to
       the `other' drive to the one used last.

       Options `1' and `2' allow screenshots  to  be  printed  (in  monochrome,  in  normal  and  large  formats
       respectively)  if  printer  emulation  is  enabled.   For  saving and loading of snapshots, and saving of
       screenshots to disk, G+DOS must be loaded first, but printing of screenshots  can  be  performed  without
       loading G+DOS.

       Finally, `X' will return from the NMI menu.

Author

       Philip Kendall (philip-fuse@shadowmagic.org.uk).

       Matan  Ziv-Av  wrote the SVGAlib and framebuffer UIs, the glib replacement code, and did some work on the
       OSS-specific sound code and the original widget UI code.

       Russell Marks wrote the sound emulation and OSS-specific sound code, the joystick emulation, some of  the
       printer code, and the original version of this man page.

       John Elliott's lib765 and libdsk libraries were used for the original +3 disk and disk image support.

       Ian Collier wrote the ZX Printer emulation (for xz80).

       Darren  Salt  wrote  the original versions of the code for +3 emulation, SLT support, MITSHM support (for
       the Xlib UI), TZX raw data blocks, RZX embedded snapshots and compression, the Kempston  mouse  emulation
       and made many improvements to the widget code.

       Alexander Yurchenko wrote the OpenBSD/Solaris-specific sound code.

       Fredrick Meunier wrote the TC2048, TS2068, Pentagon and Spectrum SE support, the CoreAudio sound code, as
       well as maintaining the OS X port and importing the graphics filter code.

       Ludvig Strigeus and The ScummVM project wrote the original graphics filter code.

       Dmitry Sanarin wrote the original Beta disk interface emulation (for Glukalka).

       Witold Filipczyk wrote the TC2068 support.

       Matthew Westcott wrote the AY logging code and the DivIDE emulation.

       Marek Januszewski wrote various bits of code to make Fuse work under Win32, including the DirectDraw user
       interface.

       Sergio Baldoví made many improvements to the Win32 UI.

       Stuart Brady wrote the DISCiPLE and +D emulation, Scorpion emulation and the HP-UX sound code.

       Garry Lancaster wrote the 8-bit IDE, ZXATASP and ZXCF interface emulations.

       Gergely  Szasz wrote the Interface 1, Microdrive emulation and Didaktik 80 emulation, the PAL TV scalers,
       the TV 3x scaler, the movie logging code, the ALSA and libao sound code, the µPD765 disk controller  used
       in the +3 and made many improvements to the widget code.

       Michael D Wynne wrote the original Opus disk interface emulation (for EightyOne).

       Patrik Persson wrote the SpeccyBoot emulation.

Version 1.6.0                                  27th February, 2021                                       fuse(1)

Beta 128 Emulation

       Fuse supports Betadisk emulation in its Pentagon and Scorpion emulation, and also under 48K, TC2048, 128K
       and  +2  (but  not +2A) emulation if the Beta128interface option from the Options,Peripherals,Disk...
       dialog is enabled. When that option is used in 48K or TC2048 emulation  the  Beta128auto-bootin48Kmachines  option additionally controls whether the machine boots directly into the TR-DOS system. See the
       DISKFILEFORMATS section for more details on supported disk file formats.

Bugs

       Selecting a startup filter doesn't work properly with user interfaces other than SDL, Win32 and GTK.

       Changing virtual consoles when using SVGAlib for joystick support causes Fuse  to  exit.  If  this  is  a
       problem, compile Fuse with the `--disable-ui-joystick' option.

       The poke finder can't search outside `normal' RAM.

       The  libao  file  output  devices not work properly with the GTK UI.  No error reporting, but the created
       file does not contain any sound data.  If you use a `weak' machine alsa09 makes a lot of clicks and  pops
       and will output `ALSA:underrun,atleast0ms.'  error messages.

Compressed Files

       Assuming  the  appropriate  libraries  were  available  when libspectrum(3) was compiled, snapshots, tape
       images, dock cartridges and input recording files (RZX) can be read from files compressed with  bzip2(3),
       gzip(3) or zip(3) just as if they were uncompressed. In the zip case, only the first supported file found
       inside  the  archive  is loaded.  There is currently no support for reading compressed +3, DISCiPLE/+D or
       Beta disk images.

Description

       Fuse  is  a  Sinclair  ZX Spectrum  emulator.  It supports several models (including the 128), with quite
       faithful emulation of the display and sound.

       The emulator can load any of the formats supported by libspectrum(3) — this includes  Z80,  SNA  and  SZX
       snapshots,  and PZX, TAP and TZX virtual-tape files. Saving to SZX, Z80 and SNA snapshots and TZX and TAP
       tape files is supported. The SLT extension to the Z80 format is partly supported (enough  for  multi-load
       games); however, loading of the old DAT-file variant is not.

       DSK,  UDI,  FDI,  TD0,  MGT,  IMG,  D40, D80, SAD, TRD, SCL and OPD disk images are supported when a disk
       interface is being emulated, including the integrated disk drives on +3, Pentagon or Scorpion machines as
       well as the +D, DISCiPLE, Opus Discovery, Beta 128 and Didaktik 80 interfaces. DCK cartridge  images  are
       supported when emulating a Timex 2068 variant. Interface 2 ROM cartridges are also supported.

       Finally, there is also support for reading and writing the RZX input recording format.

       See  the  COMPRESSEDFILES  section  for  details  on reading files compressed with bzip2(3), gzip(3) or
       zip(3).

Didaktik 80 Emulation

       Fuse  supports  Didaktik  80  (and  Didaktik  40)  emulation.   It  emulates  the original version of the
       Didaktik 80, running MDOS 1 and with a WD2797 floppy controller.  See the DISKFILEFORMATS  section  for
       more  details  on supported disk file formats.  The Didaktik 80 may only be used with 16K, 48K and TC2048
       emulation.  To press the Didaktik 80's `SNAP' button, choose the Machine,DidaktikSNAP menu option.

Disciple Emulation

       Fuse supports emulating the DISCiPLE disk and printer interface, although it does not  currently  support
       emulation of the Sinclair Network, or support emulation of a DISCiPLE attached to a 128K machine. See the
       DISKFILEFORMATS section for more details on supported disk file formats, which are the same as for +D
       emulation as described above. The DISCiPLE's printer port is emulated. (See the PRINTEREMULATION section
       for more details.) The DISCiPLE may only be used with 48K emulation at present.   To  access  disks,  you
       will first need to load GDOS, by inserting a disk containing the DOS file (SYS) and entering “RUN”.  Once
       DOS  is  loaded,  you  can  load to/from DISCiPLE disks by prefixing filenames with `dn' where `n' is the
       number of the drive in use.  For example, `LOADd1"myfile"' would load the file named `myfile'  from  the
       emulated drive 1.  Microdrive syntax may also be used.

       Snapshots  can  be  saved in a similar manner to that of the +D as described above, but note that GDOS on
       the DISCiPLE contains a bug which causes corruption as soon as  the  NMI  button  is  pressed,  affecting
       saving  of  snapshots,  and  also loading of snapshots that were originally saved with a +D or SAM Coupé.
       This will cause corruption even when a screenshot is printed, or if the menu is never even entered in the
       first place (due to Caps Shift not being pressed down, as is required for the  DISCiPLE),  provided  that
       GDOS  is loaded.  This bug is not present in G+DOS on the +D.  (Note: this was caused by saving/restoring
       the AF register twice in the NMI handler, where both AF and the AF'  shadow  register  should  have  been
       saved/restored.)

       The  NMI  button works slightly differently on the DISCiPLE than on the +D.  Caps Shift must be held down
       whilst pressing the NMI button, and there is  no  `X'  option  to  exit  the  menu.   Also,  printing  of
       screenshots  requires  GDOS to be loaded.  Depending on the UI that you're using, holding down Caps Shift
       whilst choosing the Machine,NMI menu option may be slightly tricky, or even impossible.  For the GTK UI,
       ensure that the Shift key is held before entering on the Machine menu.  For the widget UI,  it  does  not
       seem possible to perform this action.

Disk File Formats

       Fuse supports several disk image formats in its +D, Didaktik, DISCiPLE and Beta 128 emulation.

       For reading:

       .UDI
              Ultra  Disk  Image;  for  specification  please  see http://faqwiki.zxnet.co.uk/wiki/UDI_format or
              http://zxmak.chat.ru/docs.htm

              This is the only image format which can store all the relevant information of the recorded data on
              a magnetic disk, so it can be used for any nonstandard disk format. Fuse can  read  all  extended
              track types too (mixed FM/MFM, or tracks with `WEAK' data or even compressed tracks too).

       .FDI
              UKV Spectrum Debugger disk image format.

       .MGT.IMG
              DISCiPLE/+D file formats.

       .SAD
              For  compatibility  with  SAM  Coupé  disk images using these formats.  Note that SAM Coupé `.DSK'
              images share the same format as `.MGT'.

       .D80.D40
              Didaktik 80 and Didaktik 40 file formats.

       .TRD
              TR-DOS disk image. TRD and SCL sectors are loaded  interleaved,  therefore  you  might  experience
              problems with TR-DOS ROMs that use the turbo format (sequential sectors); for detailed information
              please see http://web.archive.org/web/20070808150548/http://www.ramsoft.bbk.org/tech/tr-info.zip.SCL
              A  simple  archive  format  for  TR-DOS  disk  files.  For specification please see http://www.zx-modules.de/fileformats/sclformat.html.TD0
              Teledisk image format; Fuse supports only files  which  do  not  use  the  “Advanced  Compression”
              option. Detailed description found in http://www.classiccmp.org/dunfield/img54306/td0notes.txt and
              https://web.archive.org/web/20130116072335/http://www.fpns.net/willy/wteledsk.htm.DSK
              CPC  disk  image  format; Fuse supports the plain old and the new extended CPC format too. Further
              information please  see  the  THE.DSKFORMAT  section  and  the  CPCEMU  manual  section  7.7.1
              http://www.cpc-emu.org/linux/cpcemu_e.txt or the http://www.cpctech.org.uk/docs/extdsk.html.OPD.OPU
              Opus Discovery file formats.

       Fuse  supports  most  of the above formats for writing: .UDI.FDI.MGT.IMG.SAD.D80.D40.TRD.SCL.OPD.OPU.DSK (only the old CPC format).

       You can save  disk  images  with  any  output  format,  just  select  the  appropriate  extension.  (e.g.
       `elite3.udi' to save as an UDI file). If the appropriate libraries were available when libspectrum(3) was
       compiled,  than Fuse will try to create UDI images with compressed tracks to save disk space.  There is a
       .LOG `image' format for debugging purpose. This is a plain text file that contains  three  dumps  of  the
       loaded  disk  image  at  different details.  Not all image formats can store all disk images.  You cannot
       save a disk image with an inappropriate format that loses some information (e.g. variable track length or
       sector length).

Display Size

       Some of Fuse's UIs allow resizing of the emulated Spectrum's display.  For the  window-based  ones  (GTK,
       Win32  and  Xlib), you can resize the window by, well, resizing it. :-) Exactly how this works depends on
       your window manager; you may have to make the window over twice the width and height of the original size
       before it actually scales up. Fuse attempts to keep the window `square', but with  some  window  managers
       this can mean the window will never resize at all. If you experience this problem, the `--no-aspect-hint'
       option may help.

       If  you're using the SDL UI under X11 or GTK, the window will automatically resize to be the correct size
       for the graphics filter selected.

Divide

       The DivIDE is  another  IDE  interface  for  the  Spectrum,  of  which  full  details  can  be  found  at
       http://web.archive.org/web/20150302052256/http://baze.au.com/divide/.  The interface can be activated via
       the  DivIDEinterface  option from the Options,Peripherals,Disk...  dialog, and the state of its write
       protect jumper controlled via the DivIDEwriteprotectoption.  If you're going to be using  the  DivIDE,
       you'll probably want one of the firmwares available from the DivIDE homepage.

Divmmc

       The  DivMMC  is  a  MMC  interface  for the Spectrum. Originally designed by Alessandro Dorigatti for the
       V6Z80P+ FPGA board as the fusion of DivIDE and ZXMMC+ interfaces, later assembled  as  an  interface  for
       real spectrums by Mario Prato. Currently there are variants with different RAM size, one/two memory cards
       slots, optional kempston jostick, etc.

       The  interface  can  be  activated via the DivMMCinterface option from the Options,Peripherals,Disk...
       dialog, and the state of its EEPROM write protect jumper controlled via the DivMMCwriteprotectoption.
       If you're going to be using the DivMMC, you'll need to load the ESXDOS firmware at http://www.esxdos.org/
       or use the ZX Spectrum +3e ROMs by Garry Lancaster.

       You'll also need a HDF image to store the contents of the memory card.  There are several tools to create
       and manipulate this file format, e.g., hdfmonkey at https://github.com/gasman/hdfmonkey.

File Selection

       The way you select a file (whether snapshot or tape file) depends on which UI you're using.  So  firstly,
       here's how to use the GTK file selector.

       The  selector  shows  the  directories  and files in the current directory in two separate subwindows. If
       either list is too big to fit in the window, you can use the scrollbar to see the rest (by  dragging  the
       slider,  for  example),  or you can use Shift–Tab (to move the keyboard focus to a subwindow) and use the
       cursor keys.  To change directory, double-click it.

       To choose a file to load you can either double-click it, or click it then click Ok.  Or click  Cancel  to
       abort.

       If  you're using the keyboard, probably the easiest way to use the selector is to just ignore it and type
       in the name. This isn't as irksome as it sounds, since the filename input box has filename  completion  —
       type  part of a directory or file name, then press Tab.  It should complete it. If it was a directory, it
       moves to that directory; if the completion was ambiguous, it completes as much as possible,  and  narrows
       the  filenames  shown  to  those  which  match.  You  should  press Enter when you've finished typing the
       filename, or Esc to abort.

       Now, if you're using the widget UI — the one  using  the  Spectrum  font  —  the  selector  works  a  bit
       differently. The files and directories are all listed in a single two-column-wide window (the directories
       are shown at the top, ending in `/') — the names may be truncated onscreen if they're too long to fit.

       To  move  the  cursor,  you  can  either  use  the  cursor  keys, or the Spectrum equivalents 5/6/7/8, or
       (similarly) h/j/k/l. For faster movement, the PageUp, PageDown, Home, and End keys are supported and do
       what you'd expect. To select a file or directory, press Enter.  To abort, press Esc.

       With both selectors, do bear in mind that all files are shown, whether Fuse would be able to load them or
       not.

Files

~/.fuserc

Graphics Filters

       Fuse has the ability to apply essentially arbitrary filters between building its image of the  Spectrum's
       screen,  and  displaying  it  on the emulating machine's monitor. These filters can be used to do various
       forms of smoothing, emulation of TV scanlines and  various  other  possibilities.  Support  for  graphics
       filters  varies between the different user interfaces, but there are two general classes: the GTK, Win32,
       Xlib, SVGAlib and SDL user interfaces (and  the  saving  of  .png  screenshots)  support  `interpolating'
       filters  which  use a palette larger than the Spectrum's 16 colours, while the framebuffer user interface
       currently does not support filters at all.

       A further complication arises due to the fact that the Timex machines have  their  high-resolution  video
       mode  with  twice  the  horizontal  resolution. To deal with this, Fuse treats these machines as having a
       `normal' display size which is twice the size of a normal Spectrum's screen, leading to a  different  set
       of  filters  being available for these machines. Note that any of the double or triple-sizing filters are
       available for Timex machines only when using the SDL, Win32 or GTK user interfaces.

       The available filters, along with their short name used to select them from the command line, are:

       Timexhalf(smoothed) (half)
       Timexhalf(skipping) (halfskip)
              Two Timex-machine specific filters which scale the screen down to half normal (Timex)  size;  that
              is,  the same size as a normal Spectrum screen. The difference between these two filters is in how
              they handle the high-resolution mode: the `smoothed' version  is  an  interpolating  filter  which
              averages  pairs  of  adjacent  pixels,  while the `skipping' version is a non-interpolating filter
              which simply drops every other pixel.

       Normal (normal)
              The simplest filter: just display one pixel for every pixel on the Spectrum's screen.

       Doublesize (2x)
              Scale the displayed screen up to double size.

       Triplesize (3x)
              Scale the displayed screen up to triple size. Available only with the GTK,  Win32,  Xlib  and  SDL
              user interfaces or when saving screenshots of non-Timex machines.

       Quadruplesize (4x)
              Scale  the  displayed screen up to quadruple size. Available only with the GTK, Win32 and SDL user
              interfaces.

       2xSaI (2xsai)
       Super2xSaI (super2xsai)
       SuperEagle (supereagle)
              Three interpolating filters which apply successively more smoothing. All three double the size  of
              the displayed screen.

       AdvMAME2x (advmame2x)
              A double-sizing, non-interpolating filter which attempts to smooth diagonal lines.

       AdvMAME3x (advmame3x)
              Very similar to AdvMAME2x, except that it triples the size of the displayed screen. Available only
              with  the  GTK,  Win32,  Xlib  and  SDL  user  interfaces  or when saving screenshots of non-Timex
              machines.

       TV2x (tv2x)
       TV3x (tv3x)
       TV4x (tv4x)
       TimexTV (timextv)
              Four filters which attempt to emulate the effect of television scanlines. The first is  a  double-
              sizing filter for non-Timex machines, the second is a similar triple-sizing filter, the third is a
              similar quadruple-sizing filter, while the last is a single-sizing filter for Timex machines (note
              that this means TV 2X and Timex TV produce the same size output).

       PALTV (paltv)
       PALTV2x (paltv2x)
       PALTV3x (paltv3x)
       PALTV4x (paltv4x)
              Four  filters  which  attempt  to  emulate  the  effect of the PAL TV system which layers a lower-
              resolution colour image over the top of a higher-resolution black-and-white image. The filters can
              also optionally add scanlines like the other TV series scalers.

       Dotmatrix (dotmatrix)
              A double-sizing filter which emulates the effect of a dot-matrix display.

       Timex1.5x (timex15x)
              An interpolating Timex-specific filter which scales the Timex screen up to  1.5×  its  usual  size
              (which  is therefore 3× the size of a `normal' Spectrum screen). Available only for the GTK, Win32
              and SDL user interfaces or when saving screenshots.

       Timex2x (timex2x)
              A non-interpolating Timex-specific filter which scales the Timex screen up to 2×  its  usual  size
              (which  is therefore 4× the size of a `normal' Spectrum screen). Available only for the GTK, Win32
              and SDL user interfaces or when saving screenshots.

       HQ2x (hq2x)
       HQ3x (hq3x)
       HQ4x (hq4x)
              Three filters which do high quality (but slow) antialiasing. Doubles and  triples  and  quadruples
              the size of the displayed screen respectively.

Key Mappings

       When emulating the Spectrum, keys F1 to F10 are used as shortcuts for various menu  items,  as  described
       above.  The  alphanumeric  keys  (along  with Enter and Space) are mapped as-is to the Spectrum keys. The
       other key mappings are:

       Shift  emulated as Caps Shift

       Control, Alt, and Meta
              emulated as Symbol Shift (most other modifiers are also mapped to this)

       Backspace
              emulated as Caps–0 (Delete)

       Esc    emulated as Caps–1 (Edit)

       CapsLock
              emulated as Caps–2

       Cursorkeys
              emulated as Caps–5/6/7/8 (as appropriate)

       Tab    emulated as Caps Shift–Symbol Shift (Extended Mode)

       Some further punctuation keys are supported, if they exist on your keyboard — `,', `.',  `/',  `;',  `'',
       `#', `-', and `='.  These are mapped to the appropriate symbol-shifted keys on the Spectrum.

       A  list  of  keys applicable when using the file selection dialogs is given in the FILESELECTION section
       below.

Monitor/Debugger

       Firstly, note that the vast majority of this section applies only if you're using the GTK user interface;
       if you're using one of the widget user interfaces, you'll get  a  very  basic  monitor  which  shows  the
       current values of the registers and allows you to single step through execution or continue.

       If  you  are  using  the  GTK user interface, Fuse features a moderately powerful, completely transparent
       monitor/debugger, which can be activated via the Machine,Debugger...  menu  option.  A  debugger  window
       will  appear,  showing  the  current state of the emulated machine: the top-left `pane' shows the current
       state of the Z80 and the last bytes written to any emulated peripherals. The bottom-left pane  lists  any
       active  breakpoints. Moving right, the next pane shows where the Spectrum's 64K memory map (the `W?'  and
       `C?'  indicate whether each displayed chunk is writable or  contended  respectively).   Fuse  tracks  the
       memory  mapping of the overall address space in 2KB chunks but will summarise the mapped pages where they
       are part of the same page of the underlying memory source (e.g. 8KB page sizes in the Spectrum  128K  and
       4KB pages in the Timex clones' DOCK and EXROM banks).

       The  next  pane  to  the right has a disassembly, which by default starts at the current program counter,
       although this can be modified either by  the  `disassemble'  command  (see  below)  or  by  dragging  the
       scrollbar  next  to  it. The next pane shows the current stack, and the final pane any `events' which are
       due to occur and could affect emulation. Any of these panes can be removed by use of the View menu. Below
       the displays are an entry box for debugger commands, and five buttons for controlling the debugger:

       Evaluate
              Evaluate the command currently in the entry box.

       SingleStep
              Run precisely one Z80 opcode and then stop emulation again.

       Continue
              Restart emulation, but leave the debugger window open. Note that the debugger window will  not  be
              updated while emulation is running.

       Break
              Stop emulation and return to the debugger.

       Close
              Close the debugger window and restart emulation.

       Double-clicking  on  an  entry  in  the  stack pane will cause emulation to run until the program counter
       reaches the value stored at that address, while double-clicking on an entry in  the  `events'  pane  will
       cause emulation to run until that time is reached.

       The  main  power  of  the  debugger  is via the commands entered into the entry box, which are similar in
       nature (but definitely not identical to or as powerful as) to those in gdb(1).  In general, the  debugger
       is  case-insensitive,  and  numbers will be interpreted as decimal, unless prefixed by either `0x' or `$'
       when they will be interpreted as hex. Each command can be abbreviated to the portion not in curly braces.

       ba{se} number
              Change the debugger window to displaying output in base number.  Available values are 10 (decimal)
              or 16 (hex).

       br{eakpoint} [address] [if condition]
              Set a breakpoint to stop emulation and return to the debugger whenever an opcode  is  executed  at
              address  and  condition evaluates true. If address is omitted, it defaults to the current value of
              PC.

       br{eakpoint} p{ort} (re{ad}|w{rite}) port [if condition]
              Set a breakpoint to trigger whenever IO port port  is  read  from  or  written  to  and  condition
              evaluates true.

       br{eakpoint} (re{ad}|w{rite}) [address] [if condition]
              Set  a  breakpoint  to  trigger  whenever  memory location address is read from (other than via an
              opcode fetch) or written to and condition evaluates true.  Address again defaults to  the  current
              value of PC if omitted.

       br{eakpoint} ti{me} time [if condition]
              Set  a  breakpoint  to  occur  time tstates after the start of the every frame, assuming condition
              evaluates true (if one is given).

       br{eakpoint} ev{ent} area:detail [if condition]
              Set a breakpoint to occur when the event specified by area:detail occurs and  condition  evaluates
              to true. The events which can be caught are:

              beta128:page
              beta128:unpage
                     The Beta 128 interface is paged into or out of memory respectively.
              didaktik80:page
              didaktik80:unpage
                     The Didaktik 80 interface is paged into or out of memory respectively.
              disciple:page
              disciple:unpage
                     The DISCiPLE interface is paged into or out of memory respectively.
              divide:page
              divide:unpage
                     The DivIDE interface is paged into or out of memory respectively.
              divmmc:page
              divmmc:unpage
                     The DivIDE interface is paged into or out of memory respectively.
              if1:page
              if1:unpage
                     The Interface 1 shadow ROM is paged into or out of memory.
              multiface:page
              multiface:unpage
                     The Multiface One/128/3 is paged into or out of memory respectively.
              opus:page
              opus:unpage
                     The Opus Discovery is paged into or out of memory respectively.
              plusd:page
              plusd:unpage
                     The +D interface is paged into or out of memory respectively.
              rzx:end
                     An RZX recording finishes playing.
              speccyboot:page
              speccyboot:unpage
                     The SpeccyBoot interface is paged into or out of memory.
              spectranet:page
              spectranet:unpage
                     The Spectranet interface is paged into or out of memory.
              tape:play
              tape:stop
                     The emulated tape starts or stops playing.
              zxatasp:page
              zxatasp:unpage
                     The ZXATASP interface is paged into or out of memory.
              zxcf:page
              zxcf:unpage
                     The ZXCF interface is paged into or out of memory.

              In all cases, the event can be specified as area:* to catch all events from that area.

       cl{ear} [address]
              Remove  all  breakpoints  at  address  or  the  current  value  of  PC if address is omitted. Port
              read/write breakpoints are unaffected.

       com{mmands} id<newline><debuggercommand><newline><debuggercommand><newline>...
       end
              Set things such  that  the  specified  debugger  commands  will  be  automatically  executed  when
              breakpoint  id is triggered. There is currently no user interface for entering multi-line debugger
              commands,  so  the  only  way  to  specify  this  command  is  on   the   command-line   via   the
              --debugger-command option.

       cond{ition} id [condition]
              Set  breakpoint  id  to  trigger  only  when condition is true, or unconditionally if condition is
              omitted.

       co{ntinue}
              Equivalent to the Continue button.

       del{ete} [id]
              Remove breakpoint id, or all breakpoints if id is omitted.

       di{sassemble} address
              Set the centre panel disassembly to begin at address.

       ex{it} [expression]
              Exit the emulator immediately, using the exit code resulting from the evaluation of expression, or
              0 if expression is omitted.

       fi{nish}
              Exit from the current CALL or equivalent. This isn't infallible: it works by setting  a  temporary
              breakpoint  at  the  current  contents of the stack pointer, so will not function correctly if the
              code returns to some other point or plays with  its  stack  in  other  ways.  Also,  setting  this
              breakpoint doesn't disable other breakpoints, which may trigger before this one. In that case, the
              temporary breakpoint remains, and the `continue' command can be used to return to it.

       i{gnore} idcount
              Do not trigger the next count times that breakpoint id would have triggered.

       n{ext}
              Step  to the opcode following the current one. As with the `finish' command, this works by setting
              a temporary breakpoint at the next opcode, so is not infallible.

       o{ut} portvalue
              Write value to IO port port.

       pr{int} expression
              Print the value of expression to standard output.

       se{t} addressvalue
              Poke value into memory at address.

       se{t} $variablevalue
              Set the value of the debugger variable variable to value.

       se{t} area:detailvalue
              Set the value of the system variable area:detail to value.  The  available  system  variables  are
              listed below.

       s{tep}
              Equivalent to the SingleStep button.

       t{breakpoint} [options]
              This  is  the same as the `breakpoint' command in its various forms, except that the breakpoint is
              temporary: it will trigger once and once only, and then be removed.

       Addresses can be specified in one of two forms: either an absolute addresses, specified by an integer  in
       the  range  0x0000  to 0xFFFF or as a `source:page:offset' combination, which refers to a location offset
       bytes into memory bank page, independent of where that bank is currently paged into memory. RAM  and  ROM
       pages  are  indicated, respectively, by `RAM' and `ROM' sources (e.g. offset 0x1234 in ROM 1 is specified
       as `ROM:1:0x1234').  Other available sources are: `Betadisk',  `Didaktik80RAM',  `Didaktik80ROM',
       `DISCiPLERAM', `DISCiPLEROM', `DivIDEEPROM', `DivIDERAM', `DivMMCEPROM', `DivMMCRAM', `If1', `If2',
       `MultifaceRAM',  `MultifaceROM',  `OpusRAM',  `OpusROM',  `PlusDRAM', `PlusDROM', `SpeccyBoot',
       `Spectranet', `TimexDock', `TimexEXROM', `uSource', `ZXATASP' and `ZXCF'.  Please, note that spaces  in
       memory sources should be escaped, e.g., `break Didaktik\ 80\ ROM:0:0x1234'.  The 48K machines are treated
       as  having  a  permanent  mapping  of  page 5  at  0x4000,  page 2  at  0x8000  and page 0 at 0xC000; the
       16K Spectrum is treated as having page 5 at 0x4000 and no page at 0x8000 and 0xC000.

       Anywhere the debugger is expecting a numeric value, except where it expects  a  breakpoint  id,  you  can
       instead  use a numeric expression, which uses a restricted version of C's syntax; exactly the same syntax
       is used for conditional breakpoints, with `0' being false and any other  value  being  true.  In  numeric
       expressions,  you  can  use  integer constants (all calculations are done in integers), system variables,
       debugger variables, parentheses, the standard four numeric  operations  (`+',  `-',  `*'  and  `/'),  the
       (non-)equality  operators  `=='  and  `!=', the comparison operators `>', `<', `>=' and `<=', bitwise and
       (`&'), or (`|') and exclusive or (`^') and logical and (`&&') and or (`||').  Square  brackets  (`['  and
       `]')  can be used to dereference a value; for example `[0x4000]' will give the value of the first byte of
       the screen.

       System variables are specified via an `area:detail' syntax. The available system variables are:

       ay:current
              The current AY-3-8912 register.
       divmmc:control
              The last byte written to DivMMC control port.
       spectrum:frames
              The frame count since reset. Note that this variable can only be read, not written to.
       tape:microphone
              The current level of the tape input connected to the `EAR' port. Note that this variable can  only
              be read, not written to.
       ula:last
              The last byte written to the ULA. Note that this variable can only be read, not written to.
       ula:mem1ffd
              The  last byte written to memory control port used by the ZX Spectrum +2A/3; normally addressed at
              0x1ffd, hence the name.
       ula:mem7ffd
              The last byte written to primary memory control port used  by  the  ZX  Spectrum  128  and  later;
              normally addressed at 0x7ffd, hence the name.
       ula:tstates
              The number of tstates since the last interrupt.
       z80: registername
              The value of the specified register. Both 8-bit registers and 16-bit register pairs are supported.
              The  MEMPTR  /  WZ  hidden  register is also supported. The (presumable) Q hidden register is also
              supported.
       z80:im
              The current interrupt mode of the Z80.
       z80:iff1
       z80:iff2
              1 if the specified interrupt flip-flop is currently set, or 0 if it is not set.

Movie Recording

       Fuse can save movies with sound in a specific file format (FMF).  This recording is very fast, and has  a
       moderate  size, but you need to use the fmfconv(1) program in fuse-utils(1) to convert into regular video
       and/or audio files.  The --movie-compr option allows you to set the compression level to  None,  Lossless
       or High. If zlib(3) is not available, only None is valid. The default when Zlib is available is Lossless.
       Recording  a  movie  may  slow down emulation, if you experience performance problems, you can try to set
       compression to None.

       Fuse records every displayed frame, so by default the recorded file has about 50 video frame per  second.
       A  standard  video  has  about  24–30/s  framerate,  so  if you set Options/General/Framerate1:n or the
       equivalent --rate command line option to 2 than recording frame rate reduces about 25/s. The exact  frame
       rate depends on the Z80 clock frequency which varies depending on the specific emulated machine.

       Note:  You  can  see all of the “gfx” effects only if the Fuse frame rate option is set to 1, but in most
       cases you can safely use 2. Also, movie recording stops if the emulated machine is changed.

       The recorded sound sampling rate and the channel number is equal with the Fuse generated  sound  sampling
       rate  (44100 Hz  by  default)  and  channel  number (mono by default). The common sampling frequencies in
       standard video files are 44100 Hz and 48000 Hz. If you use  --sound-freq  command  line  option  you  can
       change the frequency.

       You  can  record stereo sound if you use AYstereoseparation or the equivalent --separation command line
       switch.

       You can use fmfconv(1) to convert recorded movie file into a standard video file.

       Examplesfuse--movie-startoutput.fmf--rate2--sound-freq44100--separationACB

       start video recording about 25/s video frame rate and 44100 Hz sampling frequency  stereo  sound  default
       compression level.

Name

       fuse — Sinclair ZX Spectrum emulator

Options

--accelerate-loader
              Specify whether Fuse should attempt to accelerate tape loaders by “short circuiting”  the  loading
              loop.  This  will  in  general  speed  up loading, but may cause some loaders to fail. (Enabled by
              default, but you can use `--no-accelerate-loader' to disable).  The  same  as  the  Media  Options
              dialog's Accelerateloaders option.

       --aspect-hint
              Specify  whether  the  GTK  and Xlib user interfaces should `hint' to the window manager about the
              preferred aspect ratio for the graphics window, thus preventing resizing to non-square sizes which
              lead to Fuse not displaying correctly. This option has been observed to cause problems  with  some
              window  managers when using the GTK UI which can prevent the window from being resized or moved at
              all. (Enabled  by  default,  but  you  can  use  `--no-aspect-hint'  to  disable).  See  also  the
              `--strict-aspect-hint' option.

       --autosave-settings
              Specify  whether  Fuse's  current  settings should be automatically saved on exit. The same as the
              General Options dialog's Auto-savesettings option.

       --auto-load
              Specify whether tape and disk files should be automatically loaded when they are opened using  the
              File,Open...   menu  option. In the case of TRD/SCL disk images, inserts also a boot loader file
              when none is available. (Enabled by default, but you can use `--no-auto-load' to disable). Same as
              the Media Options dialog's Auto-loadmedia option.

       --beta128
              Emulate a Beta 128 interface. Same as the Disk Peripherals  Options  dialog's  Beta128interface
              option.

       --beta128-48boot
              When  a  Beta 128  interface  is  used in 48K or TC2048 emulation the option additionally controls
              whether the machine boots directly into the TR-DOS system. Same as the  Disk  Peripherals  Options
              dialog's Beta128auto-bootin48Kmachines option.

       --betadiskfile
              Insert  the  specified  file  into the emulated Beta disk interface's drive A: and select Pentagon
              mode on startup.

       --bw-tv
              Specify whether the display should simulate a colour or black and white television. This option is
              effective under the GTK, Win32, Xlib and SDL user interfaces: the others will  always  simulate  a
              colour TV.  The same as the General Options dialog's BlackandwhiteTV option.

       --cmos-z80
              This  option specifies that Fuse should emulate a CMOS Z80, as opposed to an NMOS Z80. Same as the
              General Options dialog's Z80isCMOS option.

       --competition-codecode
              Specify the code to be written to competition mode RZX files. The same as the RZX Options dialog's
              Competitioncode option.

       --competition-mode
              Specify whether input recordings should be made in  `competition  mode'.   The  same  as  the  RZX
              Options dialog's Competitionmode option.

       --compress-rzx
              Specify  whether  RZX files should be written out compressed. (Enabled by default, but you can use
              `--no-compress-rzx' to disable). Same as the RZX Options dialog's CompressRZXdata option.

       --confirm-actions
              Specify whether `dangerous' actions (those which could cause data loss, for example resetting  the
              Spectrum)   require   confirmation  before  occurring.  (Enabled  by  default,  but  you  can  use
              `--no-confirm-actions' to disable). This option is  the  same  as  the  General  Options  dialog's
              Confirmactions option.

       --covox
              Emulate  a  Covox  sound  interface for Pentagon/Scorpion. Same as the General Peripherals Options
              dialog's Covox option.

       --debugger-commandstring
              Specify a debugger command to be run before emulator startup. This can be used to set  breakpoints
              or  the  like.  Currently, this is the only method to input multi-line debugger commands. (See the
              MONITOR/DEBUGGER section for more information).

       --detect-loader
              Specify whether Fuse should attempt to detect when the tape is being accessed and start  and  stop
              the  virtual tape playing automatically. (Enabled by default, but you can use `--no-detect-loader'
              to disable). Same as the Media Options dialog's Detectloaders option.

       --disciple
              Emulate a DISCiPLE interface. Same as the Disk Peripherals  Options  dialog's  DISCiPLEinterface
              option.

       --disciplediskfile
              Insert the specified file into the emulated DISCiPLE's drive 1.

       --didaktik80
              Emulate  a  Didaktik  80  (or  Didaktik  40)  disk interface. Same as the Disk Peripherals Options
              dialog's Didaktik80interface option.

       --didaktik80diskfile
              Insert the specified file into the emulated Didaktik 80 (or Didaktik 40)'s drive A.

       --disk-ask-merge
              Prompt the user to confirm whether Fuse should try to merge the `B' side of a disk  image  from  a
              separate file when opening a new single-sided disk image.

       --disk-try-mergemode
              Select  whether Fuse should try to merge a separate file for the `B' side of a disk image separate
              file when opening a new disk image. Most double sided disk images are dumped as two  single  sided
              disk  images e.g.  `Golden Axe - Side A.dsk' and `Golden Axe - Side B.dsk'. So, if we want to play
              Golden Axe, first we have to insert the first disk image and when the game asks to insert  side B,
              we  have  to  find  and open the second disk image, instead of just `flip'-ing the disk inside the
              drive. If enabled, Fuse will try to open the second image too and create a double sided disk image
              (merging the two one sided disk images) and insert this merged virtual disk into the  disk  drive.
              The  function detects whether the file is one side of a double-sided image if the filename matches
              a pattern like [Ss]ide[ _][abAB12][ _.] in the file name of a disk that is being opened. If found,
              Fuse will try to open the other side of the disk too substituting the  appropriate  characters  in
              the  filename e.g.  1→2, a→b, A→B. If successful then it will merge the two images and now we have
              a double sided disk in drive. This means that if we open `Golden Axe - Side A.dsk', then Fuse will
              try to open `Golden Axe - Side B.dsk' too. Now, we can just `flip' the disk if Golden Axe asks for
              `Side B'.  The available options are Never, Withsingle-sideddrives and Always.

       --divide
              Emulate the DivIDE interface. The same as the Disk Peripherals Options dialog's  DivIDEinterface
              option.

       --divide-masterfilefile--divide-slavefilefile
              Specify an IDE image to be loaded into the DivIDE's emulated master and slave drives respectively.

       --divide-write-protect
              Specify  that the emulated DivIDE's write protect jumper should be considered set. The same as the
              Disk Peripherals Options dialog's DivIDEwriteprotect option.

       --divmmc
              Emulate the DivMMC interface. The same as the Disk Peripherals Options dialog's  DivMMCinterface
              option.

       --divmmc-filefile
              Specify an HDF image to be loaded into the DivMMC's emulated memory card.

       --divmmc-write-protect
              Specify  that the emulated DivMMC's write protect jumper that protects EEPROM should be considered
              set. The same as the Disk Peripherals Options dialog's DivMMCwriteprotect option.

       --dockfile
              Insert the specified file into the emulated Timex 2068 variant dock; also  select  the  TC2068  on
              startup if available.

       -Dmode--doublescan-modemode
              Specify whether to use doublescan modes in the FB UI.  Available values for mode are 0, 1 and 2. 0
              means `never doublescan' (use 640×480 at either 72 Hz or 60 Hz), whereas 1 and 2 both mean `try to
              use  doublescan' and will fall back on the 640×480 modes. 1 selects 72 Hz modes (the same size and
              shape as your typical 640×480), and 2 selects 60 Hz modes (overscan).

              If your monitor displays a blank screen when using 1 or 2, press F10 then try a  different  option
              or say `--fbmode 640'.

       --drive-plus3a-typetype--drive-plus3b-typetype--drive-beta128a-typetype--drive-beta128b-typetype--drive-beta128c-typetype--drive-beta128d-typetype--drive-plusd1-typetype--drive-plusd2-typetype--drive-didaktik80a-typetype--drive-didaktik80b-typetype--drive-disciple1-typetype--drive-disciple2-typetype--drive-opus1-typetype--drive-opus2-typetype
              Specify  a  disk  drive  type to emulate with the associated interface.  The available options are
              Disabled, Single-sided40track, Double-sided40track, Single-sided80track and Double-sided80track.   See  the  Disk Options dialog for more information.  The Disabled option is not supported
              for Drive 1 or Drive A of any interface.

       --drive-40-max-trackcount--drive-80-max-trackcount
              Specify the maximum number of tracks for 40 and 80 track physical drives respectively.

       --embed-snapshot
              Specify whether a snapshot should be embedded in an RZX file when recording  is  started  from  an
              existing snapshot. (Enabled by default, but you can use `--no-embed-snapshot' to disable). Same as
              the RZX Options dialog's Alwaysembedsnapshot option.

       --fastload
              Specify  whether  Fuse  should run at the fastest possible speed when the virtual tape is playing.
              (Enabled by default, but you can use `--no-fastload' to disable). The same as  the  Media  Options
              dialog's Fastloading option.

       -vmode--fbmodemode
              Specify which mode to use for the FB UI. Available values for mode are `320' (which corresponds to
              a 320×240×256 mode), the default and `640' (a 640×480×256 mode).

       --fuller
              Emulate  a  Fuller  Box  interface.  Same  as  the General Peripherals Options dialog's FullerBox
              option.

       --full-screen
              Specify whether Fuse should run in full screen mode.  This option is effective only under the  SDL
              UI.

       -gfilter--graphics-filtermode
              Specify which graphics filter to use if available. The default is normal, which uses no filtering.
              The  available  options  are  2x,  2xsai, 3x, 4x, advmame2x, advmame3x, dotmatrix, half, halfskip,
              hq2x, hq3x, hq4x, normal, super2xsai, supereagle, timex15x, timex2x, timextv,  tv2x,  tv3x,  tv4x,
              paltv, paltv2x, paltv3x, and paltv4x.  See the GRAPHICSFILTERS section for more details.

       --graphicsfilefile
              Set the filename used for graphical output from the emulated ZX Printer. See the PRINTEREMULATION
              section for more details.

       -h--help
              Give brief usage help, listing available options.

       --if2cartfile
              Insert the specified file into the emulated Interface 2.

       --interface1
              Emulate  a  Sinclair  Interface 1.  Same  as  the General Peripherals Options dialog's Interface1
              option.

       --interface2
              Emulate a Sinclair Interface 2.  (Enabled  by  default,  but  you  can  use  `--no-interface2'  to
              disable). Same as the General Peripherals Options dialog's Interface2 option.

       --issue2
              Emulate an issue 2 keyboard. Same as the General Options dialog's Issue2keyboard option.

       -jdevice--joystick-1device
              Read  from  device  to  emulate  the  first  joystick.  Fuse  will  use either `/dev/input/js0' or
              `/dev/js0' by default.

       --joystick-2device
              As for --joystick-1 but for the second joystick; the default here is  either  `/dev/input/js1'  or
              `/dev/js1'.

       --joystick-1-outputtype--joystick-2-outputtype--joystick-keyboard-outputtype
              Select  which  joystick  interface  to  attach  for  the first two real joysticks and the keyboard
              joystick. The default is 0,  which  is  no  output.  The  available  options  are  1  (cursor),  2
              (kempston),  3 (Sinclair 1), 4 (Sinclair 2), 5 (Timex 1), 6 (Timex 2), and 7 (Fuller). Same as the
              Joysticks Options dialog's Joysticktype option.

       --joystick-1-fire-1code--joystick-1-fire-2code--joystick-1-fire-3code--joystick-1-fire-4code--joystick-1-fire-5code--joystick-1-fire-6code--joystick-1-fire-7code--joystick-1-fire-8code--joystick-1-fire-9code--joystick-1-fire-10code--joystick-1-fire-11code--joystick-1-fire-12code--joystick-1-fire-13code--joystick-1-fire-14code--joystick-1-fire-15code--joystick-2-fire-1code--joystick-2-fire-2code--joystick-2-fire-3code--joystick-2-fire-4code--joystick-2-fire-5code--joystick-2-fire-6code--joystick-2-fire-7code--joystick-2-fire-8code--joystick-2-fire-9code--joystick-2-fire-10code--joystick-2-fire-11code--joystick-2-fire-12code--joystick-2-fire-13code--joystick-2-fire-14code--joystick-2-fire-15code
              Select which Fuse key code should be triggered by the applicable real joystick button  press.  The
              codes  are  the  Fuse  keyboard  codes  corresponding to the keys. The default value is 4096 which
              corresponds to the virtual joystick fire button. Same as the Joysticks Options  dialog's  Joystickfire options.

       --joystick-keyboard-upcode--joystick-keyboard-downcode--joystick-keyboard-leftcode--joystick-keyboard-rightcode--joystick-keyboard-firecode
              Select which Fuse key code should correspond with each direction and fire for the keyboard virtual
              joystick.  The  same  as  the  Keyboard Joysticks Options dialog's ButtonforUP, ButtonforDOWN,
              ButtonforLEFT, ButtonforRIGHT and ButtonforFIRE options respectively.

       --joystick-prompt
              If this option is specified, then Fuse will prompt you which form of joystick emulation  you  wish
              to  use  when  loading  a  snapshot. No prompt will be issued if the configuration in the snapshot
              matches what you are currently using. The same as  the  General  Options  dialog's  Snapjoystickprompt option.

       --kempston
              Emulate  a  Kempston  joystick. Same as the General Peripherals Options dialog's Kempstonjoystick
              option.

       --kempston-mouse
              Emulate a Kempston mouse. Same as the General Peripherals Options dialog's Kempstonmouse option.

       --keyboard-arrows-shifted
              Treat the keyboard arrow keys as shifted like  the  ZX  Spectrum+  keyboard's  arrow  keys  or  as
              unshifted like a cursor joystick that maps to the 5, 6, 7 and 8 keys. (Enabled by default, but you
              can  use  `--no-keyboard-arrows-shifted'  to  disable).  Same  as  the General Peripherals Options
              dialog's Useshiftwitharrowkeys option.

       --late-timings
              It has been observed that some real Spectrums run such that the  screen  is  rendered  one  tstate
              later  than on other real hardware. This option specifies that Fuse should emulate such a machine.
              Same as the General Options dialog's Latetimings option.

       --loading-sound
              Specify whether the sound made while tapes are loading should be emulated.  (Enabled  by  default,
              but you can use `--no-loading-sound' to disable). Same as the Sound Options dialog's Loadingsound
              option.

       -mtype--machinetype
              Specify  machine  type  to  emulate  initially.  The  default is 48, a 48K Spectrum. The available
              options are 16, 48, 48_ntsc, 128, plus2, plus2a, plus3, 2048, 2068, ts2068, pentagon, pentagon512,
              pentagon1024, scorpion and se.

       --melodik
              Emulate a Melodik AY interface for 16/48k Spectrums.  Same  as  the  General  Peripherals  Options
              dialog's Melodik option.

       --mdr-lenlength
              This  option  controls  the  number  of  blocks  in a new Microdrive cartridge.  Same as the Media
              Options dialog's MDRcartridgelen option.

       --mdr-random-len
              If this option is set, Fuse will use a random Microdrive  cartridge  length.  Same  as  the  Media
              Options dialog's RandomlengthMDRcartridge option.

       --microdrive-filefile--microdrive-2-filefile--microdrive-3-filefile--microdrive-4-filefile--microdrive-5-filefile--microdrive-6-filefile--microdrive-7-filefile--microdrive-8-filefile
              Specify Interface 1 Microdrive cartridge files to open.

       --mouse-swap-buttons
              Swap  the  left and right mouse buttons when emulating the Kempston mouse. The same as the General
              Peripherals dialog's Swapmousebuttons option.

       --movie-comprlevel
              This option sets the compression level used when  creating  movies.  Same  as  the  Movie  Options
              dialog's Moviecompression option. The available options are None, Lossless, and High (lossy). The
              default option is Lossless.  See also the MOVIERECORDING section.

       --movie-startfile
              With this command line option, Fuse will start movie recording as soon as the emulator is started.
              See also the MOVIERECORDING section.

       --movie-stop-after-rzx
              With  this  command line option, Fuse will stop movie recording when RZX playback or RZX recording
              ends. Same as the Movie Options dialog's  StoprecordingafterRZXends  option.  (Enabled  by
              default,  but  you  can use `--no-movie-stop-after-rzx' to disable).  See also the MOVIERECORDING
              section.

       --multiface1
              Emulate a Romantic Robot Multiface One interface. Same as the General Peripherals Options dialog's
              MultifaceOne option.

       --multiface128
              Emulate a Romantic Robot Multiface 128 interface. Same as the General Peripherals Options dialog's
              Multiface128 option.

       --multiface3
              Emulate a Romantic Robot Multiface 3 interface. Same as the General Peripherals  Options  dialog's
              Multiface3 option.

       --multiface1-stealth
              Set Multiface One stealth/invisible mode. Same as the General Peripherals Options dialog's StealthMultifaceOne option.

       --opus
              Emulate  an Opus Discovery interface. Same as the Disk Peripherals Options dialog's OpusDiscoveryinterface option.

       --opusdiskfile
              Insert the specified file into the emulated Opus Discovery's drive 1.

       --pal-tv2x
              Specify whether the PAL TV 2x, PAL TV 3x and PAL TV 4x scalers should also produce scanlines along
              the lines of the TV 2x and Timex TV scalers.  The same as the General Options dialog's PAL-TVuseTV2xeffect option.

       --phantom-typist-modemode
              Specify  the  keystroke  sequence  that  the  "phantom  typist" should use when starting a program
              loading. The available options are Auto, Keyword, Keystroke, Menu, Plus2A and Plus3.   The  same
              as the Media Options dialog's Phantomtypistmode option.

       -pfile--playbackfile
              Specify an RZX file to begin playback from.

       --plus3diskfile
              Insert  the  specified  file  into  the  emulated  +3's A: drive; also select the +3 on startup if
              available.

       --plus3-detect-speedlock
              Specify whether the +3 drives try to detect Speedlock protected disks, and emulate `weak' sectors.
              If the disk image file (EDSK or UDI) contains  weak  sector  data,  than  Speedlock  detection  is
              automatically omitted.  See also the WEAKDISKDATA section.  Same as the Disk Options dialog's +3DetectSpeedlock option.

       --plusd
              Emulate a +D interface. Same as the Disk Peripherals Options dialog's +Dinterface option.

       --plusddiskfile
              Insert the specified file into the emulated +D's drive 1.

       --printer
              Specify  whether  the  emulation should include a printer. Same as the General Peripherals Options
              dialog's Emulateprinters option.

       --rateframe
              Specify the frame rate, the ratio of spectrum frame updates to real frame  updates.  Same  as  the
              General Options dialog's Framerate option.

       -rfile--recordfile
              Specify an RZX file to begin recording to.

       --recreated-spectrum
              Enable  the  use of a Recreated ZX Spectrum in `Layer A' (game) mode. This is a Bluetooth keyboard
              that can be paired to the device where Fuse is running. The same as the General  Options  dialog's
              RecreatedZXSpectrum option.

       --rom-16file--rom-48file--rom-128-0file--rom-128-1file--rom-plus2-0file--rom-plus2-1file--rom-plus2a-0file--rom-plus2a-1file--rom-plus2a-2file--rom-plus2a-3file--rom-plus3-0file--rom-plus3-1file--rom-plus3-2file--rom-plus3-3file--rom-plus3e-0file--rom-plus3e-1file--rom-plus3e-2file--rom-plus3e-3file--rom-tc2048file--rom-tc2068-0file--rom-tc2068-1file--rom-ts2068-0file--rom-ts2068-1file--rom-pentagon-0file--rom-pentagon-1file--rom-pentagon-2file--rom-pentagon512-0file--rom-pentagon512-1file--rom-pentagon512-2file--rom-pentagon512-3file--rom-pentagon1024-0file--rom-pentagon1024-1file--rom-pentagon1024-2file--rom-pentagon1024-3file--rom-scorpion-0file--rom-scorpion-1file--rom-scorpion-2file--rom-scorpion-3file--rom-spec-se-0file--rom-spec-se-1file
              Specify  the  file  to be used for ROM(s) used for each machine. The options respectively refer to
              the 16K Spectrum (48.rom), 48K Spectrum (48.rom), the two ROMs for  the  128K Spectrum  (128-0.rom
              and  128-1.rom),  the two ROMs for the +2 (plus2-0.rom and plus2-1.rom), the four ROMs for the +2A
              (plus3-0.rom, plus3-1.rom, plus3-2.rom and plus3-3.rom), the four ROMs for  the  +3  (plus3-0.rom,
              plus3-1.rom,  plus3-2.rom  and  plus3-3.rom),  the  four  enhanced ROMs for the +3e (plus3e-0.rom,
              plus3e-1.rom, plus3e-2.rom and plus3e-3.rom), the TC2048 ROM (tc2048.rom), the two  ROMs  for  the
              TC2068   (tc2068-0.rom   and  tc2068-1.rom),  the  two  ROMs  for  the  TS2068  (tc2068-0.rom  and
              tc2068-1.rom), the two main ROMs and the TR-DOS ROM for the Pentagon 128K (128p-0.rom,  128p-1.rom
              and  trdos.rom),  the  two main ROMs, the TR-DOS ROM and a reset service ROM for the Pentagon 512K
              and 1024K (128p-0.rom, 128p-1.rom, trdos.rom and gluck.rom), the four ROMs for  the  Scorpion  256
              (256s-0.rom,  256s-1.rom,  256s-2.rom  and  256s-3.rom),  and  the  two  ROMs  for the Spectrum SE
              (se-0.rom and se-1.rom).

              The names in brackets denote the defaults. Note that not all these ROMs are supplied with  Fuse  —
              you must supply your own copies of those which are not.

       --rom-interface-1file--rom-beta128file--rom-plusdfile--rom-didaktik80file--rom-disciplefile--rom-multiface1file--rom-multiface128file--rom-multiface3file--rom-opusfile--rom-speccybootfile--rom-ttx2000sfile--rom-usourcefile
              Specify the file to be used for ROM(s) used for each peripheral. The options respectively refer to
              the  Interface 1 ROM (if1-2.rom), the TR-DOS ROM for Beta 128 emulation with the 48K, TC2048, 128K
              or +2 (trdos.rom), the +D ROM (plusd.rom), the Didaktik 80 ROM (didaktik80.rom), the DISCiPLE  ROM
              (disciple.rom),   the   Multiface One  ROM  (mf1.rom),  the  Multiface 128  ROM  (mf128.rom),  the
              Multiface 3  ROM  (mf3.rom),   the   Opus   Discovery   ROM   (opus.rom),   the   SpeccyBoot   ROM
              (speccyboot-1.4.rom), the TTX2000S ROM (ttx2000s.rom), and the µSource ROM (usource.rom).

              The  names  in brackets denote the defaults. Note that not all these ROMs are supplied with Fuse —
              you must supply your own copies of those which are not.

       --no-rs232-handshake
              This option makes Fuse's Interface 1 emulation assume that the RS-232 line other end is live  when
              you connect the communication channels.  See also the `--rs232-rx' and `--rs232-tx' options.

       --rs232-rx--rs232-tx
              Specify  the  communication channels (FIFO or file) to be used for Interface 1 RS-232 emulation as
              RxD and TxD wire. See also the `--rs232-handshake' options.

       --rzx-autosaves
              Specify that, while recording an RZX file,  Fuse  should  automatically  add  a  snapshot  to  the
              recording  stream  every  5 seconds.  (Default  to  on,  but  you  can use `--no-rzx-autosaves' to
              disable). Same as the RZX Options dialog's Createautosaves option; see there for more details.

       --sdl-fullscreen-modemode
              Select a screen resolution for full screen mode. Available values for mode are listed in a  table,
              when Fuse is called with --sdl-fullscreen-modelist command line option.  This option is effective
              only under the SDL UI.

       --separationtype
              Give  stereo  separation  of  the 128's AY sound channels. Same as the General Options dialog's AYstereoseparation option. The available options are None, ACB, and ABC.   The  default  option  is
              None.

       --simpleide
              Specify whether Fuse will emulate the simple 8-bit IDE interface as used by the Spectrum +3e. Same
              as the Disk Peripherals Options dialog's Simple8-bitIDE option.

       --simpleide-masterfilefile
              Specify a HDF file to connect to the emulated Simple 8-bit IDE interface's master channel.

       --simpleide-slavefilefile
              Specify a HDF file to connect to the emulated Simple 8-bit IDE interface's slave channel.

       --slt
              Support  the  SLT  trap  instruction. (Enabled by default, but you can use `--no-slt' to disable).
              Same as the Media Options dialog's Use.slttraps option.

       -sfile--snapshotfile
              Specify a  snapshot  file  to  load.  The  file  can  be  in  any  snapshot  format  supported  by
              libspectrum(3).

       --sound
              Specify  whether  Fuse  should produce sound. (Enabled by default, but you can use `--no-sound' to
              disable). Same as the Sound Options dialog's Soundenabled option.

       -ddevice--sound-devicedevice
              Specify the sound output device to use and any options to give that device. If you are  not  using
              the  SDL  UI  or  using libao or libasound(ALSA) for sound output, then the device parameter just
              specifies the device to be used for sound output.

              If you are using the SDL UI, the device parameter allows you to specify the  audio  driver  to  be
              used (e.g. dsp, alsa, dma, esd and arts).

              If  you  are  using  libao for sound output, the device parameter allows you to specify the device
              used for sound output (either `live' to a speaker or to a file) and the parameters to be used  for
              that      device.      In      general,      the     device     parameter     has     the     form
              driver[:param[=value][,param[=value][,...]].  driver selects the libao driver to be  used,  either
              one of the `live' drivers (aixs, alsa, alsa09, arts, esd, irix, macosx, nas, oss or sun) or a file
              driver (au, raw, wav or null).  The available parameter and value pairs for each device are:

              •      aixs: AIX audio system

                     •      dev=device
                            `device' gives the AIX sound device.

              •      alsa: Advanced Linux Sound Architecture version 0.5.x

                     •      card=num
                            `num' gives the ALSA card number.

                     •      dev=num
                            `num' gives the ALSA device number.

                     •      buf_size=num
                            `num' gives the ALSA buffer size in bytes.

              •      alsa09: Advanced Linux Sound Architecture version 0.9+

                     •      dev=string
                            `string' specifies the ALSA device e.g. hw:1.2

                     •      buffer_time=num
                            `num' gives the ALSA buffer time in microseconds.

                     •      period_time=num
                            `num' gives the ALSA period time in microseconds.

                     •      use_mmap=yes|y|true|t|1
                            specifies that libao use memory mapped transfer.

              •      arts: aRts soundserver: no parameters.

              •      esd: Enlightened Sound Daemon.

                     •      host=string
                            `string' gives the ESD host specification.

              •      irix: IRIX Audio Library: no parameters.

              •      macosx: MacOS X CoreAudio: no parameters.

              •      nas: Network Audio System.

                     •      host=string
                            `string' gives the NAS host specification.

                     •      buf_size=num
                            `num' gives the buffer size on the server.

              •      oss: Open Sound System.

                     •      dsp=string
                            `string' gives the OSS device to be used e.g. /dev/sound/dsp1

              •      sun: SUN audio system.

                     •      dev=string
                            `string' gives the audio device to be used.

              •      au: SUN Sparc audio file: no parameters.

              •      raw: raw file.

                     •      byteorder=string
                            `string'  can  be  any of native (host native byteorder), big (big endian) or little
                            (little endian).

              •      wav: Microsoft audio file: no parameters.

              •      null: null output: no parameters.

              •      debug: for debugging libao.

              Finally, each of the file output types (au, raw and wav)  have  an  extra  option  `file=filename'
              where `filename' gives the file output will be directed to. This defaults to `fuse-sound.ao' if it
              is not specified.

              Some examples of use:

              fuse-dalsa09:dev=hw:1

              causes Fuse to use ALSA 0.9+ output with the second (#1) sound card.

              fuse-draw:byteorder=little,file=enigma.raw

              causes Fuse to save little endian words to `enigma.raw'.

              See  the  `DEVICE'  section of ogg123(1) for up to date information of devices and options (except
              for the `file' option which is provided by Fuse itself).

              If you are using libasound or ALSA for sound output, the device parameter allows  you  to  specify
              the  device  used for sound output and some parameters to be used for that device. In general, the
              device parameter has the form
              devstr or
              param[=value][,param[=value][,...][,devstr].

              •      devstr: selects the ALSA device used, it can be any complex or  simple  ALSA  device  name.
                     e.g.:  default  or  hw:0  or  tee:plughw:0,'/tmp/out.raw',raw.   See  the  alsa-lib pcm api
                     reference    at    http://www.alsa-project.org/alsa-doc/alsa-lib/pcm.html    for    further
                     explanation.

              •      param and values:

                     •      buffer=nnnn:  set the ALSA buffer in frames, smaller value cause smaller sound delay
                            but may more buffer underrun (pops and clicks), larger value cause longer delay  but
                            fewer  underrun. By default Fuse determine the buffer size based on the actual sound
                            frequency.

                            If you use some special plugin for your pcm device (e.g.: dmix)  or  your  card  not
                            support  some needed parameter (e.g. cannot play other only 48 kHz stereo sound like
                            some AC97 sound card)  may  cause  Fuse  unable  to  set  the  needed  buffer  size,
                            appropriate  sound  frequency,  channels and so on, therefore you cannot get optimal
                            result or not hear the sound at all. In this case try the plughw:#,  (where  #  mean
                            your card number counted from 0) for ALSA device.

                     •      verbose : if given, fuse report ALSA buffer underruns to stderr.

              Some examples of use:

              fuse-dverbose,buffer=2000

              causes  Fuse  to  use the default ALSA device with 2000 frame length buffer and report ALSA buffer
              underruns on stderr.

              fuse-dtee:plughw:0,'/tmp/aufwm.raw',raw

              causes Fuse to use the first card and parallel save the  raw  audio  samples  into  /tmp/aufwm.raw
              file.

              If  you  are  using  PulseAudio  for sound output, the device parameter allows you to specify some
              parameters to be used for that soud buffer. In general, the device parameter has the form
              param[=value][,param[=value][,...].

              •      param and values:

                     •      tlength=[num]ms: set target length of the PulseAudio sound buffer  in  milliseconds.
                            Smaller value cause smaller sound delay but more buffer underruns (pops and clicks),
                            larger  value cause longer delay but fewer underruns. By default Fuse set the buffer
                            size to 30ms of sound delay.

                     •      tlength=num: set target length of the PulseAudio sound buffer in bytes.  By  default
                            Fuse set the buffer size to 30ms of sound delay.

                     •      verbose : if given, Fuse report PulseAudio buffer underruns to stderr and PulseAudio
                            buffer options to stdout.

              Some examples of use:

              fuse-dtlength=40ms

              causes Fuse to target 40ms of sound delay instead of the default 30ms.

              fuse-dverbose,tlength=2646

              causes Fuse to request a sound buffer of 2646 bytes and print info to stdout.

       --sound-force-8bit
              Force the use of 8-bit sound, even if 16-bit is possible. Same as the Sound Options dialog's Force8-bit option.

       -ffrequency--sound-freqfrequency
              Specify  what  frequency  Fuse  should use for the sound device, the default is 44.1 kHz, but some
              devices only support a single frequency or a limited range (e.g.  48 kHz or up to 22 kHz).

       --speaker-typetype
              Select the output speaker emulation, type can be TV speaker, Beeper or  Unfiltered.  Same  as  the
              Sound Options dialog's Speakertype option.

       --speccyboot
              Emulate  a  SpeccyBoot  Ethernet  interface.  Same  as  the  General  Peripherals Options dialog's
              SpeccyBoot option. See the SpeccyBoot web page at  http://patrikpersson.github.io/speccyboot/  for
              full details on the SpeccyBoot.

       --speccyboot-tapdevice
              Specify the TAP device to use for SpeccyBoot emulation.

       --specdrum
              Emulate  a  SpecDrum  interface. Same as the General Peripherals Options dialog's SpecDrum option.
              See       the       World       of       Spectrum        Infoseek        web        page        at
              http://www.worldofspectrum.org/infoseekid.cgi?id=1000062 for manuals, software and more.

       --spectranet
              Specify  whether  Fuse  will  emulate  the  Spectranet  Ethernet  interface.   Same as the General
              Peripherals Options dialog's Spectranet option. See the  SPECTRANETEMULATION  section  for  more
              details.

       --spectranet-disable
              This  option  controls  the  state  of  the  Spectranet automatic page-in jumper (J2). Same as the
              General Peripherals Options dialog's Spectranetdisable  option.  See  the  SPECTRANETEMULATION
              section for more details.

       --speedpercentage
              Specify  the  speed  (as a percentage of real Spectrum speed) at which emulation should attempt to
              proceed. Same as the General Options dialog's Emulationspeed option.

       --statusbar
              For the GTK and Win32 UI, enables the statusbar beneath the display. For  the  Xlib  and  SDL  UI,
              enables the status icons showing whether the disk and tape are being accessed. Same as the General
              Options dialog's Showstatusbar option.

       --strict-aspect-hint
              For the GTK UI, use stricter limits for the aspect ratio limits set by the `--aspect-hint' option.
              This  can  cause  some  window  managers  (for example, metacity(1)) to not allow the window to be
              resized and moved, but is necessary to prevent others  (for  example,  fvwm(1))  from  being  able
              resize the window away from square.

       --svga-modesmode1,mode2,mode3
              Specify  which SVGA mode to use for the SVGAlib UI at different screen sizes. Available values for
              mode1, mode2 and mode3 are listed in a table, when Fuse called with --svga-modeslist command line
              option.  When user select a not available mode for a size, Fuse just ignore and try  to  find  the
              best  mode for it. e.g. with --svga-modes0,0,12 Fuse use the specified 1024×768×256 SVGA mode for
              triple size filters, but select SVGA modes automatically for normal or double size  filters.   The
              above  mode  number is just an example, and mode numbers and their meanings may vary graphics card
              by graphics card.

       -tfile--tapefile
              Specify a virtual tape file to use. It must be in PZX, TAP or TZX format.

       --teletext-addr-1address--teletext-addr-2address--teletext-addr-3address--teletext-addr-4address
              Specify address or hostname of teletext packet servers.

       --teletext-port-1port--teletext-port-2port--teletext-port-3port--teletext-port-4port
              Specify TCP port of teletext packet servers.

       --textfilefile
              Set the filename used for text output from  the  emulated  printers.  See  the  PRINTEREMULATION
              section below for more details.

       --traps
              Support  traps  for  ROM tape loading/saving. (Enabled by default, but you can use `--no-traps' to
              disable). Same as the Media Options dialog's Usetapetraps option.

       --ttx2000s
              Emulate a TTX2000S teletext adaptor. Same as the General  Peripherals  Options  dialog's  TTX2000S
              option. See the TTX2000SEMULATION section for more details.

       --unittests
              This  option runs a testing framework that automatically checks portions of code, comparing actual
              results with expected ones. It is meant to detect broken code  before  a  release.  There  is  not
              graphical  mode,  the  program  just  ends  with exit code 0 if all tests are good or prints error
              messages to stdout and ends with exit code greater than 0 if there are failed tests.

       --usource
              Emulate a µSource interface. Same as the General Peripherals Options dialog's µSource option.

       -V--version
              Show which version of Fuse is being used.

       --volume-ayvolume
              Sets the relative volume of the AY-3-8912 chip from a range of 0–100%. Same as the  Sound  Options
              dialog's AYvolume option.

       --volume-beepervolume
              Sets the relative volume of the beeper from a range of 0–100%.  Same as the Sound Options dialog's
              Beepervolume option.

       --volume-covoxvolume
              Sets  the relative volume of the Covox from a range of 0–100%.  Same as the Sound Options dialog's
              Covoxvolume option.

       --volume-specdrumvolume
              Sets the relative volume of the SpecDrum from a range  of  0–100%.   Same  as  the  Sound  Options
              dialog's SpecDrumvolume option.

       --writable-roms
              Allow  Spectrum  programs  to overwrite the ROM(s). The same as the General Options dialog's AllowwritestoROM option.

       --zxatasp
              Specify whether Fuse emulate the ZXATASP interface. Same as the Disk Peripherals Options  dialog's
              ZXATASPinterface option.

       --zxatasp-upload
              Specify  the  state  of  the  ZXATASP upload jumper. Same as the Disk Peripherals Options dialog's
              ZXATASPupload option.

       --zxatasp-write-protect
              Specify the state of the ZXATASP write protect  jumper.  Same  as  the  Disk  Peripherals  Options
              dialog's ZXATASPwriteprotect option.

       --zxatasp-masterfilefile
              Specify a HDF file to connect to the emulated ZXATASP interface's master channel.

       --zxatasp-slavefilefile
              Specify a HDF file to connect to the emulated ZXATASP interface's slave channel.

       --zxcf
              Specify  whether  Fuse  emulate  the ZXCF interface. Same as the Disk Peripherals Options dialog's
              ZXCFinterface option.

       --zxcf-upload
              Specify the state of the ZXCF upload jumper. Same as the Disk Peripherals  Options  dialog's  ZXCFupload option.

       --zxcf-cffilefile
              Specify a HDF file to connect to the emulated ZXCF interface.

       --zxmmc
              Emulate  the  ZXMMC  interface.  The same as the Disk Peripherals Options dialog's ZXMMCinterface
              option.

       --zxmmc-filefile
              Specify an HDF image to be loaded into the ZXMMC's emulated memory card.

       --zxprinter
              Emulate the ZX Printer. Same as the General Peripherals Options dialog's ZXPrinter option.

       All long options which control on/off settings can be disabled using `--no-foo' (for an option  `--foo').
       For  example,  the opposite of `--issue2' is `--no-issue2'.  These options can also be modified while the
       emulator is running, using the options dialogs — see the documentation for the Options menu in the  MENUSANDKEYS section for details.

Opus Discovery Emulation

       By default, Fuse emulates the Opus Discovery interface with the optional 2k RAM expansion  and  a  second
       40 track  single  sided disk drive.  See the DISKFILEFORMATS section for more details on supported disk
       file formats. The Opus Discovery's printer port is also  emulated  for  output  only.  (See  the  PRINTEREMULATION  section for more details.) The Opus Discovery may only be used with 16K, 48K, 128K, TC2048 and
       +2 (not +2A) emulation.  To access disks, use the same syntax as Interface 1 and Microdrives.

Printer Emulation

       The various models of Spectrum supported a range  of  ways  to  connect  printers,  three  of  which  are
       supported by Fuse. Different printers are made available for the different models:

       16, 48, TC2048, TC2068, TS2068
              ZX Printer

       128/+2/Pentagon
              Serial printer (text-only)

       +2A, +3
              Parallel printer (text-only)

       If  Opus  Discovery,  +D  or  DISCiPLE  emulation  is  in use and printer emulation is enabled, text-only
       emulation of the disk interface's parallel printer interface is provided.

       Any printout is appended to one (or both) of two files, depending on  the  printer  —  these  default  to
       printout.txt  for  text  output,  and  printout.pbm  for graphics (PBM images are supported by most image
       viewers and converters). These names can be changed with the --textfile and --graphicsfile  options  from
       the  command line or configuration file. While the ZX Printer can only output graphically, simulated text
       output is generated at the same time using a crude sort of OCR based on the current character set (a  bit
       like  using  SCREEN$).  There is currently no support for graphics when using the serial/parallel output,
       though any escape codes used will be `printed' faithfully. (!)

       By the way, it's not a good idea to modify the printout.pbm file outside of Fuse if you want to  continue
       appending  to  it. The header needs to have a certain layout for Fuse to be able to continue appending to
       it correctly, and the file will be overwritten if it can't be appended to.

See Also

bzip2(3), fmfconv(1), fuse-utils(1), gzip(3), libspectrum(3), ogg123(1), xspect(1), xzx(1), zip(3).

       The comp.sys.sinclair Spectrum FAQ, at
       http://www.worldofspectrum.org/faq/index.html.

Spectranet Emulation

       The Spectranet is an Ethernet network interface for the ZX Spectrum by Dylan Thomas. The interface can be
       activated via the Spectranet option on the Peripherals preferences dialog, and the state of its automatic
       page-in  (disable)  jumper  controlled via the Spectranetdisable option. If you're going to be using the
       Spectranet,  you'll  probably  want  one  of  the  firmwares  available  from  the  Spectranet   homepage
       (http://spectrum.alioth.net/doc/index.php) which is also where you can find more information on using the
       interface.

       Installing  the  Spectranet  firmware on Fuse is slightly more complicated than on a real machine, mostly
       because Fuse's emulation doesn't support DHCP. These instructions are  correct  as  of  2012-01-26  —  if
       you're using a later firmware than this, things may have changed slightly.

       The  first  thing  you will need to do is to obtain a copy of the Spectranet installer as a .tap file (or
       similar). The installer is also available at the Spectranet site above.

       Once you have a copy of the installer, start Fuse and  tick  the  Spectranet  option  from  the  Options,Peripherals,General...  dialog, and the state of its write protect jumper controlled via the Spectranetdisable option. Once that's done, open the installer file (use the Media,Tape,Open...   command  rather
       than File,Open...  to prevent autoloading) and enter the following commands from BASIC:

       CLEAR 26999
       LOAD "" CODE
       RANDOMIZE USR 27000

       The  screen  should  turn  blue  and  you'll  see around 20 lines of message appearing as the firmware is
       installed, starting with “Erasing sector 0” and finishing with “Restoring page B”,  and  you'll  get  the
       familiar 0 OK, 0: 1 at the bottom of the screen.

       Now  untick the Spectranetdisable option from the Options,Peripherals,General...  dialog and reset the
       Spectrum. You should see a very brief blue status screen, before the  regular  copyright  screen  appears
       with  some  Spectranet  information at the top — there should be four status lines, starting with “Alioth
       Spectranet” and ending with the Spectranet's IP address (which will be 255.255.255.255 at this stage).

       Now trigger an NMI (the Machine / NMI menu option) and you should get a white on blue Spectranet NMI menu
       with five options.

       Select [A] Configure network settings — this should lead you to another menu, which will  scroll  of  the
       top of the screen; don't worry about this for now.

       You'll now need to set various options:

       [A] Enable/disable DHCP — select N
       [B] Change IP address — enter the IP address of the machine you are running Fuse on.
       [C] Change netmask — enter the appropriate netmask for the IP address you selected above. If that doesn't
       mean anything to you, try 255.255.255.0
       [D]  Change default gateway — enter the appropriate gateway address.  If you don't know any better, enter
       the IP address of your router.
       [E] Change primary DNS — enter the address of your DNS server. If you don't know any better, use Google's
       public DNS server, 8.8.8.8.

       There is no need to change options [F] or [G], but do select:

       [H] Change hostname — enter a hostname for the Spectranet-enabled machine. It doesn't really matter  what
       you  enter  here  —  it's  mostly useful just to replace the junk default name so you can see what you've
       entered for the other settings.

       Your screen should now look something like this:

       Current configuration
       ───────────────────────────────────────
       Use DHCP           : No
       IP address         : 192.168.000.002
       Netmask            : 255.255.255.000
       Default gateway    : 192.168.000.001
       Primary DNS        : 192.168.000.001
       Secondary DNS      : 255.255.255.255
       Hardware address   : FF:FF:FF:FF:FF:FF
       Hostname           : fuse
       <menu options>

       If  everything  looks  correct,  select  [I]  Save  changes  and  exit  (you'll  see  a   brief   “Saving
       configuration...” message) followed by [E] Exit, at which point you'll be returned to BASIC.

       Now type the following commands:

       %cfgnew
       %cfgcommit

       Which will show the standard 0 OK, 0:1 at the bottom of the screen.

       Reset  the  Spectrum  again  and you'll see the same four line status display, but this time with your IP
       address on the last line.

       Congratulations! You have now installed the Spectranet firmware. To save having to go  through  all  that
       every  time  you  start Fuse, save a .szx snapshot at this point, and load that in every time you want to
       use the Spectranet.

Synopsis

fuse [options]

The .Dsk Format

       In general, disk images for the +3 Spectrum are thought of as being  in  DSK  format.  However,  this  is
       actually a slight oversimplification; there are in fact two similar, but not identical, DSK formats. (The
       difference can be seen by doing `head-1dskfile': one format will start `MV - CPCEMU' and the other will
       start `EXTENDED').

       Fuse supports both the `CPCEMU' and `EXTENDED' formats.

The Emulated Spectrum

       The  emulated  Spectrum  is,  by  default,  an  unmodified 48K Spectrum with a tape player and ZX Printer
       attached. Oh, and apparently some magical snapshot load/save machine which is probably best glossed  over
       for the sake of the analogy. :-)

       To emulate different kinds of Spectrum, select the Machine,Select...  menu option, or press F9.

       The  Spectrum  emulation is paused when any dialogs appear. In the widget UI, it's also paused when menus
       or the keyboard picture are displayed.

The Poke Finder

       The `poke finder' is a tool which is designed to make the task of finding (infinite lives etc.) pokes for
       games a bit easier: it is similar to the `Lifeguard'  utility  which  was  available  for  use  with  the
       Multiface. It works by maintaining a list of locations in which the current number of lives (etc.) may be
       stored,  and  having  the  ability to remove from that list any locations which don't contain a specified
       value.

       The poke finder dialog contains an entry box for specifying the value to be searched for, a count of  the
       current  number  of  possible  locations and, if there are less than 20 possible locations, a list of the
       possible locations (in `page:offset' format). The five buttons act as follows:

       Incremented
              Remove from the list of possible locations all addresses which have not been incremented since the
              last search.

       Decremented
              Remove from the list of possible locations all addresses which have not been decremented since the
              last search.

       Search
              Remove from the list of possible locations all addresses which do not contain the value  specified
              in the `Search for' field.

       Reset
              Reset the poke finder so that all locations are considered possible.

       Close
              Close the dialog. Note that this does not reset the current state of the poke finder.

       Double-clicking  on  an  entry  in  the  list  of possible locations will cause a breakpoint to be set to
       trigger whenever that location is written to.

       An example of how to use this may make things a bit clearer. We'll use the 128K version of  Gryzor.  Load
       the  game, define keys to suit and start playing. Immediately pause the game and bring up the poke finder
       dialog. We note that we currently have 6 lives, so enter `6'  into  the  `Search  for'  field  and  click
       `Search'.  This  reduces the number of possible locations to around 931 (you may get a slightly different
       number depending on exactly when you paused the game). Play along a bit and then  (deliberately)  lose  a
       life.  Pause the game again. As we now have 5 lives, replace the `6' in the `Search for' field with a `5'
       and click `Search' again. This then reduces the list of possible locations to just  one:  page 2,  offset
       0x00BC.  This  is  the  only  location in memory which stored `6' when we had 6 lives and `5' when we had
       5 lives, so its pretty likely that this is where the  lives  count  is  stored.  Double-clicking  on  the
       `2:0x00BC'  entry in the dialog will set the appropriate breakpoint (you may wish to open the debugger at
       this point to confirm this). Play along a bit more. When you next lose a life, emulation is stopped  with
       PC  at  0x91CD.  Scrolling up a few addresses in the debugger's disassembly pane shows a value was loaded
       from 0x80BC (our hypothetical lives counter), decremented and then stored again to  0x80BC,  which  looks
       very  much  like  the  code  to  reduce  the  number of lives. We can now use the debugger to replace the
       decrement with a NOP (`set 0x91c9 0'), and playing the game some more after this reveals  that  this  has
       worked and we now have infinite lives.

The Poke Memory

       Fuse  supports  multiface POKEs, allowing to modify specific memory addresses in order to cheat (infinite
       lives, infinite ammo, etc.).

       The `poke memory' dialog contains a list of recently loaded POKEs and some entry boxes for adding  custom
       POKEs:

       Bank
              Sets the 128K memory bank (values `0' to `7') or the current memory mapping (value `8' or blank).

       Address
              Memory  address  to  modify.  Values in range 16384 to 65535 for 48K memory mode or 0 to 65535 for
              128K memory banks. GTK UI also accepts hex addresses.

       Value
              New value for the former address, in range 0 to 255. Value 256 means “Prompt to the user later”.

       It is possible to load POKEs from an external file using the File,Open...  menu option or the  drag-and-
       drop  functionality  in  the  GTK  and  Win32  UIs.   After  loading a snapshot or tape, Fuse will try to
       automatically locate a POK file with the same file name. This means that if we open `GAME.TAP', then Fuse
       will try to open `GAME.POK' and `POKES/GAME.POK'.  See  http://www.worldofspectrum.org/POKformat.txt  for
       more details about this file format.

       POKEs  loaded  in  the  list  can be activated or deactivated as the user wants and will remain in memory
       until a machine reset.

The Various Front-Ends

       Fuse  supports  various  front-ends,  or UIs (user interfaces). The usual one is GTK-based, but there are
       also SDL, Win32, Xlib, SVGAlib and framebuffer ones.

       The important difference to note is that GTK and Win32 versions uses `native' dialog boxes etc. (behaving
       like a fairly normal GUI-based program) while the others use an alternative, Fuse-specific  `widget  UI'.
       This  latter  front-end  is  easily  spotted by the way it uses the main Fuse window/screen for menus and
       dialogs, and uses the Spectrum's own font.

Ttx2000S Emulation

       Fuse supports emulating the OEL/Volex TTX2000S teletext adaptor with 16K and 48K machines.

       The interface has four tuning presets and extracts teletext signals from the vertical  blanking  interval
       of  the selected television channel.  These teletext signals are emulated by means of a simple TCP socket
       interface provided by an external server application. An example server written in  Python  is  available
       from https://github.com/ZXGuesser/teletext-packet-server

       The  default  address  for the four packet servers is 127.0.0.1 (loopback address), ports 19761 to 19764.
       Connections can also be made to other computers on a fast LAN by IP address  or  hostname.  Connecting  a
       packet server via the internet is not recommended.

       Only  one  connection  is  active at a time. Changing channel preset on the emulated interface closes any
       active connection and opens a new connection to the appropriate server. The same packet server can be set
       for multiple tuning presets.

       Note that a limitation of the TTX2000S ROM means that it only decodes the first 12 lines  of  a  teletext
       signal.  This  can be fixed by entering BASIC and executing `POKE 23394,33' then re-entering the teletext
       ROM with `RANDOMIZE USR 23500'. Alternatively just use teletext packet sources with 12 lines per field or
       fewer.

Weak Disk Data

       Some copy protections have what is described as `weak/random' data.  Each time the sector is read one  or
       more  bytes  will change, the value may be random between consecutive reads of the same sector.  Two disk
       image formats (Extended DSK and UDI) can store this type of data.  Fuse can read and use weak sector data
       from EDSK and UDI files when present, and can save back weak sector data to UDI image format.

Zxatasp And Zxcf

       The ZXATASP and ZXCF interfaces are two peripherals designed by Sami Vehmaa  which  significantly  extend
       the   capabilities   of  the  Spectrum.  More  details  on  both  are  available  from  Sami's  homepage,
       http://user.tninet.se/~vjz762w/, but a brief overview is given here.

       The real ZXATASP comes with either 128K or 512K of RAM and the ability to connect an IDE hard disks and a
       CompactFlash card, while the ZXCF comes with 128K, 512K or 1024K of RAM and  the  ability  to  connect  a
       CompactFlash  card.  From  an  emulation point of view, the two interfaces are actually very similar as a
       CompactFlash card is logically just an IDE hard disk. Currently, Fuse's emulation is fixed at having 512K
       of RAM in the ZXATASP and 1024K in the ZXCF.

       To activate the ZXATASP, simply select the  ZXATASPinterface  option  from  the  Options,Peripherals,Disk...   dialog.  The  state  of  the upload and write protect jumpers is then controlled by the ZXATASPupload and ZXATASPwriteprotect options. Similarly, the ZXCF is controlled by  the  ZXCFinterface  and
       ZXCFupload options (the ZXCF write protect is software controlled).

       If  you're  using  either  the  ZXATASP  or  ZXCF,  you almost certainly want to investigate ResiDOS, the
       operating system designed for use with the ZXATASP and ZXCF. ResiDOS provides facilities  for  using  the
       extra  RAM,  accessing  the  mass storage devices and a task manager allowing virtually instant switching
       between programs on the Spectrum. See http://www.worldofspectrum.org/residos/ for more details.

See Also

Option
Option PNG Icons
Man Pages
fuse Man Pages
Disk
Disk PNG Icons
Man Pages
options Man Pages
Filing
Filing PNG Icons
TLDR
Libinput - interface with input devices Tldr
Man Pages
dialog Man Pages
Spectrum
Spectrum PNG Icons
Man Pages
which Man Pages
← View User commands Category← Back to File management🙏  Credits & Acknowledgments