The latest version of Zero can always be downloaded from here. Zero is distributed with an installer as well as a standalone zip file that can be easily run from even a USB drive.


Recommended System Requirements

  • 1 GHz or better processor. Multi-core is even better!
  • Graphic card with up to date drivers that supports DirectX 9.0c runtime.
  • 512MB RAM.
  • Windows XP SP 2 or better.

Download Files

Zero is now available in two flavours: A regular windows version (Zero 0.7.1 Vanilla) and the retro themed one (Zero 0.6.6). Features wise they are both the same, so take your pick!

Zero 0.7.1  (Vanilla) Setup

Cybernoid2 ULA Plus


Zero 0.6.6 Setup 



The .zip versions (portable) are Zero and Zero

IMPORTANT: In order for the emulator to work correctly, you may need to download additional DirectX files from

36 thoughts to “Download”

    1. This is usually an indication that one of the .dll dependencies is failing. The likely possibilities are: .net framework 2.0 or .net framework 3.5 missing, directX 9.0c runtime missing. Which version of the .zip did you download? 32 bit or 64 bit? If it’s the latter try the setup file. If that works then it’s possible that I’m missing some 64 bit dll dependency.

  1. Mine always requires to download the Slim DX Runtime Feb 2010, even though it’s already installed… meaningly, it doesn’t see it’s installed…

      1. Cool, that did it. Took me a while to understand why games were not loading… had to type LOAD “” as in the old times…

  2. Hi there,
    very good emulator….I mostly appreciate the debugger(but, here is missing a breakpoint set in case some memory value is changed). Very good idea is also to connect right to WoS and browse the games+online downloader.

    Anyway, are there some source codes to that emulator please ?..I am a professional programmer, I would like to help developing the emulator if possible.

    Please contact me on my email please.

    Anyway very nice work,

    1. Glad you liked it. The debugger, like the emulator, is very much work in progress. I may get around to adding conditional breakpoints but can’t say for sure when! 😉

      At the moment, the source code to the emulator isn’t in the public domain as there are still some things I want to wrap up before releasing the source. The good news is that the source code *may* be available in the near future. 🙂

    1. In the build I have (development version not available to public that is), RZX playback is supported. RZX recording is something I still have to tackle. 🙂

  3. Hi Arjun,
    I am here again…looking you`re going well.

    I highly appreciate the ability to set the emulator speed. And not just predefined values(3.5, 7, …). Such feature has only WinZ80 as far as I know. GREAT !

    But, regarding to debugger, I think it needs some improvement. As I can see you know it is not working bugless.

    Try an easy example:
    1.) POKE 40000, 201
    2.) Set read breakpoint on address 40000
    3.) Randomize USR 40000
    And breakpoint occured…this is not correct, because there is no memory read, just executing. Do you use the same method for memory read to have opcode to be executed ?

    Anyway, great emulator…keep going !


    1. Hi Adler,

      Thanks for the feedback.

      I’m on vacation so can’t check the issue at the moment so will have a look at it as soon as I’m back. Cheers!


      1. Hi Arjun,
        sorry, I can no more simulate the problem described above(breakpoint on memory read). I thought that it is so, but it seems that it is caused by the fact, that sometimes monitor incorrectly stops emulation even there is no breakpoint detected. In that case there is also no information in status line(like “Memory write @ with value 5”).

        Can you please check it, why there are some emulation stops caused by monitor even there is no breakpoint detected ?

        Thank you and keep going,

        1. Hi Adler,

          In fact, I fixed the problem with memory read in the upcoming v0.6. There are now 3 memory I/O breakpoints available – read, write and execute. In v0.5, the memory read breakpoint was being triggered even for execute. For 0.6, I have also added support for breakpoint on memory execute, which should fix the problems related to memory read. I have also completely redesigned the debugger. I hope the new changes are of some use. The new version (0.6) should be out this weekend if all goes well. Stay tuned and thanks for your support!


      1. Oh, okay 🙂 Was wondering because back in the day I knew someone from the Speccy-scene called Arjun 🙂

        Thanks for your great work on the emu – sure brought and still bringing back some great memories 😀

    1. Not at all. Progress is a bit slow due to other demands in life. If you’ve been following my twitter activity (see main page) you would know that I’m working on a plain vanilla version of Zero in parallel.

  4. Thanks for making this available, it looks great!
    I downloaded it and installed it but when I try to run it I get the following error:

    Stopped working

    Problem signature:
    Problem Event Name: CLR20r3
    Problem Signature 01: zero.exe
    Problem Signature 02:
    Problem Signature 03: 51d98af2
    Problem Signature 04: Zero
    Problem Signature 05:
    Problem Signature 06: 51d98af2
    Problem Signature 07: 386
    Problem Signature 08: b
    Problem Signature 09: System.IO.FileNotFoundException
    OS Version: 6.1.7601.
    Locale ID: 3082

    Any ideas on what could I do?

    Thanks again!

    1. Hi,

      I’m looking into this problem as it’s been reported by others as well. Can you tell me what .Net frameworks are installed and what type of system config you have? Including the CPU.


  5. Great to hear 🙂
    Sorry, I’m not using Twitter that active.

    If you need any feedback on things, just let me know, okay?

    Thanks for your continued effort.

  6. Hi, Arjun!
    Am I doing something wrong when I use the Tape Deck? I’ve unchecked all the options – “Fast Load”, “Edge Load” etc and can’t view a full tape load process in realtime anyway. I’ve simply got to the end of load process in just a second but it’s not I want to. I want to see a blue and yellow lines on the border for the minutes the prog is loading and enjoy this as in my past.
    Thank you for your work!

    1. Anton, no it’s not your fault. It’s just me who forgot to add the option to turn off “Insta Load” to the tape browser. lol. Will add that in the next release. Thanks for spotting the issue!

  7. Hi Arjun,

    Just run it for the 1st time and when it’s maximized on the screen I can’t get out of this unless I launch the task manager and kill the process. How do I go back that it will open not in full screen?
    I uninstalled and installed it again – and the same. Opens in full screen.


  8. Hi Arjun

    Great work on this 🙂 – The only problem I’m having is how to enter pokes/cheats via Zero. When I select the ‘Cheat Helper’ function, I get a box that requests a .POK file. I’ve gone on to the Tip-Shop site and all I can see are the multiface pokes.

    How would I enter these on Zero?


    1. Hi Shak,

      To poke the memory directly, you need to open up the Debugger and use the Tools > Poke Memory option. I will probably add an option to poke cheats directly from the Cheat Helper at some point in the future. 🙂


    2. Wow! I didn’t see this until now. Anyway, better late than never, so here goes: To poke memory values directly (like multi-face pokes), you need to open up the Debugger > Tools > Poke Memory tool. Enter the address and value here then quit the debugger and you’re on your way! I will move this to the Cheat Helper someday.

  9. 0.7.1 bug: won’t save Joystick settings. If you quit and restart the emulator Joystick settings will be gone (I’ve configured a Competition Pro USB arcade joystick SpeedLink SL-6603-SPORTS-EU as Kempston for joy1).
    Of course I press Save button to save.

  10. Anther little problem: won’t prevent display/computer sleep when you play with an external controller. Annoying to press a key on the keyboard after a while just to avoid that…

Leave a Reply

Your email address will not be published. Required fields are marked *