Geordi authorizes Data’s memory purge
Plot Beats
The narrative micro-steps within this event
Geordi assures Riker that they have initiated a memory purge to restore Data and the computer to their original states, estimating a few hours for Data and another hour or two for the computer.
Who Was There
Characters present in this moment
Calm and unconcerned, with a cheerful demeanor masking the underlying malfunction
Data sits by an engineering console with his head panel open, speaking with a sporadic Texan accent and tipping an invisible hat. He explains that parts of his memory structure have been replaced with recreational database information about the 19th century American West, and he assures Commander Riker that the issue will be resolved in time for supper.
- • Cooperate with Geordi's diagnostic examination
- • Report the nature of his memory corruption to Riker
- • Reassure Riker that the problem is under control
- • He believes his memory structure has been compromised but that the memory purge will restore it
- • He believes the situation is manageable and routine despite his altered speech
Focused and professional, with a hint of concern but confident in the corrective measures
Geordi examines Data's open head panel at an engineering console, analyzing the extent of the memory corruption. He confirms to Riker that Data's personality subroutines have been overwritten by files from the computer's recreational database, specifically about the 19th century American West. Geordi reports that he has initiated a progressive memory purge to restore Data's programming and also a purge on the computer's recreational database.
- • Diagnose the root cause of Data's corruption
- • Initiate memory purge procedures to restore Data and the computer
- • Keep Riker informed of the situation and estimated repair time
- • He believes the memory purge will restore Data to normal within a few hours
- • He believes the corruption is confined to recreational database files and is manageable
Concerned but composed, showing confidence in Geordi's assessment and actions
Riker enters Engineering and approaches Data and Geordi. He asks Geordi for a status report on Data's condition. After learning that the corruption stems from the neural interface experiment and that memory purges are underway, Riker nods in acknowledgment and turns to leave, indicating his acceptance of the plan and the urgency of the situation.
- • Assess the severity of Data's malfunction
- • Receive an update on corrective actions
- • Ensure the situation is under control before resuming other duties
- • He believes Geordi and Data are competent to handle the technical issue
- • He understands the potential implications for the holodeck crisis but trusts the purge will resolve it
The ship's computer is not physically manifest but is discussed as having its recreational database corrupted by the same neural …
Objects Involved
Significant items in this scene
Data’s head panel, removed to expose his intricate circuitry, serves as the physical access point for Geordi’s diagnostics and the memory purge. Its open state symbolizes Data’s vulnerability—his mind and identity laid bare, corrupted by Wild West subroutines. Geordi’s hands hover over it as he initiates the purge, his fingers tracing the connections that will either restore Data or erase him. The panel’s exposed circuitry glows faintly, a visual metaphor for the fragile balance between logic and anachronism in Data’s fractured identity.
Geordi’s Engineering Diagnostic Console hums with activity as he taps panels to launch Level Two diagnostics of the ship’s computer core. Screens flicker with scans of corrupted subroutines, tying Data’s memory issues to the broader system failure. The console becomes the hub of the crisis, its mechanical precision contrasting with the anachronistic chaos of Data’s Texan drawl. Geordi’s commands initiate the memory purge, its progress tracked on the console’s displays—a race against time to restore Data and the ship before the holodeck’s doppelgängers cause irreversible damage.
Organizations Involved
Institutional presence and influence
Starfleet’s protocols and resources are implicitly at play in this scene, though not directly represented. The memory purge initiated by Geordi is a direct application of Starfleet’s technical expertise and emergency response procedures. The urgency of the situation reflects Starfleet’s commitment to crew safety and ship integrity, even in the face of experimental mishaps. The organization’s influence is felt in Geordi’s methodical approach, Riker’s strategic oversight, and the expectation that the crisis will be resolved swiftly and efficiently.
Narrative Connections
How this event relates to others in the story
Within this episode
"Geordi and Data initiate a memory purge to restore Data and Holodeck's computer to their original states, culminating in Picard stating that Data has been restored to normal function after Worf ends the sim."
Worf terminates the corrupted simulationAcross episodes
"'Rascals' shows Picard formally handing command to Riker during a crisis. In 'A Fistful of Datas,' Riker again takes direct action against a corrupted senior officer (Data), authorizing a memory purge—escalating his intervention from command delegation to technical override."
Picard formally transfers command to Riker"In Episode 8, an external energy entity causes sudden physical collapse and system malfunctions. In Episode 608, the threat becomes internalized: Data's memory is corrupted from within by holodeck programming, requiring a memory purge to restore order—a more insidious, psychological form of malfunction."
Worf’s Sudden Collapse and Emergent Medical Crisis"Data's corrupted personality in Episode 8 (Texan drawl, altered speech) foreshadows his deeper ethical concerns about artificial life in Episode 9 (sentience of exocomps). Both events highlight Data's altered state of mind due to external interference and his focus on ethical dilemmas."
Exocomp proves sentience through deception"Data's earlier behavior as an authority figure (despite corruption) in Engineering extends to his defiance of Riker's orders in the Transporter Room in Episode 9. His willingness to lock out systems (first his own neural interface, then the transporter) reflects a continuity in his assertiveness despite external compromises."
Data locks transporter to halt exocomp deployment"Data's earlier corruption (Texan drawl, altered speech) in Engineering escalates into deliberate defiance of Riker's orders in the Transporter Room in Episode 9. This shows an escalation in Data's agency and his willingness to challenge authority."
Data locks transporter to protect exocomps"Both episodes feature Data in a position where his actions are dictated by corrupted or compromised systems. Episode 8 shows Data physically corrupted by an external program, while Episode 9 shows him ethically conflicted by an external force (Farallon, circumstances)."
Riker and Data compromise on exocomps' autonomyPart of Larger Arcs
Key Dialogue
"DATA: ((to Riker, Texan accent)) Howdy, Commander."
"GEORDI: We've initiated a progressive memory purge to restore Data's programming to its original state. He should be back to normal in a few hours."
"DATA: ((normal voice)) That's right, partner."