This FAQ is divided in several sections:


Accessibility
-------------

Q: How can I run the emulator with text to speech facilities?
A: Run the emulator specifying a text to speech program (with path) like the festival scripts or mac os say script, for example:

./zesarux BSLEEZE1.TAP --enableprintchartrap --textspeechprogram speech_filters/festival_filter.sh --linewidth 100 --linewidthwaitspace 

Or, in Windows:
zesarux BSLEEZE1.TAP --enableprintchartrap --textspeechprogram speech_filters\win_balabolka.bat --linewidth 100 --linewidthwaitspace

Note: In Windows version, when you specify command line settings, the text console remains open. So speech programs start very fast.
If you don't set command line settings, speech programs start slower.

You can also set these settings in the menu, just go to Settings-> Accessibility


You can find some different speech scripts on folder speech_filters. 
For Mac OS X, you can find macos_say_filter.sh on folder app/Contents/Resources/speech_filters/

You may also want to specify the --textspeechmenu option, to activate speech also on the menu. To open the menu press the F5 key (or write the word "menu" on stdout driver).


Q: How can I stop the current speech?
A: With menu open, press ESC. With menu closed, any key stops the current speech.


Q: Speech works well, but sometimes, specially with small phrases, they are not send until some seconds or when more text appears on screen.
A: Pressing Enter forces sending the last words to speech system. Also try to adjust some parameters:
-Text to Speech: Timeout no enter (or --textspeechtimeout <seconds> on the the command line. The default value for <seconds> is 0.).
-Print Char traps: Line width (or --linewidth <characters> in the command line)
-Print Char traps: Line width wait space (or --linewidthwaitspace in the command line)


Q: Some text adventures can be played with the speech filters, but some other text adventures seem to send nothing to speech.
A: By default, if you enable "trap print" on ZEsarUX, it only traps standard rom calls. I mean, when a program uses standard rom calls to print text,
this text will be captured by the emulator. But if this game uses non standard rom calls, it won't be captured nor sent to speech.
ZEsarUX has some settings to get this; you can write manually the memory address where the game calls to print text (parameter second trap address, for advanced users); even some games are detected by the emulator and get filled this second trap address parameter automatically.
If previous does not work, or you are not an advanced user, you can enable "second trap detection" and set "Detect routine" to "Auto&all" (or you can also specify --automaticdetectchar in the command line) and the 
emulator will try to find the best solution.


Q: I'm using text to speech. When I press a key on the menu (or ESC with menu closed) the next speech items are not heard, but the current speech
item is not stopped. How can I stop the current item also?
A: Use Setting Text Speech Stop program (on menu or on command line: --textspeechstopprogram)


Q: When I set the speech program on Windows, it returns me an error: "Full path to Text to Speech program ... has spaces. It won't work on Windows."
A: Yes, it's a limitation on the Windows version of the emulator. The speech program and the stop speech program can not be located in a full path 
with spaces. It won't work if you set a relative path, because the emulator will complete and convert it to a full path. 
The solution is to move the Speech program and the Stop speech program to a path without spaces


Q: All these speech programs included in the emulator are indeed speech synthesis programs, not screen readers. Can I use screen readers with ZEsarUX?
A: Yes. There is a speech script which can be specified with --textspeechprogram ; See: http://github.com/sukiletxe/zesarux-ao2


Q: How can I create my own speech script?
A: Windows scripts receive on parameter %1 a file containing the text to send to speech, and on parameter %2 a temporal file that must be deleted
just at the end of the script (this temporal file indicates ZEsarUX when the script has finished).
Rest of operating systems (Linux, Mac, Raspberry and other Unix systems) receive the text to send to speech from standard input.
See folder speech_filters for examples


Q: Is there any audio guide to know how to enable Accesibility on ZEsarUX?
A: Yes. Download audio file:
https://www.dropbox.com/s/0ihotq5f2w3spqb/zesarux%20demo%20en.mp3?dl=1

Notice that it was recorded without enabling "Text Speech Stop program"


Q: Is there any Spanish quick guide to know how to enable Accesibility on ZEsarUX?
A: Yes, see file extras/docs/accesibilidad_instrucciones.txt 


----------------------------------------------------------------------------


Storage
-------

Q: How can I use ZXMMC emulation?
A: Run alternate ROM alternaterom_plus3e_mmcen3eE.rom with machine type Spectrum +2A. Of course you have first to select MMC file, enable MMC emulation,  and enable ZXMMC on the menu


Q: How can I use DIVMMC emulation?
A: The emulator uses by default esxdos 0.8.5 firmware (file esxmmc085.rom). It also needs a filesystem for the common esxdos files.
So, first select MMC file, the emulator comes with two mmc images for esxdos:
media/disk_images/divmmcesx085.mmc : for esxdos 0.8.5
media/disk_images/zxuno.mmc : for esxdos 0.8.6 beta (use with ZX-Uno)
Then enable MMC emulation,  and enable DIVMMC on the menu. Then reset the machine (and press space while booting if necessary)


Q: Using MMC cards bigger than 1 GB makes the emulator slow and almost hangs it
A: The emulator needs to assign as much RAM as the MMC card size. So working with a 2 GB MMC card needs 2 GB of RAM


