Minoriko's Guide to the Console

This guide instructs on how to navigate the Administrator Console in Uplink, with screenshot references on the function of each command.

Introduction - The Command Prompt

We all know batch files are fun. Any smart worker that uses a computer is bound to have a few of these to make trivial startup tasks easier. In Uplink, some of our favorite commands from the Windows and Linux command prompts return for use in the hacking of several systems.

Welcome to Minoriko's (Me-nori koh) Guide to the Console! This guide will brief you on what you will need to be able to efficiently use such a tool. Follow me!

Pre-Usage Requirements

Before trying to figure out how to get into the console and use it, you must first be able to get into the system. For general instructions on how ot get into a "Late-Game ISM", or an Internal Services Machine with a Proxy and a Firewall that disavows you upon completion of a passive trace, or a Central Mainframe, check out my Guide to Missions: [link]

For instructions how to get to a LAN's console, check out my Guide to Local Area Networks; http://steamcommunity.com/sharedfiles/filedetails/?id=221591422&insideModal=1

To be able to actually use the Console though, you don't need any extra tools or hardware. You can even use it with a stock GatewayALPHA if you have to.

To show off what you can do with the console, I will be showing how to destroy a Central Mainframe and how to run Revelation. Both require the console, partially or as a whole, to complete. Both methods will use the way that requires it as a whole.

Destroy a System

Note: This guide starts from the Main Menu of the PDR-Net Central Mainframe.

After breaking past all of the security, you will arrive at the Main Menu. Obviously, you are after the console. Enter it.
Inside, you will be greeted with the command prompt we all love. Under the username 'Valid', you have absolute access to every command available. Here's a zoom-in on the help screen:
Here's a run down on what every command does:

• help [command] - Prints the specific help tip revealed (ex. "help cd dir" would state 'changes directory to 'dir')
  
• dir - Prints all the items in a directory (ex. 'dir sys' would reveal boot.sys, kernel.sys, and os.sys)
  
• cd dir - Changes the target of console commands. (ex. 'cd usr' will change the directory to 'usr', or the file server, so you can now delete files)
  
• run [file name] - Only in the 'usr' directory, you can use this to run files on the system. (ex. 'run revelation' will run the file "Revelation" on the system.)
  
• delete - What do you think? (ex. Using 'delete' after using 'cd usr' will delete every file in the 'usr' directory)
  
• shutdown - Shuts the system down and instantly restarts it.(ex. Using 'shutdown' after deleting the 'sys' directory will cause the system to not be able to restart, and disconnects you)
  
• disconnect - Ends your session with the system, yielding a 'Connection terminated by remote host' screen. This is not an active trace. (ex. When you're done with a Destroy Mulitple Files mission, it's easier to type 'disconnect')
  
• exit - Returns you to the main menu. (ex. When you have forgotten to disable the firewall, simply type 'exit' and go to security in a Late Game ISM)

To destroy a central mainframe, you need to know this set of commands in this order. They can all be typed at the same time, one after another, and you do not have to wait for one process to end before starting another. Be careful and make sure that you have deleted all three directories before running the shutdown command!

• cd usr
  
• delete
  
• cd log
  
• delete
  
• cd sys
  
• delete
  
• shutdown

Here's what they look like in use.
Remember that you can only use the delete command with a directory specified. Using the delete command is the equivalent of running over each file with a File_Deleter v1.0.
After all the files are deleted, the prompt will let you know.
Same warning as above. Using the delete command is the equivalent of running over each file with a Log_Deleter v1.0. This step isn't required, and the stand-alone game mod Onlink discourages it, giving each system an obscene number of logs.
Same warning as above. The delete command will prevent the system from restarting after running the shutdown command. It will not cause the system to fail until you have shut it down, however.
After all of this is done, type 'shutdown' and the system will successfully shutdown. However, when trying to load boot.sys and kernel.sys, it will be unable to find them and disconnect you. This is not an active trace. After this is done, you will be unable to connect to the Central Mainframe until the news article is released.

Run Revelation

Note: This section assumes you have read the above section.

Connect to the system you want to destroy with Revelation. We will be using the PDR-Net Developments Internal Services Machine. Go to the File Server.
Copy Revelation from your memory banks with your File_Copier v1.0,
And paste it into the File Server. There must be 3Gqs of open space. If there isn't, use your File_Deleter until there is.
After Revelation is copied, go to the Console in the Admin Menu.
Run the program, and you will be disconnected.

Running a program doesn't always disconnect you. Running another program, such as RevelationTracer, will resolve in the command prompt and then give you the option to type another command, exit, or disconnect.

Conclusion

I didn't really know anything about command prompt before playing this game. After learning it, however, I noticed that some of the commands do work in command prompt. I wasn't stupid enough to use them, but you can indeed change directories with 'cd' and use a 'del' command to delete. After this, I started making my batch files for making opening a few links to some web pages I use for workstuff easier.

Just another gift to our lives from Uplink. Thank you for reading Minoriko's Guide to the Console.

[Aurora Yukihime]

^^~

[Username Unavailable]

Just want to throw this out there, you're awesome for making all of these guides for Uplink, I always refer back to them when I need help on something.

[Aurora Yukihime]

I'm pretty sure any functioning OS terminal is better than the Uplink terminal. :p Hell, I'd argue a certain visual novel's terminal is stronger. Ahaha~

[Jmcgee1125]

Linux terminal > Windows terminal.

>>>>> Uplink terminal

[Harokai]

You brought me from my Commands Discussion. My prior experience with Hacknet was really enjoyable, it had HUD and everything could be done with a mouse. But the Terminal was always on the side, and actually there is a part of the game where you lose the hud, and need to manage only in the terminal.
I played basically using commands. Finished. And tried this Uplink.

If we could actually manually hack on Deus Ex (the first one) we would be playing Uplink. But I was kinda deceived by my own lack of know-how, Uplink looks like a hacking puzzle game, where you get a arsenal of automatic hacking softwares and just use them. Like the File_Deleter, why can't I just /cd bin -> rm * -> cd .. -> disconnect or /cd bin -> delete all -> cd ..

Soo that's what I want to know, can I play Uplink using only commands? Like Run example.exe which will hack something and show the files, then I search the files using commands, and manually delete the logs.

Sorry, long post, didn't know how to explain...

[Aurora Yukihime]

Yes.

[VoidTheWarranty]

ok but if you do you do (cd log) enter then delete

[Aurora Yukihime]

There is, but it is for your purposes useless and slow. Deleting logs on the target computer is unnecessary as they will have already been traced through upon the first few seconds of an active trace (see HUD_MapTrace). You only need to remove InterNIC logs as your first hop.

[VoidTheWarranty]

is there a comand that will delete the logs?

[VoidTheWarranty]

thanks