.ONR File

In the universe of 77Pacer Studios, usually the Main Adventure Series, the .ONR File extension refers to Owner files for a Central Processing Unit (CPU), specifically the type that is installed in a vehicle. The technology of this kind of CPU is modeled after the technology used in the Knight Industries Two Thousand (K.I.T.T.), as well as its predecessor, the Knight Automated Roving Robot (K.A.R.R.). The .ONR file contains data about whoever is assigned as an owner to the CPU, as well as whatever vehicle the device is installed in. The file has a simple sounding but rather complex programming that gives it a special function to keep the CPU in check to make sure that it always remains loyal to the person(s) who are assigned as its owner. While the CPU can have more than one .ONR file, indicating that the vehicle in question would have multiple owners, this would be considered a waste of space, so it would be better recommended to have an .ONR file that has data about the multiple owners of the vehicle.

While the programming can seem to be perfect at first, it does have its fair share of weaknesses. In the event that the CPU sustains damage (mainly the shockwave kind) that causes a glitch in the programming, should the CPU get angry at the owner it's assigned to, there's a chance that it will betray the original owner by deleting the .ONR file that corresponded to the original owner. If the vehicle the CPU is installed in is allowed to run around freely without at least one .ONR file in the CPU's databanks, it will become an indescribably dangerous killing machine within the area it's in, causing a great deal of serious property damage, as well as serious injury or even death to humans. But if it's with another individual, regardless whether or not they are evil and have stolen the car for their own purposes, if the CPU is angry with the original owner, it will delete the .ONR file for the original owner(s), and in its place create a new .ONR file for the "new owner(s)" of the vehicle, indicating that it's now maintaining loyalty to the new owner(s).

Under normal circumstances, the CPU is unable to delete any .ONR files in its databanks due to its loyalty programming being told never to allow the CPU to do this. But if the CPU's anger level towards the original owner reaches a high enough level, it can easily override this programming. So it would be imperative to NEVER do anything to anger the CPU. Although the vehicle with the corrupted CPU can delete and create .ONR files, there's still a file with loyalty to the original owner that's actually part of the CPU's Operating System (OS), referred to as an .LTY file. The contents of the .LTY file include data about loyalty, as well as who is the original owner of the CPU, but it's the .ONR file that allows the loyalty to come into play. If the .ONR file is deleted and or replaced, depending on whether the vehicle is roaming around free unoccupied or is accompanied by at least one person other than the original owner, the corresponding .LTY file will always remain in the CPU's databanks, just sitting there unable to trigger the loyalty to the original owner as a result of the missing .ONR file. Due to the fact that the .LTY file is part of the CPU's OS, the CPU can't delete it, as if it did, it would've rendered itself inoperable. In other words, deleting the .LTY file would've been the CPU version of Seppuku, a form of Japanese ritual suicide.

## History

### Spy Cruiser One Hundred (S.C.O.H.)

Th first vehicle to be operated by Doctor Danno with a CPU installed onboard was a red 2002 Chrysler PT Cruiser, with the CPU giving it the name "Spy Cruiser One Hundred (S.C.O.H.)" in 2005. The CPU was so advanced that it even had files in the databanks that ensured that it maintained loyalty to the owner, in this case Danno himself. Despite this, the CPU wasn't without its flaws, and it was a prototype of the CPUs that would succeed it. When it came to the programming of .ONR files in the databanks of the CPU for SCOH, each .ONR file could only be assigned to one person only, so if there were multiple owners, other .ONR files would've had to be created due to this limitation. Of course, like any computer, the CPU had a hard drive with a limited amount of space. In this case, SCOH's hard drive had a total capacity of 500 Gigabytes, with only 1 Gigabyte being the OS, and the remaining 499 Gigabytes being free space. The .LTY File was 100 MegaBytes, while one .ONR File took up an additional 10 MegaBytes. However, the first .ONR file to be created in the CPU's databanks, "DANIEL\_C.\_S\*\*\*\*I.ONR", would be the only .ONR file that would ever exist in the CPUs databanks for the next 3 years. This CPU took a year for Wimpy of Doctor Danno's Camera Crew to build and program.