Q: How can I use ZXpand emulation?
A: ZXpand emulation does not use a mmc/sd emulation, like ZXMMC/DIVMMC. Instead it uses files and folders stored in your computer.
You must enable ZXpand when you are in ZX-81 machine mode, and set the root directory for emulation (it uses current directory by default).
ZXpand root directory will be the root directory for ZXpand interface. Only files or folders with maximum 8 characters for name and 3 for extension will be shown. They are always shown on uppercase. Folders which are not uppercase, are shown but can not be accessed.


Q: How can I use DIVIDE emulation?
A: The emulator uses by default esxdos 0.8.5 firmware (file esxide085.rom). It also needs a filesystem for the common esxdos files.
So, first select IDE file, the emulator comes with one ide image for esxdos:
media/disk_images/divideesx085.ide : for esxdos 0.8.5
Then enable IDE emulation,  and enable DIVIDE on the menu. Then reset the machine (and press space while booting if necessary)


Q: What are file formats with extensions .mmc and .ide?
A: They are both the same, both are dumps of mmc or ide cards. I use different extensions to distinguish between mmc images and ide images.
Besides using esxdos or other divide/divmmc firmware, you can also access those file image cards from Linux, Mac OS X, or Windows:
-Linux: you can use command "mount" with option -o loop to mount these images. It file image has a partition, you must first use losetup utility
-Mac OS X: change extension to .img and you can mount it using Finder. You should unmount it and change the extension back to .mmc or .ide for ZEsarUX 
to list it in File Selector
-Windows: Windows doesn't have native support for mounting file images. You may use ImDisk:
http://www.ltr-data.se/opencode.html/#ImDisk
Or find another program to access disk images

Q: What is file format with extension .mmcide?
A: A file with extension .mmcide is generated by expanding a hdf file, which can have a MMC or IDE raw image. So, a .mmcide is a file with .mmc or .ide extension, both are valid


Q: Where are located the mmc and ide files? Some examples refer to them but I can't found them. Even more, previous versions of ZEsarUX included them
A: Media folder has been separated from the emulator main distributed file. You have to download the extra-media package


Q: I want to use dandanator but the emulator is closed when I enable it. I'm using Mac OS X
A: Seems some versions of Mac OSX closes the emulator when enabling dandanator. It seems related to the real video setting, so disabling real video (and
also disabling auto-enable real video) solves it. You may also hear some audio noise on the dandanator menu. I haven't found a definitive solution for this


----------------------------------------------------------------------------


Audio Drivers
-------------

Q: Audio has much latency using SDL audio driver. This audio is used on Linux/Unix and Windows. What can I do to reduce latency?
A: Try setting a lower value for --sdlsamplesize parameter


Q: Audio does not sound well on Raspberry pi.
A: Try using sdl audio driver.



----------------------------------------------------------------------------


Video Drivers
-------------


Q: There are a lot of video drivers. What is the difference between them?
A: There are three kind of video drivers:

1) Complete video drivers. They show a graphical window like the emulated machine:
-XWindows: X11 Driver. Can run on Unix systems
-SDL: SDL Driver. Can run on Unix systems and Windows (Mingw)
-Cocoa: Cocoa Driver. Used on Mac OS X
-FBdev: Framebuffer driver. Used on Linux

2) Mixed graphical/text drivers. They are text drivers but simulate a graphical window using text:
-AA. Ascii-Art video driver. Black & White text. Can run any support that has the library
-Caca: Cacalib video driver. Like AA but with colours. Can run any support that has the library

3) Text only drivers:
-Curses: Text driver with colours. Can read keyboard. Can run on Unix systems
-Stdout: Basic text printing and text-graphic simulation. Can trap character routines and speech capabilities. Can read keyboard. Can run on Unix systems
-Simpletext: Like stdout but can not read keyboard, can not trap character routines and does not have speech capabilities. This driver is intended to work on any system, without any additional library.


Q: I have put ZEsarUX on fullscreen but it does not fill the whole screen and/or does not have normal proportions
A: The fullscreen feature is experimental and it depends on the video driver, operating system and window manager. So there are some cases which works perfect and some which does not. So if this is your case, where the fullscreen is not working, please be patient and wait for future fixes (and use window mode instead of full screen).

----------------------------------------------------------------------------


Debugging
---------

Q: What is ZEsarUX remote command protocol?
A: ZEsarUX remote command protocol (or ZRCP) is a kind of API you can connect to ZEsarUX using a network tcp port. You can connect to it using
a telnet client, or maybe you can create a external frontend (maybe an IDE) that connects remotely to ZEsarUX and interacts with it.
It's disabled by default, you may enable it from Settings->Debug or from command line with --enable-remoteprotocol. The default port is 10000.
It's supported on all emulator versions, but on Windows it's only supported on the ZEsarUX-pthreads version

There are two good examples which use ZRCP:
1)
https://github.com/maziac/z80-debug
This plugin enables VSCode to debug ZEsarUX by using ZRCP
Please read the documentation on its web site to know how it works

2)
https://github.com/Tenebrous/vscode-zx-debugger
This plugin enables VSCode to debug ZEsarUX by using ZRCP

To install it:
Open VSCode, go to "Extensions" and find "ZX Debugger extension" from user Tenebrous
Install it
-open a project/folder in VSCode
-go to debug -> add configuration. Add zx-debugger
-and then go to debug menu-start debugging

Note: you will need mono/.net libraries


