{"id":14397,"date":"2026-07-03T02:00:00","date_gmt":"2026-07-03T06:00:00","guid":{"rendered":"https:\/\/www.both.org\/?p=14397"},"modified":"2026-07-03T00:24:15","modified_gmt":"2026-07-03T04:24:15","slug":"hands-on-with-freedos-beta1","status":"publish","type":"post","link":"https:\/\/www.both.org\/?p=14397","title":{"rendered":"Hands-on with FreeDOS Beta1"},"content":{"rendered":"<div class=\"pld-like-dislike-wrap pld-template-1\">\r\n    <div class=\"pld-like-wrap  pld-common-wrap\">\r\n    <a href=\"javascript:void(0)\" class=\"pld-like-trigger pld-like-dislike-trigger  \" title=\"\" data-post-id=\"14397\" data-trigger-type=\"like\" data-restriction=\"cookie\" data-already-liked=\"0\">\r\n                        <i class=\"fas fa-thumbs-up\"><\/i>\r\n                <\/a>\r\n    <span class=\"pld-like-count-wrap pld-count-wrap\">    <\/span>\r\n<\/div><\/div>\n<p class=\"wp-block-paragraph\">The FreeDOS Project recently passed its <a href=\"https:\/\/www.both.org\/?p=14240\">32-year anniversary<\/a>. This is a long time for any open source project, especially one that reproduces a classic operating system like DOS. We&#8217;re excited that so many people still download and use FreeDOS in 2026.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">To celebrate the FreeDOS anniversary, I shared some early releases of the FreeDOS distribution, available from the <a href=\"https:\/\/www.freedos.org\">FreeDOS Project<\/a> website. Download the FreeDOS <a href=\"https:\/\/www.ibiblio.org\/pub\/micro\/pc-stuff\/freedos\/files\/distributions\/pre-1.0\/\">Alpha5 and Beta1<\/a> if you&#8217;d like to see where it all started.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">I recently took a look back at the <a href=\"https:\/\/www.both.org\/?p=14364\">FreeDOS Alpha5<\/a> distribution. The &#8220;alpha&#8221; releases were essentially prototypes of what FreeDOS could be. In the Alpha5 version (1996) many traditional DOS commands and features were not yet working. However, by the time we released FreeDOS Beta1 (1998) things were in much better shape. The DOS commands now worked more like the traditional DOS versions they replaced. And most importantly, you could now boot your computer with the FreeDOS kernel from Beta1 and <em>most<\/em> things would work. Let&#8217;s take a hands-on look at Beta1.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A note about the name<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">As you review these screenshots, you may notice some inconsistencies with the name. Sometimes the screenshots say &#8220;FreeDOS&#8221; and others use &#8220;Free-DOS&#8221; with a hyphen. There&#8217;s some history here:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Starting in 1994 when I first <a href=\"https:\/\/groups.google.com\/g\/comp.os.msdos.apps\/c\/oQmT4ETcSzU\/m\/O1HR8PE2u-EJ\">announced<\/a> the project, I called it &#8220;PD-DOS&#8221; because I assumed giving away the source code was the same as public domain. But others pointed out that because we used the GNU General Public License, the project was actually Free software, so I quickly renamed it &#8220;Free-DOS&#8221; after a few weeks. We dropped the hyphen several years later, around the time that Pat Villani published his book, <a href=\"https:\/\/www.routledge.com\/FreeDOS-Kernel-An-MS-DOS-Emulator-for-Platform-Independence-amp-Embedded-System-Development\/Villani\/p\/book\/9780879304362\">The FreeDOS Kernel<\/a> in 1996.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">While we had officially adopted the &#8220;FreeDOS&#8221; (no hyphen) name by the time we released the Beta1 distribution in 1998, we weren&#8217;t always consistent with how we named it. That&#8217;s why a few screenshots still show the name as &#8220;Free-DOS&#8221; instead of &#8220;FreeDOS.&#8221; For consistency in this review, I&#8217;ll refer to this distribution simply as &#8220;Beta1&#8221; so I can avoid confusing you with &#8220;Free-DOS&#8221; or &#8220;FreeDOS.&#8221;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Installing the Beta1 distribution<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">We provided the Beta1 distribution as a set of ten zip files: base1, base2, edit1, lang1, sys1, util1, source1, source2, source3, and source4. Only the &#8220;base&#8221; files were actually required.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">To install Beta1, you first unzipped the contents of these archives to separate floppy disks. But because the early kernel wasn&#8217;t yet stable, Beta1 didn&#8217;t provide a boot disk to install from. Instead, you had to unzip the installer to your system&#8217;s hard disk and run it from there.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The installer used special files in the installer&#8217;s directory and on each of the floppies to control its behavior. When the installer started up, it first displayed the contents of the <code>OEM.TXT<\/code> file from the installer&#8217;s directory:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>----------------------------------------------------------------------\n\nSTOP!  READ THIS!\n=================\n\nIf you downloaded the FreeDOS *disk sets* in separate zip files,\nfirst make sure that you unzipped the files onto separate floppies\nbefore you run this Install program.  That is, make sure you aren't\ninstalling from base-1.zip, base-2.zip, lang-1.zip, etc.  :)\n\nIf you downloaded the *contents* of each install disk, then you are ok.\n\nAlso, please run the Install program from a directory on your hard\ndisk, and not from a boot floppy, at least in version 1.x.  Otherwise,\nthe Install program will not be able to find the UNZIP program that it\nneeds to extract the distribution packages.  (This will be fixed in\nversion 2.0).\n\n----------------------------------------------------------------------<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The installer then read the contents of <code>INSTALL.DAT<\/code> for the list of <em>disk sets<\/em> in the distribution. Each disk set was marked <code>Y<\/code> for <em>required<\/em> or <code>?<\/code> for <em>prompt the user to install<\/em>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>base: Y\nedit: ?\nlang: ?\nsource: ?\nsys: ?\nutil: ?<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">As the installer processed each disk set, it used matching lines from the <code>INSTALL.TXT<\/code> file to display information about the disk set. These descriptions were usually one or two lines long:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>base: The essential DOS utilities, which reproduce the functionality\nbase: of MS-DOS.\nedit: The free emacs clone, \"freemacs\".  Other COMPLETELY FREE editors\nedit: will be added to the distribution later.\nlang: Free compilers and assemblers.  Also includes some cool BASIC\nlang: programs you can run under BWBasic (included in \"base\".)\nsource: Source code to all the programs in the distribution.\nsys: Various free system utilities, such as system information\nsys: programs and keyboard locking programs.\nutil: Free file and directory utilities.<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Each floppy contained its own list of packages, stored in a file like <code>BASE.1<\/code> for the base1 floppy, <code>BASE.2<\/code> for the base2 floppy, or generally <em>set.n<\/em> for any floppy in a disk set. For example, the <code>BASE.1<\/code> file on the base1 floppy marked each package with <code>Y<\/code> (required):<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>asgn14x: Y\nattr-x: Y\nb1932-x: Y\nbwbas-x: Y\ncdx13-x: Y\nckdsk-x: Y\nclsx-x: Y\ncom072bx: Y\ncomp-x: Y\ncopy-x: Y\ndbg095x: Y\ndeltr-x: Y\ndocs: Y\nfdsk04x: Y\nfdxms-x: Y\nfmt10x: Y\nhelpdocs: Y\nlabel-x: Y\nloadhi-x: Y\nmkdir-x: Y\nmode-x: Y\nmove-x: Y<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The installer read from the matching lines in a <code>.TXT<\/code> file to display information about each package, such as <code>BASE.TXT<\/code> for each of the floppies in the &#8220;base&#8221; disk set. For example, the first few lines in the <code>BASE.TXT<\/code> file on the base1 floppy listed these packages:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>asgn14x: Steffen Kaiser's ASSIGN program, version 1.4.  Allows you to\nasgn14x: assign one drive letter to a different drive.\nattr-x: The ATTRIB program, to view and set file attributes.\nb1932-x: Pat Villani's DOS-C kernel (the FreeDOS Kernel.)  This is\nb1932-x: beta code, but Pat says it is okay to distribute anyway.  It\nb1932-x: is more stable than any previous DOS-C kernel.\nb1932-x: THIS DOES NOT AUTOMATICALLY INSTALL THE DOS-C KERNEL AS YOUR\nb1932-x: DEFAULT OS.  YOU WILL NEED TO RUN THE BAT FILE IN THE KERNEL\nb1932-x: DIRECTORY TO CREATE A BOOTABLE DOS-C FLOPPY.\nbwbas-x: Ted Campbell's ByWater BASIC interpreter.<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If the installer found a <code>.END<\/code> file on the floppy, it knew it had finished with that disk set. Otherwise, it assumed at least one more floppy in the disk set and prompted for the next floppy, then repeated the process until it found a floppy with a <code>.END<\/code> file.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This mechanism made it easy to extend the installer to include other disk sets and more packages for later versions of the distribution, without having to update the program. Here&#8217;s a sample session from installing Beta1:<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"533\" height=\"400\" src=\"http:\/\/www.both.org\/wp-content\/uploads\/2026\/07\/beta1-1.png\" alt=\"white text on a black background: install from what path?\" class=\"wp-image-14383\"\/><figcaption class=\"wp-element-caption\">Installing FreeDOS Beta 1<\/figcaption><\/figure>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"533\" height=\"400\" src=\"http:\/\/www.both.org\/wp-content\/uploads\/2026\/07\/beta1-3.png\" alt=\"white text on a black background: install the editor series?\" class=\"wp-image-14384\"\/><figcaption class=\"wp-element-caption\">Installing FreeDOS Beta 1<\/figcaption><\/figure>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"533\" height=\"400\" src=\"http:\/\/www.both.org\/wp-content\/uploads\/2026\/07\/beta1-6.png\" alt=\"white text on a black background: load the util-1 disk\" class=\"wp-image-14385\"\/><figcaption class=\"wp-element-caption\">Installing FreeDOS Beta 1<\/figcaption><\/figure>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"533\" height=\"400\" src=\"http:\/\/www.both.org\/wp-content\/uploads\/2026\/07\/beta1-7.png\" alt=\"white text on a black background: the install program completed successfully\" class=\"wp-image-14386\"\/><figcaption class=\"wp-element-caption\">Installing FreeDOS Beta 1<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Installing Beta1 didn&#8217;t automatically make your system bootable with the FreeDOS kernel. Instead, you had to create your own boot floppy. At the time, we felt this was the safest option, so you could test FreeDOS without committing your hard disk to always booting from a still-incomplete DOS kernel. To create a boot floppy, go to the <code>DOS\\BIN\\KERNEL<\/code> directory and run the <code>INSTALL.BAT<\/code> file, which will do the manual step to write the kernel boot image to a 1.44 MB floppy disk:<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"533\" height=\"400\" src=\"http:\/\/www.both.org\/wp-content\/uploads\/2026\/07\/beta1-kernel-install.png\" alt=\"white text on a black background: a command to install a kernel on a floppy\" class=\"wp-image-14388\"\/><figcaption class=\"wp-element-caption\">Making a boot floppy<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">You can now boot from this floppy to use the FreeDOS kernel:<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"533\" height=\"400\" src=\"http:\/\/www.both.org\/wp-content\/uploads\/2026\/07\/beta1-kernel-boot-dir.png\" alt=\"white text on a black background: file listing of a boot floppy\" class=\"wp-image-14387\"\/><figcaption class=\"wp-element-caption\">Booting the kernel floppy<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">This early kernel used a multi-step <em>initial program loader<\/em> or &#8220;IPL&#8221; to load the kernel image into memory, before booting the system. That&#8217;s why the directory listing of the boot floppy shows several extra files.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Exploring the Beta1 distribution<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Like the &#8220;alpha&#8221; distributions before it, Beta1 installed its files using a hierarchical structure. Starting at the <code>DOS<\/code> directory (or wherever you installed Beta1) all EXE, COM, and SYS programs were stored in the <code>BIN<\/code> directory. Online help files were in <code>HELP<\/code> and general program documentation was saved in <code>DOC<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Beta1 provided replacements for many of the classic DOS commands, and by this time the programs worked mostly as you&#8217;d expect. Available commands included ASSIGN, ATTRIB, BWBASIC (the <a href=\"https:\/\/www.both.org\/?p=12971\">ByWater BASIC<\/a> interpreter), CDX (a CD-ROM extender like MSCDEX), CHKDSK, COMP, DEBUG, DELTREE, FDISK, FDXMS (a replacement XMS driver, like EMM386), FIND, FORMAT, LABEL, LOADHI (load TSR drivers into high memory, like LH or LOADHIGH), MODE, MORE, MOVE, PAUSE, SORT, SWSUBST (replacing both JOIN and SUBST), TSDK (a RAM disk driver, like RAMDISK), UNZIP, ZIP, as well as our own <code>COMMAND.COM<\/code> shell (contributed by Tim Norman).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Some commands that were usually <em>internal<\/em> commands in classic DOS were actually <em>external<\/em> commands in Beta1. The shell didn&#8217;t support all internal commands yet, so we provided external versions of CLS (plus an extended version called CLSX), COPY, DATE, DEL, MAN (like HELP), MKDIR, RMDIR, TIME, TYPE, VERIFY, and VERSION.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, we still did not have an editor; <a href=\"https:\/\/www.both.org\/?p=12955\">FreeDOS Edit<\/a> (contributed by Joe Cosentino), <a href=\"https:\/\/www.both.org\/?p=7385\">FreeDOS edlin<\/a> (by Gregory Pietsch), and other editors like the <a href=\"https:\/\/www.both.org\/?p=14056\">FED editor<\/a> were added much later. Instead, we provided <a href=\"https:\/\/www.both.org\/?p=12986\">Freemacs<\/a> (by Russell Nelson, similar to GNU Emacs) on the edit1 floppy, with Freemacs extensions including MINT program modes, emulation for 101-key keyboards, EGA support, FORTRAN and LaTeX edit modes, and an integrated spell program.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What runs, and what doesn&#8217;t<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">After installing Beta1, and booting from the FreeDOS Kernel boot floppy, I tested this early distribution with several of my favorite DOS games and applications. It&#8217;s important to note that while the kernel was quite advanced, not all features were implemented yet. Some programs, like the DOOM installer, flatly refused to run. Commander Keen exited with an &#8220;Out of memory&#8221; error. The Wolfenstein 3D installer worked, but the game did not.<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"533\" height=\"400\" src=\"http:\/\/www.both.org\/wp-content\/uploads\/2026\/07\/beta1-wolf-install.png\" alt=\"colorful screen showing the installation of a program\" class=\"wp-image-14389\"\/><figcaption class=\"wp-element-caption\">Wolfenstein 3D installs but won&#8217;t run on Beta1<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">But many other programs worked fine on this old kernel. For example, I copied DOOM from my modern FreeDOS virtual machine, and was able to play a game:<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"533\" height=\"400\" src=\"http:\/\/www.both.org\/wp-content\/uploads\/2026\/07\/beta1-doom.png\" alt=\"first person view of a hand holding a gun in an alien environment\" class=\"wp-image-14393\"\/><figcaption class=\"wp-element-caption\">DOOM runs great on Beta1<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The venerable Lotus 1-2-3 spreadsheet worked great on Beta1. I was able to perform different calculations flawlessly, such as this linear regression:<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"533\" height=\"400\" src=\"http:\/\/www.both.org\/wp-content\/uploads\/2026\/07\/beta1-123-regress.png\" alt=\"spreadsheet program showing a linear regression\" class=\"wp-image-14390\"\/><figcaption class=\"wp-element-caption\">Lotus 1-2-3 runs fine on Beta1<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">I had some troubles running my favorite DOS spreadsheet, As-Easy-As. The application would randomly freeze and crash the virtual machine. Running As-Easy-As with the <code>\/NE<\/code> (no EMS) option didn&#8217;t fix it. However, using the <code>\/NT<\/code> (no turbo keyboard) seems to prevent crashes. After running the application with that command line option, I could use all the regular features of As-Easy-As, although it reported that my freshly-installed shareware copy had already been run 1,376 times:<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"467\" height=\"350\" src=\"http:\/\/www.both.org\/wp-content\/uploads\/2026\/07\/beta1-aseasy-open.png\" alt=\"start-up screen showing &quot;unregistered copy used 1376 times&quot;\" class=\"wp-image-14391\"\/><figcaption class=\"wp-element-caption\">As-Easy-As on Beta1<\/figcaption><\/figure>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"533\" height=\"400\" src=\"http:\/\/www.both.org\/wp-content\/uploads\/2026\/07\/beta1-aseasy-regress.png\" alt=\"spreadsheet program showing a linear regression\" class=\"wp-image-14392\"\/><figcaption class=\"wp-element-caption\">As-Easy-As on Beta1<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">I wasn&#8217;t able to run Microsoft Word 5.5 for DOS. The program repeatedly complained that &#8220;No file handles are available&#8221; despite having <code>FILES=20<\/code> in my <code>CONFIG.SYS<\/code> file.<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"533\" height=\"400\" src=\"http:\/\/www.both.org\/wp-content\/uploads\/2026\/07\/beta1-word.png\" alt=\"error message showing &quot;no file handles are available&quot;\" class=\"wp-image-14395\"\/><figcaption class=\"wp-element-caption\">I couldn&#8217;t run Word for DOS on Beta1<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">However, Word&#8217;s <code>MSD<\/code> program (Microsoft Diagnostics) runs fine and reports that my QEMU virtual machine is a 486, and the operating system is MS-DOS 3.3:<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"533\" height=\"400\" src=\"http:\/\/www.both.org\/wp-content\/uploads\/2026\/07\/beta1-msd.png\" alt=\"diagnostic program showing operating system details\" class=\"wp-image-14394\"\/><figcaption class=\"wp-element-caption\">MSD reports &#8220;MS-DOS 3.31&#8221; on Beta1<\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Try it for yourself<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">There&#8217;s more to explore in the Beta1 distribution. Download this original distribution and install it on your virtual machine. If you use QEMU, I recommend using the <code>isapc<\/code> machine type, which emulates a legacy ISA PC from the 1990s. Use the QEMU monitor to change floppies, using the <code>change floppy0<\/code> command to give it the filename for the next floppy disk image. Here&#8217;s an example showing the output from <code>DIR A:<\/code> of the base1 floppy, then using the QEMU monitor change the floppy to use the base2 floppy before running <code>DIR A:<\/code> again:<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"792\" height=\"698\" src=\"http:\/\/www.both.org\/wp-content\/uploads\/2026\/07\/qemu-change-floppy0.png\" alt=\"3 application windows for the QEMU emulator\" class=\"wp-image-14396\"\/><figcaption class=\"wp-element-caption\">Load a new floppy image with &#8220;change floppy0&#8221;<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Install the Beta1 distribution to take a step back in time to the early days of FreeDOS. As you explore Beta1, keep in mind that this was still an early release. Expect some bugs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, the current version of FreeDOS is quite stable, and I encourage you to try this more modern DOS. Download the FreeDOS 1.4 distribution (2025) from the <a href=\"https:\/\/www.freedos.org\">FreeDOS Project<\/a> website. Or download our test release, updated monthly, and help us test the next FreeDOS distribution. The FreeDOS T2607 (July 2026) test release includes an updated kernel that now supports running Windows 3.1, as well as other improvements.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Take a look back at this important milestone in FreeDOS history<\/p>\n","protected":false},"author":33,"featured_media":4259,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[340,106],"tags":[267,316],"class_list":["post-14397","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-freedos","category-history","tag-freedos","tag-history"],"modified_by":"Jim Hall","_links":{"self":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/14397","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/users\/33"}],"replies":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=14397"}],"version-history":[{"count":4,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/14397\/revisions"}],"predecessor-version":[{"id":14402,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/14397\/revisions\/14402"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/media\/4259"}],"wp:attachment":[{"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=14397"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=14397"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=14397"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}