Ondographics

Download

One archive, unzipped anywhere: run.cmd runs the app where it sits and install.cmd puts it in the Start menu. Nothing in it needs administrator rights, and nothing in it needs to be signed, because nothing in it is a repackaged executable.

Download Ondographics-1.11.8-portable.zip (165.7 MB) Served from this site. No account, no waiting, no redirect.

What you are downloading

Archive
Ondographics-1.11.8-portable.zip
Version
1.11.8
Size
165.7 MB (173767319 bytes)
SHA-256
d9e4e42504aa353c71d71c3c27f3a0c2c45bcbf20bc5328c8052ac61e1ea323a
Runtime
Electron 44.7.0, the stock win32-x64 release, unpacked and unmodified
Contains
the application and the stock runtime. No downloader, no installer wrapper, no third-party tool of any kind.
Licence
MIT

Checking it

Windows can hash the file for you. Open a Command Prompt where it landed and run: 

certutil -hashfile Ondographics-1.11.8-portable.zip SHA256

The line it prints should be the checksum above, character for character. If it is not, the download was changed in transit and you should not run it.

After it downloads

  1. Unzip the archive anywhere you like.
  2. run.cmd runs the app from that folder. Nothing is copied, and the only thing written outside it is your own settings folder.
  3. install.cmd installs it instead: the app goes to %LOCALAPPDATA%\Programs\Ondographics, with a Start menu entry and an entry in Apps & features. One at a time is what a Start menu entry means, so use one or the other.

Installing it has the details, including what Windows may ask about a .cmd that arrived in a downloaded folder, and the options both scripts take.

How it is stored

The archive is held in this site's own storage as one file, and streamed to you from there. It is stored in 21 parts of about 8 MB, because that is what one upload will take, but what is kept and what you receive is the one archive: there is nothing to join up afterwards.

Three things arrive with it that are worth knowing. Its length is declared before the first byte, so your browser can show real progress rather than a guessed one. Its SHA-256 is in the response headers, so a download manager can check the file for you as it lands. And it answers byte ranges, so a download that is cut off halfway - a dropped connection, a laptop that slept, a browser closed by accident - carries on from where it stopped instead of starting over, and anything that wants to look at part of the file is given that part rather than all 166 MB.

If the file you end up with is not exactly 173767319 bytes, it did not arrive whole: resume it if your browser offers to, and only delete it and start again if it does not. If Windows says the archive is invalid, the file is short or the connection was cut: check the length first. A truncated archive is the one failure that looks like a working download until Windows refuses to open it.

The release's own record is at /release/manifest.json: the archive's name, its length, its SHA-256, and the 21 parts it is uploaded in.