Q: What is "Memory zone"?
A: Memory zone is a concept used on some debug menu items, that allows to read different zones of memory, like rom, ram, divmmc ram, zxuno flash, etc.
Usually you can change the current memory zone by pressing "Z" on a debug menu.
There is even a "File memory zone", that allows you to read a file (up to 16 MB) and use the debug menus with it. To load a file in that zone, you should open the File utilities menu, select a file, and press key F (Shift-f), which means "File memory zone"


Q: When a ZEsarUX kernel panic is generated, I can see on the console the cpu registers and after that, a list of pointer calls but no call names. How can I see the emulator call names?
A: Just set the following compilation settings:
export CFLAGS="-g -rdynamic"
export LDFLAGS="-g -rdynamic"

Before ./configure, then ./configure (with your desired settings) ; make clean ; make
Then, when a ZEsarUX kernel panic is generated, you will see the call names on the backtrace. This is only valid on Linux or Mac (and Mac seems to enable these compilation settings by default)

----------------------------------------------------------------------------


Windows
-------

Q: Every time the speech program is run, a new window console opens. I'm using Windows.
A: You have two options to solve it:
1) Open the emulator from Windows console (cmd) and pass at least one parameter, or the --nodisableconsole parameter
2) If you open the emulator by double clicking on the emulator, set the parameter --nodisableconsole on .zesaruxrc configuration file


Q: How can I select files from other drives?
A: On file selector window, press shift+D to select another drive.
You can also switch to File name section (pressing TAB twice) and write letter number and ':', for example: C:
Remember that : appears pressing symbol shift (Ctrl or Alt)+letter Z


Q: I enabled the ZEsarUX remote command protocol, used a telnet client to client, but I only see the Welcome message and I can not type anything
A: Try disabling Windows firewall


Q: I hear some audio "clicking" when no sound is being generated from the emulated machine
A: If you hear those annoying sounds, for example, in the copyright message of the Spectrum 48kb, without pressing any key, I'm sorry that problem doesn't have fix yet. The same audio libraries I use (SDL) works perfect on Linux or Mac, but not on Windows. Seems there's some kind of problem with Mingw+SDL+Windows and it doesn't happen always, it also depends on your sound card and the driver. You may reduce a bit this effect by enabling the Silence detector on Audio settings. More details:
After spending two days testing the Windows audio clicking issue I can confirm:
-It has nothing to do with my sdl audio module. The same is used in Mac and Linux and they don't have the same problem
-Tested by filling the audio buffer with fixed value and the clicking also appears. Seems the clicking happens when a sample value of 0 "appears" in the final hardware buffer. If I fill the audio buffer with 0, no change is produced in the hardware buffer and you don't hear any clicking. If you fill the buffer with something else different than 0, you may hear a clicking
-There's no difference on enabling real audio, ay audio chip, etc. So as I said, I can confirm there's not a bug in my module
-My Windows development machine is Virtual box. The default virtual audio card is a Intel HD. That has a lot of clicking. I changed it to a AC97 virtual card and the clicking has gone in the 90% of cases
-Seems there's some kind of issue with MinGW+SDL+Audio driver. With the same test, sometimes the clicking appear and some others don't. (With ac97 card)
-As some of you had made tests with real windows machines and you don't have clicking, I can be sure, again, it's not a bug in my software
-It seems also the audio module is sensible to O.S. multitask. I mean, if you change to another Windows task and leave ZEsarUX in the background, some clicking may appear. That doesn't happen in other operating systems. That confirms me, again, Windows is not my preferred operating system ;)
-I tried changing the audio sdl module to another one, programming a Direct Sound native windows module. But I haven't found any examples to do that on my MinGW environment. 
-So, until I couldn't change the audio module to something different (DirectSound or SDL2-which already have tested) some of you will have clicking on Windows. It will depend on your audio card and audio driver
-That clicking issue is not related with clicks at startup or looping click in tbblue browser. These two others are probably bugs in my code




----------------------------------------------------------------------------


ZX-Spectrum
-----------

Q: My Spectrum game does rainbow/hi-colour effects but the emulator does not show them.
A: Enable Real Video Setting. Real Video is a feature that uses a bit more cpu from your machine but displays the emulated machine as it should. Same reason as ZX-80/ZX-81


----------------------------------------------------------------------------


ZX-80 & ZX-81
-------------

Q: My ZX80 or ZX81 game uses hi-res resolution but the emulator does not show the display well.
A: Enable Real Video Setting. Real Video is a feature that uses a bit more cpu from your machine but displays the emulated machine as it should. Same reason as ZX Spectrum. If you enabled real video and it does not show any image, try also enabling WRX.


Q: I tried to run the ZX81 Sponzy ROM on the emulator but it doesn't work
A: You will probably have set "Custom machine" from the menu. But the sponzy rom is 16KB long and the emulator loads only 8KB rom by default.
To be able to use this rom, you must enable RAM on addresses 2000h-3fffh. So:

1) Set normal ZX81 machine. Go to menu hardware->"ZX80/81 8K RAM in 2000H" and enable it
2) Machine Selection->Custom machine. Select sponzy rom and machine type ZX81. It will load only the first 8 KB of ROM. It will hang the ZX81 and 
the display will show "trash", also the "Real Video" setting is auto-enabled.
3) The trick here is to load the rest of the ROM on addresses 2000h-3fffh. To do that, go to menu Debugging-> Load binary block. Select the same
sponzy rom file, set address to 0, and set lenght to 0 (to load the whole file). The emulator will load the whole file, but addresses 0000-1fffh are
write protected, but it is not a problem so these addresses are already loaded since pass 2. Addresses 2000h-3fffh will be written (so we enabled RAM here) with the rest of the Sponzy ROM
4) Go to menu debugging->Reset
5) The rom is working now but you will probably see only a white display. So, Sponzy rom uses WRX display mode. You must enable it on menu Display Settings->WRX


