MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Remem",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "27": {
                "pageid": 27,
                "ns": 0,
                "title": "Recovering an Unresponsive Laptop",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "Every once in a while, someone comes to the TRS-80 Model 100 mailing\nlist asking how to recover a laptop they bought off ebay that is\nunresponsive to the power button.\n\n== Clear the RAM File System ==\n\nAlthough the Model T laptops use standard AA batteries, understand that there is an internal battery soldered to the motherboard that maintains power to the RAM even when the main batteries are dead or removed.\n\nOften with units that have sat unused for awhile these problems occur:\n\n* the nicad is drained\n* the RAM is in some random state\n* the contrast knob is in some random state\n\nYou need to resolve all three, but you need to do it in the right\norder. Almost always you can recover a Model T without resorting to\nmore serious troubleshooting.\n\n# Leave the laptop plugged in to the wallcube overnight with Memory Power switch on, and the power off. I don't think it matters whether you use good AA's or the wallcube at this point.\n# Let the unit sit with the Memory Power button off and no plug or other cables connected or batteries in the battery compartment for about 15 minutes in order to clear the RAM.\n# Turn the memory power switch back on, reinstall the AA batteries and/or connect the power cable\n# With the power-button ON, hold down Ctrl-shift-break simultaneously, and hit reset button to clear the RAM\n\nNow fiddle with the contrast knob. Hopefully you will see the normal Model 100 main menu.\n\n== Check the Display ==\n\nIn rarer cases, the problem is a bad display, or problematic (internal) display connection. If the \"clear RAM\" steps above do not resolve the issues, the display is the next thing to check.\n\nTo diagnose this problem,\n# Perform cold-boot (CTRL-BREAK-Reset)\n# Hit the Enter key\n# Type \"beep\" (without quotes) and hit Enter again\nThe machine will make a beep sound if it is actually working (meaning it has a bad LCD or bad LCD connection). Your recourse at this stage is to find a replacement display. Club100 or another community member may be able to help you.\n\nIf it doesn't work you could have multiple problems, including a bad display, bad keyboard, or a problem with the mainboard.\n\n== Otherwise ==\n\nIf none of the steps above lead you to a resolution, then more serious troubleshooting begins. Head over to the Model 100 mailing list (you can subscribe at [http://club100.org/list.html Model 100 Mailing List] )\n\n[[Category:Model T Hardware Hacking]]"
                    }
                ]
            },
            "70": {
                "pageid": 70,
                "ns": 0,
                "title": "Relocating Loader (RLC) Format",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "== What is RLC ==\n\nThe Model 100 uses an 8085 CPU. This CPU does not support position independent\nmachine code, at least in any traditional sense.\n\nAlso, the Model 100 has no built-in support for transferring binary machine\nlanguage files over the serial port.\n\nPresumably for these reasons, someone created the RLC format. RLC is a representation of an 8085 machine\nlanguage program that is relocatable and 7-bit clean.\n\nThere are many programs in the Compuserve Model 100 SIG archive, for example, that are formatted\nas RLC files.\n\n== Format ==\n\n=== Overview ===\n\nRLC is an ASCII base-16 representation of an 8085 machine language\nprogram. Unlike traditional hexadecimal, however, it uses the ASCII characters\n<pre>0123456789:;<=>?</pre>\nIt starts with a header, followed by the body, and ends with a\nchecksum. Whitespace is permitted, and most RLC files seem to keep the data\nless than 128 bytes per line.\n\n=== START ===\n\nOne value must be supplied at load time which does not appear\nin the RLC file: the START address. START is\nwhere the user wants to locate the relocatable image. The first field in the body\nwill be poked into RAM starting at START. Note that there must be sufficient space\nCLEAR'ed at START to load the program.\n\n=== Header ===\n\nThe first line starts with (in ASCII format) the number of bytes in the RLC\nfile, followed by the offset within the image to the entry point.\n\nThe numeric values are space separated. For example, here is the first line of\nan RLC file coding for a 7387 byte image, whose entry point is the first byte\nof the image.\n\n<pre>\n7387  0\n</pre>\n\nIt is not clear whether the header needs to be on its own line. It is also\nunclear whether the first line needs to start with a space.\n\n=== Body ===\n\nThe body of the RLC file is a sequence of fields and whitespace.\nWhitespace is generally needed just to separate lines.\n\nThe two types of fields are octets and relocation offsets.\n\n==== Octet ====\n\nAn octet is a two-ASCII-character, base-16 representation of a byte. The high nibble appears first.\n\nNo separator between octets is required.\n\n==== Relocation Offset ====\n\nA relocation offset is represented by an '@' sign and followed by a\nbig-endian, base-16 representation of an address to be relocated.\n\n<pre>\n@035>\n</pre>\n\nIn hexadecimal, this would represent the offset 0x035E, or 862 in decimal.\n\nIn order to format as 8085 binary, this is added to the user-requested START\naddress for the image and formatted in little-endian byte order (least\nsignificant byte first).\n\n=== Checksum ===\n\nThe RLC file ends with the checksum in decimal format.\n\nThe checksum is the arithmetic sum of all offsets and octets in\nthe image. It is at least a 32-bit integer.\n\nIn the examples I have seen, it occurs on its own\nline and is preceded by a space.\n\n[[Category:Model T Developer Reference]]"
                    }
                ]
            }
        }
    }
}