Within one month of the ownership of the vehicle, Danno and SCOH went on a rescue mission, which went successful. Though the details of the rescue mission are unknown to this day, what is known however is the fact that on the way home after the mission's completion, a glitch in the GPS navigation system in SCOH's CPU caused the vehicle to veer into a tree and crash into it. While both SCOH in general and Danno were unhurt, the only thing that truly took damage from the impact was the CPU itself. The shockwave damage the CPU sustained from impacting the tree at 35 Miles Per Hour caused a change in SCOH's programming, which resulted in erratic and annoying behavior, including teasing Danno.

Aware of SCOH's corrupted programming that resulted from the shockwave damage sustained from impacting the tree, and to avert any further potential disaster, Danno switched the vehicle's systems to Manual Override, which left the CPU unable to do anything other than speak. Though very annoyed at SCOH's repeated teasing and other verbal antics, Danno managed to drive SCOH all the way back home, where the vehicle was shut down and put into storage until a solution to the programming glitches could be found. Unfortunately, a solution to the programming glitches was never found, so the vehicle would just sat there in storage accumulating dust to the point when all the dust would form a powder like substance, and the gasoline in the gas tank would eventually turn stale. The CPU's personality would turn to very angry as a result of remaining in storage for so long.

Eventually, in May 2008, the Black Thrasher broke into the base of 77Pacer Studios, found the shut down SCOH vehicle, then reactivated and hijacked it, driving it back out of the garage where the vehicle sat for 3 years. The reactivation of the vehicle also triggered the automatic driving systems to reactivate themselves. Due to the gasoline turning stale in the gas tank, the automatic guidance systems in the CPU set a route to the nearest gas station to replace the old stale gasoline with new gasoline. In the meantime, the vehicle relied on its backup electric motor to move, all the while playing the sound of a gas engine.

Just when Black Thrasher was starting to enjoy his new ride, SCOH responded in appreciation to Black Thrasher's positive compliment. Shocked and confused that the car actually spoke to him, the Black Thrasher pulled over, got out of the car, then asked what was going on. It wasn't long before SCOH and the Black Thrasher finally got to know each other and formed a new companionship, prompting SCOH's CPU to finally delete the file "DANIEL\_C.\_S\*\*\*\*i.ONR" and in its place create the file "BLACK\_THRASHER.ONR", showing new loyalty to the Black Thrasher. Now teaming up with SCOH, Black Thrasher got back into the vehicle, which resumed its course to the nearest gas station.

The trip to the gas station however was unsuccessful, mainly due to the interference of Doctor Danno, as well as the rest of the staff of 77Pacer Studios. The 77Pacer Studios Air Force (77PSAF) was able to at least stall SCOH and the Black Thrasher enough for the new and improved Spy Pacer Five Thousand (S.P.F.T.) to be able to stop SCOH by flattening the tires and destroying SCOH's gas tank, prompting SCOH's CPU to cancel the gas station trip and shut down in what would be referred to as "Surrender Mode". Though not shown in the movie *Return of the Black Thrasher*, while in Surrender Mode, SCOH was towed back to base, put back in storage, and shut down once more. To this day, it's presumed to still be in that same storage space, as its destruction is never the least bit hinted in the Main Adventure series.

### Spy Pacer Five Thousand (S.P.F.T.)

The Spy Pacer Five Thousand's CPU was installed into a red 1977 AMC Pacer hatchback. The SPFT CPU itself was essentially an upgraded and improved version of the prototype CPU installed in the Spy Cruiser One Hundred, with many of the improvements being to correct any programming flaws that plagued the programming of its predecessor, as well as being able to withstand any shockwaves from any impacts. Another improvement is that the .ONR file, which in this case had the .ONR2 extension, (to differentiate from the SCOH CPU's .ONR file extension) was upgraded to allow for a profile for a selected group of multiple persons for the same .ONR file instead of the obsolete method of having only one person per .ONR file. Each .ONR2 file was capable of housing up a profile of up to 10,000 people.