----------------------------------------------------------------------------


ZX-UNO
------

Q: Why DIVMMC on ZX-Uno uses esxdos 0.8.6 beta 4 and other Spectrum models use esxdos 0.8.5?
A: When using ZX-Uno emulation, the esxdos firmware is included with the ZX-Uno Flash image zxuno.flash. ZX-Uno comes with esxdos 0.8.6 beta 4.
When you are using divmmc on other Spectrum models, the emulator loads esxdos 0.8.5 firmware (file esxmmc085.rom).


Q: Why using ZX-Uno some emulator settings on the menu are changed?
A: Some settings on ZX-Uno are shared from the same ones on the menu. For example: DivMMC emulation, Keyboard Issue, Contended Memory, Timing (Timing can not be changed from the menu), ULAPlus, etc...
So these settings on the emulator can be changed using the ZX-Uno bios, or even the ZX-Uno boot process changes them (specially divmmc emulation)


Q: Where can I find the following keys of ZX-Uno: Edit, Break, Delete, etc..
A: These keys are not new keys on ZX-Uno, instead they are combination of keys, like on Spectrum+, +2, etc. Original speccy only had 40 keys, to do function edit, for example, you had to press Shift+1. Break key is the combination of pressing Shift+Space. So, in Spectrum+, +2 and higher, these alternate keys are inded combinations of keys. When you press Edit, for example, the keyboard is pressing Shift+1. So, in the emulator, you must use Shift+key combinations to get them.
There are some keyboard stickers for ZX-Uno that locate, for example, Break function on ESC key or Edit function on F2 key. These are not valid on the emulator, except ESC key,
which is mapped to Break on ZX-Uno. Almost all F-function key have other meanings on the emulator. NMI function seems to be mapped to F5 in some ZX-Uno stickers, but F5 opens ZEsarUX menu; to generate a NMI you must go to Debug menu


Q: How can I change the FPGA emulation core?
A: You can not change it. ZEsarUX does not emulate the ZX-Uno FPGA. ZEsarUX emulates the following on ZX-Uno mode:
-Z80
-Normal hardware of a Spectrum +2A: Audio Chip, Beeper, Tape, etc...
-Additional Memory of ZX-Uno
-SPI Flash
-DivMMC
-Internal 256 ZX-Uno registers: Masterconf, Mastermapper, etc
-Other additional features: ULAplus...

So, you can not change the emulation core, you can not, for example, upload a FPGA core with emulation for Atari 2600...


Q: Why ZX-Uno boot and bios seem to use a lot of physical CPU and reduces FPS?
A: On ZX-Uno boot process and entering its bios, the Z80 Turbo mode is set to 8X, so the emulator uses eight times the cpu power more than on normal 1X mode. This is why it uses more physical CPU and FPS are reduced. It should not happen if your computer is very fast.
You may change a the setting "Deny turbo on boot" on menu Settings->Hardware so it denies changing turbo mode on these 2 cases


----------------------------------------------------------------------------


Z88
---

Q: How can I write files from my local hard disk to a Z88 File Card?
A: Take a look at this video:
https://www.youtube.com/watch?v=mxaVURSAO3o


Q: How can I use hybrid RAM+EPROM cards for writing?
A: Although ZEsarUX supports these cards to be written on slot 3, OZ doesn't seem to recognize them to be written. 
EPROM part is 512kb size and this is not a standard EPROM size. 
But these cards are recognized for reading when have data like a new oz release (insert it on slot 1 to be boot)


Q: I'm very interested in the Cambridge Z88, but I don't know how to use it. Where can I find the documentation?
A: You can find it at https://cambridgez88.jira.com/wiki/display/UG45/
or in the ZEsarUX extras package:
extras/docs/z88/Z88UGV4.pdf

----------------------------------------------------------------------------


Chloe
-----


Q: What is Chloe?
A: The Chloe 280SE is a new 8-bit computer.

Operating System: esxDOS
CPU: Zilog Z80A @ 3.5MHz
Memory: 256 Kibibytes
Firmware: SE Basic IV
Palette: 256 colors
Video modes: 40 column, 80 column, Spectrum and Timex compatible modes
Audio: 6 channel AY


----------------------------------------------------------------------------


Prism
-----

Q: What is Prism?
A: Prism is Jeff Braine's FPGA based "Spectrum Compatible" computer. As well as trying to stay compatible with as many pieces of Spectrum software as possible, the aim for Prism 
was to add the many features Jeff used to wish were coming with the "next Spectrum" whenever a new model was rumored.  Extra memory, extra screen modes, new ways of decoding 
the screen data, extra colours, redefinable colours... All these and more have been added to Prism, which is still being developed. 

Some features of Prism include:

