We've Moved! Just as Gamepedia has joined forces with Fandom, this wiki had joined forces with our Fandom equivalent. The wiki has been archived and we ask that readers and editors move to the now combined wiki on Fandom. Click to go to the new wiki.

We are currently performing an upgrade to our software. This upgrade will bring MediaWiki from version 1.31 to 1.33. While the upgrade is being performed on your wiki it will be in read-only mode. For more information check here.

Starport Nuka terminals

From The Vault - Fallout Wiki
Jump to: navigation, search
 
Gametitle-fo4nw.png
Gametitle-fo4nw.png

This page lists Starport Nuka terminals.

Manager's Terminal

text= Header
Welcome text

Starport Nuka - Management Office

Body

Outbound Communication GH700101

TranscriptVaultBoy.png

To: Peyton Huxley, Executive Assistant to Mr. Bradberton

This is Penning over at Starport Nuka. We're experiencing all sorts of minor control malfunctions with the older-model robots in the Galactic Zone. I'm sending over some of the incident reports. Nothing serious yet, but if Star Control ever loses its connection with these robots, I'm not sure what they'll do.

Personally, I think our hardware is too far behind the software to have Star Control run the whole show right now. I know you don't want to hear it, but we really need to shut down the Galactic Zone and do a major overhaul before we have a catastrophic failure.

Outbound Communication GH700243

TranscriptVaultBoy.png

To: John-Caleb Bradberton, CEO Nuka-Cola Corporation

This is Penning over at Starport Nuka. Sorry to disturb you directly Mr. Bradberton, but we have a bit of a crisis on our hands over here. I'm certain your assistant can fill you in on the details if he hasn't already.

I realize that Project Cobalt has put a lot of our resources on hold, but if we don't get some help soon, this could get out of control. Star Control was never meant to handle this many robots at one time, and we keep being asked to add more and older models to system. Please approve my requisition for new staff and maintenance requests as soon as possible.

Inbound Communication KLK00901

TranscriptVaultBoy.png

From: Ingrid Suvenstein, Starport Nuka Technician

Ryan, Mark and I are tired of fixing these robots and getting them to play nice with Star Control. The new system has put a strain on their control modules, and some of the older models just can't take the extra load. We're behind schedule as it is, and now you want us to chaperone tour groups through Star Control? If you want this stuff fixed quicker, you need to hire more staff or get to the bottom of why our purchase orders keep getting held up.

Inbound Communication KLK00944

TranscriptVaultBoy.png

From: Mark Reisman, Starport Nuka Technician

Look, Penning. I'm about one day away from quitting if you don't get us some real help around here. We've got six units offline again today, and fixing each one takes almost our entire shift. Ingrid and I have been putting in sixty-hour weeks just to keep things from falling apart around here. Look, get it together or I'm walking.

Star Control Mainframe

Note
This is a very complex terminal; its contents have been simplified for easy display.
text= Header

|--==[ STAR CONTROL ]==--|

Welcome text

Systemized Telemetry for Automated Robot Control

Body



Boot sequences that display once upon activating the terminal, depending on the number of cores installed




****** MAINLINK(R) SYSTEM BIOS - V10.2.1.1 ******
COPYRIGHT 2076 ROBCO(R)
LOADER V2.05
EXEC VERSION 57.09
LOAD ROM(1): STAR_CONTROL

************* STAR_CONTROL - V1.1.7 *************
INIT RobCo Data Exchange Protocol V3.11... [OK]
LINK Establishing Mainframe Interlink... [OK]
MOUNT Mounting STAR Cores... [<Token.ValueInt=DLC04GZ_StarCoresInstalled>/<Token.ValueInt=DLC04GZ_StarCoresTotal>] [FAIL]

No Star Cores detected. A minimum of one (1) control core is required to initialize Emergency Operations Mode. Boot sequence aborted.


[No Cores]






****** MAINLINK(R) SYSTEM BIOS - V10.2.1.1 ******
COPYRIGHT 2076 ROBCO(R)
LOADER V2.05
EXEC VERSION 57.09
LOAD ROM(1): STAR_CONTROL

