::GTX::> Frequently Asked Questions

GioTux is a single .bat file that turns Command Prompt into a themed, Linux-flavored shell. When you launch it, it boots like a small OS — mounting a "filesystem," loading "drivers," dropping a custom color theme, then expanding to fill the screen — and lands you on a ::GTX::> prompt.

There's no virtual machine and nothing is replaced behind the scenes. It's still your real Command Prompt, running real commands against your real files and processes underneath the theme.

It's a working shell, not just a paint job. Commands like ls, cd, cat, grep, find, ps, kill, ipconfig, and df all run against your actual system — they list real files, kill real processes, and read your real network config.

Windows only, since it's built entirely out of batch scripting plus a bit of PowerShell for extras (system info, the fullscreen switch, secure password prompts). Both come standard on any modern Windows install — nothing extra to install for the core shell.

Type exit. If you're in admin mode or DOS mode it drops you back to the normal prompt first; typing it again (or from the normal prompt) logs you out cleanly and closes the window. shutdown is a different, much more serious command — see below.

The core set covers everyday file work: ls / list (and dir for your current path), pwd, cd, mkdir, rmdir (add -r for non-empty folders), touch, rm (also supports -r), cp, mv, and cat.

On top of that there's grep [text] [file] to search inside a file, find [name] to search by filename from the current directory down, and history to see what you've typed.

Yes — nano or vi both open a bundled editor for the file you name. It needs a nano.exe sitting in a nano\ folder next to GioTux; if it's missing, GioTux tells you instead of failing silently.

whoami, hostname, date, and uptime give you the basics. ps lists running processes and kill [PID] stops one. df shows disk space, and ping [host] / ipconfig cover networking.

ginfo is the standout: a full-screen dashboard showing OS, hostname, terminal, user, CPU, GPU, and memory, plus a live ANSI color test — press ENTER to return to the shell.

open [file or program] launches it with whatever app Windows has set as the default — same as double-clicking it in Explorer.

A tiny scripting format GioTux interprets line by line. It supports echo, cls, title, color, wait, pause, cowsay, set (variables), calc, random, input, conditional if statements with goto, and exit — enough to build a small branching program, not just a script that prints top to bottom.

Run one with run [appname] (or just type the app's name directly), and see everything installed in the current folder or next to GioTux with apps.

Drop a batch-based game directly into a games\ folder that sits next to GioTux.bat — GioTux creates that folder automatically if it doesn't exist. Then run it with game [filename]. It launches in its own separate console window, so it never touches GioTux's own shell, and it can only ever point at files that live directly inside games\ — no paths, slashes, or drive letters allowed in the name.

Real system-level controls, gated behind a confirmation screen: restarting or shutting down the computer, locking the workstation, listing users, starting/stopping services, toggling the firewall, flushing DNS, resetting networking, kicking off a Defender scan, opening Windows Update, cleaning temp files, opening Event Viewer, forcing a Group Policy update, refreshing environment variables, checking disks, running sfc /scannow or DISM's RestoreHealth, and managing file ownership/permissions.

Type admin to unlock it (after acknowledging a warning screen), or run admin help any time to see the full command list.

It's built to make that hard. Entering it always shows a warning screen you have to explicitly accept, and if you've set a passcode (see below), that's required too. Individual destructive actions — like shutdown, disk repairs, or removing a passcode — ask for a separate confirmation on top of that. Nothing fires without you saying yes at least once, usually twice.

Yes — admin setpass sets a password or PIN. It's encrypted with Windows' own Data Protection API and tied to your specific Windows user account, so the saved file can't be read or reused by anyone else, even on the same machine. The file is also locked down (hidden, read-only, delete-denied) and can only be changed or removed through admin setpass / admin removepass while already in admin mode.

You get three attempts. Get all three wrong and GioTux locks you out of admin mode for that session — no bypassing it from the shell.

Yes. Typing adb with no arguments drops you into a dedicated ADB/Fastboot console with its own prompt and help screen — commands like devices, shell, install, uninstall, push, pull, reboot, and logcat, plus fastboot-prefixed commands for flashing partitions, reading bootloader variables, and rebooting. You can also run a single command directly with adb [args] without entering the full mode.

It looks for platform-tools in C:\platform-tools; if it's missing, GioTux tells you and opens the official Android developer download page.

cmd switches you into a real, unmodified black-and-white console — genuine DOS-style Command Prompt — while GioTux's own commands (ls, ginfo, admin, etc.) keep working alongside whatever native Windows commands you run. Typing exit from there brings back the themed prompt. It's a safety net for when you need the unmodified console without leaving GioTux entirely.

gui launches a companion Python desktop app (giotux_gui.py) that's expected to sit next to GioTux.bat. It requires Python to be installed and on your PATH — GioTux checks for both and tells you plainly if either is missing rather than failing silently.

customize walks you through picking a background and text color from the standard 16-color console palette, and the choice is saved permanently to a small config file in your user profile — it's restored automatically every time you boot GioTux. Run customize default to reset back to the classic light-green-on-black look.

• cowsay [text] — an ASCII cow says whatever you typed
• fortune — a random developer-flavored fortune cookie
• matrix — ambient falling-character rain in the terminal (Ctrl+C to stop)
• sudo [command] — a harmless, joking "permission granted" wrapper
• hack [target] — a fake, harmless "breach sequence" for laughs

Yes — there's a secret easter egg triggered by a specific sequence typed at the prompt. We're not going to spoil it here. If you find it, you'll know.

Typing exit from the normal prompt logs out cleanly. The only thing that persists between sessions is the small color-preference file mentioned above (and, if you've set one, the encrypted admin passcode file) — both live quietly in your user profile.

No. The real shutdown command and admin mode's restart/shutdown subcommands all require you to type an explicit confirmation before anything happens. Nothing destructive fires without you confirming first.

No — the core shell works fully offline. A couple of specific commands reach out to the network on purpose: ping (obviously), the ADB download link if platform-tools isn't found, and the hidden easter egg's final step, which fetches a small ASCII animation if curl is available.