1fuse(1) Emulators fuse(1)
2
6 fuse — Sinclair ZX Spectrum emulator
7
9 fuse [options]
10
12 Fuse is a Sinclair ZX Spectrum emulator. It supports several models
13 (including the 128), with quite faithful emulation of the display and
14 sound.
15 The emulator can load any of the formats supported by libspectrum(3) —
17 this includes Z80, SNA and SZX snapshots, and PZX, TAP and TZX virtual-
18 tape files. Saving to SZX, Z80 and SNA snapshots and TZX and TAP tape
19 files is supported. The SLT extension to the Z80 format is partly sup‐
20 ported (enough for multi-load games); however, loading of the old DAT-
21 file variant is not.
22 DSK, UDI, FDI, TD0, MGT, IMG, D40, D80, SAD, TRD, SCL and OPD disk
24 images are supported when a disk interface is being emulated, including
25 the integrated disk drives on +3, Pentagon or Scorpion machines as well
26 as the +D, DISCiPLE, Opus Discovery, Beta 128 and Didaktik 80 inter‐
27 faces. DCK cartridge images are supported when emulating a Timex 2068
28 variant. Interface 2 ROM cartridges are also supported.
29 Finally, there is also support for reading and writing the RZX input
31 recording format.
32 See the COMPRESSED FILES section for details on reading files com‐
34 pressed with bzip2(3), gzip(3) or zip(3).
35
37 --accelerate-loader
38 Specify whether Fuse should attempt to accelerate tape loaders
39 by “short circuiting” the loading loop. This will in general
40 speed up loading, but may cause some loaders to fail. (Enabled
41 by default, but you can use `--no-accelerate-loader' to dis‐
42 able). The same as the Media Options dialog's Accelerate loaders
43 option.
44 --aspect-hint
46 Specify whether the GTK+ and Xlib user interfaces should `hint'
47 to the window manager about the preferred aspect ratio for the
48 graphics window, thus preventing resizing to non-square sizes
49 which lead to Fuse not displaying correctly. This option has
50 been observed to cause problems with some window managers when
51 using the GTK+ UI which can prevent the window from being
52 resized or moved at all. (Enabled by default, but you can use
53 `--no-aspect-hint' to disable). See also the
54 `--strict-aspect-hint' option.
55 --autosave-settings
57 Specify whether Fuse's current settings should be automatically
58 saved on exit. The same as the General Options dialog's Auto-
59 save settings option.
60 --auto-load
62 Specify whether tape and disk files should be automatically
63 loaded when they are opened using the File, Open... menu
64 option. In the case of TRD/SCL disk images, inserts also a boot
65 loader file when none is available. (Enabled by default, but you
66 can use `--no-auto-load' to disable). Same as the Media Options
67 dialog's Auto-load media option.
68 --beta128
70 Emulate a Beta 128 interface. Same as the Disk Peripherals
71 Options dialog's Beta 128 interface option.
72 --beta128-48boot
74 When a Beta 128 interface is used in 48K or TC2048 emulation the
75 option additionally controls whether the machine boots directly
76 into the TR-DOS system. Same as the Disk Peripherals Options
77 dialog's Beta 128 auto-boot in 48K machines option.
78 --betadisk file
80 Insert the specified file into the emulated Beta disk inter‐
81 face's drive A: and select Pentagon mode on startup.
82 --bw-tv
84 Specify whether the display should simulate a colour or black
85 and white television. This option is effective under the GTK+,
86 Win32, Xlib and SDL user interfaces: the others will always sim‐
87 ulate a colour TV. The same as the General Options dialog's
88 Black and white TV option.
89 --cmos-z80
91 This option specifies that Fuse should emulate a CMOS Z80, as
92 opposed to an NMOS Z80. Same as the General Options dialog's Z80
93 is CMOS option.
94 --competition-code code
96 Specify the code to be written to competition mode RZX files.
97 The same as the RZX Options dialog's Competition code option.
98 --competition-mode
100 Specify whether input recordings should be made in `competition
101 mode'. The same as the RZX Options dialog's Competition mode
102 option.
103 --compress-rzx
105 Specify whether RZX files should be written out compressed.
106 (Enabled by default, but you can use `--no-compress-rzx' to dis‐
107 able). Same as the RZX Options dialog's Compress RZX data
108 option.
109 --confirm-actions
111 Specify whether `dangerous' actions (those which could cause
112 data loss, for example resetting the Spectrum) require confirma‐
113 tion before occurring. (Enabled by default, but you can use
114 `--no-confirm-actions' to disable). This option is the same as
115 the General Options dialog's Confirm actions option.
116 --covox
118 Emulate a Covox sound interface for Pentagon/Scorpion. Same as
119 the General Peripherals Options dialog's Covox option.
120 --debugger-command string
122 Specify a debugger command to be run before emulator startup.
123 This can be used to set breakpoints or the like. Currently, this
124 is the only method to input multi-line debugger commands. (See
125 the MONITOR/DEBUGGER section for more information).
126 --detect-loader
128 Specify whether Fuse should attempt to detect when the tape is
129 being accessed and start and stop the virtual tape playing auto‐
130 matically. (Enabled by default, but you can use
131 `--no-detect-loader' to disable). Same as the Media Options dia‐
132 log's Detect loaders option.
133 --disciple
135 Emulate a DISCiPLE interface. Same as the Disk Peripherals
136 Options dialog's DISCiPLE interface option.
137 --discipledisk file
139 Insert the specified file into the emulated DISCiPLE's drive 1.
140 --didaktik80
142 Emulate a Didaktik 80 (or Didaktik 40) disk interface. Same as
143 the Disk Peripherals Options dialog's Didaktik 80 interface
144 option.
145 --didaktik80disk file
147 Insert the specified file into the emulated Didaktik 80 (or
148 Didaktik 40)'s drive A.
149 --disk-ask-merge
151 Prompt the user to confirm whether Fuse should try to merge the
152 `B' side of a disk image from a separate file when opening a new
153 single-sided disk image.
154 --disk-try-merge mode
156 Select whether Fuse should try to merge a separate file for the
157 `B' side of a disk image separate file when opening a new disk
158 image. Most double sided disk images are dumped as two single
159 sided disk images e.g. `Golden Axe - Side A.dsk' and `Golden
160 Axe - Side B.dsk'. So, if we want to play Golden Axe, first we
161 have to insert the first disk image and when the game asks to
162 insert side B, we have to find and open the second disk image,
163 instead of just `flip'-ing the disk inside the drive. If
164 enabled, Fuse will try to open the second image too and create a
165 double sided disk image (merging the two one sided disk images)
166 and insert this merged virtual disk into the disk drive. The
167 function detects whether the file is one side of a double-sided
168 image if the filename matches a pattern like [Ss]ide[
169 _][abAB12][ _.] in the file name of a disk that is being opened.
170 If found, Fuse will try to open the other side of the disk too
171 substituting the appropriate characters in the filename e.g.
172 1→2, a→b, A→B. If successful then it will merge the two images
173 and now we have a double sided disk in drive. This means that if
174 we open `Golden Axe - Side A.dsk', then Fuse will try to open
175 `Golden Axe - Side B.dsk' too. Now, we can just `flip' the disk
176 if Golden Axe asks for `Side B'. The available options are
177 Never, With single-sided drives and Always.
178 --divide
180 Emulate the DivIDE interface. The same as the Disk Peripherals
181 Options dialog's DivIDE interface option.
182 --divide-masterfile file
184 --divide-slavefile file
185 Specify an IDE image to be loaded into the DivIDE's emulated
186 master and slave drives respectively.
187 --divide-write-protect
189 Specify that the emulated DivIDE's write protect jumper should
190 be considered set. The same as the Disk Peripherals Options dia‐
191 log's DivIDE write protect option.
192 --divmmc
194 Emulate the DivMMC interface. The same as the Disk Peripherals
195 Options dialog's DivMMC interface option.
196 --divmmc-file file
198 Specify an HDF image to be loaded into the DivMMC's emulated
199 memory card.
200 --divmmc-write-protect
202 Specify that the emulated DivMMC's write protect jumper that
203 protects EEPROM should be considered set. The same as the Disk
204 Peripherals Options dialog's DivMMC write protect option.
205 --dock file
207 Insert the specified file into the emulated Timex 2068 variant
208 dock; also select the TC2068 on startup if available.
209 -D mode
211 --doublescan-mode mode
212 Specify whether to use doublescan modes in the FB UI. Available
213 values for mode are 0, 1 and 2. 0 means `never doublescan' (use
214 640×480 at either 72 Hz or 60 Hz), whereas 1 and 2 both mean
215 `try to use doublescan' and will fall back on the 640×480 modes.
216 1 selects 72 Hz modes (the same size and shape as your typical
217 640×480), and 2 selects 60 Hz modes (overscan).
218 If your monitor displays a blank screen when using 1 or 2, press
220 F10 then try a different option or say `--fbmode 640'.
221 --drive-plus3a-type type
223 --drive-plus3b-type type
224 --drive-beta128a-type type
225 --drive-beta128b-type type
226 --drive-beta128c-type type
227 --drive-beta128d-type type
228 --drive-plusd1-type type
229 --drive-plusd2-type type
230 --drive-didaktik80a-type type
231 --drive-didaktik80b-type type
232 --drive-disciple1-type type
233 --drive-disciple2-type type
234 --drive-opus1-type type
235 --drive-opus2-type type
236 Specify a disk drive type to emulate with the associated inter‐
237 face. The available options are Disabled, Single-sided 40
238 track, Double-sided 40 track, Single-sided 80 track and Dou‐
239 ble-sided 80 track. See the Disk Options dialog for more infor‐
240 mation. The Disabled option is not supported for Drive 1 or
241 Drive A of any interface.
242 --drive-40-max-track count
244 --drive-80-max-track count
245 Specify the maximum number of tracks for 40 and 80 track physi‐
246 cal drives respectively.
247 --embed-snapshot
249 Specify whether a snapshot should be embedded in an RZX file
250 when recording is started from an existing snapshot. (Enabled by
251 default, but you can use `--no-embed-snapshot' to disable). Same
252 as the RZX Options dialog's Always embed snapshot option.
253 --fastload
255 Specify whether Fuse should run at the fastest possible speed
256 when the virtual tape is playing. (Enabled by default, but you
257 can use `--no-fastload' to disable). The same as the Media
258 Options dialog's Fastloading option.
259 -v mode
261 --fbmode mode
262 Specify which mode to use for the FB UI. Available values for
263 mode are `320' (which corresponds to a 320×240×256 mode), the
264 default and `640' (a 640×480×256 mode).
265 --fuller
267 Emulate a Fuller Box interface. Same as the General Peripherals
268 Options dialog's Fuller Box option.
269 --full-screen
271 Specify whether Fuse should run in full screen mode. This
272 option is effective only under the SDL UI.
273 -g filter
275 --graphics-filter mode
276 Specify which graphics filter to use if available. The default
277 is normal, which uses no filtering. The available options are
278 2x, 2xsai, 3x, advmame2x, advmame3x, dotmatrix, half, halfskip,
279 hq2x, hq3x, normal, super2xsai, supereagle, timex15x, timextv,
280 tv2x, paltv, paltv2x, and paltv3x. See the GRAPHICS FILTERS
281 section for more details.
282 --graphicsfile file
284 Set the filename used for graphical output from the emulated
285 ZX Printer. See the PRINTER EMULATION section for more details.
286 -h
288 --help
289 Give brief usage help, listing available options.
290 --if2cart file
292 Insert the specified file into the emulated Interface 2.
293 --interface1
295 Emulate a Sinclair Interface 1. Same as the General Peripherals
296 Options dialog's Interface 1 option.
297 --interface2
299 Emulate a Sinclair Interface 2. (Enabled by default, but you can
300 use `--no-interface2' to disable). Same as the General Peripher‐
301 als Options dialog's Interface 2 option.
302 --issue2
304 Emulate an issue 2 keyboard. Same as the General Options dia‐
305 log's Issue 2 keyboard option.
306 -j device
308 --joystick-1 device
309 Read from device to emulate the first joystick. Fuse will use
310 either `/dev/input/js0' or `/dev/js0' by default.
311 --joystick-2 device
313 As for --joystick-1 but for the second joystick; the default
314 here is either `/dev/input/js1' or `/dev/js1'.
315 --joystick-1-output type
317 --joystick-2-output type
318 --joystick-keyboard-output type
319 Select which joystick interface to attach for the first two real
320 joysticks and the keyboard joystick. The default is 0, which is
321 no output. The available options are 1 (cursor), 2 (kempston), 3
322 (Sinclair 1), 4 (Sinclair 2), 5 (Timex 1), 6 (Timex 2), and 7
323 (Fuller). Same as the Joysticks Options dialog's Joystick type
324 option.
325 --joystick-1-fire-1 code
327 --joystick-1-fire-2 code
328 --joystick-1-fire-3 code
329 --joystick-1-fire-4 code
330 --joystick-1-fire-5 code
331 --joystick-1-fire-6 code
332 --joystick-1-fire-7 code
333 --joystick-1-fire-8 code
334 --joystick-1-fire-9 code
335 --joystick-1-fire-10 code
336 --joystick-1-fire-11 code
337 --joystick-1-fire-12 code
338 --joystick-1-fire-13 code
339 --joystick-1-fire-14 code
340 --joystick-1-fire-15 code
341 --joystick-2-fire-1 code
342 --joystick-2-fire-2 code
343 --joystick-2-fire-3 code
344 --joystick-2-fire-4 code
345 --joystick-2-fire-5 code
346 --joystick-2-fire-6 code
347 --joystick-2-fire-7 code
348 --joystick-2-fire-8 code
349 --joystick-2-fire-9 code
350 --joystick-2-fire-10 code
351 --joystick-2-fire-11 code
352 --joystick-2-fire-12 code
353 --joystick-2-fire-13 code
354 --joystick-2-fire-14 code
355 --joystick-2-fire-15 code
356 Select which Fuse key code should be triggered by the applicable
357 real joystick button press. The codes are the Fuse keyboard
358 codes corresponding to the keys. The default value is 4096 which
359 corresponds to the virtual joystick fire button. Same as the
360 Joysticks Options dialog's Joystick fire options.
361 --joystick-keyboard-up code
363 --joystick-keyboard-down code
364 --joystick-keyboard-left code
365 --joystick-keyboard-right code
366 --joystick-keyboard-fire code
367 Select which Fuse key code should correspond with each direction
368 and fire for the keyboard virtual joystick. The same as the Key‐
369 board Joysticks Options dialog's Button for UP, Button for DOWN,
370 Button for LEFT, Button for RIGHT and Button for FIRE options
371 respectively.
372 --joystick-prompt
374 If this option is specified, then Fuse will prompt you which
375 form of joystick emulation you wish to use when loading a snap‐
376 shot. No prompt will be issued if the configuration in the snap‐
377 shot matches what you are currently using. The same as the Gen‐
378 eral Options dialog's Snap joystick prompt option.
379 --kempston
381 Emulate a Kempston joystick. Same as the General Peripherals
382 Options dialog's Kempston joystick option.
383 --kempston-mouse
385 Emulate a Kempston mouse. Same as the General Peripherals
386 Options dialog's Kempston mouse option.
387 --keyboard-arrows-shifted
389 Treat the keyboard arrow keys as shifted like the ZX Spectrum+
390 keyboard's arrow keys or as unshifted like a cursor joystick
391 that maps to the 5, 6, 7 and 8 keys. (Enabled by default, but
392 you can use `--no-keyboard-arrows-shifted' to disable). Same as
393 the General Peripherals Options dialog's Use shift with arrow
394 keys option.
395 --late-timings
397 It has been observed that some real Spectrums run such that the
398 screen is rendered one tstate later than on other real hardware.
399 This option specifies that Fuse should emulate such a machine.
400 Same as the General Options dialog's Late timings option.
401 --loading-sound
403 Specify whether the sound made while tapes are loading should be
404 emulated. (Enabled by default, but you can use `--no-load‐
405 ing-sound' to disable). Same as the Sound Options dialog's Load‐
406 ing sound option.
407 -m type
409 --machine type
410 Specify machine type to emulate initially. The default is 48, a
411 48K Spectrum. The available options are 16, 48, 48_ntsc, 128,
412 plus2, plus2a, plus3, 2048, 2068, ts2068, pentagon, pentagon512,
413 pentagon1024, scorpion and se.
414 --melodik
416 Emulate a Melodik AY interface for 16/48k Spectrums. Same as the
417 General Peripherals Options dialog's Melodik option.
418 --mdr-len length
420 This option controls the number of blocks in a new Microdrive
421 cartridge. Same as the Media Options dialog's MDR cartridge len
422 option.
423 --mdr-random-len
425 If this option is set, Fuse will use a random Microdrive car‐
426 tridge length. Same as the Media Options dialog's Random length
427 MDR cartridge option.
428 --microdrive-file file
430 --microdrive-2-file file
431 --microdrive-3-file file
432 --microdrive-4-file file
433 --microdrive-5-file file
434 --microdrive-6-file file
435 --microdrive-7-file file
436 --microdrive-8-file file
437 Specify Interface 1 Microdrive cartridge files to open.
438 --mouse-swap-buttons
440 Swap the left and right mouse buttons when emulating the Kemp‐
441 ston mouse. The same as the General Peripherals dialog's Swap
442 mouse buttons option.
443 --movie-compr level
445 This option sets the compression level used when creating
446 movies. Same as the Movie Options dialog's Movie compression
447 option. The available options are None, Lossless, and High
448 (lossy). The default option is Lossless. See also the MOVIE
449 RECORDING section.
450 --movie-start filename
452 With this command line option, Fuse will start movie recording
453 as soon as the emulator is started. See also the MOVIE RECORDING
454 section.
455 --movie-stop-after-rzx
457 With this command line option, Fuse will stop movie recording
458 when RZX playback or RZX recording ends. Same as the Movie
459 Options dialog's Stop recording after RZX ends option. (Enabled
460 by default, but you can use `--no-movie-stop-after-rzx' to dis‐
461 able). See also the MOVIE RECORDING section.
462 --multiface1
464 Emulate a Romantic Robot Multiface One interface. Same as the
465 General Peripherals Options dialog's Multiface One option.
466 --multiface128
468 Emulate a Romantic Robot Multiface 128 interface. Same as the
469 General Peripherals Options dialog's Multiface 128 option.
470 --multiface3
472 Emulate a Romantic Robot Multiface 3 interface. Same as the Gen‐
473 eral Peripherals Options dialog's Multiface 3 option.
474 --multiface1-stealth
476 Set Multiface One stealth/invisible mode. Same as the General
477 Peripherals Options dialog's Stealth Multiface One option.
478 --opus
480 Emulate an Opus Discovery interface. Same as the Disk Peripher‐
481 als Options dialog's Opus Discovery interface option.
482 --opusdisk file
484 Insert the specified file into the emulated Opus Discovery's
485 drive 1.
486 --pal-tv2x
488 Specify whether the PAL TV 2x and PAL TV 3x scalers should also
489 produce scanlines along the lines of the TV 2x and Timex TV
490 scalers. The same as the General Options dialog's PAL-TV use
491 TV2x effect option.
492 --phantom-typist-mode mode
494 Specify the keystroke sequence that the "phantom typist" should
495 use when starting a program loading. The available options are
496 Auto, Keyword, Keystroke, Menu, Plus 2A and Plus 3. The same as
497 the Media Options dialog's Phantom typist mode option.
498 -p file
500 --playback file
501 Specify an RZX file to begin playback from.
502 --plus3disk file
504 Insert the specified file into the emulated +3's A: drive; also
505 select the +3 on startup if available.
506 --plus3-detect-speedlock
508 Specify whether the +3 drives try to detect Speedlock protected
509 disks, and emulate `weak' sectors. If the disk image file (EDSK
510 or UDI) contains weak sector data, than Speedlock detection is
511 automatically omitted. See also the WEAK DISK DATA section.
512 Same as the Disk Options dialog's +3 Detect Speedlock option.
513 --plusd
515 Emulate a +D interface. Same as the Disk Peripherals Options
516 dialog's +D interface option.
517 --plusddisk file
519 Insert the specified file into the emulated +D's drive 1.
520 --printer
522 Specify whether the emulation should include a printer. Same as
523 the General Peripherals Options dialog's Emulate printers
524 option.
525 --rate frame
527 Specify the frame rate, the ratio of spectrum frame updates to
528 real frame updates. Same as the General Options dialog's Frame
529 rate option.
530 -r file
532 --record file
533 Specify an RZX file to begin recording to.
534 --recreated-spectrum
536 Enable the use of a Recreated ZX Spectrum in `Layer A' (game)
537 mode. This is a Bluetooth keyboard that can be paired to the
538 device where Fuse is running. The same as the General Options
539 dialog's Recreated ZX Spectrum option.
540 --rom-16 file
542 --rom-48 file
543 --rom-128-0 file
544 --rom-128-1 file
545 --rom-plus2-0 file
546 --rom-plus2-1 file
547 --rom-plus2a-0 file
548 --rom-plus2a-1 file
549 --rom-plus2a-2 file
550 --rom-plus2a-3 file
551 --rom-plus3-0 file
552 --rom-plus3-1 file
553 --rom-plus3-2 file
554 --rom-plus3-3 file
555 --rom-plus3e-0 file
556 --rom-plus3e-1 file
557 --rom-plus3e-2 file
558 --rom-plus3e-3 file
559 --rom-tc2048 file
560 --rom-tc2068-0 file
561 --rom-tc2068-1 file
562 --rom-ts2068-0 file
563 --rom-ts2068-1 file
564 --rom-pentagon-0 file
565 --rom-pentagon-1 file
566 --rom-pentagon-2 file
567 --rom-pentagon512-0 file
568 --rom-pentagon512-1 file
569 --rom-pentagon512-2 file
570 --rom-pentagon512-3 file
571 --rom-pentagon1024-0 file
572 --rom-pentagon1024-1 file
573 --rom-pentagon1024-2 file
574 --rom-pentagon1024-3 file
575 --rom-scorpion-0 file
576 --rom-scorpion-1 file
577 --rom-scorpion-2 file
578 --rom-scorpion-3 file
579 --rom-spec-se-0 file
580 --rom-spec-se-1 file
581 Specify the file to be used for ROM(s) used for each machine.
582 The options respectively refer to the 16K Spectrum (48.rom),
583 48K Spectrum (48.rom), the two ROMs for the 128K Spectrum
584 (128-0.rom and 128-1.rom), the two ROMs for the +2 (plus2-0.rom
585 and plus2-1.rom), the four ROMs for the +2A (plus3-0.rom,
586 plus3-1.rom, plus3-2.rom and plus3-3.rom), the four ROMs for the
587 +3 (plus3-0.rom, plus3-1.rom, plus3-2.rom and plus3-3.rom), the
588 four enhanced ROMs for the +3e (plus3e-0.rom, plus3e-1.rom,
589 plus3e-2.rom and plus3e-3.rom), the TC2048 ROM (tc2048.rom), the
590 two ROMs for the TC2068 (tc2068-0.rom and tc2068-1.rom), the two
591 ROMs for the TS2068 (tc2068-0.rom and tc2068-1.rom), the two
592 main ROMs and the TR-DOS ROM for the Pentagon 128K (128p-0.rom,
593 128p-1.rom and trdos.rom), the two main ROMs, the TR-DOS ROM and
594 a reset service ROM for the Pentagon 512K and 1024K (128p-0.rom,
595 128p-1.rom, trdos.rom and gluck.rom), the four ROMs for the
596 Scorpion 256 (256s-0.rom, 256s-1.rom, 256s-2.rom and
597 256s-3.rom), and the two ROMs for the Spectrum SE (se-0.rom and
598 se-1.rom).
599 The names in brackets denote the defaults. Note that not all
601 these ROMs are supplied with Fuse — you must supply your own
602 copies of those which are not.
603 --rom-interface-1 file
605 --rom-beta128 file
606 --rom-plusd file
607 --rom-didaktik80 file
608 --rom-disciple file
609 --rom-multiface1 file
610 --rom-multiface128 file
611 --rom-multiface3 file
612 --rom-opus file
613 --rom-speccyboot file
614 --rom-usource file
615 Specify the file to be used for ROM(s) used for each peripheral.
616 The options respectively refer to the Interface 1 ROM
617 (if1-2.rom), the TR-DOS ROM for Beta 128 emulation with the 48K,
618 TC2048, 128K or +2 (trdos.rom), the +D ROM (plusd.rom), the
619 Didaktik 80 ROM (didaktik80.rom), the DISCiPLE ROM (disci‐
620 ple.rom), the Multiface One ROM (mf1.rom), the Multiface 128 ROM
621 (mf128.rom), the Multiface 3 ROM (mf3.rom), the Opus Discovery
622 ROM (opus.rom), the SpeccyBoot ROM (speccyboot-1.4.rom), and the
623 µSource ROM (usource.rom).
624 The names in brackets denote the defaults. Note that not all
626 these ROMs are supplied with Fuse — you must supply your own
627 copies of those which are not.
628 --no-rs232-handshake
630 This option makes Fuse's Interface 1 emulation assume that the
631 RS-232 line other end is live when you connect the communication
632 channels. See also the `--rs232-rx' and `--rs232-tx' options.
633 --rs232-rx
635 --rs232-tx
636 Specify the communication channels (FIFO or file) to be used for
637 Interface 1 RS-232 emulation as RxD and TxD wire. See also the
638 `--rs232-handshake' options.
639 --rzx-autosaves
641 Specify that, while recording an RZX file, Fuse should automati‐
642 cally add a snapshot to the recording stream every 5 seconds.
643 (Default to on, but you can use `--no-rzx-autosaves' to dis‐
644 able). Same as the RZX Options dialog's Create autosaves option;
645 see there for more details.
646 --sdl-fullscreen-mode mode
648 Select a screen resolution for full screen mode. Available val‐
649 ues for mode are listed in a table, when Fuse is called with
650 --sdl-fullscreen-mode list command line option. This option is
651 effective only under the SDL UI.
652 --separation type
654 Give stereo separation of the 128's AY sound channels. Same as
655 the General Options dialog's AY stereo separation option. The
656 available options are None, ACB, and ABC. The default option is
657 None.
658 --simpleide
660 Specify whether Fuse will emulate the simple 8-bit IDE interface
661 as used by the Spectrum +3e. Same as the Disk Peripherals
662 Options dialog's Simple 8-bit IDE option.
663 --simpleide-masterfile file
665 Specify a HDF file to connect to the emulated Simple 8-bit IDE
666 interface's master channel.
667 --simpleide-slavefile file
669 Specify a HDF file to connect to the emulated Simple 8-bit IDE
670 interface's slave channel.
671 --slt
673 Support the SLT trap instruction. (Enabled by default, but you
674 can use `--no-slt' to disable). Same as the Media Options dia‐
675 log's Use .slt traps option.
676 -s file
678 --snapshot file
679 Specify a snapshot file to load. The file can be in any snapshot
680 format supported by libspectrum(3).
681 --sound
683 Specify whether Fuse should produce sound. (Enabled by default,
684 but you can use `--no-sound' to disable). Same as the Sound
685 Options dialog's Sound enabled option.
686 -d device
688 --sound-device device
689 Specify the sound output device to use and any options to give
690 that device. If you are not using the SDL UI or using libao or
691 libasound (ALSA) for sound output, then the device parameter
692 just specifies the device to be used for sound output.
693 If you are using the SDL UI, the device parameter allows you to
695 specify the audio driver to be used (e.g. dsp, alsa, dma, esd
696 and arts).
697 If you are using libao for sound output, the device parameter
699 allows you to specify the device used for sound output (either
700 `live' to a speaker or to a file) and the parameters to be used
701 for that device. In general, the device parameter has the form
702 driver[:param[=value][,param[=value][,...]]. driver selects the
703 libao driver to be used, either one of the `live' drivers (aixs,
704 alsa, alsa09, arts, esd, irix, macosx, nas, oss or sun) or a
705 file driver (au, raw, wav or null). The available parameter and
706 value pairs for each device are:
707 · aixs: AIX audio system
709 · dev=device
711 `device' gives the AIX sound device.
712 · alsa: Advanced Linux Sound Architecture version 0.5.x
714 · card=num
716 `num' gives the ALSA card number.
717 · dev=num
719 `num' gives the ALSA device number.
720 · buf_size=num
722 `num' gives the ALSA buffer size in bytes.
723 · alsa09: Advanced Linux Sound Architecture version 0.9+
725 · dev=string
727 `string' specifies the ALSA device e.g. hw:1.2
728 · buffer_time=num
730 `num' gives the ALSA buffer time in microseconds.
731 · period_time=num
733 `num' gives the ALSA period time in microseconds.
734 · use_mmap=yes|y|true|t|1
736 specifies that libao use memory mapped transfer.
737 · arts: aRts soundserver: no parameters.
739 · esd: Enlightened Sound Daemon.
741 · host=string
743 `string' gives the ESD host specification.
744 · irix: IRIX Audio Library: no parameters.
746 · macosx: MacOS X CoreAudio: no parameters.
748 · nas: Network Audio System.
750 · host=string
752 `string' gives the NAS host specification.
753 · buf_size=num
755 `num' gives the buffer size on the server.
756 · oss: Open Sound System.
758 · dsp=string
760 `string' gives the OSS device to be used e.g.
761 /dev/sound/dsp1
762 · sun: SUN audio system.
764 · dev=string
766 `string' gives the audio device to be used.
767 · au: SUN Sparc audio file: no parameters.
769 · raw: raw file.
771 · byteorder=string
773 `string' can be any of native (host native byte‐
774 order), big (big endian) or little (little
775 endian).
776 · wav: Microsoft audio file: no parameters.
778 · null: null output: no parameters.
780 · debug: for debugging libao.
782 Finally, each of the file output types (au, raw and wav) have an
784 extra option `file=filename' where `filename' gives the file
785 output will be directed to. This defaults to `fuse-sound.ao' if
786 it is not specified.
787 Some examples of use:
789 fuse -d alsa09:dev=hw:1
791 causes Fuse to use ALSA 0.9+ output with the second (#1) sound
793 card.
794 fuse -d raw:byteorder=little,file=enigma.raw
796 causes Fuse to save little endian words to `enigma.raw'.
798 See the `DEVICE' section of ogg123(1) for up to date information
800 of devices and options (except for the `file' option which is
801 provided by Fuse itself).
802 If you are using libasound or ALSA for sound output, the device
804 parameter allows you to specify the device used for sound output
805 and some parameters to be used for that device. In general, the
806 device parameter has the form
807 devstr or
808 param[=value][,param[=value][,...][,devstr].
809 · devstr: selects the ALSA device used, it can be any com‐
811 plex or simple ALSA device name. e.g.: default or hw:0 or
812 tee:plughw:0,'/tmp/out.raw',raw. See the alsa-lib pcm
813 api reference at
814 http://www.alsa-project.org/alsa-doc/alsa-lib/pcm.html
815 for further explanation.
816 · param and values:
818 · buffer=nnnn: set the ALSA buffer in frames,
820 smaller value cause smaller sound delay but may
821 more buffer underrun (pops and clicks), larger
822 value cause longer delay but fewer underrun. By
823 default Fuse determine the buffer size based on
824 the actual sound frequency.
825 If you use some special plugin for your pcm device
827 (e.g.: dmix) or your card not support some needed
828 parameter (e.g. cannot play other only 48 kHz
829 stereo sound like some AC97 sound card) may cause
830 Fuse unable to set the needed buffer size, appro‐
831 priate sound frequency, channels and so on, there‐
832 fore you cannot get optimal result or not hear the
833 sound at all. In this case try the plughw:#,
834 (where # mean your card number counted from 0) for
835 ALSA device.
836 · verbose : if given, fuse report ALSA buffer under‐
838 runs to stderr.
839 Some examples of use:
841 fuse -d verbose,buffer=2000
843 causes Fuse to use the default ALSA device with 2000 frame
845 length buffer and report ALSA buffer underruns on stderr.
846 fuse -d tee:plughw:0,'/tmp/aufwm.raw',raw
848 causes Fuse to use the first card and parallel save the raw
850 audio samples into /tmp/aufwm.raw file.
851 --sound-force-8bit
853 Force the use of 8-bit sound, even if 16-bit is possible. Same
854 as the Sound Options dialog's Force 8-bit option.
855 -f frequency
857 --sound-freq frequency
858 Specify what frequency Fuse should use for the sound device, the
859 default is 44.1 kHz, but some devices only support a single fre‐
860 quency or a limited range (e.g. 48 kHz or up to 22 kHz).
861 --speaker-type type
863 Select the output speaker emulation, type can be TV speaker,
864 Beeper or Unfiltered. Same as the Sound Options dialog's Speaker
865 type option.
866 --speccyboot
868 Emulate a SpeccyBoot Ethernet interface. Same as the General
869 Peripherals Options dialog's SpeccyBoot option. See the Speccy‐
870 Boot web page at http://patrikpersson.github.io/speccyboot/ for
871 full details on the SpeccyBoot.
872 --speccyboot-tap device
874 Specify the TAP device to use for SpeccyBoot emulation.
875 --specdrum
877 Emulate a SpecDrum interface. Same as the General Peripherals
878 Options dialog's SpecDrum option. See the World of Spectrum
879 Infoseek web page at http://www.worldofspectrum.org/infos‐
880 eekid.cgi?id=1000062 for manuals, software and more.
881 --spectranet
883 Specify whether Fuse will emulate the Spectranet Ethernet inter‐
884 face. Same as the General Peripherals Options dialog's Spec‐
885 tranet option. See the SPECTRANET EMULATION section for more
886 details.
887 --spectranet-disable
889 This option controls the state of the Spectranet automatic page-
890 in jumper (J2). Same as the General Peripherals Options dialog's
891 Spectranet disable option. See the SPECTRANET EMULATION section
892 for more details.
893 --speed percentage
895 Specify the speed (as a percentage of real Spectrum speed) at
896 which emulation should attempt to proceed. Same as the General
897 Options dialog's Emulation speed option.
898 --statusbar
900 For the GTK+ and Win32 UI, enables the statusbar beneath the
901 display. For the Xlib and SDL UI, enables the status icons show‐
902 ing whether the disk and tape are being accessed. Same as the
903 General Options dialog's Show statusbar option.
904 --strict-aspect-hint
906 For the GTK+ UI, use stricter limits for the aspect ratio limits
907 set by the `--aspect-hint' option. This can cause some window
908 managers (for example, metacity(1)) to not allow the window to
909 be resized and moved, but is necessary to prevent others (for
910 example, fvwm(1)) from being able resize the window away from
911 square.
912 --svga-modes mode1,mode2,mode3
914 Specify which SVGA mode to use for the SVGAlib UI at different
915 screen sizes. Available values for mode1, mode2 and mode3 are
916 listed in a table, when Fuse called with --svga-modes list com‐
917 mand line option. When user select a not available mode for a
918 size, Fuse just ignore and try to find the best mode for it.
919 e.g. with --svga-modes 0,0,12 Fuse use the specified
920 1024×768×256 SVGA mode for triple size filters, but select SVGA
921 modes automatically for normal or double size filters. The
922 above mode number is just an example, and mode numbers and their
923 meanings may vary graphics card by graphics card.
924 -t file
926 --tape file
927 Specify a virtual tape file to use. It must be in PZX, TAP or
928 TZX format.
929 --textfile file
931 Set the filename used for text output from the emulated print‐
932 ers. See the PRINTER EMULATION section below for more details.
933 --traps
935 Support traps for ROM tape loading/saving. (Enabled by default,
936 but you can use `--no-traps' to disable). Same as the Media
937 Options dialog's Use tape traps option.
938 --unittests
940 This option runs a testing framework that automatically checks
941 portions of code, comparing actual results with expected ones.
942 It is meant to detect broken code before a release. There is not
943 graphical mode, the program just ends with exit code 0 if all
944 tests are good or prints error messages to stdout and ends with
945 exit code greater than 0 if there are failed tests.
946 --usource
948 Emulate a µSource interface. Same as the General Peripherals
949 Options dialog's µSource option.
950 -V
952 --version
953 Show which version of Fuse is being used.
954 --volume-ay volume
956 Sets the relative volume of the AY-3-8912 chip from a range of
957 0–100%. Same as the Sound Options dialog's AY volume option.
958 --volume-beeper volume
960 Sets the relative volume of the beeper from a range of 0–100%.
961 Same as the Sound Options dialog's Beeper volume option.
962 --volume-covox volume
964 Sets the relative volume of the Covox from a range of 0–100%.
965 Same as the Sound Options dialog's Covox volume option.
966 --volume-specdrum volume
968 Sets the relative volume of the SpecDrum from a range of 0–100%.
969 Same as the Sound Options dialog's SpecDrum volume option.
970 --writable-roms
972 Allow Spectrum programs to overwrite the ROM(s). The same as the
973 General Options dialog's Allow writes to ROM option.
974 --zxatasp
976 Specify whether Fuse emulate the ZXATASP interface. Same as the
977 Disk Peripherals Options dialog's ZXATASP interface option.
978 --zxatasp-upload
980 Specify the state of the ZXATASP upload jumper. Same as the Disk
981 Peripherals Options dialog's ZXATASP upload option.
982 --zxatasp-write-protect
984 Specify the state of the ZXATASP write protect jumper. Same as
985 the Disk Peripherals Options dialog's ZXATASP write protect
986 option.
987 --zxatasp-masterfile file
989 Specify a HDF file to connect to the emulated ZXATASP inter‐
990 face's master channel.
991 --zxatasp-slavefile file
993 Specify a HDF file to connect to the emulated ZXATASP inter‐
994 face's slave channel.
995 --zxcf
997 Specify whether Fuse emulate the ZXCF interface. Same as the
998 Disk Peripherals Options dialog's ZXCF interface option.
999 --zxcf-upload
1001 Specify the state of the ZXCF upload jumper. Same as the Disk
1002 Peripherals Options dialog's ZXCF upload option.
1003 --zxcf-cffile file
1005 Specify a HDF file to connect to the emulated ZXCF interface.
1006 --zxmmc
1008 Emulate the ZXMMC interface. The same as the Disk Peripherals
1009 Options dialog's ZXMMC interface option.
1010 --zxmmc-file file
1012 Specify an HDF image to be loaded into the ZXMMC's emulated mem‐
1013 ory card.
1014 --zxprinter
1016 Emulate the ZX Printer. Same as the General Peripherals Options
1017 dialog's ZX Printer option.
1018 All long options which control on/off settings can be disabled using
1020 `--no-foo' (for an option `--foo'). For example, the opposite of
1021 `--issue2' is `--no-issue2'. These options can also be modified while
1022 the emulator is running, using the options dialogs — see the documenta‐
1023 tion for the Options menu in the MENUS AND KEYS section for details.
1024
1026 Fuse supports various front-ends, or UIs (user interfaces). The usual
1027 one is GTK+-based, but there are also SDL, Win32, Xlib, SVGAlib and
1028 framebuffer ones.
1029 The important difference to note is that GTK+ and Win32 versions uses
1031 `native' dialog boxes etc. (behaving like a fairly normal GUI-based
1032 program) while the others use an alternative, Fuse-specific `widget
1033 UI'. This latter front-end is easily spotted by the way it uses the
1034 main Fuse window/screen for menus and dialogs, and uses the Spectrum's
1035 own font.
1036
1038 Since many of the keys available are devoted to emulation of the Spec‐
1039 trum's keyboard, the primary way of controlling Fuse itself (rather
1040 than the emulated machine) is via the menus. There are also function
1041 key shortcuts for some menu options.
1042 In the GTK+ and Win32 version, the menu bar is always visible at the
1044 top of the Fuse window. You can click on a menu name to pop it up.
1045 Alternatively, you can press F1 to display a pop-up version of the menu
1046 bar, which you can then navigate with the cursor keys or mouse.
1047 In the widget UI pressing F1 is the only way to get the main menu; and
1049 unlike the GTK+ version, the emulator pauses while the menus are being
1050 navigated. The menus show which key to press for each menu option in
1051 brackets. Pressing Esc exits a menu, and pressing Enter exits the menu
1052 system entirely (as well as `confirming' any current dialog).
1053 Here's what the menu options do, along with the function key mappings
1055 for those items which have them:
1056 F3
1058 File, Open...
1059 Open a Spectrum file. Snapshots will be loaded into memory; tape
1060 images will be inserted into the emulated tape deck, and if the
1061 Auto-load media option is set will being loading. Opening a disk
1062 image or a Timex dock image will cause the appropriate machine
1063 type (+3, Pentagon or TC2068) to be selected with the image
1064 inserted, and disks will automatically load if the Auto-load
1065 media option is set. See the FILE SELECTION section below for
1066 details on how to choose the file. Note that this behaviour is
1067 different from previous versions of Fuse, when this option would
1068 open only snapshots.
1069 F2
1071 File, Save Snapshot...
1072 Save a snapshot (machine state, memory contents, etc.) to file.
1073 You can select the filename to be saved to. If it has a .szx,
1074 .z80 or .sna extension, the snapshot will be saved in that for‐
1075 mat. Otherwise, it will be saved as a .szx file.
1076 File, Recording, Record...
1078 Start recording input to an RZX file, initialised from the cur‐
1079 rent emulation state. You will be prompted for a filename to
1080 use.
1081 File, Recording, Record from snapshot...
1083 Start recording input to an RZX file, initialised from a snap‐
1084 shot. You will first be asked for the snapshot to use and then
1085 the file to save the recording to.
1086 File, Recording, Continue recording...
1088 Continue recording input into an existing RZX file from the last
1089 recorded state. Finalised recordings cannot be resumed. You will
1090 be prompted for the recording to continue.
1091 Insert
1093 File, Recording, Insert snapshot
1094 Inserts a snapshot of the current state into the RZX file. This
1095 can be used at a later point to roll back to the inserted state
1096 by using one of the commands below.
1097 Delete
1099 File, Recording, Rollback
1100 Rolls back the recording to the point at which the previous
1101 snapshot was inserted. Recording will continue from that point.
1102 File, Recording, Rollback to...
1104 Roll back the recording to any snapshot which has been inserted
1105 into the recording.
1106 File, Recording, Play...
1108 Playback recorded input from an RZX file. This lets you replay
1109 keypresses recorded previously. RZX files generally contain a
1110 snapshot with the Spectrum's state at the start of the record‐
1111 ing; if the selected RZX file doesn't, you'll be prompted for a
1112 snapshot to load as well.
1113 File, Recording, Stop
1115 Stop any currently-recording/playing RZX file.
1116 File, Recording, Finalise...
1118 Compact a RZX file. Any interspersed snapshot will be removed
1119 and the recording cannot be continued. All action replays sub‐
1120 mitted to the RZX Archive should be finalised.
1121 File, AY Logging, Record...
1123 Start recording the bytes output via the AY-3-8912 sound chip to
1124 a PSG file. You will be prompted for a filename to save the
1125 recording to.
1126 File, AY Logging, Stop
1128 Stop any current AY logging.
1129 File, Screenshot, Open SCR Screenshot...
1131 Load an SCR screenshot (essentially just a binary dump of the
1132 Spectrum's video memory) onto the current screen. Fuse supports
1133 screenshots saved in the Timex hi-colour and hi-res modes as
1134 well as `normal' Spectrum screens, and will make a simple con‐
1135 version if a hi-colour or hi-res screenshot is loaded onto a
1136 non-Timex machine.
1137 File, Screenshot, Save Screen as SCR...
1139 Save a copy of whatever's currently displayed on the Spectrum's
1140 screen as an SCR file. You will be prompted for a filename to
1141 save the screenshot to.
1142 File, Screenshot, Open MLT Screenshot...
1144 Load an MLT screenshot onto the current screen. The MLT format
1145 is similar to the SCR format but additionally supports capturing
1146 images that use techniques to display more than two colours in
1147 each Spectrum attribute square. Fuse will only load the bitmap
1148 version of an image on a Sinclair machine but on a Timex clone
1149 it can show the full colour detail captured in the image by
1150 using the hi-colour mode.
1151 File, Screenshot, Save Screen as MLT...
1153 Save a copy of whatever's currently displayed on the Spectrum's
1154 screen as an MLT file. You will be prompted for a filename to
1155 save the screenshot to.
1156 File, Screenshot, Save Screen as PNG...
1158 Save the current screen as a PNG file. You will be prompted for
1159 a filename to save the screenshot to.
1160 File, Scalable Vector Graphics, Start capture in line mode...
1162 Start trapping the video output functions present in ROM to copy
1163 the picture to SVG files, thus creating vectorized scalable pic‐
1164 ture; it is expected to be fully operational in BASIC only, but
1165 few machine code programs could work, if they use the ROM
1166 addresses to output text or graphics. The initial picture size
1167 is 256×176, but it is increased everytime a `scroll' happens. On
1168 every CLS a new file will be created, with an increasing
1169 sequence number. CIRCLEs will be described as a sequence of
1170 lines, so the original `imprecisions' will be still visible.
1171 The text output will be fully understood and decoded: normal
1172 ASCII characters will be converted into COURIER scalable fonts,
1173 UDG graphics into dot matrix areas, GRAPHICS blocky characters
1174 into small squares. A slightly transparent output permits to
1175 show a bit of the overlapped text and graphics elements. Lower
1176 portion of the screen (normally bound to stream #0 and #1) won't
1177 be captured.
1178 File, Scalable Vector Graphics, Start capture in dot mode...
1180 As above, but line capture is disabled. A line will be rendered
1181 as a sequence of dots.
1182 File, Scalable Vector Graphics, Stop capture
1184 Stop the SVG capture function.
1185 File, Movie, Record...
1187 Fuse can record movie (video and audio) into a file with special
1188 format which can be converted later to a common video file for‐
1189 mat with the fmfconv(1) utility. You will be prompted for a
1190 filename to save video. Please see MOVIE RECORDING section.
1191 File, Movie, Record from RZX...
1193 Start movie recording and RZX playback at the same time. You
1194 will be prompted for a filename to play from and a filename to
1195 save video.
1196 File, Movie, Pause
1198 Pause movie recording which is currently in progress.
1199 File, Movie, Continue
1201 Resume movie recording which has been previously paused.
1202 File, Movie, Stop
1204 Stop movie recording which is currently in progress.
1205 File, Load Binary Data...
1207 Load binary data from a file into the Spectrum's memory. After
1208 selecting the file to load data from, you can choose where to
1209 load the data and how much data to load.
1210 File, Save Binary Data...
1212 Save an arbitrary chunk of the Spectrum's memory to a file.
1213 Select the file you wish to save to, followed by the location
1214 and length of data you wish to save.
1215 F10
1217 File, Exit
1218 Exit the emulator. A confirmation dialog will appear checking
1219 you actually want to do this.
1220 F4
1222 Options, General...
1223 Display the General Options dialog, letting you configure Fuse.
1224 (With the widget UI, the keys shown in brackets toggle the
1225 options, Enter confirms any changes, and Esc aborts). Note that
1226 any changed settings only apply to the currently-running Fuse.
1227 The options available are:
1229 Emulation speed
1231 Set how fast Fuse will attempt to emulate the Spectrum,
1232 as a percentage of the speed at which the real machine
1233 runs. If your machine isn't fast enough to keep up with
1234 the requested speed, Fuse will just run as fast as it
1235 can. Note that if the emulation speed is faster than
1236 500%, no sound output will be produced.
1237 Frame rate
1239 Specify the frame rate, the ratio of spectrum frame
1240 updates to real frame updates. This is useful if your
1241 machine is having trouble keeping up with the spectrum
1242 screen updates.
1243 Issue 2 keyboard
1245 Early versions of the Spectrum used a different value for
1246 unused bits on the keyboard input ports, and a few games
1247 depended on the old value of these bits. Enabling this
1248 option switches to the old value, to let you run them.
1249 Recreated ZX Spectrum
1251 Enable the use of a Recreated ZX Spectrum in `Layer A'
1252 (game) mode. This is a Bluetooth keyboard that can be
1253 paired to the device where Fuse is running.
1254 Use shift with arrow keys
1256 Treat the keyboard arrow keys as shifted like the ZX
1257 Spectrum+ keyboard's arrow keys or as unshifted like a
1258 cursor joystick that maps to the 5, 6, 7 and 8 keys.
1259 Allow writes to ROM
1261 If this option is selected, Fuse will happily allow pro‐
1262 grams to overwrite what would normally be ROM. This prob‐
1263 ably isn't very useful in most circumstances, especially
1264 as the 48K ROM overwrites parts of itself.
1265 Late timings
1267 If selected, Fuse will cause all screen-related timings
1268 (for example, when the screen is rendered and when memory
1269 contention occurs) to be one tstate later than “normal”,
1270 an effect which is present on some real hardware.
1271 Z80 is CMOS
1273 If selected, Fuse will emulate a CMOS Z80, as opposed to
1274 an NMOS Z80. The undocumented `OUT (C),0' instruction
1275 will be replaced with `OUT (C),255' and emulation of a
1276 minor timing bug in the NMOS Z80's `LD A,I' and `LD A,R'
1277 instructions will be disabled.
1278 RS-232 handshake
1280 If you turn this option off, Fuse assumes the RS-232 line
1281 other end is live when you connect the communication
1282 channels. See also the `--rs232-rx' and `--rs232-tx'
1283 options.
1284 Black and white TV
1286 This option allows you to choose whether to simulate a
1287 colour or black and white television. This is effective
1288 only under the GTK+, Win32, Xlib and SDL user interfaces:
1289 the others will always simulate a colour TV.
1290 PAL-TV use TV2x effect
1292 This option allows you to choose whether the PAL TV 2x
1293 and higher scalers also reproduce scanlines in the same
1294 way as the TV 2x, TV 3x and Timex TV scalers.
1295 Show statusbar
1297 For the GTK+ and Win32 UI, enables the statusbar beneath
1298 the display. For the SDL UI, enables the status icons
1299 showing whether the disk and tape are being accessed.
1300 This option has no effect for the other user interfaces.
1301 Snap joystick prompt
1303 If set, Fuse will prompt you which physical joystick or
1304 keyboard you want to connect to the joystick interface
1305 enabled in the snapshot unless it already matches your
1306 current configuration.
1307 Confirm actions
1309 Specify whether `dangerous' actions (those which could
1310 cause data loss, for example resetting the Spectrum)
1311 require confirmation before occurring.
1312 Auto-save settings
1314 If this option is selected, Fuse will automatically write
1315 its currently selected options to its configuration file
1316 on exit (either in xml format if libxml2 was available
1317 when Fuse was compiled or plain text). If this option is
1318 off, you'll have to manually use Options, Save afterwards
1319 to ensure that this setting gets written to Fuse's con‐
1320 figuration file. Note that if you turn this option on,
1321 loading a snapshot could enable peripherals that would be
1322 written permanently to the configuration file.
1323 Options, Media...
1325 Display the Media Options dialog, letting you configure Fuse's
1326 tape and Microdrive options. (With the widget UI, the keys shown
1327 in brackets toggle the options, Enter confirms any changes, and
1328 Esc aborts). Note that any changed settings only apply to the
1329 currently-running Fuse.
1330 Auto-load media
1332 On many occasions when you open a tape or disk file, it's
1333 because it's got a program in you want to load and run.
1334 If this option is selected, this will automatically hap‐
1335 pen for you when you open one of these files using the
1336 File, Open... menu option — you must then use the Media
1337 menu to use tapes or disks for saving data to, or for
1338 loading data into an already running program.
1339 Detect loaders
1341 If this option is enabled, Fuse will attempt to detect
1342 when a loading routine is in progress, and then automati‐
1343 cally start the virtual tape to load the program in. This
1344 is done by using a heuristic to identify a loading rou‐
1345 tine, so is by no means infallible, but works in most
1346 cases.
1347 Phantom typist mode
1349 Specify the keystroke sequence that the "phantom typist"
1350 should use when starting a program loading. Available
1351 options are
1352 Auto
1354 Keyword
1356 Keystroke
1358 Menu
1360 Plus 2A
1362 Plus 3
1364 The first four of these correspond to automatic detection
1366 based on machine model, keyword based entry, keystroke
1367 based entry, and selection from a 128K style menu. Plus
1368 2A and Plus 3 also correspond to selection from a 128K
1369 style menu, but have special handling for games which
1370 need to be loaded with `LOAD ""CODE'. The most likely use
1371 for this option will be use Keystroke if you have changed
1372 the default 48K ROM for one with keystroke entry.
1373 Fastloading
1375 If this option is enabled, then Fuse will run at the
1376 fastest possible speed when the virtual tape is playing,
1377 thus dramatically reducing the time it takes to load pro‐
1378 grams. You may wish to disable this option if you wish to
1379 stop the tape at a specific point.
1380 Use tape traps
1382 Ordinarily, Fuse intercepts calls to the ROM tape-loading
1383 routine in order to load from tape files more quickly
1384 when possible. But this can (rarely) interfere with TZX
1385 loading; disabling this option avoids the problem at the
1386 cost of slower (i.e. always real-time) tape-loading.
1387 When tape-loading traps are disabled, you need to start
1388 tape playback manually, by pressing F8 or choosing the
1389 Media, Tape, Play menu item. Fuse also uses tape traps to
1390 intercept the tape-saving routine in the ROM to save tape
1391 files quickly, tapes can also be saved using the Media,
1392 Tape, Record Start menu item.
1393 Accelerate loaders
1395 If this option is enabled, then Fuse will attempt to
1396 accelerate tape loaders by “short circuiting” the loading
1397 loop. This will in general speed up loading, but may
1398 cause some loaders to fail.
1399 Use .slt traps
1401 The multi-load aspect of SLT files requires a trap
1402 instruction to be supported. This instruction is not gen‐
1403 erally used except for this trap, but since it's not
1404 inconceivable that a program could be wanting to use the
1405 real instruction instead, you can choose whether to sup‐
1406 port the trap or not.
1407 MDR cartridge len
1409 This option controls the number of blocks in a new Micro‐
1410 drive cartridge. If the value smaller than 10 or greater
1411 than 254 Fuse assumes 10 or 254. Average real capacity
1412 is around 180 blocks (90 Kb).
1413 Random length MDR cartridge
1415 If this option is enabled, Fuse will use a random Micro‐
1416 drive cartridge length (around 180 blocks) instead of the
1417 length specified in the MDR cartridge len option.
1418 Options, Sound...
1420 Display the Sound Options dialog, letting you configure Fuse's
1421 sound output. (With the widget UI, the keys shown in brackets
1422 toggle the options, Enter confirms any changes, and Esc aborts).
1423 Note that any changed settings only apply to the currently-run‐
1424 ning Fuse.
1425 Sound enabled
1427 Specify whether sound output should be enabled at all.
1428 When this option is disabled, Fuse will not make any
1429 sound.
1430 Loading sound
1432 Normally, Fuse emulates tape-loading noise when loading
1433 from PZXs, TAPs or TZXs in real-time, albeit at a delib‐
1434 erately lower volume than on a real Spectrum. You can
1435 disable this option to eliminate the loading noise
1436 entirely.
1437 AY stereo separation
1439 By default, the sound output is mono, since this is all
1440 you got from an unmodified Spectrum. But enabling this
1441 option gives you so-called ACB stereo (for sound from the
1442 128 and other clone's AY-3-8912 sound chip).
1443 Force 8-bit
1445 Force the use of 8-bit sound even if 16-bit (the default)
1446 is available. Note that (when the option is enabled) if
1447 8-bit sound isn't available then there will be no sound
1448 at all, so it's best not to use this option unless you
1449 have a specific need for it.
1450 Speaker type
1452 This option allows the emulation of the sound output sys‐
1453 tem to be modified. Different choices of speaker limit
1454 the bass and treble response that can be produced from
1455 the machine. Choose between a “TV” type speaker and a
1456 small “Beeper” type speaker that significantly limits
1457 bass and treble response. Choose “Unfiltered” to get
1458 unmodified (but less accurate) sound output.
1459 AY volume
1461 Sets the relative volume of the AY-3-8912 chip from a
1462 range of 0–100%.
1463 Beeper volume
1465 Sets the relative volume of the beeper from a range of
1466 0–100%.
1467 Covox volume
1469 Sets the relative volume of the Covox from a range of
1470 0–100%.
1471 SpecDrum volume
1473 Sets the relative volume of the SpecDrum from a range of
1474 0–100%.
1475 Options, Peripherals, General...
1477 Display the General Peripherals Options dialog, letting you con‐
1478 figure the peripherals which Fuse will consider to be attached
1479 to the emulated machine. (With the widget UI, the keys shown in
1480 brackets toggle the options, Enter confirms any changes, and Esc
1481 aborts). Note that any changed settings only apply to the cur‐
1482 rently-running Fuse. Also note that any changes that enable and
1483 disable peripherals may result in a hard reset of the emulated
1484 machine.
1485 Kempston joystick
1487 If this option is selected, Fuse will emulate a Kempston
1488 joystick interface (probably the most widely supported
1489 type on the Spectrum). Note that this option is basi‐
1490 cally equivalent to plugging the interface itself into a
1491 Spectrum, not to connecting a joystick; this affects how
1492 the Spectrum responds to a read of input port 31. To use
1493 a Kempston joystick in a game, this option must be
1494 enabled, and you must also select a Kempston joystick the
1495 Options, Joysticks menu.
1496 Kempston mouse
1498 If this option is selected, Fuse will emulate a Kempston
1499 mouse interface.
1500 If you're using Fuse full-screen, your mouse is automati‐
1502 cally used as if attached to the Kempston interface. Oth‐
1503 erwise, you'll need to click on the Spectrum display in
1504 order to tell Fuse to grab the pointer (and make it
1505 invisible); to tell Fuse to release it, click the middle
1506 button (or wheel) or press Escape.
1507 With the framebuffer UI, Fuse prefers to use GPM; if this
1509 is not available, it will fall back to built-in PS/2
1510 mouse support. In this mode, it tries /dev/input/mice,
1511 /dev/mouse then /dev/psaux, stopping when it successfully
1512 opens one. The first of these is preferred since (at
1513 least on Linux, with a 2.6-series kernel) any type of
1514 mouse can be used and any connected mouse may be used.
1515 Swap mouse buttons
1517 If this option is enabled, the left and right mouse but‐
1518 tons will be swapped when emulating a Kempston mouse.
1519 Fuller Box
1521 If this option is selected, Fuse will emulate a Fuller
1522 Box AY sound and joystick interface. This emulation is
1523 only available for the 16k, 48k and TC2048 machines.
1524 Melodik
1526 If this option is selected, Fuse will emulate a Melodik
1527 AY sound interface. These interfaces and many similar
1528 ones were produced to make the 48K Spectrum compatible
1529 with the same AY music as the 128K Spectrum. This emula‐
1530 tion is only available for the 16k, 48k and TC2048
1531 machines.
1532 Interface 1
1534 If this option is selected, Fuse will emulate the simple
1535 Sinclair Interface 1, and allow Microdrive cartridges to
1536 be connected and disconnected via the Media, Interface 1,
1537 Microdrive menus. It also enables support for the Inter‐
1538 face 1 RS-232 interface.
1539 Interface 2
1541 If this option is selected, Fuse will emulate a cartridge
1542 port as found on the Interface 2. Cartridges can then be
1543 inserted and removed via the Media, Cartridge, Inter‐
1544 face 2 menu. Note that the Pentagon, Scorpion, Inter‐
1545 face 2, ZXATASP and ZXCF all use the same hardware mecha‐
1546 nism for accessing some of their extended features, so
1547 only one of these should be selected at once or unpre‐
1548 dictable behaviour will occur.
1549 Multiface One
1551 If this option is selected, Fuse will emulate the Roman‐
1552 tic Robot Multiface One. Available for 16K, 48K and
1553 Timex TC2048 machines.
1554 Multiface 128
1556 If this option is selected, Fuse will emulate the Roman‐
1557 tic Robot Multiface 128. Available for 16K, 48K, Timex
1558 TC2048, 128K, +2 and SE machines.
1559 Multiface 3
1561 If this option is selected, Fuse will emulate the Roman‐
1562 tic Robot Multiface 3. Available for +2A, +3 and +3e
1563 machines.
1564 Stealth Multiface One
1566 This option controls the `invisible' or `stealth' mode of
1567 Multiface One, as the physical switch on the side of the
1568 interface.
1569 Emulate printers
1571 If this option is selected, Fuse will emulate a printer.
1572 See the PRINTER EMULATION section for more details.
1573 ZX Printer
1575 If this option is selected, Fuse will emulate the ZX
1576 Printer. See the PRINTER EMULATION section for more
1577 details.
1578 SpeccyBoot interface
1580 If this option is selected, Fuse will emulate a Speccy‐
1581 Boot interface which allows booting a ZX Spectrum over an
1582 Ethernet network. See the SpeccyBoot web page at
1583 http://patrikpersson.github.io/speccyboot/ for more
1584 details.
1585 SpecDrum interface
1587 If this option is selected, Fuse will emulate a Cheetah
1588 SpecDrum sound interface. See the World of Spectrum
1589 Infoseek web page at http://www.worldofspec‐
1590 trum.org/infoseekid.cgi?id=1000062 for manuals, software
1591 and more. This emulation is only available for the 48k,
1592 128k and TC2048 machines.
1593 Spectranet
1595 If this option is selected, Fuse will emulate the Spec‐
1596 tranet interface, which provides an Ethernet interface
1597 for the Spectrum. See the SPECTRANET EMULATION section
1598 for more details.
1599 Spectranet disable
1601 This option controls the state of the Spectranet auto‐
1602 matic page-in jumper (J2). See the SPECTRANET EMULATION
1603 section for more details.
1604 µSource
1606 If this option is selected, Fuse will emulate a Currah
1607 µSource interface. See the World of Spectrum Infoseek
1608 web page at http://www.worldofspectrum.org/infos‐
1609 eekid.cgi?id=1000080 for the manual.
1610 Covox interface
1612 If this option is selected, Fuse will emulate a Covox
1613 digital sound interface. This emulation is only available
1614 for the Pentagon, Pentagon 512k, Pentagon 1024k and Scor‐
1615 pion machines. The Pentagon variants use port 0xfb and
1616 the Scorpion version uses port 0xdd.
1617 Options, Peripherals, Disk...
1619 Display the Disk Peripherals Options dialog, letting you config‐
1620 ure the disk interface peripherals which Fuse will consider to
1621 be attached to the emulated machine. (With the widget UI, the
1622 keys shown in brackets toggle the options, Enter confirms any
1623 changes, and Esc aborts). Note that any changed settings only
1624 apply to the currently-running Fuse. Also note that any changes
1625 that enable and disable peripherals may result in a hard reset
1626 of the emulated machine.
1627 Simple 8-bit IDE
1629 If this option is selected, Fuse will emulate the simple
1630 8-bit IDE interface as used by the Spectrum +3e, and
1631 allow hard disks to be connected and disconnected via the
1632 Media, IDE, Simple 8-bit menu.
1633 ZXATASP interface
1635 If this option is selected, Fuse will emulate the ZXATASP
1636 interface, which provides both additional RAM and an IDE
1637 interface. See the ZXATASP AND ZXCF section for more
1638 details.
1639 ZXATASP upload
1641 This option controls the state of the ZXATASP upload
1642 jumper. See the ZXATASP AND ZXCF section for more
1643 details.
1644 ZXATASP write protect
1646 This option controls the state of the ZXATASP write pro‐
1647 tect jumper. See the ZXATASP AND ZXCF section for more
1648 details.
1649 ZXCF interface
1651 If this option is selected, Fuse will emulate the ZXCF
1652 interface, which provides both additional RAM and a Com‐
1653 pactFlash interface. See the ZXATASP AND ZXCF section for
1654 more details.
1655 ZXCF upload
1657 This option controls the state of the ZXCF upload jumper.
1658 See the ZXATASP AND ZXCF section for more details.
1659 ZXMMC interface
1661 If this option is selected, Fuse will emulate the ZXMMC
1662 interface. Available for +2A, +3 and +3e machines.
1663 DivIDE interface
1665 If this option is selected, Fuse will emulate the DivIDE
1666 interface. See the DIVIDE section for more details.
1667 DivIDE write protect
1669 This option controls the state of the DivIDE write pro‐
1670 tection jumper. See the DIVIDE section for more details.
1671 DivMMC interface
1673 If this option is selected, Fuse will emulate the DivMMC
1674 interface. See the DIVMMC section for more details.
1675 DivMMC write protect
1677 This option controls the state of the DivMMC write pro‐
1678 tection jumper that prevents flashing the EEPROM chip.
1679 See the DIVMMC section for more details.
1680 +D interface
1682 If this option is selected, Fuse will emulate the +D
1683 interface. See the +D EMULATION section for more
1684 details.
1685 Didaktik 80 interface
1687 If this option is selected, Fuse will emulate the Didak‐
1688 tik 80 (or Didaktik 40) interface. See the DIDAKTIK 80
1689 EMULATION section for more details.
1690 DISCiPLE interface
1692 If this option is selected, Fuse will emulate the DISCi‐
1693 PLE interface. See the DISCIPLE EMULATION section for
1694 more details.
1695 Beta 128 interface
1697 If this option is selected, Fuse will emulate the
1698 Beta 128 interface. See the BETA 128 EMULATION section
1699 for more details. Beta 128 emulation is enabled for the
1700 Pentagon and Scorpion machines regardless of this option.
1701 Beta 128 auto-boot in 48K machines
1703 If this option is selected, then when a Beta 128 inter‐
1704 face is used in 48K or TC2048 emulation, the machine will
1705 boot directly into the TR-DOS system.
1706 Opus Discovery interface
1708 If this option is selected, Fuse will emulate the Opus
1709 Discovery interface. See the OPUS DISCOVERY EMULATION
1710 section for more details.
1711 Options, RZX...
1713 Display the RZX Options dialog, letting you configure how Fuse's
1714 deals with RZX input recordings. (With the widget UI, the keys
1715 shown in brackets toggle the options, Enter confirms any
1716 changes, and Esc aborts). Note that any changed settings only
1717 apply to the currently-running Fuse.
1718 Create autosaves
1720 If this option is selected, Fuse will add a snapshot into
1721 the recording stream every 5 seconds while creating an
1722 RZX file, thus enabling the rollback facilities to be
1723 used without having to explicitly add snapshots into the
1724 stream. Older snapshots will be pruned from the stream to
1725 keep the file size and number of snapshots down: each
1726 snapshot up to 15 seconds will be kept, then one snapshot
1727 every 15 seconds until one minute, then one snapshot
1728 every minute until 5 minutes, and then one snapshot every
1729 5 minutes. Note that this “pruning” applies only to auto‐
1730 matically inserted snapshots: snapshots manually inserted
1731 into the stream will never be pruned.
1732 Compress RZX data
1734 If this option is selected, and zlib was available when
1735 Fuse was compiled, any RZX files written by Fuse will be
1736 compressed. This is generally a good thing as it makes
1737 the files significantly smaller, and you probably want to
1738 turn it off only if you're debugging the RZX files or
1739 there's some other program which doesn't support com‐
1740 pressed RZX files.
1741 Competition mode
1743 Any input recordings which are started when this option
1744 is selected will be made in `competition mode'. In
1745 essence, this means that Fuse will act just like a real
1746 Spectrum would: you can't load snapshots, pause the emu‐
1747 lation in any way, change the speed or anything that you
1748 couldn't do on the real machine. If any of these things
1749 are attempted, or if the emulated Fuse is running more
1750 than 5% faster or slower than normal Spectrum speed, then
1751 the recording will immediately be stopped.
1752 If libgcrypt was available when Fuse was compiled, then
1754 recordings made with competition mode active will be dig‐
1755 itally signed, in theory to `certify' that it was made
1756 with the above restrictions in place. However, this pro‐
1757 cedure is not secure (and cannot be made so), so the
1758 presence of any signature on an RZX file should not be
1759 taken as providing proof that it was made with competi‐
1760 tion mode active. This feature is included in Fuse
1761 solely as it was one of the requirements for Fuse to be
1762 used in an on-line tournament.
1763 Competition code
1765 The numeric code entered here will be written into any
1766 RZX files made in competition mode. This is another fea‐
1767 ture for on-line tournaments which can be used to `prove'
1768 that the recording was made after a specific code was
1769 released. If you're not playing in such a tournament, you
1770 can safely ignore this option.
1771 Always embed snapshot
1773 Specify whether a snapshot should be embedded in an RZX
1774 file when recording is started from an existing snapshot.
1775 Options, Movie...
1777 Display the Movie Options dialog, letting you configure how
1778 Fuse's deals with movie recordings.
1779 Movie compression
1781 This option set the compression level to None, Lossless
1782 or High. (See the MOVIE RECORDING section for more infor‐
1783 mation).
1784 Stop recording after RZX ends
1786 If this option is selected, Fuse will stop any movie
1787 recording after a RZX playback is finished.
1788 Options, Joysticks
1790 Fuse can emulate many of the common types of joystick which were
1791 available for the Spectrum. The input for these emulated joy‐
1792 sticks can be taken from real joysticks attached to the emulat‐
1793 ing machine (configured via the Options, Joysticks, Joy‐
1794 stick 1... and Options, Joysticks, Joystick 2... options), or
1795 from the q, a, o, p, and Space keys on the emulating machines
1796 keyboard, configured via the Options, Joysticks, Keyboard...
1797 option. Note that when using the keyboard to emulate a joystick,
1798 the q, a, o, p, and Space keys will not have their normal effect
1799 (to avoid problems with games which do things like use p for
1800 pause when using a joystick).
1801 Each of the joysticks (including the `fake' keyboard joystick)
1803 can be configured to emulate any one of the following joystick
1804 types:
1805 None
1807 No joystick: any input will simply be ignored.
1808 Cursor
1810 A cursor joystick, equivalent to pressing 5
1811 (left), 6 (down), 7 (up), 8 (right), and 0 (fire).
1812 Kempston
1814 A Kempston joystick, read from input port 31. Note
1815 that the Options, Peripherals, General, Kempston
1816 interface option must also be set for the input to
1817 be recognised.
1818 Sinclair 1
1820 Sinclair 2
1821 The `left' and `right' Sinclair joysticks, equiva‐
1822 lent to pressing 1 (left), 2 (right), 3 (down), 4
1823 (up), and 5 (fire), or 6 (left), 7 (right), 8
1824 (down), 9 (up), and 0 (fire) respectively.
1825 Timex 1
1827 Timex 2
1828 The `left' and `right' joysticks as attached to
1829 the Timex 2068 variant's built-in joystick inter‐
1830 face.
1831 For the real joysticks, it is also possible to configure what
1833 effect each button on the joystick will have: this can be Joy‐
1834 stick Fire, equivalent to pressing the emulated joystick's fire
1835 button, Nothing, meaning to have no effect, or any Spectrum key,
1836 meaning that pressing that button will be equivalent to pressing
1837 that Spectrum key.
1838 Options, Select ROMs, Machine ROMs
1840 An individual dialog is available for each Spectrum variant emu‐
1841 lated by Fuse which allows selection of the ROM(s) used by that
1842 machine. Simply select the ROM you wish to use, and then reset
1843 the Spectrum for the change to take effect.
1844 Options, Select ROMs, Peripheral ROMs
1846 The same as the Machine ROMs menu, but an individual dialog is
1847 available for peripherals that need a ROM. Simply select the ROM
1848 you wish to use, and then reset the Spectrum for the change to
1849 take effect.
1850 Options, Filter...
1852 Select the graphics filter currently in use. See the GRAPHICS
1853 FILTERS section for more details.
1854 F11
1856 Options, Full Screen
1857 Switch Fuse between full screen and windowed mode. This menu is
1858 only available under the SDL UI.
1859 Options, Disk Options...
1861 When emulating disk drives, Fuse allows the specification of the
1862 physical drive units attached to the emulated interface. Each
1863 drive can be set to be one of the following types:
1864 Disabled
1866 Single-sided 40 track
1868 Double-sided 40 track
1870 Single-sided 80 track
1872 Double-sided 80 track
1874 The Disabled option is not supported for Drive 1 or Drive A of
1876 any interface.
1877 The available options that can be set are:
1879 +3 Drive A
1881 Defaults to a single-sided 40 track drive.
1882 +3 Drive B
1884 Defaults to a double-sided 80 track drive.
1885 +3 Detect Speedlock
1887 Specify whether the +3 drives try to detect Speedlock
1888 protected disks, and emulate `weak' sectors. If the disk
1889 image file (EDSK or UDI) contains weak sector data, than
1890 Speedlock detection is automatically omitted. See also
1891 the WEAK DISK DATA section.
1892 Beta 128 Drive A
1894 Defaults to a double-sided 80 track drive.
1895 Beta 128 Drive B
1897 Defaults to a double-sided 80 track drive.
1898 Beta 128 Drive C
1900 Defaults to a double-sided 80 track drive.
1901 Beta 128 Drive D
1903 Defaults to a double-sided 80 track drive.
1904 +D Drive 1
1906 Defaults to a double-sided 80 track drive.
1907 +D Drive 2
1909 Defaults to a double-sided 80 track drive.
1910 Didaktik 80 Drive A
1912 Defaults to a double-sided 80 track drive.
1913 Didaktik 80 Drive B
1915 Defaults to a double-sided 80 track drive.
1916 DISCiPLE Drive 1
1918 Defaults to a double-sided 80 track drive.
1919 DISCiPLE Drive 2
1921 Defaults to a double-sided 80 track drive.
1922 Opus Drive 1
1924 Defaults to a single-sided 40 track drive.
1925 Opus Drive 2
1927 Defaults to a single-sided 40 track drive.
1928 Try merge 'B' side of disks
1930 This option prompts the user to confirm whether Fuse
1931 should try to merge the `B' side of a disk image from a
1932 separate file when opening a new single-sided disk image.
1933 Confirm merge disk sides
1935 Select whether Fuse should try to merge a separate file
1936 for the `B' side of a disk image separate file when open‐
1937 ing a new disk image. Most double sided disk images are
1938 dumped as two single sided disk images e.g. `Golden Axe
1939 - Side A.dsk' and `Golden Axe - Side B.dsk'. So, if we
1940 want to play Golden Axe, first we have to insert the
1941 first disk image and when the game asks to insert side B,
1942 we have to find and open the second disk image, instead
1943 of just `flip'-ing the disk inside the drive. If enabled,
1944 Fuse will try to open the second image too and create a
1945 double sided disk image (merging the two one sided disk
1946 images) and insert this merged virtual disk into the disk
1947 drive. The function detects whether the file is one side
1948 of a double-sided image if the filename matches a pattern
1949 like [Ss]ide[ _][abAB12][ _.] in the file name of a disk
1950 that is being opened. If found, Fuse will try to open the
1951 other side of the disk too substituting the appropriate
1952 characters in the filename e.g. 1→2, a→b, A→B. If suc‐
1953 cessful then it will merge the two images and now we have
1954 a double sided disk in drive. This means that if we open
1955 `Golden Axe - Side A.dsk', then Fuse will try to open
1956 `Golden Axe - Side B.dsk' too. Now, we can just `flip'
1957 the disk if Golden Axe asks for `Side B'. The available
1958 options are Never, With single-sided drives and Always.
1959 Options, Save
1961 This will cause Fuse's current options to be written to
1962 .fuserc in your home directory (Unix-like systems), or
1963 fuse.cfg in your %USERPROFILE% folder (Windows), from
1964 which they will be picked up again when Fuse is
1965 restarted. The best way to update this file is by using
1966 this option, but it's a simple XML file if libxml2 was
1967 available when Fuse was compiled (otherwise, plain text),
1968 and shouldn't be too hard to edit by hand if you really
1969 want to.
1970 Pause
1972 Machine, Pause
1973 Pause or unpause emulation. This option is available only
1974 under the GTK+ and Win32 UIs; to pause the other user
1975 interfaces, simply press F1 to bring up the main menu.
1976 F5
1978 Machine, Reset
1979 Reset the emulated Spectrum.
1980 Machine, Hard reset
1982 Reset the emulated Spectrum. A hard reset is equivalent
1983 to turning the Spectrum's power off, and then turning it
1984 back on.
1985 F9
1987 Machine, Select...
1988 Choose a type of Spectrum to emulate. An brief overview
1989 of the Sinclair, Amstrad and Timex can be found at
1990 http://www.nvg.ntnu.no/sinclair/computers/zxspec‐
1991 trum/zxspectrum.htm while more technical information can
1992 be found at http://www.worldofspectrum.org/faq/refer‐
1993 ence/reference.htm, and http://www.worldofspec‐
1994 trum.org/faq/reference/tmxreference.htm.
1995 Spectrum 16K
1997 Spectrum 48K
1998 The original machines as released by Sinclair in
1999 1982 with 16 or 48K of RAM respectively.
2000 Spectrum 48K (NTSC)
2002 The NTSC 48K machine released in limited numbers
2003 in parts of South America.
2004 Spectrum 128K
2006 The 128K machine as released by Sinclair in
2007 1985 (Spain) or 1986 (UK).
2008 Spectrum +2
2010 The first machine released by Amstrad, in 1986.
2011 From an emulation point of view, the +2 is virtu‐
2012 ally identical to the 128K.
2013 Spectrum +2A
2015 Spectrum +3
2016 The two machines released by Amstrad in 1988.
2017 Technically very similar to each other, except
2018 that the +3 features a 3″ disk drive while the +2A
2019 does not.
2020 Spectrum +3e
2022 A +3 with modified ROMs allowing access to IDE
2023 hard disks via the simple 8-bit interface, as
2024 activated from the Options, Peripherals, Disk...
2025 dialog. See http://www.worldofspec‐
2026 trum.org/zxplus3e/ for more details.
2027 Timex TC2048
2029 Timex TC2068
2030 The variants of the Spectrum as released by Timex
2031 in Portugal.
2032 Timex TS2068
2034 The variant of the Spectrum released by Timex in
2035 North America.
2036 Pentagon 128K
2038 Russian clone of the Spectrum. There were many
2039 different machines called Pentagon from 1989 to
2040 2006, this machine corresponds to a 1991 era Pen‐
2041 tagon 128K with the optional AY sound chip and the
2042 integrated Beta 128 disk interface, and is the
2043 version of the machine most often emulated. More
2044 technical details can be found at
2045 http://www.worldofspectrum.org/rusfaq/index.html,
2046 Pentagon 512K
2048 Pentagon 1024K
2049 Newer versions of the Pentagon Russian Spectrum
2050 clones which incorporate more memory and the “Mr
2051 Gluk Reset Service” ROM offering a more powerful
2052 firmware.
2053 Scorpion ZS 256
2055 Another Russian clone of the Spectrum. Some
2056 details can be found at http://www.worldofspec‐
2057 trum.org/rusfaq/index.html. Like all the Russian
2058 clones, they have built in 3.5″ disk drives,
2059 accessed via the Beta 128 disk interface and TR-
2060 DOS (the Technology Research Disk Operating Sys‐
2061 tem). The most important distinction from the Pen‐
2062 tagon 128k and similar machines is the display
2063 timing details.
2064 Spectrum SE
2066 A recent variant designed by Andrew Owen and Jarek
2067 Adamski, which is possibly best thought of as a
2068 cross between the 128K machine and the Timex vari‐
2069 ants, allowing 272K of RAM to be accessed. Some
2070 more details are available at http://www.worldof‐
2071 spectrum.org/faq/reference/sereference.htm and
2072 documentation of the extended BASIC is available
2073 at https://github.com/cheveron/sebasic4/wiki. The
2074 bug tracker for the BASIC is at
2075 https://github.com/cheveron/seba‐
2076 sic4/issues?state=open.
2077 Machine, Debugger...
2079 Start the monitor/debugger. See the MONITOR/DEBUGGER sec‐
2080 tion for more information.
2081 Machine, Poke Finder...
2083 Start the `poke finder'. See the POKE FINDER section for
2084 more information.
2085 Machine, Poke Memory...
2087 Allow one to use multiface POKEs for things such as infi‐
2088 nite lives. See the POKE MEMORY section for more informa‐
2089 tion.
2090 Machine, Memory Browser...
2092 Start the memory browser. It should be fairly obvious
2093 what this does; perhaps the only thing worth noting is
2094 that emulation is paused until you close the window.
2095 Machine, NMI
2097 Sends a non-maskable interrupt to the emulated Spectrum.
2098 Due to a typo in the standard 48K ROM, this will cause a
2099 reset, but modified ROMs are available which make use of
2100 this feature. When the +D (or DISCiPLE) is emulated, this
2101 is used to access the +D (or DISCiPLE)'s screenshot and
2102 snapshot features (see the +D EMULATION and DISCIPLE EMU‐
2103 LATION sections below). For the DISCiPLE, Caps Shift
2104 must be held down whilst pressing the NMI button. For
2105 some UIs, this may be tricky, or even impossible to do.
2106 Note that GDOS on the DISCiPLE contains a bug which
2107 causes corruption of saved snapshots, and a failure to
2108 return from the NMI menu correctly. This bug is not
2109 present in G+DOS on the +D.
2110 Machine, Multiface Red Button
2112 Presses the Multiface One/128/3 red button to active the
2113 interface.
2114 Machine, Didaktik SNAP
2116 Presses the Didaktik 80 (or Didaktik 40)'s `SNAP' button.
2117 F7
2119 Media, Tape, Open...
2120 Choose a PZX, TAP or TZX virtual-tape file to load from.
2121 See the FILE SELECTION section below for details on how
2122 to choose the file. If Auto-load media is set in the
2123 Media Options dialog (as it is by default), you may use
2124 the File, Open... menu option instead, and the tape will
2125 begin loading automatically. Otherwise, you have to
2126 start the load in the emulated machine (with LOAD "" or
2127 the 128's Tape Loader option, though you may need to
2128 reset first).
2129 To guarantee that TZX files will load properly, you
2131 should select the file, make sure tape-loading traps are
2132 disabled in the Media Options dialog, then press F8 (or
2133 do Media, Tape, Play). That said, most TZXs will work
2134 with tape-loading traps enabled (often quickly loading
2135 partway, then loading the rest real-time), so you might
2136 want to try it that way first.
2137 F8
2139 Media, Tape, Play
2140 Start playing the PZX, TAP or TZX file, if required.
2141 (Choosing the option (or pressing F8) again pauses play‐
2142 back, and a further press resumes). To explain — if tape-
2143 loading traps have been disabled (in the Media Options
2144 dialog), starting the loading process in the emulated
2145 machine isn't enough. You also have to `press play', so
2146 to speak :-), and this is how you do that. You may also
2147 need to `press play' like this in certain other circum‐
2148 stances, e.g. TZXs containing multi-load games may have a
2149 stop-the-tape request (which Fuse obeys).
2150 Media, Tape, Browse
2152 Browse through the current tape. A brief display of each
2153 of the data blocks on the current tape will appear, from
2154 which you can select which block Fuse will play next.
2155 With the GTK+ UI, emulation will continue while the
2156 browser is displayed; double-clicking on a block will
2157 select it. In the other UIs, emulation is paused and you
2158 can use the cursor keys and press Enter to select it. If
2159 you decide you don't want to change block, just press
2160 Escape.
2161 Media, Tape, Rewind
2163 Rewind the current virtual tape, so it can be read again
2164 from the beginning.
2165 Media, Tape, Clear
2167 Clear the current virtual tape. This is particularly use‐
2168 ful when you want a `clean slate' to add newly-saved
2169 files to, before doing Media, Tape, Write... (or F6).
2170 F6
2172 Media, Tape, Write...
2173 Write the current virtual-tape contents to a TZX file.
2174 You will be prompted for a filename. The virtual-tape
2175 contents are the contents of the previously-loaded tape
2176 (if any has been loaded since you last did a Media, Tape,
2177 Clear), followed by anything you've saved from the emu‐
2178 lated machine since. These newly-saved files are not
2179 written to any tape file until you choose this option!
2180 Media, Tape, Record Start
2182 Starts directly recording the output from the emulated
2183 Spectrum to the current virtual-tape. This is useful when
2184 you want to record using a non-standard ROM or from a
2185 custom save routine. Most tape operations are disabled
2186 during recording. Stop recording with the Media, Tape,
2187 Write... menu option.
2188 Media, Tape, Record Stop
2190 Stops the direct recording and places the new recording
2191 into the virtual-tape.
2192 Media, Interface 1
2194 Virtual Microdrive images are accessible only when the
2195 Interface 1 is active from the Options, Peripherals, Gen‐
2196 eral... dialog. Note that any changes to the Microdrive
2197 image will not be written to the file on disk until the
2198 appropriate save option is used.
2199 Media, Interface 1, Microdrive 1, Insert New
2201 Insert a new (unformatted) Microdrive cartridge into emu‐
2202 lated Microdrive 1.
2203 Media, Interface 1, Microdrive 1, Insert...
2205 Insert an existing Microdrive cartridge image into emu‐
2206 lated Microdrive 1. You will be prompted for a filename.
2207 Media, Interface 1, Microdrive 1, Eject
2209 Eject the Microdrive image in Microdrive 1. If the image
2210 has been modified, you will be asked as to whether you
2211 want any changes saved.
2212 Media, Interface 1, Microdrive 1, Save
2214 Save the Microdrive image in Microdrive 1.
2215 Media, Interface 1, Microdrive 1, Save as...
2217 Write the Microdrive image in Microdrive 1 to a file. You
2218 will be prompted for a filename.
2219 Media, Interface 1, Microdrive 1, Write protect, Enable
2221 Enable the write protect tab for the image in Micro‐
2222 drive 1.
2223 Media, Interface 1, Microdrive 1, Write protect, Disable
2225 Disable the write protect tab for the image in Micro‐
2226 drive 1.
2227 Media, Interface 1, Microdrive 2, ...
2229 Media, Interface 1, Microdrive 3, ...
2230 Media, Interface 1, Microdrive 4, ...
2231 Media, Interface 1, Microdrive 5, ...
2232 Media, Interface 1, Microdrive 6, ...
2233 Media, Interface 1, Microdrive 7, ...
2234 Media, Interface 1, Microdrive 8, ...
2235 Equivalent options for the other emulated Microdrives.
2236 Media, Interface 1, RS232, Plug RxD
2238 Media, Interface 1, RS232, Unplug RxD
2239 Media, Interface 1, RS232, Plug TxD
2240 Media, Interface 1, RS232, Unplug TxD
2241 Connect or disconnect a communication channels (FIFO or
2242 file) to use as the RS-232 TxD or RxD wire.
2243 Media, Disk
2245 Virtual floppy disk images are accessible when emulating
2246 a +3, +3e, Pentagon or Scorpion, or when the Beta 128,
2247 Opus Discovery, +D, Didaktik or DISCiPLE interface
2248 options are enabled and a machine compatible with the
2249 chosen interface is selected. (See THE .DSK FORMAT,
2250 BETA 128 EMULATION, OPUS DISCOVERY EMULATION, +D EMULA‐
2251 TION, DIDAKTIK 80 EMULATION and DISCIPLE EMULATION sec‐
2252 tions below for notes on the file formats supported).
2253 Once again, any changes made to a disk image will not
2255 affect the file which was `inserted' into the drive. If
2256 you do want to keep any changes, use the appropriate
2257 `eject and write' option before exiting Fuse.
2258 Media, Disk, +3, Drive A:, Insert...
2260 Insert a disk-image file to read/write in the +3's emu‐
2261 lated drive A:.
2262 Media, Disk, +3, Drive A:, Eject
2264 Eject the disk image currently in the +3's emulated
2265 drive A: — or from the emulated machine's perspective,
2266 eject it. Note that any changes made to the image will
2267 not be saved.
2268 Media, Disk, +3, Drive A:, Save
2270 Save the disk image currently in the +3's drive A:.
2271 Media, Disk, +3, Drive A:, Save as...
2273 Save the current state of the disk image currently in the
2274 +3's drive A: to a file. You will be prompted for a file‐
2275 name.
2276 Media, Disk, +3, Drive B:, Insert...
2278 As above, but for the +3's drive B:. Fuse emulates
2279 drive B: as a second 3″ drive.
2280 Media, Disk, +3, Drive B:, Eject
2282 As above, but for drive B:.
2283 Media, Disk, +3, Drive B:, Save
2285 As above, but for drive B:.
2286 Media, Disk, +3, Drive B:, Save as...
2288 As above, but for drive B:.
2289 Media, Disk, Beta, Drive A:, Insert New
2291 Insert a new (unformatted) disk into the emulated Beta
2292 drive A:.
2293 Media, Disk, Beta, Drive A:, Insert...
2295 Media, Disk, Beta, Drive A:, Eject
2296 Media, Disk, Beta, Drive A:, Save
2297 Media, Disk, Beta, Drive A:, Save as...
2298 As above, but for the emulated Beta disk drive A:.
2299 Media, Disk, Beta, Drive A:, Write protect, Enable
2301 Enable the write protect tab for the image in Beta
2302 drive A:.
2303 Media, Disk, Beta, Drive A:, Write protect, Disable
2305 Disable the write protect tab for the image in Beta
2306 drive A:.
2307 Media, Disk, Beta, Drive B:, ...
2309 Media, Disk, Beta, Drive C:, ...
2310 Media, Disk, Beta, Drive D:, ...
2311 As above, but for the remaining emulated Beta disk inter‐
2312 face drives.
2313 Media, Disk, Opus, Drive 1, Insert New
2315 Media, Disk, Opus, Drive 1, Insert...
2316 Media, Disk, Opus, Drive 1, Eject
2317 Media, Disk, Opus, Drive 1, Save
2318 Media, Disk, Opus, Drive 1, Save as...
2319 Media, Disk, Opus, Drive 1, Write protect, Enable
2320 Media, Disk, Opus, Drive 1, Write protect, Disable
2321 Media, Disk, Opus, Drive 2, ...
2322 As above, but for the emulated Opus Discovery drives.
2323 Media, Disk, +D, Drive 1, Insert New
2325 Media, Disk, +D, Drive 1, Insert...
2326 Media, Disk, +D, Drive 1, Eject
2327 Media, Disk, +D, Drive 1, Save
2328 Media, Disk, +D, Drive 1, Save as...
2329 Media, Disk, +D, Drive 1, Write protect, Enable
2330 Media, Disk, +D, Drive 1, Write protect, Disable
2331 Media, Disk, +D, Drive 2, ...
2332 As above, but for the emulated +D drives.
2333 Media, Disk, Didaktik 80, Drive A, Insert New
2335 Media, Disk, Didaktik 80, Drive A, Insert...
2336 Media, Disk, Didaktik 80, Drive A, Eject
2337 Media, Disk, Didaktik 80, Drive A, Save
2338 Media, Disk, Didaktik 80, Drive A, Save as...
2339 Media, Disk, Didaktik 80, Drive A, Write protect, Enable
2340 Media, Disk, Didaktik 80, Drive A, Write protect, Disable
2341 Media, Disk, Didaktik 80, Drive B, ...
2342 As above, but for the emulated Didaktik 80 drives.
2343 Media, Disk, DISCiPLE, Drive 1, Insert New
2345 Media, Disk, DISCiPLE, Drive 1, Insert...
2346 Media, Disk, DISCiPLE, Drive 1, Eject
2347 Media, Disk, DISCiPLE, Drive 1, Save
2348 Media, Disk, DISCiPLE, Drive 1, Save as...
2349 Media, Disk, DISCiPLE, Drive 1, Write protect, Enable
2350 Media, Disk, DISCiPLE, Drive 1, Write protect, Disable
2351 Media, Disk, DISCiPLE, Drive 2, ...
2352 As above, but for the emulated DISCiPLE drives.
2353 Media, Cartridge, Timex Dock, Insert...
2355 Insert a cartridge into the Timex 2068 dock. This will
2356 cause the emulated machine to be changed to the TC2068
2357 (if it wasn't already a 2068 variant) and reset.
2358 Media, Cartridge, Timex Dock, Eject
2360 Remove the cartridge from the Timex 2068 dock. This will
2361 cause the emulated machine to be reset.
2362 Media, Cartridge, Interface 2, Insert...
2364 Insert a cartridge into the Interface 2 cartridge slot.
2365 This will cause the emulated machine to be reset and the
2366 cartridge loaded.
2367 Media, Cartridge, Interface 2, Eject...
2369 Remove the cartridge from the Interface 2 cartridge slot.
2370 This will cause the emulated machine to be reset.
2371 Media, IDE, Simple 8-bit, Master, Insert...
2373 Connect an IDE hard disk to the simple 8-bit interface's
2374 master channel.
2375 Media, IDE, Simple 8-bit, Master, Commit
2377 Cause any writes which have been done to virtual hard
2378 disk attached to the simple 8-bit interface's master
2379 channel to be committed to the real disk, such that they
2380 survive the virtual disk being ejected.
2381 Media, IDE, Simple 8-bit, Master, Eject
2383 Eject the virtual hard disk from the simple 8-bit inter‐
2384 face's master channel. Note that any writes to the vir‐
2385 tual hard disk will be lost unless the Media, IDE, Simple
2386 8-bit, Master, Commit option is used before the disk is
2387 ejected.
2388 Media, IDE, Simple 8-bit, Slave, Insert...
2390 Media, IDE, Simple 8-bit, Slave, Commit
2391 Media, IDE, Simple 8-bit, Slave, Eject
2392 The same as the Media, IDE, Simple 8-bit, Master entries
2393 above, but for the simple 8-bit interface's slave chan‐
2394 nel.
2395 Media, IDE, ZXATASP, Master, Insert...
2397 Media, IDE, ZXATASP, Master, Commit
2398 Media, IDE, ZXATASP, Master, Eject
2399 Media, IDE, ZXATASP, Slave, Insert...
2400 Media, IDE, ZXATASP, Slave, Commit
2401 Media, IDE, ZXATASP, Slave, Eject
2402 The same as the Media, IDE, Simple 8-bit, Master entries
2403 above, but for the two channels of the ZXATASP interface.
2404 Media, IDE, ZXCF CompactFlash, Insert...
2406 Media, IDE, ZXCF CompactFlash, Commit
2407 Media, IDE, ZXCF CompactFlash, Eject
2408 The same as the Media, IDE, Simple 8-bit, Master entries
2409 above, but for the ZXCF interface's CompactFlash slot.
2410 Media, IDE, ZXMMC, Insert...
2412 Media, IDE, ZXMMC, Commit
2413 Media, IDE, ZXMMC, Eject
2414 The same as the Media, IDE, Simple 8-bit entries above,
2415 but for the memory card slot of the ZXMMC interface.
2416 Media, IDE, DivIDE, Master, Insert...
2418 Media, IDE, DivIDE, Master, Commit
2419 Media, IDE, DivIDE, Master, Eject
2420 Media, IDE, DivIDE, Slave, Insert...
2421 Media, IDE, DivIDE, Slave, Commit
2422 Media, IDE, DivIDE, Slave, Eject
2423 The same as the Media, IDE, Simple 8-bit entries above,
2424 but for the two channels of the DivIDE interface.
2425 Media, IDE, DivMMC, Insert...
2427 Media, IDE, DivMMC, Commit
2428 Media, IDE, DivMMC, Eject
2429 The same as the Media, IDE, Simple 8-bit entries above,
2430 but for the memory card slot of the DivMMC interface.
2431 Help, Keyboard picture...
2433 Display a diagram showing the Spectrum keyboard, and the
2434 various keywords that can be generated with each key from
2435 (48K) BASIC. Under the GTK+ and Win32 UIs, this will
2436 appear in a separate window and emulation continues. With
2437 the other UIs, the picture remains onscreen (and the emu‐
2438 lator paused) until you press Esc or Enter.
2439
2441 When emulating the Spectrum, keys F1 to F10 are used as shortcuts for
2442 various menu items, as described above. The alphanumeric keys (along
2443 with Enter and Space) are mapped as-is to the Spectrum keys. The other
2444 key mappings are:
2445 Shift emulated as Caps Shift
2447 Control, Alt, and Meta
2449 emulated as Symbol Shift (most other modifiers are also mapped
2450 to this)
2451 Backspace
2453 emulated as Caps–0 (Delete)
2454 Esc emulated as Caps–1 (Edit)
2456 Caps Lock
2458 emulated as Caps–2
2459 Cursor keys
2461 emulated as Caps–5/6/7/8 (as appropriate)
2462 Tab emulated as Caps Shift–Symbol Shift (Extended Mode)
2464 Some further punctuation keys are supported, if they exist on your key‐
2466 board — `,', `.', `/', `;', `'', `#', `-', and `='. These are mapped
2467 to the appropriate symbol-shifted keys on the Spectrum.
2468 A list of keys applicable when using the file selection dialogs is
2470 given in the FILE SELECTION section below.
2471
2473 Some of Fuse's UIs allow resizing of the emulated Spectrum's display.
2474 For the window-based ones (GTK+, Win32 and Xlib), you can resize the
2475 window by, well, resizing it. :-) Exactly how this works depends on
2476 your window manager; you may have to make the window over twice the
2477 width and height of the original size before it actually scales up.
2478 Fuse attempts to keep the window `square', but with some window man‐
2479 agers this can mean the window will never resize at all. If you experi‐
2480 ence this problem, the `--no-aspect-hint' option may help.
2481 If you're using the SDL UI under X11 or GTK+, the window will automati‐
2483 cally resize to be the correct size for the graphics filter selected.
2484
2486 Fuse has the ability to apply essentially arbitrary filters between
2487 building its image of the Spectrum's screen, and displaying it on the
2488 emulating machine's monitor. These filters can be used to do various
2489 forms of smoothing, emulation of TV scanlines and various other possi‐
2490 bilities. Support for graphics filters varies between the different
2491 user interfaces, but there are two general classes: the GTK+, Win32,
2492 Xlib, SVGAlib and SDL user interfaces (and the saving of .png screen‐
2493 shots) support `interpolating' filters which use a palette larger than
2494 the Spectrum's 16 colours, while the framebuffer user interface cur‐
2495 rently does not support filters at all.
2496 A further complication arises due to the fact that the Timex machines
2498 have their high-resolution video mode with twice the horizontal resolu‐
2499 tion. To deal with this, Fuse treats these machines as having a `nor‐
2500 mal' display size which is twice the size of a normal Spectrum's
2501 screen, leading to a different set of filters being available for these
2502 machines. Note that any of the double or triple-sizing filters are
2503 available for Timex machines only when using the SDL, Win32 or GTK+
2504 user interfaces.
2505 The available filters, along with their short name used to select them
2507 from the command line, are:
2508 Timex half (smoothed) (half)
2510 Timex half (skipping) (halfskip)
2511 Two Timex-machine specific filters which scale the screen down
2512 to half normal (Timex) size; that is, the same size as a normal
2513 Spectrum screen. The difference between these two filters is in
2514 how they handle the high-resolution mode: the `smoothed' version
2515 is an interpolating filter which averages pairs of adjacent pix‐
2516 els, while the `skipping' version is a non-interpolating filter
2517 which simply drops every other pixel.
2518 Normal (normal)
2520 The simplest filter: just display one pixel for every pixel on
2521 the Spectrum's screen.
2522 Double size (2x)
2524 Scale the displayed screen up to double size.
2525 Triple size (3x)
2527 Scale the displayed screen up to triple size. Available only
2528 with the GTK+, Win32, Xlib and SDL user interfaces or when sav‐
2529 ing screenshots of non-Timex machines.
2530 2xSaI (2xsai)
2532 Super 2xSaI (super2xsai)
2533 SuperEagle (supereagle)
2534 Three interpolating filters which apply successively more
2535 smoothing. All three double the size of the displayed screen.
2536 AdvMAME2x (advmame2x)
2538 A double-sizing, non-interpolating filter which attempts to
2539 smooth diagonal lines.
2540 AdvMAME3x (advmame3x)
2542 Very similar to AdvMAME2x, except that it triples the size of
2543 the displayed screen. Available only with the GTK+, Win32, Xlib
2544 and SDL user interfaces or when saving screenshots of non-Timex
2545 machines.
2546 TV 2x (tv2x)
2548 TV 3x (tv3x)
2549 Timex TV (timextv)
2550 Three filters which attempt to emulate the effect of television
2551 scanlines. The first is a double-sizing filter for non-Timex
2552 machines, the second is a similar triple-sizing filter, while
2553 the last is a single-sizing filter for Timex machines (note that
2554 this means TV 2X and Timex TV produce the same size output).
2555 PAL TV (paltv)
2557 PAL TV 2x (paltv2x)
2558 PAL TV 3x (paltv3x)
2559 Three filters which attempt to emulate the effect of the PAL TV
2560 system which layers a lower-resolution colour image over the top
2561 of a higher-resolution black-and-white image. The filters can
2562 also optionally add scanlines like the other TV series scalers.
2563 Dot matrix (dotmatrix)
2565 A double-sizing filter which emulates the effect of a dot-matrix
2566 display.
2567 Timex 1.5x (timex15x)
2569 An interpolating Timex-specific filter which scales the Timex
2570 screen up to 1.5× its usual size (which is therefore 3× the size
2571 of a `normal' Spectrum screen). Available only for the GTK+,
2572 Win32 and SDL user interfaces or when saving screenshots.
2573 HQ 2x (hq2x)
2575 HQ 3x (hq3x)
2576 Two filters which do high quality (but slow) antialiasing. Dou‐
2577 bles and triples the size of the displayed screen respectively.
2578
2580 The emulated Spectrum is, by default, an unmodified 48K Spectrum with a
2581 tape player and ZX Printer attached. Oh, and apparently some magical
2582 snapshot load/save machine which is probably best glossed over for the
2583 sake of the analogy. :-)
2584 To emulate different kinds of Spectrum, select the Machine, Select...
2586 menu option, or press F9.
2587 The Spectrum emulation is paused when any dialogs appear. In the widget
2589 UI, it's also paused when menus or the keyboard picture are displayed.
2590
2592 The various models of Spectrum supported a range of ways to connect
2593 printers, three of which are supported by Fuse. Different printers are
2594 made available for the different models:
2595 16, 48, TC2048, TC2068, TS2068
2597 ZX Printer
2598 128/+2/Pentagon
2600 Serial printer (text-only)
2601 +2A, +3
2603 Parallel printer (text-only)
2604 If Opus Discovery, +D or DISCiPLE emulation is in use and printer emu‐
2606 lation is enabled, text-only emulation of the disk interface's parallel
2607 printer interface is provided.
2608 Any printout is appended to one (or both) of two files, depending on
2610 the printer — these default to printout.txt for text output, and print‐
2611 out.pbm for graphics (PBM images are supported by most image viewers
2612 and converters). These names can be changed with the --textfile and
2613 --graphicsfile options from the command line or configuration file.
2614 While the ZX Printer can only output graphically, simulated text output
2615 is generated at the same time using a crude sort of OCR based on the
2616 current character set (a bit like using SCREEN$). There is currently no
2617 support for graphics when using the serial/parallel output, though any
2618 escape codes used will be `printed' faithfully. (!)
2619 By the way, it's not a good idea to modify the printout.pbm file out‐
2621 side of Fuse if you want to continue appending to it. The header needs
2622 to have a certain layout for Fuse to be able to continue appending to
2623 it correctly, and the file will be overwritten if it can't be appended
2624 to.
2625
2627 The ZXATASP and ZXCF interfaces are two peripherals designed by Sami
2628 Vehmaa which significantly extend the capabilities of the Spectrum.
2629 More details on both are available from Sami's homepage,
2630 http://user.tninet.se/~vjz762w/, but a brief overview is given here.
2631 The real ZXATASP comes with either 128K or 512K of RAM and the ability
2633 to connect an IDE hard disks and a CompactFlash card, while the ZXCF
2634 comes with 128K, 512K or 1024K of RAM and the ability to connect a Com‐
2635 pactFlash card. From an emulation point of view, the two interfaces are
2636 actually very similar as a CompactFlash card is logically just an IDE
2637 hard disk. Currently, Fuse's emulation is fixed at having 512K of RAM
2638 in the ZXATASP and 1024K in the ZXCF.
2639 To activate the ZXATASP, simply select the ZXATASP interface option
2641 from the Options, Peripherals, Disk... dialog. The state of the upload
2642 and write protect jumpers is then controlled by the ZXATASP upload and
2643 ZXATASP write protect options. Similarly, the ZXCF is controlled by the
2644 ZXCF interface and ZXCF upload options (the ZXCF write protect is soft‐
2645 ware controlled).
2646 If you're using either the ZXATASP or ZXCF, you almost certainly want
2648 to investigate ResiDOS, the operating system designed for use with the
2649 ZXATASP and ZXCF. ResiDOS provides facilities for using the extra RAM,
2650 accessing the mass storage devices and a task manager allowing virtu‐
2651 ally instant switching between programs on the Spectrum. See
2652 http://www.worldofspectrum.org/residos/ for more details.
2653
2655 The DivIDE is another IDE interface for the Spectrum, of which full
2656 details can be found at http://web.ar‐
2657 chive.org/web/20150302052256/http://baze.au.com/divide/. The interface
2658 can be activated via the DivIDE interface option from the Options,
2659 Peripherals, Disk... dialog, and the state of its write protect jumper
2660 controlled via the DivIDE write protect option. If you're going to be
2661 using the DivIDE, you'll probably want one of the firmwares available
2662 from the DivIDE homepage.
2663
2665 The DivMMC is a MMC interface for the Spectrum. Originally designed by
2666 Alessandro Dorigatti for the V6Z80P+ FPGA board as the fusion of DivIDE
2667 and ZXMMC+ interfaces, later assembled as an interface for real spec‐
2668 trums by Mario Prato. Currently there are variants with different RAM
2669 size, one/two memory cards slots, optional kempston jostick, etc.
2670 The interface can be activated via the DivMMC interface option from the
2672 Options, Peripherals, Disk... dialog, and the state of its EEPROM
2673 write protect jumper controlled via the DivMMC write protect option.
2674 If you're going to be using the DivMMC, you'll need to load the ESXDOS
2675 firmware at http://www.esxdos.org/ or use the ZX Spectrum +3e ROMs by
2676 Garry Lancaster.
2677 You'll also need a HDF image to store the contents of the memory card.
2679 There are several tools to create and manipulate this file format,
2680 e.g., hdfmonkey at https://github.com/gasman/hdfmonkey.
2681
2683 The Spectranet is an Ethernet network interface for the ZX Spectrum by
2684 Dylan Thomas. The interface can be activated via the Spectranet option
2685 on the Peripherals preferences dialog, and the state of its automatic
2686 page-in (disable) jumper controlled via the Spectranet disable option.
2687 If you're going to be using the Spectranet, you'll probably want one of
2688 the firmwares available from the Spectranet homepage (http://spec‐
2689 trum.alioth.net/doc/index.php) which is also where you can find more
2690 information on using the interface.
2691 Installing the Spectranet firmware on Fuse is slightly more complicated
2693 than on a real machine, mostly because Fuse's emulation doesn't support
2694 DHCP. These instructions are correct as of 2012-01-26 — if you're using
2695 a later firmware than this, things may have changed slightly.
2696 The first thing you will need to do is to obtain a copy of the Spec‐
2698 tranet installer as a .tap file (or similar). The installer is also
2699 available at the Spectranet site above.
2700 Once you have a copy of the installer, start Fuse and tick the Spec‐
2702 tranet option from the Options, Peripherals, General... dialog, and
2703 the state of its write protect jumper controlled via the Spectranet
2704 disable option. Once that's done, open the installer file (use the
2705 Media, Tape, Open... command rather than File, Open... to prevent
2706 autoloading) and enter the following commands from BASIC:
2707 CLEAR 26999
2709 LOAD "" CODE
2710 RANDOMIZE USR 27000
2711 The screen should turn blue and you'll see around 20 lines of message
2713 appearing as the firmware is installed, starting with “Erasing sector
2714 0” and finishing with “Restoring page B”, and you'll get the familiar
2715 0 OK, 0: 1 at the bottom of the screen.
2716 Now untick the Spectranet disable option from the Options, Peripherals,
2718 General... dialog and reset the Spectrum. You should see a very brief
2719 blue status screen, before the regular copyright screen appears with
2720 some Spectranet information at the top — there should be four status
2721 lines, starting with “Alioth Spectranet” and ending with the Spec‐
2722 tranet's IP address (which will be 255.255.255.255 at this stage).
2723 Now trigger an NMI (the Machine / NMI menu option) and you should get a
2725 white on blue Spectranet NMI menu with five options.
2726 Select [A] Configure network settings — this should lead you to another
2728 menu, which will scroll of the top of the screen; don't worry about
2729 this for now.
2730 You'll now need to set various options:
2732 [A] Enable/disable DHCP — select N
2734 [B] Change IP address — enter the IP address of the machine you are
2735 running Fuse on.
2736 [C] Change netmask — enter the appropriate netmask for the IP address
2737 you selected above. If that doesn't mean anything to you, try
2738 255.255.255.0
2739 [D] Change default gateway — enter the appropriate gateway address. If
2740 you don't know any better, enter the IP address of your router.
2741 [E] Change primary DNS — enter the address of your DNS server. If you
2742 don't know any better, use Google's public DNS server, 8.8.8.8.
2743 There is no need to change options [F] or [G], but do select:
2745 [H] Change hostname — enter a hostname for the Spectranet-enabled
2747 machine. It doesn't really matter what you enter here — it's mostly
2748 useful just to replace the junk default name so you can see what you've
2749 entered for the other settings.
2750 Your screen should now look something like this:
2752 Current configuration
2754 ───────────────────────────────────────
2755 Use DHCP : No
2756 IP address : 192.168.000.002
2757 Netmask : 255.255.255.000
2758 Default gateway : 192.168.000.001
2759 Primary DNS : 192.168.000.001
2760 Secondary DNS : 255.255.255.255
2761 Hardware address : FF:FF:FF:FF:FF:FF
2762 Hostname : fuse
2763 <menu options>
2764 If everything looks correct, select [I] Save changes and exit (you'll
2766 see a brief “Saving configuration...” message) followed by [E] Exit, at
2767 which point you'll be returned to BASIC.
2768 Now type the following commands:
2770 %cfgnew
2772 %cfgcommit
2773 Which will show the standard 0 OK, 0:1 at the bottom of the screen.
2775 Reset the Spectrum again and you'll see the same four line status dis‐
2777 play, but this time with your IP address on the last line.
2778 Congratulations! You have now installed the Spectranet firmware. To
2780 save having to go through all that every time you start Fuse, save a
2781 .szx snapshot at this point, and load that in every time you want to
2782 use the Spectranet.
2783
2785 The way you select a file (whether snapshot or tape file) depends on
2786 which UI you're using. So firstly, here's how to use the GTK+ file
2787 selector.
2788 The selector shows the directories and files in the current directory
2790 in two separate subwindows. If either list is too big to fit in the
2791 window, you can use the scrollbar to see the rest (by dragging the
2792 slider, for example), or you can use Shift–Tab (to move the keyboard
2793 focus to a subwindow) and use the cursor keys. To change directory,
2794 double-click it.
2795 To choose a file to load you can either double-click it, or click it
2797 then click Ok. Or click Cancel to abort.
2798 If you're using the keyboard, probably the easiest way to use the
2800 selector is to just ignore it and type in the name. This isn't as irk‐
2801 some as it sounds, since the filename input box has filename completion
2802 — type part of a directory or file name, then press Tab. It should
2803 complete it. If it was a directory, it moves to that directory; if the
2804 completion was ambiguous, it completes as much as possible, and narrows
2805 the filenames shown to those which match. You should press Enter when
2806 you've finished typing the filename, or Esc to abort.
2807 Now, if you're using the widget UI — the one using the Spectrum font —
2809 the selector works a bit differently. The files and directories are all
2810 listed in a single two-column-wide window (the directories are shown at
2811 the top, ending in `/') — the names may be truncated onscreen if
2812 they're too long to fit.
2813 To move the cursor, you can either use the cursor keys, or the Spectrum
2815 equivalents 5/6/7/8, or (similarly) h/j/k/l. For faster movement, the
2816 Page Up, Page Down, Home, and End keys are supported and do what you'd
2817 expect. To select a file or directory, press Enter. To abort, press
2818 Esc.
2819 With both selectors, do bear in mind that all files are shown, whether
2821 Fuse would be able to load them or not.
2822
2824 Firstly, note that the vast majority of this section applies only if
2825 you're using the GTK+ user interface; if you're using one of the widget
2826 user interfaces, you'll get a very basic monitor which shows the cur‐
2827 rent values of the registers and allows you to single step through exe‐
2828 cution or continue.
2829 If you are using the GTK+ user interface, Fuse features a moderately
2831 powerful, completely transparent monitor/debugger, which can be acti‐
2832 vated via the Machine, Debugger... menu option. A debugger window will
2833 appear, showing the current state of the emulated machine: the top-left
2834 `pane' shows the current state of the Z80 and the last bytes written to
2835 any emulated peripherals. The bottom-left pane lists any active break‐
2836 points. Moving right, the next pane shows where the Spectrum's 64K mem‐
2837 ory map (the `W?' and `C?' indicate whether each displayed chunk is
2838 writable or contended respectively). Fuse tracks the memory mapping of
2839 the overall address space in 2KB chunks but will summarise the mapped
2840 pages where they are part of the same page of the underlying memory
2841 source (e.g. 8KB page sizes in the Spectrum 128K and 4KB pages in the
2842 Timex clones' DOCK and EXROM banks).
2843 The next pane to the right has a disassembly, which by default starts
2845 at the current program counter, although this can be modified either by
2846 the `disassemble' command (see below) or by dragging the scrollbar next
2847 to it. The next pane shows the current stack, and the final pane any
2848 `events' which are due to occur and could affect emulation. Any of
2849 these panes can be removed by use of the View menu. Below the displays
2850 are an entry box for debugger commands, and five buttons for control‐
2851 ling the debugger:
2852 Evaluate
2854 Evaluate the command currently in the entry box.
2855 Single Step
2857 Run precisely one Z80 opcode and then stop emulation again.
2858 Continue
2860 Restart emulation, but leave the debugger window open. Note that
2861 the debugger window will not be updated while emulation is run‐
2862 ning.
2863 Break
2865 Stop emulation and return to the debugger.
2866 Close
2868 Close the debugger window and restart emulation.
2869 Double-clicking on an entry in the stack pane will cause emulation to
2871 run until the program counter reaches the value stored at that address,
2872 while double-clicking on an entry in the `events' pane will cause emu‐
2873 lation to run until that time is reached.
2874 The main power of the debugger is via the commands entered into the
2876 entry box, which are similar in nature (but definitely not identical to
2877 or as powerful as) to those in gdb(1). In general, the debugger is
2878 case-insensitive, and numbers will be interpreted as decimal, unless
2879 prefixed by either `0x' or `$' when they will be interpreted as hex.
2880 Each command can be abbreviated to the portion not in curly braces.
2881 ba{se} number
2883 Change the debugger window to displaying output in base number.
2884 Available values are 10 (decimal) or 16 (hex).
2885 br{eakpoint} [address] [if condition]
2887 Set a breakpoint to stop emulation and return to the debugger
2888 whenever an opcode is executed at address and condition evalu‐
2889 ates true. If address is omitted, it defaults to the current
2890 value of PC.
2891 br{eakpoint} p{ort} (re{ad}|w{rite}) port [if condition]
2893 Set a breakpoint to trigger whenever IO port port is read from
2894 or written to and condition evaluates true.
2895 br{eakpoint} (re{ad}|w{rite}) [address] [if condition]
2897 Set a breakpoint to trigger whenever memory location address is
2898 read from (other than via an opcode fetch) or written to and
2899 condition evaluates true. Address again defaults to the current
2900 value of PC if omitted.
2901 br{eakpoint} ti{me} time [if condition]
2903 Set a breakpoint to occur time tstates after the start of the
2904 every frame, assuming condition evaluates true (if one is
2905 given).
2906 br{eakpoint} ev{ent} area:detail [if condition]
2908 Set a breakpoint to occur when the event specified by
2909 area:detail occurs and condition evaluates to true. The events
2910 which can be caught are:
2911 beta128:page
2913 beta128:unpage
2914 The Beta 128 interface is paged into or out of memory
2915 respectively.
2916 didaktik80:page
2917 didaktik80:unpage
2918 The Didaktik 80 interface is paged into or out of memory
2919 respectively.
2920 disciple:page
2921 disciple:unpage
2922 The DISCiPLE interface is paged into or out of memory
2923 respectively.
2924 divide:page
2925 divide:unpage
2926 The DivIDE interface is paged into or out of memory
2927 respectively.
2928 divmmc:page
2929 divmmc:unpage
2930 The DivIDE interface is paged into or out of memory
2931 respectively.
2932 if1:page
2933 if1:unpage
2934 The Interface 1 shadow ROM is paged into or out of mem‐
2935 ory.
2936 multiface:page
2937 multiface:unpage
2938 The Multiface One/128/3 is paged into or out of memory
2939 respectively.
2940 opus:page
2941 opus:unpage
2942 The Opus Discovery is paged into or out of memory respec‐
2943 tively.
2944 plusd:page
2945 plusd:unpage
2946 The +D interface is paged into or out of memory respec‐
2947 tively.
2948 rzx:end
2949 An RZX recording finishes playing.
2950 speccyboot:page
2951 speccyboot:unpage
2952 The SpeccyBoot interface is paged into or out of memory.
2953 spectranet:page
2954 spectranet:unpage
2955 The Spectranet interface is paged into or out of memory.
2956 tape:play
2957 tape:stop
2958 The emulated tape starts or stops playing.
2959 zxatasp:page
2960 zxatasp:unpage
2961 The ZXATASP interface is paged into or out of memory.
2962 zxcf:page
2963 zxcf:unpage
2964 The ZXCF interface is paged into or out of memory.
2965 In all cases, the event can be specified as area:* to catch all
2967 events from that area.
2968 cl{ear} [address]
2970 Remove all breakpoints at address or the current value of PC if
2971 address is omitted. Port read/write breakpoints are unaffected.
2972 com{mmands} id <newline>
2974 <debugger command> <newline>
2975 <debugger command> <newline>
2976 ...
2977 end
2978 Set things such that the specified debugger commands will be
2979 automatically executed when breakpoint id is triggered. There is
2980 currently no user interface for entering multi-line debugger
2981 commands, so the only way to specify this command is on the com‐
2982 mand-line via the --debugger-command option.
2983 cond{ition} id [condition]
2985 Set breakpoint id to trigger only when condition is true, or
2986 unconditionally if condition is omitted.
2987 co{ntinue}
2989 Equivalent to the Continue button.
2990 del{ete} [id]
2992 Remove breakpoint id, or all breakpoints if id is omitted.
2993 di{sassemble} address
2995 Set the centre panel disassembly to begin at address.
2996 ex{it} [expression]
2998 Exit the emulator immediately, using the exit code resulting
2999 from the evaluation of expression, or 0 if expression is omit‐
3000 ted.
3001 fi{nish}
3003 Exit from the current CALL or equivalent. This isn't infallible:
3004 it works by setting a temporary breakpoint at the current con‐
3005 tents of the stack pointer, so will not function correctly if
3006 the code returns to some other point or plays with its stack in
3007 other ways. Also, setting this breakpoint doesn't disable other
3008 breakpoints, which may trigger before this one. In that case,
3009 the temporary breakpoint remains, and the `continue' command can
3010 be used to return to it.
3011 i{gnore} id count
3013 Do not trigger the next count times that breakpoint id would
3014 have triggered.
3015 n{ext}
3017 Step to the opcode following the current one. As with the `fin‐
3018 ish' command, this works by setting a temporary breakpoint at
3019 the next opcode, so is not infallible.
3020 o{ut} port value
3022 Write value to IO port port.
3023 pr{int} expression
3025 Print the value of expression to standard output.
3026 se{t} address value
3028 Poke value into memory at address.
3029 se{t} $variable value
3031 Set the value of the debugger variable variable to value.
3032 se{t} area:detail value
3034 Set the value of the system variable area:detail to value. The
3035 available system variables are listed below.
3036 s{tep}
3038 Equivalent to the Single Step button.
3039 t{breakpoint} [options]
3041 This is the same as the `breakpoint' command in its various
3042 forms, except that the breakpoint is temporary: it will trigger
3043 once and once only, and then be removed.
3044 Addresses can be specified in one of two forms: either an absolute
3046 addresses, specified by an integer in the range 0x0000 to 0xFFFF or as
3047 a `source:page:offset' combination, which refers to a location offset
3048 bytes into memory bank page, independent of where that bank is cur‐
3049 rently paged into memory. RAM and ROM pages are indicated, respec‐
3050 tively, by `RAM' and `ROM' sources (e.g. offset 0x1234 in ROM 1 is
3051 specified as `ROM:1:0x1234'). Other available sources are: `Betadisk',
3052 `Didaktik 80 RAM', `Didaktik 80 ROM', `DISCiPLE RAM', `DISCiPLE ROM',
3053 `DivIDE EPROM', `DivIDE RAM', `DivMMC EPROM', `DivMMC RAM', `If1',
3054 `If2', `Multiface RAM', `Multiface ROM', `Opus RAM', `Opus ROM', `PlusD
3055 RAM', `PlusD ROM', `SpeccyBoot', `Spectranet', `Timex Dock', `Timex
3056 EXROM', `uSource', `ZXATASP' and `ZXCF'. Please, note that spaces in
3057 memory sources should be escaped, e.g., `break Didak‐
3058 tik\ 80\ ROM:0:0x1234'. The 48K machines are treated as having a per‐
3059 manent mapping of page 5 at 0x4000, page 2 at 0x8000 and page 0 at
3060 0xC000; the 16K Spectrum is treated as having page 5 at 0x4000 and no
3061 page at 0x8000 and 0xC000.
3062 Anywhere the debugger is expecting a numeric value, except where it
3064 expects a breakpoint id, you can instead use a numeric expression,
3065 which uses a restricted version of C's syntax; exactly the same syntax
3066 is used for conditional breakpoints, with `0' being false and any other
3067 value being true. In numeric expressions, you can use integer constants
3068 (all calculations are done in integers), system variables, debugger
3069 variables, parentheses, the standard four numeric operations (`+', `-',
3070 `*' and `/'), the (non-)equality operators `==' and `!=', the compari‐
3071 son operators `>', `<', `>=' and `<=', bitwise and (`&'), or (`|') and
3072 exclusive or (`^') and logical and (`&&') and or (`||'). Square brack‐
3073 ets (`[' and `]') can be used to dereference a value; for example
3074 `[0x4000]' will give the value of the first byte of the screen.
3075 System variables are specified via an `area:detail' syntax. The avail‐
3077 able system variables are:
3078 ay:current
3080 The current AY-3-8912 register.
3081 divmmc:control
3082 The last byte written to DivMMC control port.
3083 spectrum:frames
3084 The frame count since reset. Note that this variable can only be
3085 read, not written to.
3086 tape:microphone
3087 The current level of the tape input connected to the `EAR' port.
3088 Note that this variable can only be read, not written to.
3089 ula:last
3090 The last byte written to the ULA. Note that this variable can
3091 only be read, not written to.
3092 ula:mem1ffd
3093 The last byte written to memory control port used by the ZX
3094 Spectrum +2A/3; normally addressed at 0x1ffd, hence the name.
3095 ula:mem7ffd
3096 The last byte written to primary memory control port used by the
3097 ZX Spectrum 128 and later; normally addressed at 0x7ffd, hence
3098 the name.
3099 ula:tstates
3100 The number of tstates since the last interrupt.
3101 z80: register name
3102 The value of the specified register. Both 8-bit registers and
3103 16-bit register pairs are supported. The MEMPTR / WZ hidden reg‐
3104 ister is also supported. The (presumable) Q hidden register is
3105 also supported.
3106 z80:im
3107 The current interrupt mode of the Z80.
3108 z80:iff1
3109 z80:iff2
3110 1 if the specified interrupt flip-flop is currently set, or 0 if
3111 it is not set.
3112
3114 The `poke finder' is a tool which is designed to make the task of find‐
3115 ing (infinite lives etc.) pokes for games a bit easier: it is similar
3116 to the `Lifeguard' utility which was available for use with the Multi‐
3117 face. It works by maintaining a list of locations in which the current
3118 number of lives (etc.) may be stored, and having the ability to remove
3119 from that list any locations which don't contain a specified value.
3120 The poke finder dialog contains an entry box for specifying the value
3122 to be searched for, a count of the current number of possible locations
3123 and, if there are less than 20 possible locations, a list of the possi‐
3124 ble locations (in `page:offset' format). The five buttons act as fol‐
3125 lows:
3126 Incremented
3128 Remove from the list of possible locations all addresses which
3129 have not been incremented since the last search.
3130 Decremented
3132 Remove from the list of possible locations all addresses which
3133 have not been decremented since the last search.
3134 Search
3136 Remove from the list of possible locations all addresses which
3137 do not contain the value specified in the `Search for' field.
3138 Reset
3140 Reset the poke finder so that all locations are considered pos‐
3141 sible.
3142 Close
3144 Close the dialog. Note that this does not reset the current
3145 state of the poke finder.
3146 Double-clicking on an entry in the list of possible locations will
3148 cause a breakpoint to be set to trigger whenever that location is writ‐
3149 ten to.
3150 An example of how to use this may make things a bit clearer. We'll use
3152 the 128K version of Gryzor. Load the game, define keys to suit and
3153 start playing. Immediately pause the game and bring up the poke finder
3154 dialog. We note that we currently have 6 lives, so enter `6' into the
3155 `Search for' field and click `Search'. This reduces the number of pos‐
3156 sible locations to around 931 (you may get a slightly different number
3157 depending on exactly when you paused the game). Play along a bit and
3158 then (deliberately) lose a life. Pause the game again. As we now have
3159 5 lives, replace the `6' in the `Search for' field with a `5' and click
3160 `Search' again. This then reduces the list of possible locations to
3161 just one: page 2, offset 0x00BC. This is the only location in memory
3162 which stored `6' when we had 6 lives and `5' when we had 5 lives, so
3163 its pretty likely that this is where the lives count is stored. Double-
3164 clicking on the `2:0x00BC' entry in the dialog will set the appropriate
3165 breakpoint (you may wish to open the debugger at this point to confirm
3166 this). Play along a bit more. When you next lose a life, emulation is
3167 stopped with PC at 0x91CD. Scrolling up a few addresses in the debug‐
3168 ger's disassembly pane shows a value was loaded from 0x80BC (our hypo‐
3169 thetical lives counter), decremented and then stored again to 0x80BC,
3170 which looks very much like the code to reduce the number of lives. We
3171 can now use the debugger to replace the decrement with a NOP (`set
3172 0x91c9 0'), and playing the game some more after this reveals that this
3173 has worked and we now have infinite lives.
3174
3176 Fuse supports multiface POKEs, allowing to modify specific memory
3177 addresses in order to cheat (infinite lives, infinite ammo, etc.).
3178 The `poke memory' dialog contains a list of recently loaded POKEs and
3180 some entry boxes for adding custom POKEs:
3181 Bank
3183 Sets the 128K memory bank (values `0' to `7') or the current
3184 memory mapping (value `8' or blank).
3185 Address
3187 Memory address to modify. Values in range 16384 to 65535 for 48K
3188 memory mode or 0 to 65535 for 128K memory banks. GTK+ UI also
3189 accepts hex addresses.
3190 Value
3192 New value for the former address, in range 0 to 255. Value 256
3193 means “Prompt to the user later”.
3194 It is possible to load POKEs from an external file using the File,
3196 Open... menu option or the drag-and-drop functionality in the GTK+ and
3197 Win32 UIs. After loading a snapshot or tape, Fuse will try to automat‐
3198 ically locate a POK file with the same file name. This means that if we
3199 open `GAME.TAP', then Fuse will try to open `GAME.POK' and
3200 `POKES/GAME.POK'. See http://www.worldofspectrum.org/POKformat.txt for
3201 more details about this file format.
3202 POKEs loaded in the list can be activated or deactivated as the user
3204 wants and will remain in memory until a machine reset.
3205
3207 In general, disk images for the +3 Spectrum are thought of as being in
3208 DSK format. However, this is actually a slight oversimplification;
3209 there are in fact two similar, but not identical, DSK formats. (The
3210 difference can be seen by doing `head -1 dskfile': one format will
3211 start `MV - CPCEMU' and the other will start `EXTENDED').
3212 Fuse supports both the `CPCEMU' and `EXTENDED' formats.
3214
3216 Fuse supports Betadisk emulation in its Pentagon and Scorpion emula‐
3217 tion, and also under 48K, TC2048, 128K and +2 (but not +2A) emulation
3218 if the Beta 128 interface option from the Options, Peripherals, Disk...
3219 dialog is enabled. When that option is used in 48K or TC2048 emulation
3220 the Beta 128 auto-boot in 48K machines option additionally controls
3221 whether the machine boots directly into the TR-DOS system. See the DISK
3222 FILE FORMATS section for more details on supported disk file formats.
3223
3225 By default, Fuse emulates the Opus Discovery interface with the
3226 optional 2k RAM expansion and a second 40 track single sided disk
3227 drive. See the DISK FILE FORMATS section for more details on supported
3228 disk file formats. The Opus Discovery's printer port is also emulated
3229 for output only. (See the PRINTER EMULATION section for more details.)
3230 The Opus Discovery may only be used with 16K, 48K, 128K, TC2048 and +2
3231 (not +2A) emulation. To access disks, use the same syntax as Inter‐
3232 face 1 and Microdrives.
3233
3235 Fuse supports emulating the +D disk and printer interface. See the DISK
3236 FILE FORMATS section for more details on supported disk file formats.
3237 The +D's printer port is emulated. (See the PRINTER EMULATION section
3238 for more details.) The +D may only be used with 48K, 128K and +2 (not
3239 +2A) emulation. To access disks, you will first need to load G+DOS, by
3240 inserting a disk containing the DOS file (+SYS) and entering “RUN”.
3241 Once DOS is loaded, you can load to/from +D disks by prefixing file‐
3242 names with `dn' where `n' is the number of the drive in use. For exam‐
3243 ple, `LOAD d1"myfile"' would load the file named `myfile' from the emu‐
3244 lated drive 1. Microdrive syntax may also be used.
3245 To save a snapshot, choose the Machine, NMI menu option, and then press
3247 `4' to save a 48K snapshot, or `5' to save a 128K snapshot. When sav‐
3248 ing a 128K snapshot, you must then press Y or N to indicate whether the
3249 screen changed while saving the snapshot, to finish saving. You can
3250 also choose `3' to save a screenshot to disk. Holding Caps Shift
3251 together with any of these options will cause the +D to save to the
3252 `other' drive to the one used last.
3253 Options `1' and `2' allow screenshots to be printed (in monochrome, in
3255 normal and large formats respectively) if printer emulation is enabled.
3256 For saving and loading of snapshots, and saving of screenshots to disk,
3257 G+DOS must be loaded first, but printing of screenshots can be per‐
3258 formed without loading G+DOS.
3259 Finally, `X' will return from the NMI menu.
3261
3263 Fuse supports Didaktik 80 (and Didaktik 40) emulation. It emulates the
3264 original version of the Didaktik 80, running MDOS 1 and with a WD2797
3265 floppy controller. See the DISK FILE FORMATS section for more details
3266 on supported disk file formats. The Didaktik 80 may only be used with
3267 16K, 48K and TC2048 emulation. To press the Didaktik 80's `SNAP' but‐
3268 ton, choose the Machine, Didaktik SNAP menu option.
3269
3271 Fuse supports emulating the DISCiPLE disk and printer interface,
3272 although it does not currently support emulation of the Sinclair Net‐
3273 work, or support emulation of a DISCiPLE attached to a 128K machine.
3274 See the DISK FILE FORMATS section for more details on supported disk
3275 file formats, which are the same as for +D emulation as described
3276 above. The DISCiPLE's printer port is emulated. (See the PRINTER EMULA‐
3277 TION section for more details.) The DISCiPLE may only be used with 48K
3278 emulation at present. To access disks, you will first need to load
3279 GDOS, by inserting a disk containing the DOS file (SYS) and entering
3280 “RUN”. Once DOS is loaded, you can load to/from DISCiPLE disks by pre‐
3281 fixing filenames with `dn' where `n' is the number of the drive in use.
3282 For example, `LOAD d1"myfile"' would load the file named `myfile' from
3283 the emulated drive 1. Microdrive syntax may also be used.
3284 Snapshots can be saved in a similar manner to that of the +D as
3286 described above, but note that GDOS on the DISCiPLE contains a bug
3287 which causes corruption as soon as the NMI button is pressed, affecting
3288 saving of snapshots, and also loading of snapshots that were originally
3289 saved with a +D or SAM Coupé. This will cause corruption even when a
3290 screenshot is printed, or if the menu is never even entered in the
3291 first place (due to Caps Shift not being pressed down, as is required
3292 for the DISCiPLE), provided that GDOS is loaded. This bug is not
3293 present in G+DOS on the +D. (Note: this was caused by saving/restoring
3294 the AF register twice in the NMI handler, where both AF and the AF'
3295 shadow register should have been saved/restored.)
3296 The NMI button works slightly differently on the DISCiPLE than on the
3298 +D. Caps Shift must be held down whilst pressing the NMI button, and
3299 there is no `X' option to exit the menu. Also, printing of screenshots
3300 requires GDOS to be loaded. Depending on the UI that you're using,
3301 holding down Caps Shift whilst choosing the Machine, NMI menu option
3302 may be slightly tricky, or even impossible. For the GTK+ UI, ensure
3303 that the Shift key is held before entering on the Machine menu. For
3304 the widget UI, it does not seem possible to perform this action.
3305
3307 Fuse supports several disk image formats in its +D, Didaktik, DISCiPLE
3308 and Beta 128 emulation.
3309 For reading:
3311 .UDI
3313 Ultra Disk Image; for specification please see
3314 http://faqwiki.zxnet.co.uk/wiki/UDI_format or
3315 http://zxmak.chat.ru/docs.htm
3316 This is the only image format which can store all the relevant
3318 information of the recorded data on a magnetic disk, so it can
3319 be used for any non standard disk format. Fuse can read all
3320 extended track types too (mixed FM/MFM, or tracks with `WEAK'
3321 data or even compressed tracks too).
3322 .FDI
3324 UKV Spectrum Debugger disk image format.
3325 .MGT .IMG
3327 DISCiPLE/+D file formats.
3328 .SAD
3330 For compatibility with SAM Coupé disk images using these for‐
3331 mats. Note that SAM Coupé `.DSK' images share the same format
3332 as `.MGT'.
3333 .D80 .D40
3335 Didaktik 80 and Didaktik 40 file formats.
3336 .TRD
3338 TR-DOS disk image. TRD and SCL sectors are loaded interleaved,
3339 therefore you might experience problems with TR-DOS ROMs that
3340 use the turbo format (sequential sectors); for detailed informa‐
3341 tion please see http://web.ar‐
3342 chive.org/web/20070808150548/http://www.ram‐
3343 soft.bbk.org/tech/tr-info.zip
3344 .SCL
3346 A simple archive format for TR-DOS disk files. For specification
3347 please see http://www.zx-modules.de/fileformats/sclformat.html
3348 .TD0
3350 Teledisk image format; Fuse supports only files which do not use
3351 the “Advanced Compression” option. Detailed description found in
3352 http://www.classiccmp.org/dunfield/img54306/td0notes.txt and
3353 https://web.ar‐
3354 chive.org/web/20130116072335/http://www.fpns.net/willy/wteledsk.htm
3355 .DSK
3357 CPC disk image format; Fuse supports the plain old and the new
3358 extended CPC format too. Further information please see the THE
3359 .DSK FORMAT section and the CPCEMU manual section 7.7.1
3360 http://www.cpc-emu.org/linux/cpcemu_e.txt or the
3361 http://www.cpctech.org.uk/docs/extdsk.html
3362 .OPD .OPU
3364 Opus Discovery file formats.
3365 Fuse supports most of the above formats for writing: .UDI .FDI .MGT
3367 .IMG .SAD .D80 .D40 .TRD .SCL .OPD .OPU .DSK (only the old CPC format).
3368 You can save disk images with any output format, just select the appro‐
3370 priate extension. (e.g. `elite3.udi' to save as an UDI file). If the
3371 appropriate libraries were available when libspectrum(3) was compiled,
3372 than Fuse will try to create UDI images with compressed tracks to save
3373 disk space. There is a .LOG `image' format for debugging purpose. This
3374 is a plain text file that contains three dumps of the loaded disk image
3375 at different details. Not all image formats can store all disk images.
3376 You cannot save a disk image with an inappropriate format that loses
3377 some information (e.g. variable track length or sector length).
3378
3380 Some copy protections have what is described as `weak/random' data.
3381 Each time the sector is read one or more bytes will change, the value
3382 may be random between consecutive reads of the same sector. Two disk
3383 image formats (Extended DSK and UDI) can store this type of data. Fuse
3384 can read and use weak sector data from EDSK and UDI files when present,
3385 and can save back weak sector data to UDI image format.
3386
3388 Fuse can save movies with sound in a specific file format (FMF). This
3389 recording is very fast, and has a moderate size, but you need to use
3390 the fmfconv(1) program in fuse-utils(1) to convert into regular video
3391 and/or audio files. The --movie-compr option allows you to set the
3392 compression level to None, Lossless or High. If zlib(3) is not avail‐
3393 able, only None is valid. The default when Zlib is available is Loss‐
3394 less. Recording a movie may slow down emulation, if you experience
3395 performance problems, you can try to set compression to None.
3396 Fuse records every displayed frame, so by default the recorded file has
3398 about 50 video frame per second. A standard video has about 24–30/s
3399 framerate, so if you set Options/General/Frame rate 1:n or the equiva‐
3400 lent --rate command line option to 2 than recording frame rate reduces
3401 about 25/s. The exact frame rate depends on the Z80 clock frequency
3402 which varies depending on the specific emulated machine.
3403 Note: You can see all of the “gfx” effects only if the Fuse frame rate
3405 option is set to 1, but in most cases you can safely use 2. Also, movie
3406 recording stops if the emulated machine is changed.
3407 The recorded sound sampling rate and the channel number is equal with
3409 the Fuse generated sound sampling rate (44100 Hz by default) and chan‐
3410 nel number (mono by default). The common sampling frequencies in stan‐
3411 dard video files are 44100 Hz and 48000 Hz. If you use --sound-freq
3412 command line option you can change the frequency.
3413 You can record stereo sound if you use AY stereo separation or the
3415 equivalent --separation command line switch.
3416 You can use fmfconv(1) to convert recorded movie file into a standard
3418 video file.
3419 Examples
3421 fuse --movie-start output.fmf --rate 2 --sound-freq 44100 --separation
3423 ACB
3424 start video recording about 25/s video frame rate and 44100 Hz sampling
3426 frequency stereo sound default compression level.
3427
3429 Assuming the appropriate libraries were available when libspectrum(3)
3430 was compiled, snapshots, tape images, dock cartridges and input record‐
3431 ing files (RZX) can be read from files compressed with bzip2(3),
3432 gzip(3) or zip(3) just as if they were uncompressed. In the zip case,
3433 only the first supported file found inside the archive is loaded.
3434 There is currently no support for reading compressed +3, DISCiPLE/+D or
3435 Beta disk images.
3436
3438 Selecting a startup filter doesn't work properly with user interfaces
3439 other than SDL, Win32 and GTK+.
3440 Changing virtual consoles when using SVGAlib for joystick support
3442 causes Fuse to exit. If this is a problem, compile Fuse with the
3443 `--disable-ui-joystick' option.
3444 The poke finder can't search outside `normal' RAM.
3446 The libao file output devices not work properly with the GTK+ UI. No
3448 error reporting, but the created file does not contain any sound data.
3449 If you use a `weak' machine alsa09 makes a lot of clicks and pops and
3450 will output `ALSA: underrun, at least 0ms.' error messages.
3451
3453 ~/.fuserc
3454
3456 bzip2(3), fmfconv(1), fuse-utils(1), gzip(3), libspectrum(3),
3457 ogg123(1), xspect(1), xzx(1), zip(3).
3458 The comp.sys.sinclair Spectrum FAQ, at
3460 http://www.worldofspectrum.org/faq/index.html.
3461
3463 Philip Kendall (philip-fuse@shadowmagic.org.uk).
3464 Matan Ziv-Av wrote the SVGAlib and framebuffer UIs, the glib replace‐
3466 ment code, and did some work on the OSS-specific sound code and the
3467 original widget UI code.
3468 Russell Marks wrote the sound emulation and OSS-specific sound code,
3470 the joystick emulation, some of the printer code, and the original ver‐
3471 sion of this man page.
3472 John Elliott's lib765 and libdsk libraries were used for the original
3474 +3 disk and disk image support.
3475 Ian Collier wrote the ZX Printer emulation (for xz80).
3477 Darren Salt wrote the original versions of the code for +3 emulation,
3479 SLT support, MITSHM support (for the Xlib UI), TZX raw data blocks, RZX
3480 embedded snapshots and compression, the Kempston mouse emulation and
3481 made many improvements to the widget code.
3482 Alexander Yurchenko wrote the OpenBSD/Solaris-specific sound code.
3484 Fredrick Meunier wrote the TC2048, TS2068, Pentagon and Spectrum SE
3486 support, the CoreAudio sound code, as well as maintaining the OS X port
3487 and importing the graphics filter code.
3488 Ludvig Strigeus and The ScummVM project wrote the original graphics
3490 filter code.
3491 Dmitry Sanarin wrote the original Beta disk interface emulation (for
3493 Glukalka).
3494 Witold Filipczyk wrote the TC2068 support.
3496 Matthew Westcott wrote the AY logging code and the DivIDE emulation.
3498 Marek Januszewski wrote various bits of code to make Fuse work under
3500 Win32, including the DirectDraw user interface.
3501 Sergio Baldoví made many improvements to the Win32 UI.
3503 Stuart Brady wrote the DISCiPLE and +D emulation, Scorpion emulation
3505 and the HP-UX sound code.
3506 Garry Lancaster wrote the 8-bit IDE, ZXATASP and ZXCF interface emula‐
3508 tions.
3509 Gergely Szasz wrote the Interface 1, Microdrive emulation and Didak‐
3511 tik 80 emulation, the PAL TV scalers, the TV 3x scaler, the movie log‐
3512 ging code, the ALSA and libao sound code, the µPD765 disk controller
3513 used in the +3 and made many improvements to the widget code.
3514 Michael D Wynne wrote the original Opus disk interface emulation (for
3516 EightyOne).
3517 Patrik Persson wrote the SpeccyBoot emulation.
3519Version 1.5.7 9th December, 2018 fuse(1)