************* STAR_CONTROL - V1.1.7 *************
INIT RobCo Data Exchange Protocol V3.11... [OK]
LINK Establishing Mainframe Interlink... [OK]
MOUNT Mounting STAR Cores... [<Token.ValueInt=DLC04GZ_StarCoresInstalled>/<Token.ValueInt=DLC04GZ_StarCoresTotal>] [OK]
CONNECT Connecting to linked robotics... [FAIL]

Insufficient Star Cores to assert control over linked robotic systems. Emergency Operations Mode may provide limited functionality.


[1 Core or more]





****** MAINLINK(R) SYSTEM BIOS - V10.2.1.1 ******
COPYRIGHT 2076 ROBCO(R)
LOADER V2.05
EXEC VERSION 57.09
LOAD ROM(1): STAR_CONTROL

************* STAR_CONTROL - V1.1.7 *************
INIT RobCo Data Exchange Protocol V3.11... [OK]
LINK Establishing Mainframe Interlink... [OK]
MOUNT Mounting STAR Cores... [<Token.ValueInt=DLC04GZ_StarCoresInstalled>/<Token.ValueInt=DLC04GZ_StarCoresTotal>] [OK]
CONNECT Connecting to linked robotics... [OK]

Completing boot sequence. Please wait...


[20 Cores or more]

These messages display upon repeated returns if defensive protocol was not disengaged






WARNING:
A fault has been detected in the [Defensive Mode] Protocol. Please disable this Protocol and contact a RobCo Enterprise Systems Engineer for assistance.

STAR CORES:
<Token.ValueInt=DLC04GZ_StarCoresInstalled>/<Token.ValueInt=DLC04GZ_StarCoresTotal> Star Cores required for full functionality.

AVAILABLE COMMANDS:


[1-19 cores]





WARNING:
A fault has been detected in the [Defensive Mode] Protocol. Please disable this Protocol and contact a RobCo Enterprise Systems Engineer for assistance.

STAR CORES:
<Token.ValueInt=DLC04GZ_StarCoresInstalled>/<Token.ValueInt=DLC04GZ_StarCoresTotal> Star Cores installed.

AVAILABLE COMMANDS:


[20 Cores or more]

These messages display after disengaging the protocol




STAR CORES:
<Token.ValueInt=DLC04GZ_StarCoresInstalled>/<Token.ValueInt=DLC04GZ_StarCoresTotal> Star Cores required for full functionality.

AVAILABLE COMMANDS:


[1-19 Cores]





STAR CORES:
<Token.ValueInt=DLC04GZ_StarCoresInstalled>/<Token.ValueInt=DLC04GZ_StarCoresTotal> Star Cores installed.

AVAILABLE COMMANDS:


[20 Cores or more]

Tracking Bug Protocol Menu






***** EMERGENCY OPERATIONS MODE *****
Emergency Protocol: Tracking Bug
Status: INACTIVE

Description: Establishes a weak connection to linked robotic systems in the target area, allowing them to be detected and tracked by the user. Once a target has been selected, it cannot be changed.

Select target:


[Inactive]






***** EMERGENCY OPERATIONS MODE *****
Emergency Protocol: Tracking Bug
Status: ACTIVE

The Tracking Bug was set successfully.


[Active]

Selective Shutdown menu (the text is identical, with only the Roman numeral changing)






***** EMERGENCY OPERATIONS MODE *****
Emergency Protocol: Selective Shutdown I
Status: INACTIVE

Description: Connects to all linked robotic systems with the specified firmware and issues an emergency shutdown order, overriding all other commands. Once selected, the target cannot be changed.

Select target:


[Inactive]






***** EMERGENCY OPERATIONS MODE *****
Emergency Protocol: Selective Shutdown I
Status: ACTIVE

The Selective Shutdown was issued successfully.


[Active]


Limited Control menu






***** EMERGENCY OPERATIONS MODE *****
Emergency Protocol: Limited Control
Status: ACTIVE

The Limited Control Order was issued successfully.


[Inactive]






***** EMERGENCY OPERATIONS MODE *****
Emergency Protocol: Selective Shutdown I
Status: ACTIVE

The Selective Shutdown was issued successfully.