* 512K SRAM. This can be addressed using a number of paging methods, compatible with different models
     * Spectrum 128 (port 7FFD), 
     * Spectrum +2A/+3 (ports 7FFD & 1FFD)
     * Chloe 280SE (ports 7FFD, FF and F4)
     * Pentagon 512 (port 7FFD - same as Spectrum 128 but also uses bit 6 and 7 to page in the extra banks of memory)

* 1MB Flash memory used in place of the ROM which allows the user to install and choose between up to 256 different ROMs (assuming the ROM is 16K in size)

* "ULA2" accesses up to 32K Video RAM divided into 4 pages of 8K, allowing new screen modes with higher resolution and/or numbers of colours and new methods of decoding the screen data:
    * 128x96, 256x96, 128x192, 256x192, 512x192, 256x384, 512x384 resolutions possible
    *  8, 16, 32, 64, 256 colours on screen at once without software tricks (depending on the screen mode and data decoding options)
    * 4096 colours on screen at once using special "Brainebow" mode
    * 8x8, 8x1 and 4x8 attribute square sizes available in hardware without needing software tricks (depending on the screen mode and data decoding options)
    * 4 colours in a 4x8 attribute square using special "chunk-o-vision" mode (based on the screen mode of a common US competitor of the Spectrum with too many browns)
    * 8 and 16 colour "planar" modes without colour clash available without needing software tricks (depending on the screen mode and data decoding options)
    * User defined 256 colour palette chosen from a master 4096 colour palette (* the full ULA2 specification allows for 24 bit colour, but the development Prism only does 12 bit colour)

* Compatibility options allow the user to turn off some of Prism's advanced features to allow certain software to work (eg it's possible to limit Prism to 128K so that Out Run, 
Turbo Out Run and Carrier Command work)

* Special "VRAM aperture" means VRAM is only presented to the CPU where it is necessary, allowing the user to use higher screen resolutions etc without the screen getting 
corrupted by system variables and the beginning of BASIC. This option can be disabled at boot to retain compatibility with the small amount of software which expects 16K 
of VRAM to be available (mainly Timex/Chloe/SpectrumSE software)

* Special "VRAM Write" (aka "Planar Write") options allow the user to select which VRAM page or combination of pages are written to in the screen area of memory. This gives 
the user easier access to the video memory when working with higher resolutions or planar video modes.

* User selectable CPU speed 

* Additionally Prism supports ULAplus, Radastan screen mode, Zesarux screen modes, Multiface 128 and DivMMC

Take a look at http://zxprism.blogspot.com.es for more information and demos


Q: I'm stuck at the Prism boot menu. I select "Boot" but it resets and return to the boot menu
A: You have to change the Flash Page, the default is 0, the boot rom. Change to value 2 or higher and then select "Boot"
See files on extras/docs/prism/ to know which roms are included in the Flash

----------------------------------------------------------------------------


TBBlue
------


Q: I can't run TBBlue machine. I get the following error: "Erro ao inicializar cartao!"
A: TBBlue machine needs a SD/MMC image to boot. You must select file image "media/disk_images/tbblue.mmc" on Storage->MMC->MMC File.
Then enable MMC emulation and DivMMC ports (but not DivMMC paging), and do a hard reset
Or you can select it from the command line with:
./zesarux --mmc-file tbblue.mmc --enable-mmc --enable-divmmc-ports --machine tbblue

Note: tbblue.mmc is included on the base package (and not on extras) because it is needed to boot that machine

Q: I have enabled divmmc on Tbblue bios, but seems it's not working (no esxdos or nextos)
A: Sometimes, enabling divmmc on tbblue bios requires closing and reopening ZEsarUX. The technical answer for this issue,
is that enabling/disabling divmmc on tbblue is not done the same way as when you enable/disable it from ZEsarUX menu, 
tbblue does not disables entirely divmmc, only automatic memory paging


Q: Why can't enable divmmc paging (or full divmmc emulation) from command line/config file on TBBlue? When exiting emulator, these settings are not saved on configuration file. But... if I force them to enable from command line, TBBlue does not boot, and then doing a hard reset it boots ok
A: TBBlue needs divmmc paging disabled to boot, if not, divmmc firmware will be activated on the tbblue boot and then it hangs. When you do a hard reset, some internal tbblue registers (reg 6, bit 4) are reset to zero. Resetting this register 6, divmmc paging is disabled and so the boot works ok. But when initializing the emulator the sequence is:

-Apply most of the command line settings (divmmc settings are not applied here)
-Initialize machine, CPU registers, I/O ports, and some tbblue registers to zero, including register 6. So divmmc paging is disabled
-Apply the rest of command line settings, including divmmc settings. If you enabled divmmc paging here, it will be enabled
-Pass control to Z80. Having divmmc paging enabled, does not boot tbblue
You may ask now.... why do you apply some command line before initializing machine and some others after? I won't answer it here, it's too complex ;) If you want
to know the answer, please e-mail me.


Q: What is the difference between TBBlue and Spectrum Next?
A: In a nut shell: TBBlue is the very same firmware that runs on all boards. Some boards have less space, so runs less features. 
In order, most complete do less complete:

1 - Next
2 - Multicore
3 - WXEDA and DE2
4 - DE1
5 - VTrucco and FBLabs

Next and Multicore have HDMI output, others dont. Next have FM sound, others don´t. 1,2 and 3 group have 256 colors and sprites, others dont.
But still, EXACT THE SAME TBBlue