There was however one oversight: the functionality of making multiple .ONR files that existed in the programming of SCOH's CPU was also implemented in the programming of SPFT's CPU during the early days of programming and debugging the SPFT CPU in early January 2006, and still exists in the final product to this day. Wimpy originally thought of removing the functionality of creating more than one .ONR2 files, considering that it wasn't needed due to the new .ONR2 file being capable of housing a profile for up to 10K people, but he feared that doing so would've risked seriously corrupting the CPU's programming, so he instead simply left it in the programming and concealed it with the built-in Debug Mode. Due to the fact that the .LTY file extension of SCOH was incompatible with the new OS system of the SPFT CPU to allow for it to communicate with the new .ONR2 file, a new version of the .LTY file extension (in this case was .LTY2) had to be created.

A month after the shutdown of SCOH in 2005, work began on what would become the CPU for SPFT. Later, at one point in early November 2006, Danno at first owned a purple 1968 Pontiac Firebird Trans Am, but unfortunately the CPU was nowhere near complete at that point. Worse, the car's engine overheated due to a faulty thermostat. Unable to find a good enough engine to replace the overheated one, the Firebird was sadly junked before the CPU could be finished in time to be installed in that. Had the CPU been installed in the Firebird, it would've been called the "Spy Trans Am Four Thousand" (S.T.A.F.T.).

Eventually, the red 1977 AMC Pacer Hatchback was obtained in April 2007, and yet the work on the CPU was still unfinished by that point, as it would not be finished until late January 2008. While it took 3 years to build this CPU, considering the improvements that it had over its predecessor, it was absolutely worth all that time. The main reason it took 3 times as long for Wimpy to build the SPFT CPU as it did for the SCOH CPU to build was due to the fact that as mentioned before, construction started by building "another SCOH" CPU with better technology than before, then inspecting the programming and debugging it. The flaws were eventually straightened out on this second device. To add to the improvements, everything in terms of disk space on SPFT's CPU was a heavy upgrade of its predecessor: 2 Terabytes capacity, 100 Gigabytes of which was the Operating System, 1 of which was the .LTY2 file, and each .ONR2 file was 100MB.

Although this device could be maintained and updated, it was hoped that this would mean that the prototype CPU's flaws could also be corrected, but unfortunately that wasn't the case, which would explain why SCOH's CPU wasn't capable of being repaired using data from SPFT's data, because as mentioned before, the SCOH CPU was only designed as an experimental prototype. Apparently the prototype CPU wasn't built with update compatibility in mind. Worse, due to it using outdated file formats, the .ONR2 and .LTY2 file extensions weren't compatible with the OS of the SCOH CPU despite the fact that the SPFT CPU that utilized the .ONR2 and .LTY2 files were built on the exact same basic platform as the SCOH CPU. However, while nobody ever thought of it, the SCOH CPU could be reattached to the old developer station that was used to program it as well as SPFT.

#### **Spy Truck Eight Thousand (S.T.E.T.)**

The CPU for the Spy Truck Eight Thousand was a brand new setup of the basic CPU platform that was created entirely from scratch, and compared to the CPUs of SCOH and SPFT, not only was this CPU easier to program, but it took a LOT LESS TIME to construct (in this case, it took a week to build the base CPU, and another week to program the OS). In terms of disk space, the capacity was incredibly expanded to 100 Terabytes in capacity, with an OS taking up 10 Terabytes, 2 of which was the .LTY3 File. Not only that, the .ONR3 file was 100 Gigabytes. In fact, there were plans to put this CPU model into production due to how easy this device was to build, but that idea was scrapped when it was soon realized how deadly of a weapon a vehicle equipped with an onboard CPU built by 77Pacer Studios could be should it run amok as a result of corrupted data.