[Active]


Defensive Mode menu






Protocol: Defensive Mode
Status: ACTIVE

Description: Engages live-fire defensive mode for all linked robots and turrets. Activating this protocol will require a system reset.

NOTE: A critical fault has been detected. Please disable this Protocol and contact a RobCo Enterprise Systems Engineer for assistance.



[Inactive]






Deactivating Defensive Mode... done.

Initiating System Reset... done.

WARNING:
A critical fault has been detected in the [Defensive Mode] protocol. [Defensive Mode] will be disabled until the fault has been repaired.


[Active]

Display Case menu





Protocol: Display Case Access
Status: BUSY

[Opening]




Protocol: Display Case Access
Status: CLOSED

[Closed]




Protocol: Display Case Access
Status: OPEN

[Open]

System Logs menu
***** STAR CONTROL SYSTEM LOGS *****

Initialize Emergency Operations Mode

This option is only available the first time the player activates the terminal after activating the terminal and reloads the terminal command list

Continue

This option appears each time after installing new cores

View Star Core Network

If less than 35 cores were retrieved
TranscriptVaultBoy.png

Accessing Star Core Interlink... done.

[<Token.ValueInt=DLC04GZ_StarCoresInstalled>] Star Core(s) are currently installed.

A total of [<Token.ValueInt=DLC04GZ_StarCoresNotInstalled>] other Star Cores were detected within range. Isolating locations...

[<Token.ValueInt=DLC04GZ_StarCoresPlayer>]: In the Star Control Chamber
[<Token.ValueInt=DLC04GZ_StarCoresExteriorLeft>]: In the Galactic Zone Grounds
[<Token.ValueInt=DLC04GZ_StarCoresNukaGalaxyLeft>]: In Nuka-Galaxy
[<Token.ValueInt=DLC04GZ_StarCoresTheaterLeft>]: In Starlight Interstellar Theater
[<Token.ValueInt=DLC04GZ_StarCoresVaultTecLeft>]: In Vault-Tec: Among the Stars
[<Token.ValueInt=DLC04GZ_StarCoresBattlezoneLeft>]: In RobCo Battlezone
[<Token.ValueInt=DLC04GZ_StarCoresOutsideLeft>]: Outside the Galactic Zone

If all star cores were retrieved
TranscriptVaultBoy.png

Accessing Star Core Interlink... done.

[<Token.ValueInt=DLC04GZ_StarCoresInstalled>] Star Core(s) are currently installed.

No other Star Cores were detected within range.

Emergency Protocol: Tracking Bug

Galactic Zone Grounds

Nuka-Galaxy

Starlight Interstellar Theater

Vault-Tec: Among the Stars

RobCo Battlezone

Cancel

Emergency Protocol: Selective Shutdown I

Target: Eyebot Firmware

Target: Handy Firmware

Target: Nukatron Firmware

Cancel

Emergency Protocol: Selective Shutdown II

This menu is identical to the Selective Shutdown I menu, except for the inclusion of the following additional options

Target: Protectron Firmware

Target: Assaultron Firmware

Target: Sentry Firmware

Target: Turret Firmware

Emergency Protocol: Limited Control

Target: Eyebot Firmware

Target: Handy Firmware

Target: Nukatron Firmware

Target: Protectron Firmware

Target: Assaultron Firmware

Target: Sentry Firmware

Target: Turret Firmware

Cancel

Protocol: Defensive Mode

Deactivate Defensive Mode

Cancel

Protocol: Display Case Access

Open Display Case

If less than 35 cores are installed
TranscriptVaultBoy.png

Accessing Display Case Control... done.

ERROR: Corrupted control software detected.
Initializing additional Star Cores to bypass corrupted blocks...

ERROR: Insufficient Cores for software bypass.
<Token.ValueInt=DLC04GZ_StarCoresInstalled> Star Cores detected;
<Token.ValueInt=DLC04GZ_StarCoresTotal> required.

Please install additional Star Cores to proceed.

Open Display Case

TranscriptVaultBoy.png

Accessing Display Case Control... done.

ERROR: Corrupted control software detected.
Initializing additional Star Cores to bypass corrupted blocks... done.