Q: Booting TBBlue is a bit slow. Can I run a sna snapshot without having to wait for the tbblue boot process?
A: Yes. You can use the tbblue-fast-boot-mode setting and it will go directly to a 48 rom, but with all the Next features enabled (except divmmc). For example, you can run the Dungeonette game with: 

./zesarux --noconfigfile --zoom 1 --machine tbblue --realvideo --enabletimexvideo --tbblue-fast-boot-mode --sna-no-change-machine --enable-esxdos-handler --esxdos-root-dir /Users/cesarhernandez/Downloads/Dungeonette/ /Users/cesarhernandez/Downloads/Dungeonette/project.sna

You can also load a .nex file with a similar command line:
./zesarux --noconfigfile --zoom 1  --machine tbblue --realvideo --enabletimexvideo --tbblue-fast-boot-mode --enable-esxdos-handler --esxdos-root-dir /Users/cesarhernandez/Downloads/Warhawk/ /Users/cesarhernandez/Downloads/Warhawk/Warhawk.nex

Q: Trying the breakout demo, it gives me the error: Nonsense in basic at line 10
A: That is an old version which uses previous NextOS basic. Change line 10 to:
10 LOAD "breakout.SPR" BANK 10 


Q: Can I use CSpect SD card images from site http://www.zxspectrumnext.online/cspect/ ?
A: Of course. As they say in the web page "for use with CSpect and real ZX Spectrum Next board", ZEsarUX behaves almost a real ZX Spectrum next board,
so you can use the SD card images. Just some things to take into account:
-You should rename the img file to extension .mmc. If you don't do it, it won't appear in the File Browser (unless you change the filter to show all files), but can be used even with .img extension
-Those img file size are not multiple of 16 kb. It will tell you an error but the file can be used
-Writing changes to a mmc file bigger than 2 gb may generate error on Mac OS. In these cases I recommend you to disable the "Persistent writes" setting
-It seems the CSpect 2 GB image file is a bit smaller than 2gb, so it can be used even on Mac and write changes to it.
-Using mmc files bigger than 1 gb may be slow. So be patient when opening the image or writing changes.

----------------------------------------------------------------------------


TSConf
------


Q: When I do a hard reset, the screen goes to black and seems it runs nothing
A: Do a hard reset and just after that, keep pressing Symbol Shift (CTRL or ALT) and you will return to the TSConf Bios

Q: Some .spg games seem to fail loading
A: Be sure you haven't enabled divmmc or divide paging, it's incompatible with some of them  


----------------------------------------------------------------------------


CPC 464
-------


Q: Why many games don't load, or hang on menu, or shows corrupted display?
A: CPC emulation is currently experimental. Many features don't work well:
* No full CRTC support
* No joystick support
* No hardware scroll full support


----------------------------------------------------------------------------


Sam Coupe
---------


Q: How are special keys (like edit or Symbol) mapped? 
A: Key mapping is:
-CTRL key is CNTRL on Sam Coupe
-Left Alt is Symbol on Sam Coupe
-Right Alt is Edit on Sam Coupe
-Keypad numbers are mapped to F numbers on Sam Coupe


Q: How can I load from Sam Coupe disk?
A: Disk emulation is not finished yet. You can only load from tape

Q: Why the sound is so ugly?
A: I'm not emulating the Sam Coupe audio chip (SAA1099), but simulating the audio by the audio chip from the Spectrum (AY-3-8912).
This is why it does not sound real. In the future I will emulate the SAA1099 perfectly ;)

Q: How can I load some turbo tapes (tzx)?
A: Seems to be a timing bug on the Sam Coupe emulation and the ROM does not detect the right load speed. But you can change manually
the cpu speed (from menu->settings->cpu) to 2x or 4x, most of these demos use these loading speeds. But keep also in mind that some loading tapes recorded, for example,
at 400% speed, need 2X turbo setting (not 4X)

----------------------------------------------------------------------------


QL
--


Q: Does keyboard work?
A: QL low level keyboard handling routines do not fully work yet but tries to do its best


Q: Backspace on QL works. But why the native combination (CTRL+Left) does not work? I'm using Mac OS X
A: You'd better use backspace. But if you want to use the native combination, try:
-press and hold left key
-it will move one position to the left
-before it starts moving quickly to the left, hold CTRL


Q: How can I stop a program?
A: Try CTRL+Space


Q: How can I load a program from microdrive or floppy?
A: Microdrive or floppy emulation it's beta. You can try by opening the Storage menu and select root folder for game/program (usually where the boot file is located) on mdv1/mdv2/flp1 settings. Some games require to use flp1, you may also select mdv1 and flp1 both to the same folder
You can also load a game "manually", by loading the binary file from ZEsarUX menu "Debug->Load binary block".
You must inspect the basic loader program and execute all the sentences except lbytes. lbytes must be simulated manually from that menu

Q: I loaded Spook (Pacman clone) but does not seem to work. When the game appears, pressing a cursor key, restarts the game in a loop
A: Seems to fail if sound on game is enable (by default). Disable sound on that game by pressing F3



----------------------------------------------------------------------------



Miscellaneous
-------------

Q: Alt key is not read on Mac OS X, using X11 (xquartz) driver. On Spectrum and ZX80/81 modes, Alt is the same as Ctrl, but on Z88, Alt is the Square key. So it is important on Z88 this key to be read.
A: Go to X11 Preferences > Input > Option keys send Alt_L and Alt_R.