One new feature of the STET CPU had was that this new device was now capable of truly knowing right from wrong, and really admitting to seeing the error of its ways. Not only that, the .LTY file (which in this case used the .LTY3 file extension due to incompatibility with SCOH's .LTY or SPFT's .LTY2 file extensions) was now able to create a backup of the .ONR files (using the .ONR3 file extension in this case) just in case the CPU deleted them out of anger. Despite the advantages of the STET CPU had over the SCOH and SPFT models, it was just nearing 100% completion by the events of the *Revenge of the White Thrasher* series. By that point, Wimpy had the project so classified and top secret that even Doctor Danno himself was unaware of the vehicle's existence, and was getting so close to having the project finished when the White Thrasher broke into the base of 77Pacer Studios, stole the STET vehicle, and attacked the Treehouse Base 3000 All that was needed to be done to mark the official completion of the CPU was to test run it. So far, this CPU's programming is the closest 77Pacer Studios ever been to actually having a vehicle with a CPU that was absolutely flawless.

The STET CPU had a restraining bolt mounted on the CPU that always kept strict loyalty to whoever was driving it. This device worked sort of like a "mind control device" for the CPU. The restraining bolt was to remain on the CPU until testing was completed. When the White Thrasher stole the vehicle, the restraining device caused the CPU to stray onto the path of evil, showing loyalty to the White Thrasher due to the fact that she was the one in the driver's seat. Due to the fact that the CPU strayed onto the path of evil, it deleted the file "77PACER\_STUDIOS.ONR3" and in its place created the new file "WHITE\_THRASHER.ONR3". This triggered the file "77PACER\_STUDIOS.LTY3" to generate a duplicate of the .ONR3 file that was deleted by the CPU. Unfortunately, despite the new file's creation, it couldn't be utilized while the file that triggered loyalty to the White Thrasher was still in use. Unlike the programming of the CPUs of SCOH and SPFT, which allowed for multiple .ONR and .ONR2 files to be created in their databanks, respectively, STET's CPU normally couldn't allow for the use of multiple .ONR3 files at once in its databanks except through debugging purposes (in this case, this was allowed through means of the restraining bolt). Instead, it was designed to handle using only one .ONR3 file in the databanks. While the CPU's hard drive could handle having multiple .ONR3 files exist in the databanks at once, only one .ONR3 file could be used at a time. Because of this, the backed-up .ONR3 file wasn't able to allow the loyalty to 77Pacer Studios to come into play until the CPU's programming ceased usage of the .ONR3 file that triggered loyalty to the White Thrasher, which occurred when the CPU betrayed the White Thrasher.

Despite the strict programming of the restraining bolt, it had a very short lifespan of 6 hours and needed recharging, therefore would shut down as soon as its battery died. Luckily, the STET CPU was able to overcome the device as soon as the restraining bolt's battery died, allowing it to see the error of its ways and betray the White Thrasher by ejecting her out of the driver's seat. Following this, STET instructed Danno and SPFT to destroy the restraining bolt, which is exactly what they did. STET soon eliminated the file "WHITE\_THRASHER.ONR3" from its databanks, thereby allowing the backed-up file "77PACER\_STUDIOS.LTY3" to finally come into play. This all resulted in the STET CPU showing loyalty not only to Doctor Danno himself, but also to everyone who works for 77Pacer Studios.

## Real life .ONR and .LTY file extensions

Here's information about the real life .ONR file, as well as information about the real life .LTY file. However, as of yet, there's no information about real life versions of the following file extensions:

1. .ONR2 (Owner file extension used in the Spy Pacer Five Thousand's CPU databanks)
2. .ONR3 (Owner file extension used in the Spy Truck Eight Thousand's CPU databanks)
3. .LTY2 (Loyalty file extension used as part of the Operating System of the Spy Pacer Five Thousand's CPU)
4. .LTY3 (Loyalty file extension used as part of the Operating System of the Spy Truck Eight Thousand's CPU)

Even if the other 4 fictional file extensions did exist, they will not work in the CPUs of SPFT (.ONR2 and .LTY2) or STET (.ONR3 and .LTY3).