Security lock released. Opening...

Close Display Case

TranscriptVaultBoy.png

Accessing Display Case Control... done.

ERROR: Corrupted control software detected.
Initializing additional Star Cores to bypass corrupted blocks... done.

Security lock engaged. Closing...

System Logs

Operating Instructions

TranscriptVaultBoy.png

OPERATING INSTRUCTIONS
Star Control, Build v.1.1.7

The Systemized Telemetry for Automated Robot Control (Star Control) system, developed by RobCo Industries(TM), is a complete solution for corporate clients needing to adminster a large number of robots and defensive systems.

Star Control technology is built on a series of highly redundant, interchangable telemetry modules (Star Cores). At runtime, these Cores establish a radio communications interlink between the Star Control mainframe and the linked robotic systems, allowing the mainframe to coordinate their actions and issue commands irrespective of their underlying operating protocols.

Individual Star Cores may be safely replaced during normal operation. In the event of a major failure, Star Control can still boot into a limited-functionality Emergency Mode if at least one Star Core is present. While the system is in Emergency Mode, all robots and defenses will continue to act on their prior operating instructions. As Cores are replaced, a series of emergency protocols will be progressively unlocked as computing resources permit, allowing the user to react to urgent problems until full functionality can be restored.

For additional sales, service, or technical support, please contact the RobCo Enterprise Solutions division. Thank you for choosing RobCo.

Technician's Log: 8/31/2077

TranscriptVaultBoy.png

Technician's Log - 8/31/2077

Finished the install job for the new mainframe today. Mark and I fired it up for a test run after hours. Seemed to go pretty well. RobCo's communications interlink doesn't play nice with older-model Handys we've got working concessions-- big surprise there-- but I'm still glad we went with their bid over the one from General Atomics. Their 'Director' system is a mess-- single point of failure and all. Star Control may be overkill, but at least it has some redundancy if something does go wrong.

Technician's Log: 9/29/2077

TranscriptVaultBoy.png

Technician's Log - 9/29/2077

It's been almost a month, and Star Control is still working perfectly. That never happens-- big install jobs like this are always a disaster. And we've got military-grade robots running around with live weapons. This thing seems like an accident waiting to happen. But so far, it works as advertised. Color me impressed.

Mark and I have been digging through the control code, and we've verified that the Defensive Mode protocol Admin wanted seems to be in place. If there is a major emergency of some kind, we flip the system into Defensive Mode and use the robots to secure the park. There's no real way to test it; let's just hope it never comes to that.

Technician's Log: 10/22/77

TranscriptVaultBoy.png

Technician's Log - 10/22/2077

The mainframe tours have been a big hit. Lucky us. First we lose our workspace to that ridiculous diorama, and now we have to babysit a bunch of snotty six-year-olds who can't resist pushing all the big glowy buttons.

We're going to start integrating the robots at the junkyard into the system this weekend. I'm not sure if Star Control's interlink will work at that range, but it's worth a shot. This thing keeps surprising me.

Kendell's Log: 2/29/2284

TranscriptVaultBoy.png

Kendell's Log - 2/29/2284

Took us three days, but we finally broke through the rubble around the north gate. Walked right in. No turrets, no combat bots, nothing. The only robot I had to put down was that damned Nukatron that kept trying to sell me a ten-dollar bottle of Nuka-Cherry. Stupid thing wouldn't even take caps.

This here's the real prize, though-- top-of-the-line pre-war tech, still humming along. My girl Tiana says these glowy things are 'redundant', which I guess means we can take 'em. Oughta fetch a good price back in town.

Kendell's Log: 4/11/2286

TranscriptVaultBoy.png

Kendell's Log - 4/11/2286

Colter's gangs took Nuka-Town. We got survivors incoming. I had the boys throw up some defenses, but they ain't gonna last long.

I told Tiana to turn on that Defensive Mode she told me about. She panicked-- said we'd taken too many Cores from this thing; it couldn't handle the reboot. Sent everyone she could find to go strip Cores from the other rides.

The girl means well, but with the gangs breathing down our necks, I gotta do something. What's the worst that could happen?