Q: I'm using cacalib or curses driver, on pure text console. The emulator says it has kempston mouse support, but it does not work. What can I do?
A: Install gpmmouse to have mouse support on these drivers. 


Q: I'm using cacalib or curses driver and the position of the kempston mouse is not read when moving it. Only when I push left or right button.
A: Mouse position on text mode drivers (cacalib and curses) is only read when you push a button, and not when you move the mouse.


Q: How is pronounced the name of the emulator?
A: Phonetically: ZEsarUX is pronounced: θesar´uks
One by one, every letter:
Z like th on think
E like e on let
S like s on sing
A like a on cat
R like r on round 
U like u on put
X like x on linux
And saying the accent on the final syllable 
You can also play zesarux.mp3 to hear how it sounds


Q: What is the origin of the name of the emulator?
A: ZEsarUX comes from:
ZX Second-Emulator And Released for UniX.
I write second-emulator with a hyphen because I changed the order of the two words to have the final name... If not, name would be:
ZsEarUX :P
Second because it's my second emulator. The first was ZXSpectr:
https://github.com/chernandezba/zxspectr
Why the capital letters? Because one of the first names I thought was ZEUX, but there's another emulator called zeus... 
Then I thought some name like mine (Cesar) and adding letters zx (for zx spectrum) and also UX for UNIX/Linux, so Linux was the first supported platform. Then I simply joined all these letters and have a translation for every letter to a word, on a phrase with sense: 
ZX Second-Emulator And Released for UniX.
It's important to write lowercase and uppercase characters correctly. Uppercase letters refer to the most important part of the name: "ZX", "Emulator", "UniX"
And lowercase letters refer to the less important part : "second", "and", "released"


Q: Can this emulator run on MS-DOS?
A: No, it can not, you can only run it on Windows, Mac, Linux, Raspberry pi and other Unix compatible systems. But you can try my old ZXSpectr emulator:
https://github.com/chernandezba/zxspectr
It does run on MS-DOS. It was created on June 1996, so it's more than 20 years old!


Q: Using the menu "video out to file" generates a raw video file. Seems I have to use the program "mplayer" to run it, I tried but I didn't succeed. I'm using Mac
A: Playing the raw video on Mac it's a bit tricky, but yes, you can use mplayer for Mac.
First download MplayerX from:
http://mplayerx.org

Then, when you enable video out on ZEsarUX, a window will be appear with the parameters needed for mplayer, but also on console (enabling verbose debug). For example:
mplayer -demuxer rawvideo -rawvideo fps=5:w=720:h=576:format=bgr24 /Users/chernandezba/Documents/video.rwv
(this example was for a video recording on TSConf machine)

So, MplayerX has a beautiful fronted for Mac but it also has a command line program to play video; this is what you need to play the video generated from ZEsarUX
You should run the command line mplayer by opening a Terminal, and write:
/Applications/MPlayerX.app/Contents/Resources/MPlayerX.mplayer.bundle/Contents/Resources/x86_64/mplayer XXXX

Where XXXX are all the parameters that ZEsarUX gave you. In this example, the command line sentence will be:
/Applications/MPlayerX.app/Contents/Resources/MPlayerX.mplayer.bundle/Contents/Resources/x86_64/mplayer -demuxer rawvideo -rawvideo fps=5:w=720:h=576:format=bgr24 /Users/chernandezba/Documents/video.rwv


Q: Is there any manual or documentation?
A: There is no manual, and there won't be never. The reason is that, in the past, I spent lots of hours making documentation for my previous emulator, ZXSpectr, and I wasted lots of hours, more than doing the emulator. But you have the following:
-This FAQ file
-Menu entries with help (pressing F1 in most of them) and item tooltips when no key is pressed
-docs folder with many information
-youtube videos showing different features of ZEsarUX. https://www.youtube.com/user/chernandezba
-And my own help. You can ask me by mail, forums, twitter and Facebook ZEsarUX group


Q: Can I use ZEsarUX as a standalone AY player?
A: Yes, you can run ZEsarUX from command line and enable a setting to exit emulator when finishing playing the ay file. 
You can also specify a limit for "infinite" tracks (tracks defined with no limit length), for example:

./zesarux --noconfigfile extras/media/ay_files/Spectrum/Games/CHASEHQ.AY --ayplayer-inf-length 60 --ayplayer-end-exit --vo null

Using Linux or Mac you can also use ZEsarUX as a random ay file player, with the following piece of code:

while [ 1 == 1 ]; do
    ARCH=`ls -1 extras/media/ay_files/Spectrum/Games/| python -c "import sys; import random; print(random.choice(sys.stdin.readlines()).rstrip())"`
    echo $ARCH
    ./zesarux --noconfigfile extras/media/ay_files/Spectrum/Games/$ARCH --ayplayer-inf-length 60 --ayplayer-end-exit --vo null
done


Q: What is Man Software?
A: It's the brand name for software I have been making since I was a child on the Spectrum. Many programs and games you can find on folder my_soft/ are signed by this brand. Many others are signed by my real name, but all are made by me.
You can find also a "Man Software GUI Style" on the ZEsarUX menu, that uses a font type I invented when I was a child.


Q: What is ZX Vision?
A: ZX Vision is the new ZEsarUX windows style used since version 7.2. These windows can be moved, resized, scrolled, minimized and much more.... The name is inspired by "Turbo Vision" text windows environment used on old Borland Turbo C and Turbo Pascal compilers.

Q: What is ZX Desktop?
A: ZX Desktop enables you to have a space on the right to place zxvision windows or other widgets. This is a work in progress, so expect improvements in the next versions


Q: What are the files required to run the emulator? I see lots of files, even the Extras packages have a lot more
A: The emulator is really very small. The extras packages is not needed to run it, as it includes:
-Documentation. docs folder. 37 MB
-Examples. media folder: 62 MB. snap_tests folder: 34 MB
-Some .ide, .mmc, .flash image files: 229 MB

The emulator only really needs the following files to run (included in the main package):
-The executable file: "zesarux" or "zesarux.exe" which is 2 MB size aproximately
-rom files: 5 MB
-Some dll files on Windows version
-zxuno.flash if running ZX-Uno machine
-tbblue.mmc if running TBBlue machine
These three types of files doesn't use more than 10 MB.
You can even try to delete all the unnecessary files and the emulator will also work. 


Q: When I enable video out to file setting, or "Reduce to 0.75" a big "Z" letter is added to the display. Can I erase it?
A: No, you can't. Because I want that final video has that watermark, so anyone that sees it knows which emulator is used to record it ;)
However, you can move the letter, go to Settings->GUI->OSD->Watermark position


Q: Why the emulator doesn't use more beautiful menus, like the usual menus on Windows/Mac/Linux etc? / Why are you limiting the GUI interface to these simple menus? / Why don't you have a better file selector?
A: The GUI interface is a custom one, I did it copying the style of the menus of Spectrum 128k machines. I'm not using any native menus on Mac, Windows, etc, because my menus are integrated inside the emulator window.
This has the advantage of having the same style menus (and all the emulator) in all operating systems that you run ZEsarUX. All have the same appearance.
Also, using some GUI needs additional libraries, and I want it to have the minimum dependencies.
The file selector is also a custom window, so don't expect a popup appear with your usual File selector window.
Maybe the GUI it's a bit difficult to use, but when you have been using a couple of hours, you won't prefer any other! 
I recommend you to use hotkeys for faster selection, redefining some F-keys, and using the mouse.
This could probably be the only one piece of ZEsarUX that I won't ever change. I like the GUI; you are using a retro-machines emulator, so.... you must use a retro-GUI ;)


Q: How do I uninstall ZEsarUX
A: It's very easy. ZEsarUX doesn't create more files when installed, it only saves the configuration file.
Depending on the operating system:

-Linux: 
--if you compiled from sources and did a "make install", all your files were installed starting on the installation prefix, that can be changed with the "--prefix" setting to the configure folder, and by default it's /usr/local. Supose the instalation prefix it's called "INSTALLPREFIX", you need to remove:

*executable emulator: INSTALLPREFIX/bin/zesarux
*data files: folder INSTALLPREFIX/share/zesarux/

--if you installed a binary version downloaded from the ZEsarUX web page, you need to remove:
*executable emulator: /usr/bin/zesarux
*data files: folder /usr/share/zesarux/

--if you downloaded any other binary version, not from the ZEsarUX web page, please ask the package mantainer how to do that ;)


-Mac:

--if you compiled from sources and did a "make install", follow the same procedure as Linux
--if you installed a binary version downloaded from the ZEsarUX web page, you only need to drag the ZEsarUX icon app to the Trash


-Windows:
--if you installed a binary version downloaded from the ZEsarUX web page, it's all contained on the extracted files from the .zip. Just remove the extracted folder


Finally, if you want to remove also the configuration file:
-Linux: located on $HOME/.zesaruxrc
-Mac: located on $HOME/.zesaruxrc
-Windows: located on your home folder, name ".zesaruxrc". Your home folder is something like "c:\users\myusername\"


Q: The emulator runs slower than a real Spectrum. I'm using a Raspberry Pi One (or another slow cpu)
A: You can use the Spectrum reduced core, which can be set on compile time but also switchable from menu or command line setting.
Using that core, the following features will NOT be available or will NOT be properly emulated:
Debug t-states, Char detection, +3 Disk, Save to tape, Divide, Divmmc, Multiface, RZX, Raster interrupts, ZX-Uno DMA, TBBlue DMA, Datagear DMA, TBBlue Copper, Audio DAC, Stereo AY, Video out to file, Last core frame statistics, Tone generator.
Some of these features should not have any effect on cpu performance if you don't enable them, like Divide or Raster interrupts, but this afirmation is only true on Intel cpu and
cpu with Speculative Execution. Raspberri Pi One (or Zero) does not have Speculative Execution on the cpu, so using the reduced core will use less real cpu and the emulator
will run fine.
A raw and fast explanation about this is that "if" sentences, on the spectrum emulation core, that are not true (like having raster interrupts disabled), do not impact on the cpu use 
if you have Speculative Execution (like Intel cpu), but do really impact on the cpu use on cpu which does not have Speculative Execution (like Raspberry)

So, you can recompile with the "--spectrum-reduced-core" setting on the configure script, to have it always enabled by default, but also you can switch it on by using 
the command line setting "--spectrum-reduced-core" when running ZEsarUX, and even more, you can switch it on from the menu, Settings->Hardware settings




Q: I have a question not listed here. What can I do?
A: Send a mail to chernandezba (at) hotmail.com and I will answer you.


