Skip to content

About

Play your whole Xbox 360 library from your PC or NAS, straight from Aurora, without filling the console's drive, even with 2,300 games. Open-source NetISO server for RGH, JTAG and BadUpdate: ISOs, extracted games and GOD as virtual discs, per-game launchers Aurora scans as real titles (art, TUs, DLC), Guide stays working. Windows or Docker.

Resources

Stars

1 star

Watchers

0 watching

Forks

Repository files navigation

NetDisc360: network games for homebrew Xbox 360

Play your whole Xbox 360 library from your PC or NAS. Every game shows up in Aurora as if it were installed, without filling your Xbox's hard drive.

Download the latest release Tests Tests on the dev branch Runs on Windows or Docker MIT license

Quick start  ·  Install guide  ·  Docker  ·  Troubleshooting  ·  More homebrew

The NetDisc360 dashboard: 13 games served, two consoles each playing a different game at 24 MB/s together, and a chart of the game data sent to each console over the last two minutes
The dashboard on your PC or NAS: your games, every console and what it's playing, and how fast each game streams.

Keep your games on your PC or NAS and play them on your Xbox 360 just like installed games. Each one appears in Aurora with its name, cover art, title updates and DLC; pick it and it starts.

  • Your Xbox's drive stays free. The games stay on your PC or NAS. The console keeps only a small launcher and Aurora's cover art for each one (about 3.3 MB in all), so even a 20 GB drive holds about 3,700 games, and 2,300 games take about 7.5 GB instead of many terabytes. See How many games fit.
  • Set it up once. Start NetDisc360 on your PC, choose your game folders, and that's it. New games show up in Aurora by themselves and removed ones disappear. It can start with Windows, and on a NAS it runs in Docker.
  • Every console in the house. Several Xboxes can play from the same library at the same time, and the dashboard shows what each one is playing.
  • Every kind of game copy. ISOs, extracted games and Games on Demand, from as many folders as you like. Nothing to convert or copy.
  • Multi-disc games just work. Each disc gets its own tile, and when a game asks for its next disc, NetDisc360 puts it in for you. A game with an install disc, like GTA V, offers to install it first.
  • Feels like the real thing. A loading screen you can cancel with B, a clear message when something is wrong, and the Guide keeps working in your games.
  • Faster than the disc. With a gigabit USB network adapter, games read at up to about 26 MB/s, where the console's own DVD drive manages about 16 MB/s at best and NetISO on its own about 7 MB/s.

The dashboard as two consoles connect: new games are added to each console's Aurora, then one console starts Halo Reach while the other plays Gears of War 3 A game starting on the Xbox: the NetDisc360 logo, then the loading screen's four steps, Server, Mount, Disc and Start
In action: two consoles get their games and play at the same time (left), and a game starts on the Xbox (right).

For the homebrew crowd. NetDisc360 is an open-source NetISO server that replaces netiso-srv, for any modded 360 with DashLaunch and Aurora: RGH, JTAG, or a stock console with BadUpdate or ABadAvatar. Extracted games and GOD packages are served as virtual discs, so nothing gets converted to ISO. Each game gets a small launcher XEX with the game's own Title ID and Media ID, so Aurora scans it as the real game and fetches its art, title updates and DLC itself. The DashLaunch plugin, NetDisc360.xex, is the disc drive itself: open-source code in place of cOz's closed NetISO.xex, so you don't need that plugin any more. It takes over \Device\Cdrom0, reads 64 KB or more per request with several requests in flight (NetISO asked for 4 KB and waited for each), reconnects and remounts when the network blips, never kills the Guide, and answers a game's XSwapDisc by mounting the other disc. One exe for Windows with a web dashboard, or a Docker image for Linux and NAS. How it works has the details.

NetDisc360 on your PC or NAS gives Aurora a tile for each game over Aurora's FTP, and streams the game disc to the Xbox over NetISO as you play

Best with NetUsb360. It makes a gigabit USB network adapter work on the Xbox, whose own network port is 100 Mbit/s, at most about 12 MB/s. See Speed and More Xbox 360 homebrew.

Contents

Quick start

You need a modded Xbox 360 with DashLaunch and Aurora, and a Windows PC or a NAS with your games on the same network. What you need links to each of them.

  1. Download NetDisc360.exe and NetDisc360.xex from the Releases page.

  2. Copy NetDisc360.xex to your USB drive, add a text file NetDisc360.ini next to it with the line server= and your PC's IP address (for example server=192.168.1.20), and load the plugin in launch.ini:

    [Plugins]
    plugin1 = Usb:\NetDisc360.xex
  3. In Aurora's settings, turn on the FTP server and add the scan path Hdd1:\NetDisc360\Games with depth 1.

  4. On the PC, start NetDisc360.exe and add your game folders on the dashboard that opens in your browser. On Linux or a NAS, run it with Docker Compose instead: get docker-compose.yml and .env.example, rename .env.example to .env and fill it in (see Quick install with Docker Compose), run docker compose up -d and open http://<its address>:8360.

  5. Reboot the console. Within a minute or two your games show up in Aurora's game list. Pick one and play.

Install goes through each step in detail, and Docker has every setting. To load games as fast as your network allows, see Speed.

What you need

NetDisc360 brings the PC side and the console plugin that ties it to Aurora. The rest comes from other homebrew projects, linked here.

On the console

  • A modded Xbox 360 on the same network as your PC. RGH and JTAG consoles work, and so do stock consoles with BadUpdate or ABadAvatar 1.3 (see ConsoleMods' BadUpdate guide), with XeUnshackle or XeUnshackle-Max. NetDisc360 is developed on ABadAvatar 1.3 with XeUnshackle-Max, which carries on into Aurora by itself after the console starts (auto continue).
  • Aurora, the dashboard your games show up in (tested with 0.7b.2), and DashLaunch, which loads the plugins at boot.
  • NetDisc360.xex from this project's Releases page. It makes a game on the server look like a disc in the console's drive, and ties the games to Aurora. You no longer need cOz's NetISO plugin (NetISO.xex) or the NetISO kit's modified Nova.xex; see Coming from NetISO.xex if you use them now.

On your PC or NAS

  • NetDisc360.exe from the Releases page, for Windows 10 or 11, or the Docker image for Linux or a NAS. It replaces NetISO's own server, so you don't need server.exe or netiso-srv.
  • Your games: ISOs, extracted game folders (with default.xex at the top) or Games on Demand packages. ISOs in .7z or .zip archives play once the dashboard has compressed them (see Compressed games).

Optional: NetUsb360 with a gigabit USB network adapter for faster loading, and FastFTP360 for copying files to the console; see More Xbox 360 homebrew.

Install

1. Set up the console

  1. Copy the plugins to the root of your USB drive (the one DashLaunch reads launch.ini from):

    Usb:\
      launch.ini
      NetDisc360.xex
      NetDisc360.ini      <- you make this one in step 2
      NetUsb360.xex       <- optional, see More Xbox 360 homebrew
    

    On an RGH or JTAG console that keeps its plugins on the hard drive, put them in the same folder there instead (for example Hdd1:\Plugins).

  2. Tell the plugin where your PC is. Make a text file NetDisc360.ini next to NetDisc360.xex with the line server= and your PC's IP address, for example server=192.168.1.20. The server's dashboard shows this address, and its setup wizard makes the file for you. Give your PC a fixed address in your router, so it doesn't change.

  3. Load the plugins in DashLaunch. Open launch.ini and set its [Plugins] section like this (leave the rest of the file as it is):

    [Paths]
    Default = Hdd:\Apps\Aurora\Aurora.xex
    
    [Plugins]
    plugin1 = Usb:\NetUsb360.xex
    plugin2 = Usb:\NetDisc360.xex

    Default is where your Aurora is; this makes the console boot straight into it. Leave out the NetUsb360.xex line if you don't use a USB network adapter, and number the others from plugin1. DashLaunch loads at most 5 plugins.

  4. Turn on Aurora's FTP server and add the game folder. Reboot the console into Aurora. In Aurora's settings, make sure the FTP server is on, and under Content, Scan paths, add Hdd1:\NetDisc360\Games with depth 1 (the folder can be empty; the PC fills it).

    Aurora's FTP login is xboxftp / xboxftp unless you changed it. Changing it is a good idea (see Security); then enter the same login on the PC.

2. Start the server

On Windows: put NetDisc360.exe anywhere, for example in the folder with your games, and double-click it. It opens its dashboard in your web browser (http://127.0.0.1:8360) and keeps running behind its icon in the notification area, by the clock.

  • The first time, a setup wizard walks you through it: a password for the dashboard, your game folders, finding your Xbox on the network (with a ready-made NetDisc360.ini to download), and Aurora's FTP login. It then checks the console over FTP: that DashLaunch's launch.ini loads NetDisc360.xex, that its NetDisc360.ini points to this PC, and that NetDisc360.xex and NetUsb360 are the newest releases. Skip any step, or run it again from Settings > About.
  • If the folder NetDisc360.exe is in has games, it starts out as a game folder. Add more with Add a folder. Subfolders count too. The Game folders page lists them; removing one there only stops serving it.
  • The Dashboard shows how many games it serves, which consoles are connected, how fast each one's game streams (a chart of the last two minutes), and what happened lately.
  • The Games page shows every game it serves as covers or a list, with its format, Title ID and size, and which console is playing it. Click a game for its details. A game that is in your folders more than once shows at the top, where you choose which copy to play.
  • The Consoles page lists every console that has used the server: whether it's on (the server pings each console every 30 seconds, so one that's switched off shows as Offline), what it plays, what it was sent, whether its Aurora answers, when its game folders were updated, and its last five events (a game started, games added, launchers updated to a new version). Choose there which consoles get your games in Aurora (every console that connects, or only the ones you name).
  • Settings > Xbox & Aurora has Aurora's FTP login (enter it if you changed it in Aurora), and Settings > Windows has Start with Windows, to have the server start, hidden, every time you sign in. Settings also has updates and backups.
  • Latest releases, at the bottom of the sidebar, links to the newest NetDisc360, FastFTP360 and NetUsb360 downloads.
  • Close the browser tab and forget about it. The server keeps running. Click its icon to open the dashboard again (starting NetDisc360.exe again does the same); right-click it and pick Quit NetDisc360 to stop the server.
  • When Windows Firewall asks, allow it on private networks.
  • From your phone or another computer: under Settings > Dashboard, set a password and turn on Other devices can open it. Then open http://<your PC's address>:8360 there.

The setup wizard's Aurora step: the console check shows the FTP login works, NetISO 1.0 is loaded with NetISO.xex.txt pointing to this PC, and NetIsoTiles.xex and NetUsb360.xex are the newest releases The Games page: games as covers, each marked ISO, Extracted or GOD, two of them showing the console playing them
The first run walks you through setup (left). The Games page shows every game, its format, and which console is playing it (right).

A game's details: Gears of War, an ISO disc image of 7.54 GB, its Title ID, disc number, folder and path, and its name in Aurora The Consoles page: two consoles, each playing a game, with what it was sent, its ping, whether its Aurora answers, when its game folders were updated, and its recent activity
A game's details (left), and the Consoles page with what each console is doing (right).

Settings, Dashboard: the theme, cover art, Other devices can open it (on) and the dashboard's password (set) The dashboard on a phone: games served, two consoles playing, 20 MB/s streaming and the bandwidth chart
Set a password and let other devices in (left), then check on your games from your phone (right).

Settings are saved in %APPDATA%\NetDisc360\netdisc.ini, with the FTP password encrypted for your Windows user. The Log page shows what the server does. The exe also still runs from a command prompt with options, with the same dashboard.

With Docker (Linux, a NAS, a Raspberry Pi): see Docker below.

3. Turn on the console

Turn the console on. Within a minute or two of Aurora starting, the server adds a folder for each game to Hdd1:\NetDisc360\Games, asks Aurora to scan it, and Aurora fetches the names and cover art. Your games are then in Aurora's game list next to your installed games, in the Xbox 360 category too. It doesn't matter whether the PC or the console starts first.

Aurora's game list on an Xbox 360, showing Call of Duty: Black Ops and other games served by NetDisc360 with their covers
Aurora on the Xbox: games from your PC sit in the game list with their covers, just like installed games.

For more consoles, repeat step 1 on each one (their NetDisc360.ini holds the same PC address). Each console gets its own game folders and can play a different game at the same time.

Coming from NetISO.xex

NetDisc360.xex used to be called NetIsoTiles.xex and needed cOz's NetISO.xex next to it. Now it is the disc drive itself. To switch: copy NetDisc360.xex to where NetIsoTiles.xex was, take the NetISO.xex line out of launch.ini and put NetDisc360.xex in place of NetIsoTiles.xex. Your NetISO.xex.txt keeps working (the plugin reads it when there's no server= in NetDisc360.ini), and so do the settings in a NetIsoTiles.ini.

While NetISO.xex is still in launch.ini before NetDisc360.xex, NetISO stays the disc drive and the plugin only does what NetIsoTiles.xex did, so you can try both. Don't load NetISO.xex after NetDisc360.xex: two disc drives don't mix, and the dashboard's console check warns about it.

Docker

The same server runs in Docker on Linux, a NAS or anything else with Docker, with the same dashboard.

Quick install with Docker Compose

You need two files in a new folder: docker-compose.yml and .env.

1. docker-compose.yml (download):

# NetDisc360. Rename .env.example to .env, fill it in, then: docker compose up -d
services:
  netdisc360:
    image: ghcr.io/marcusisdahl/netdisc360:${NETDISC_TAG:-latest}
    container_name: netdisc360
    network_mode: host                                       # the Xbox connects on port 4323, the dashboard on NETDISC_WEB_PORT
    environment:
      - TZ=${TZ:-Etc/UTC}
      - NETDISC_WEB_PORT=${NETDISC_WEB_PORT:-8360}           # the dashboard's port
      - NETDISC_WEB_PASSWORD=${NETDISC_WEB_PASSWORD:-}       # the dashboard's password
      - NETDISC_FTP_USER=${NETDISC_FTP_USER:-xboxftp}        # Aurora's FTP login (Aurora: Settings > FTP)
      - NETDISC_FTP_PASSWORD=${NETDISC_FTP_PASSWORD:-xboxftp}
      - NETDISC_XBOX=${NETDISC_XBOX:-}                       # only these consoles (IPs, commas); empty: all
    volumes:
      - ${NETDISC_CONFIG_DIR:-./config}:/config              # settings, owned by 1000:1000
      - ${NETDISC_GAMES_DIR:?set NETDISC_GAMES_DIR in .env}:/games:ro   # ISOs, extracted games and GOD packages
    restart: unless-stopped

2. .env.example (download), the settings the compose file reads:

# NetDisc360's settings for docker-compose.yml. Rename this file to .env next
# to docker-compose.yml and fill it in:   mv .env.example .env

# The folder with your games: ISOs, extracted games and GOD packages,
# subfolders too. Mounted read-only.
NETDISC_GAMES_DIR=/path/to/games

# The folder for the dashboard's settings (netdisc.ini). It must be writable
# by user 1000:1000:   sudo chown 1000:1000 ./config
NETDISC_CONFIG_DIR=./config

# The dashboard's port: open it at http://<this machine>:8360.
NETDISC_WEB_PORT=8360

# The dashboard's password. Without one, anyone on your network can open the
# dashboard and change its settings.
NETDISC_WEB_PASSWORD=changeme

# Aurora's FTP login (Aurora: Settings > FTP).
NETDISC_FTP_USER=xboxftp
NETDISC_FTP_PASSWORD=xboxftp

# Only these consoles' game folders are kept up to date: IP addresses,
# separated by commas. Empty: every console that connects.
NETDISC_XBOX=

# Your time zone, for the log's times.
TZ=Etc/UTC

# The image version: latest, or a release like 1.0.0 to stay on it, or dev
# for a test build of what's coming in the next release.
NETDISC_TAG=latest

Important

Rename .env.example to .env (Docker Compose only reads .env), set NETDISC_GAMES_DIR to your games folder, and change NETDISC_WEB_PASSWORD from changeme to a password of your own before you use it for real.

3. Start it. In that folder:

curl -fsSLO https://raw.githubusercontent.com/marcusisdahl/NetDisc360/main/docker-compose.yml
curl -fsSLO https://raw.githubusercontent.com/marcusisdahl/NetDisc360/main/.env.example
mv .env.example .env && nano .env
mkdir config && sudo chown 1000:1000 config
docker compose up -d

Then open the dashboard at http://<the machine's address>:8360 (or the port you set in NETDISC_WEB_PORT).

Or add it to your own docker-compose.yml, next to your other containers, with the values written in directly instead of in .env:

services:
  netdisc360:
    image: ghcr.io/marcusisdahl/netdisc360:latest
    container_name: netdisc360
    network_mode: host                          # the Xbox connects on port 4323, the dashboard on NETDISC_WEB_PORT
    environment:
      - TZ=Etc/UTC
      - NETDISC_WEB_PORT=8360                   # the dashboard's port
      - NETDISC_WEB_PASSWORD=changeme           # the dashboard's password
      - NETDISC_FTP_USER=xboxftp                # Aurora's FTP login (Aurora: Settings > FTP)
      - NETDISC_FTP_PASSWORD=xboxftp
    volumes:
      - /path/to/netdisc360/config:/config      # settings, owned by 1000:1000
      - /path/to/games:/games:ro                # ISOs, extracted games and GOD packages
    restart: unless-stopped

Give the config folder to user 1000:1000 (sudo chown 1000:1000 /path/to/netdisc360/config), then docker compose up -d.

More game folders: add them as more volumes (for example - /mnt/nas/isos:/isos:ro) and add them on the dashboard. docker compose logs -f netdisc360 shows the server's log, and docker compose pull && docker compose up -d updates it to the latest release. Docker Desktop on Windows or macOS has no host networking: use ports: with 4323:4323 and 8360:8360 (your NETDISC_WEB_PORT) instead and set NETDISC_XBOX.

Settings

It uses the image ghcr.io/marcusisdahl/netdisc360, published with each release for x86-64 and ARM64. To build it yourself instead, clone this repository and run docker build -t ghcr.io/marcusisdahl/netdisc360 ., then docker compose up -d (a later docker compose pull swaps it back for the published one). Any setting below can be added as an environment: line in the compose file.

Setting Default
volume /games Your games (read-only is fine). Mount more folders next to it, like /isos, and add them on the dashboard.
volume /config The dashboard's settings (netdisc.ini). It must be writable by user 1000:1000.
NETDISC_WEB_PASSWORD The dashboard's password. Or NETDISC_WEB_PASSWORD_FILE with the path of a Docker secret. Set this way, it can't be changed on the dashboard.
NETDISC_WEB_PORT 8360 The dashboard's port. 0: no dashboard.
NETDISC_XBOX every console that connects Only these consoles' game folders are kept up to date: IP addresses, separated by commas. Needed on Docker Desktop (Windows, macOS), where the server doesn't see the consoles' own addresses.
NETDISC_FTP_USER xboxftp Aurora's FTP login.
NETDISC_FTP_PASSWORD xboxftp Or NETDISC_FTP_PASSWORD_FILE with the path of a Docker secret.
NETDISC_NO_CATEGORY true: leave Aurora's Xbox 360 category alone.
NETDISC_NO_SCAN true: don't ask Aurora to scan after changes.
NETDISC_NO_PUSH true: only serve games; leave the console alone.
NETDISC_XBOX_FOLDER, NETDISC_AURORA /Hdd1/NetDisc360/Games, /Hdd1/Apps/Aurora As --xbox-folder and --aurora.
NETDISC_PORT, NETDISC_FTP_PORT 4323, 21
NETDISC_VERBOSE true: log every request.
TZ UTC Your time zone, for the log's times.
  • The variables from NETDISC_XBOX down are only the first start's settings. Once the server has saved its settings in /config, what's saved there wins, and you change them on the dashboard. (NETDISC_WEB_PASSWORD, the ports and NETDISC_VERBOSE always apply.)
  • The compose file uses host networking, so the console reaches the server on port 4323 of the host and the server sees the console's real address. With port mapping instead (ports: with 4323:4323 and 8360:8360, as on Docker Desktop), set NETDISC_XBOX.
  • The server runs as user 1000:1000. If it can't read your games, add user: "<uid>:<gid>" to the service with an ID that can (and give the config folder to that ID).
  • Unraid, TrueNAS and Synology: docs/nas.md has an Unraid template and the steps for each.
  • Monitoring: http://<server>:8360/metrics gives Prometheus (and so Grafana or Home Assistant) the games served, games started, and each console's connections, data sent, speed, ping and whether it plays. With a dashboard password, give it as HTTP Basic auth (any user name).
  • Games linked into the games folder (symlinks, say to another share) are followed, unless the link points back at a folder it is in.
  • Without Docker Compose: docker run -d --name netdisc360 --network host --restart unless-stopped -v /path/to/games:/games:ro -v /path/to/config:/config -e NETDISC_WEB_PASSWORD=<a password> ghcr.io/marcusisdahl/netdisc360.

Playing

Pick the game's tile. The NetDisc360 logo plays for three seconds while the game already loads underneath (any button skips it). Then the loading screen shows four steps (Server, Mount, Disc and Start), a bar that fills to 100%, and how long it has been since you pressed the tile. Then the game starts.

The NetDisc360 logo intro: the disc draws itself, then the name and the tagline, Network games for homebrew Xbox 360

The loading screen: Skate 3 at the Disc step, 62%, with B to cancel GTA V's install notice: A starts the install disc, X plays anyway, B goes back to Aurora
The loading screen, and the notice for a game whose install disc hasn't been installed yet.

The loading screen right after a reboot: The Xbox's network is still starting after the reboot. Waiting for the server... 42 s The loading screen's error for a server that doesn't answer: Can't reach the NetISO server, with what to check, and A for Aurora or X to try again
Right after a reboot it waits for the network (left). When something is wrong, it says what and what to do (right).

  • B cancels at any step and goes back to Aurora at once.

  • Right after a reboot the console can't reach the server for a minute or two, and the NetISO plugin needs a little longer still. For the first 4 minutes after boot the screen waits for both instead of failing.

  • When something goes wrong, the screen says what and what to do: the server doesn't answer, the NetISO plugin isn't loaded, the game is no longer on the server, the disc didn't show up, a different game is in the drive, or the game didn't start. A goes back to Aurora and X tries again; after a minute it goes back to Aurora by itself.

  • Games with an install disc (GTA V, Forza Motorsport 4) check for the install first. If the install disc's content isn't on the console's hard drive or USB storage, the screen asks: A starts the install disc so you can install it, X plays anyway, B goes back to Aurora. Without its install, GTA V freezes at "Loading story mode". You can also skip the install disc: Copy to Xbox on the game's page copies the content straight to the console's hard drive over Aurora's FTP, with a progress bar.

  • Games on more than one disc get a tile for each disc. When the game asks for another disc (GTA V's install disc asks for the play disc once it has installed), NetDisc360 puts that disc in over the network and the game carries on, as if you had swapped it. A notification says when the game is ready to swap and when the other disc goes in. Every disc of the game has to be in your game folders.

  • Your PC can sleep. When the server doesn't answer, the launcher wakes the PC with Wake-on-LAN and waits up to 90 seconds for it. Turn on Wake-on-LAN in the PC's BIOS and in its network adapter's settings (Device Manager > the adapter > Power Management: "Allow this device to wake the computer"). NetDisc360 tells each console the PC's MAC address; turn it off, or give another MAC address, under Settings > Xbox & Aurora.

  • Your saves are backed up. When a console is back in Aurora after a game, NetDisc360 copies that game's saves from every profile on the console's hard drive to the PC, and keeps the newest 10 of each game. Settings > Backups > Game saves lists them, downloads them, puts them back on a console, or backs up every game's saves at once.

There is no unmount step: the plugin keeps the last game mounted until another one is mounted.

Start a game from the dashboard. On the Games page, press a game's play button (or open it and pick Start on and the console): Aurora starts it as if you had picked its tile, from your phone or the couch. It uses Aurora's own web server (Aurora's settings, HTTP server, on port 9999), with the login under Settings > Xbox & Aurora (xboxhttp / xboxhttp unless you changed it in Aurora). Both Aurora 0.7b.2's own web server and the older one of the NetISO kit's Nova.xex work, with Aurora's HTTP login on or off. A game installed on that console starts from where it's installed.

What you played. NetDisc360 counts how often and how long each game is played (from the moment the game reads its disc until the console is back in Aurora), kept next to the settings in plays.ini. The Games page sorts by Recently played or Most played, and a game's details say when you last played it.

Your console from the dashboard. The Consoles page shows each console's temperatures (processor, graphics, memory), the profile signed in and what's running, as Aurora's web server tells it. From there:

  • Screenshots lists the screenshots Aurora keeps on the console: look at them, save one to the PC as a PNG, delete one, or take one of what's on screen now.
  • Restart Aurora starts Aurora again, from a game too.
  • Turn off turns the console off as with its power button. It goes through the console's debug monitor, so it works where xbdm.xex is loaded as a DashLaunch plugin. Settings > Xbox & Aurora can also turn a console off by itself 15 minutes to 2 hours after its last game.

A game's details have netiso.log: the log of its tile on the console (each step of the loading screen and why it stopped), read over Aurora's FTP server while Aurora is on screen.

Play together. Several consoles can play the same game from the same copy at the same time, system link included. Here two consoles play Call of Duty: Modern Warfare 2 against each other over system link, each streaming the game from NetDisc360:

The dashboard and the Consoles page while two consoles play Call of Duty: Modern Warfare 2 over system link: both consoles connected and playing, and the game data streamed to each one

Speed

cOz's NetISO plugin loads games at about 7 MB/s however fast your network is, because it asks the server for 4 KB at a time and waits for each piece before asking for the next. NetDisc360.xex asks for 64 KB at a time, with 4 requests in flight and a 64 KB receive buffer, with nothing to set up.

It can go faster still. Add these lines to NetDisc360.ini (next to the plugin) and reboot the console:

read_kb=256
rcv_kb=64

Installing GTA V from its install disc, on a console with a TP-Link UE306 USB adapter and NetUsb360, measured with NetISO.xex doing the reads (the plugin's own drive sends several requests at once, so it should do at least as well):

Speed
NetISO on its own (4 KB per request) about 7 MB/s
read_kb=64, no bigger receive buffer (rcv_kb=0) about 17 MB/s
read_kb=256, no bigger receive buffer about 19 MB/s
read_kb=256, rcv_kb=64 about 26 MB/s

That is about as fast as the adapter goes on the console's USB 2.0 port. The console's own network port stops at about 12 MB/s.

Test network speed on a console's card (the Consoles page) shows what the network between the server and that console can do, without starting a game: it writes a 32 MB test file to the console over Aurora's FTP, reads it back, deletes it and shows both speeds. A slow cable, switch port, Wi-Fi bridge or adapter shows up there. FTP adds its own overhead, so games can go a little faster than the test.

  • read_kb is how much the drive asks for in one request, in KB: 64 by default, 256 or 1024 for more. NetISO's own server, netiso-srv, cuts replies of 128 KB or more short, so keep 64 with it; NetDisc360 serves any size.
  • read_depth is how many requests are in flight at once: 4 by default, up to 8.
  • rcv_kb is the receive buffer for the drive's connection: 64 by default; 0 leaves the console's own.
  • The plugin reads the first NetDisc360.ini it finds: next to it, then on the root of the USB drive, then on the root of Hdd1:. An old NetIsoTiles.ini is read if there's none.
  • Hdd1:\Apps\NetDisc360\disc.log says what the drive uses, each disc it mounts, and any read it had to retry.
  • With NetISO.xex still loaded first, read_kb (4, 16, 64, 256 or 1024) and rcv_kb (16 to 256) patch NetISO's reads instead, as NetIsoTiles.xex did; each game's netiso.log then says what was set.

How many games fit

Each game takes about 3.3 MB on the console's drive:

  • 0.14 MB for its launcher, the folder in Hdd1:\NetDisc360\Games that Aurora shows as the game. All the games share one 2.9 MB helper in Hdd1:\Apps\NetDisc360, which shows the loading screen and starts the disc.
  • About 3.1 MB for its art, which Aurora downloads for any game in its list: screenshots (1.3 MB), background (1 MB), cover (0.66 MB) and banner (measured on a console with 39 games).

The game itself stays on your PC or NAS. A game's install content (GTA V's install disc puts 8.3 GB on the drive), title updates and DLC take space as they would with the disc. The table keeps 1 GB free for Aurora, your saves and updates.

Console drive Free for you Games that fit
20 GB about 13 GB about 3,700
60 GB about 51 GB about 15,500
120 GB about 106 GB about 32,500
250 GB and up about 227 GB and up more than you'll ever need

The console's own system keeps part of every drive, which is why a 20 GB drive has about 13 GB free. The 60 GB figure is measured; the others are worked out the same way.

More Xbox 360 homebrew

Two companion projects from the same GitHub account make NetDisc360 faster and the console easier to manage. The dashboard's Latest releases links to the newest version of all three.

NetUsb360: a faster network for your Xbox

The Xbox 360's own network port is 100 Mbit/s. NetUsb360 is a DashLaunch plugin that lets the console use a gigabit USB Ethernet adapter instead (ASIX AX88179 or Realtek based, such as the TP-Link UE306), so games over NetISO load at about 26 MB/s and FTP to the console reaches about 29 MiB/s. It is plugin1 in the launch.ini above; plug the adapter in instead of the network cable.

NetUsb360 is our faster fork of CUsbEnet by proferabg, which brought the USB Ethernet driver from early Xbox 360 development kits to homebrew consoles. The fork adds bigger and batched receive transfers, an ACK-batching build and TP-Link UE300 support. Coming from CUsbEnet? Put NetUsb360.xex in its place in launch.ini, and don't load both. NetUsb360 used to be called UsbNet360; an old UsbNet360.xex keeps working, and NetDisc360 still recognises it.

FastFTP360: copy files to and from your Xbox, fast

A fast FTP server app for the console, for games, saves and other files: about 27 MiB/s, where Aurora's own FTP managed about 19.5 MiB/s on the same console. It uses the same folder names and login as Aurora's FTP. Start it from Aurora when you need it; NetDisc360 keeps using Aurora's own FTP, which runs whenever Aurora is open.

More on github.com/marcusisdahl.

Troubleshooting

Check my setup on the Consoles page checks the server and each console in one go: your game folders and what's in them, Aurora's FTP login, the game folder on the console, DashLaunch's launch.ini and its plugins, the address in NetISO.xex.txt, and whether Aurora's scan paths cover the game folder (Hdd1:\NetDisc360\Games) (read from Aurora's own settings, never changed). On Windows it also says when the network is set to Public, where Windows Firewall keeps the consoles out, and offers to make it Private (Windows asks for an administrator's OK). Copy report copies the results without your addresses and Windows user name, to paste into an issue.

  • No games appear in Aurora. Check that Aurora's scan paths include Hdd1:\NetDisc360\Games (depth 1; Check my setup tells), that Aurora's FTP server is on, and that the FTP login under the dashboard's Settings > Xbox & Aurora matches Aurora's. The Consoles page says whether each console's Aurora answers, and the Log page what the server is waiting for.
  • "The server doesn't answer" on the loading screen. Check the server= address in NetDisc360.ini (or NetISO.xex.txt) against the one the dashboard shows (NetDisc360 fixes it by itself when the PC's address changed; restart the console after), and that Windows Firewall allows NetDisc360.exe on private networks and your network isn't set to Public (Check my setup tells). Hdd1:\Apps\NetDisc360\disc.log says which file the address came from and whether the drive could connect. Right after a reboot the console needs a moment before it can reach the server.
  • A game has no cover art. On the Consoles page, click Fix missing art on the console's card while it's in Aurora. It lists the games Aurora has no cover for, and on Fetch the art again renames their folders so Aurora looks them up again. See Cover art.
  • "Can't listen on port 4323". Another NetISO server (netiso-srv, server.exe, or a second copy of this one) is still running. Close it.
  • "Choose which copy to play" on the Games page. The same game is in your folders more than once. Pick the copy to play there; NetDisc360 remembers it. To free up space, delete the copies you don't play.
  • The dashboard doesn't open. Another program may be using port 8360; the log says so. Start the server with --web-port and another port. Opened from another device by a name rather than an address, it says to use the address until it has a password.
  • "NetDisc360: this game asks for a disc it has no tile for". The game's other disc isn't in your game folders. Add it; the server gives it a tile, and the swap works the next time you start the game.
  • Something else. Each game writes netiso.log in its folder on the console (Hdd1:\NetDisc360\Games\<game>), with each step and why it stopped; the dashboard's Log page shows what the server did. How it works explains both.

Updating

On Windows NetDisc360 looks for a new version on GitHub twice a day. When one is out, the dashboard says so and Settings > Updates shows what changed in every version since yours, not only the newest. Install and restart says what will happen, then backs up your settings, downloads the new NetDisc360.exe, checks it against the release's checksum, puts it in place of the old one and starts it again. If the backup can't be made, nothing is installed. After the restart the dashboard shows what's new in the version you now have, and Update history lists each version you've run, when it came, and the settings backup made before it. Should the new version not start, the old one puts itself back within two minutes, says so on the dashboard, and doesn't install that version by itself again. Turn on Install updates by themselves and it does that on its own while no console is playing. Include test versions offers pre-releases too. To update by hand instead, quit NetDisc360 from its notification-area icon, replace NetDisc360.exe with the new one and start it again; the settings stay either way.

Settings, Updates: NetDisc360 1.1.0 is out, with Install and restart, what's new in it, and the update options Settings, Backups: Back up now, Restore from a file, weekly automatic backups keeping the newest five, and the list of backups with Download and Restore
A new version, with what's new and one click to install it (left), and your settings' backups (right).

With Docker the dashboard shows that a new version is out, and you update the image yourself: docker compose pull && docker compose up -d.

To try what's coming next, use the dev image: set NETDISC_TAG=dev in .env (or image: ghcr.io/marcusisdahl/netdisc360:dev), then docker compose pull && docker compose up -d. It is built from the dev branch each time something is added there (what's new since the last release, its tests, its image builds), so it can have bugs a release won't; back up your settings first (Settings > Backups). Set NETDISC_TAG back to latest and pull again to return to the releases.

On its next visit to the console the new version replaces the launchers in Hdd1:\NetDisc360\Games with its own by itself. Only NetDisc360.xex needs a hand: copy the new one over the old one on your USB drive and reboot the console (the release notes say when it changed).

Moving from Hdd1:\NetISO

Versions before this one kept everything in Hdd1:\NetISO. Now the game folders are in Hdd1:\NetDisc360\Games, which Aurora scans on its own, and NetDisc360's own files (the helper that starts the games, wake.ini, disc.log) are in Hdd1:\Apps\NetDisc360 with your other apps. On its first visit the new version moves a console's game folders over by renaming them on the console's drive, so nothing is copied again. It then restarts Aurora, and as Aurora starts it moves its scan path Hdd1:\NetISO and its list of those games to the new folder, so they keep their cover art, favourites and play history; once that's done NetDisc360 restarts Aurora once more so the list shows it. A folder whose name is taken in the new place, or that isn't NetDisc360's (NetISO Sync), stays in Hdd1:\NetISO, which goes once it's empty. If you had set another game folder under Settings > Xbox & Aurora, nothing moves.

Backups

Settings > Backups keeps copies of your settings: netdisc.ini and the disc map, never your games. NetDisc360 backs them up by itself once a week (or every day, or turn it off), and before every update and every restore, keeping the newest five of those. Back up now makes one that stays until you delete it. Each backup can be downloaded, restored or deleted, and Restore from a file brings back one you downloaded, or a netdisc.ini by itself, for example on a new PC or from the Windows app into Docker. Restored settings apply at once; a changed port takes effect at the next start. The backups are zips in the Backups folder next to the settings file (%APPDATA%\NetDisc360\Backups, or /config/Backups in Docker).

Sync between computers

Take a laptop along and your game save backups, profile backups and play history come with you. Settings > Sync connects NetDisc360 to a small sync service on your own Cloudflare account (a Worker that keeps the files in R2, usually within the free tier), set up once with the steps in sync/README.md. Each computer connects with the owner key and gets a key of its own. From then on each one syncs when it starts, every 5 minutes and after each save backup, so a save backed up on one computer shows under Settings > Backups > Game saves on the others, ready to restore on a console there. Game folders, consoles and passwords stay on each computer, and nothing is ever deleted in the cloud. The sidebar says when the last sync was, and Settings > Sync how much the cloud holds.

Saves follow the profile. When a console is in Aurora, each profile on it gets that game's newest saves from your save backups, made on any console and synced from any computer. Nothing is lost on the way: if the console's saves are already in a backup (older ones), the newest simply go on; if they are in no backup, they are backed up first. When a profile played on two consoles since they last matched, both are kept and the dashboard asks which to use (Keep this console's makes them the newest everywhere, Use the other's puts those on this console). Only the saves of profiles that are on the console are touched, and only for games with a save backup. Turn it off under Settings > Backups > Game saves.

The server in detail

What NetDisc360.exe does, all from one file:

  • Serves your games to the NetISO plugin over the NetISO protocol (TCP port 4323), like netiso-srv. New and removed games are picked up without a restart: the folders are looked at every second, or, where that takes long (a big library on a NAS), less often, at most every 30 seconds, so the NAS's disks can sleep. A game added in between still starts at once.
  • Keeps Hdd1:\NetDisc360\Games current over Aurora's FTP. A new game gets its folder once its file has stopped changing for 10 s, named after the game without region, language and revision tags (Banjo-Kazooie - Nuts & Bolts (USA) (En,Ja,Fr,De,Es,It).iso becomes Banjo-Kazooie - Nuts & Bolts; tags like (Disc 2) stay). A removed game loses its folder, and launchers from an older build are replaced. Only folders that hold nothing but the launcher's own files are ever removed, and nothing is removed when the server has no games.
  • Asks Aurora to scan after adding or removing games (SITE INITIATESCAN, a command of Aurora's FTP server), so new games show up at once with their art.
  • Puts the games in Aurora's Xbox 360 category (see below).
  • Gives NetDisc360 and FastFTP360 their art in Aurora: cover, background, icon and banner (see Cover art).
  • Serves each game once. A game that is there more than once (the same Title ID and disc, as an ISO, a folder or a package) is a conflict: the dashboard shows a notice and a badge on Games, the activity list says so, and on Windows the icon shows a notification. The Games page lists every copy with its path; Play this one picks the copy to serve, and Keep the copies that play now settles all of them at once. The choice is kept in the settings file. Until you choose, an ISO is served before a GOD package before a folder. A copy that turns up later, or the chosen copy going, asks again.
  • Tells an incomplete ISO. An ISO shorter than the files on it say (a download or copy that stopped) is marked Incomplete on the Games page and the dashboard, since the game would crash where it reads the missing part. Copy it again.
  • Keeps the games of a folder that's away. A game folder that can't be read, or that had games and suddenly has none (a NAS share that isn't mounted shows as the empty folder under it), holds back every removal until its games are back, so they don't drop out of Aurora. The Game folders page shows it. If you emptied a folder on purpose, remove it from the list (or restart NetDisc360) and its games go.
  • Serves several consoles at once. Each console plays its own game, and each one's Hdd1:\NetDisc360\Games is kept current on its own: one console being off doesn't hold up another.
  • Leaves out games installed on the console. A game that is installed on the console's hard drive (in Hdd1:\Games, or as Games on Demand in Content) gets no tile, so Aurora doesn't list it twice; the installed copy plays as before. The Games page says where each game is installed. Turn it off, or name other folders, under Settings > Xbox & Aurora. With it off, the game keeps its NetISO tile too, and that tile asks which copy to play: A starts the copy on the Xbox (it loads faster and works with the PC off), X plays it from the PC.
  • Takes old games off Aurora's list and hides the PC games while the PC is off, with two scripts in Aurora (see Aurora's scripts).
  • Finds the PC again after its address changes. A router can give the PC a new address after a restart, and the console then looks for the server at the old one. When a console is in Aurora and the address in its NetDisc360.ini (server=) or NetISO.xex.txt is one this PC had before (and nothing answers there now), NetDisc360 writes the new one in, and says to restart the console. Turn it off under Settings > Xbox & Aurora.
  • Keeps Windows awake while a console plays, and for 10 minutes after, so a game doesn't lose its disc to the PC going to sleep. Turn it off under Settings > Windows.

Choose which copy to play: Halo Reach is in the folders twice, as E:\Games\Halo Reach (backup).iso (playing now) and D:\Xbox 360\Halo Reach.iso, each with a button to play it
A game that's in your folders twice: pick the copy to play on the Games page.

Option Default
<folder> ... the current folder Folders with your games.
--config <file> Keep the settings in this file. What's saved there (the dashboard's changes) wins over these options. The Windows app uses %APPDATA%\NetDisc360\netdisc.ini, the Docker image /config/netdisc.ini.
--web-port <n> 8360 The dashboard's port. 0: no dashboard.
--web-bind <address> 127.0.0.1 Where the dashboard listens: 127.0.0.1 for this computer only, 0.0.0.0 for the network too (the Docker image's default). Set a password for it on the dashboard or with NETDISC_WEB_PASSWORD.
--xbox <address> every console that connects Keep only this console's game folders up to date. Give it once for each console.
--ftp-user, --ftp-password xboxftp Aurora's FTP login.
--xbox-folder <path> /Hdd1/NetDisc360/Games The game folder on the console, as an FTP path. NetDisc360's own files go in /Hdd1/Apps/NetDisc360.
--aurora <path> /Hdd1/Apps/Aurora Aurora's folder, for the Xbox 360 category.
--no-push Only serve games; leave the console alone.
--no-category Leave Aurora's Xbox 360 category alone.
--no-scan Don't ask Aurora to scan after adding or removing games.
--installed <folders> /Hdd1/Games Where games installed on the console are, as FTP paths with semicolons between. Those, and Games on Demand, get no tile.
--no-installed Give installed games a tile too, which asks which copy to play.
--installed-every <s> 300 How often each console's installed games are looked at again, so a game installed or deleted on the console (in Aurora, over FTP) gets or loses its tile. They're also looked at when Aurora starts and when a game ends; 0: only then.
--no-aurora-scripts Don't write the cleanup script and the "Hide PC games while NetDisc360 is off" filter.
--aurora-web-port <n> 9999 Aurora's web server, for starting games from the dashboard, the console's status and screenshots, and restarting Aurora.
--xbdm-port <n> 730 The consoles' debug monitor (xbdm.xex), which turns them off.
--online-wait <s> 120 After Aurora's FTP comes back, the longest wait for the console to come online before writing game folders (see below).
--ping <s> 30 How often each console is pinged (a connection attempt to its FTP port; the Xbox answers no ordinary ping) to see that it's still on; 0: never. A console that answered before and stops (and whose connection ends) shows as Offline.
--remove-wait <s> 60 How long after the server starts (or its game folders change on the dashboard) a game folder whose game is gone stays on the console, so a games folder or drive that isn't there yet (or isn't added on the dashboard yet) doesn't drop its games from Aurora.
--port, --ftp-port 4323, 21
-v Log every request.

-r and -b from netiso-srv are accepted and ignored. NetDisc360.exe --help lists every option.

Cover art

Aurora looks a game up online (name and art) only once, when its scan first finds it, and a game it finds while the console is still coming online keeps its folder name and gets no art. Aurora's FTP server answers a minute or two before the console can reach out after a boot, so when Aurora's FTP comes back the server writes new game folders once the console has connected to it (the NetISO plugin does that as soon as it can), or after 2 minutes at most (--online-wait). After a game played over NetISO there is no wait. A game that has no art anyway gets it with Fix missing art on the Consoles page: the server reads Aurora's game database (Data\Databases\content.db) over FTP to find the games whose cover in Aurora's Data\GameData folder is missing or empty, renames each one's folder in Hdd1:\NetDisc360\Games (to the game's name with its tags, or with a number), and asks Aurora to scan. Aurora then drops the old entry and looks the game up again, so it forgets anything else it kept for that entry. Renaming a folder by hand works the same way. The server keeps a renamed folder, since it matches folders to games by their netiso.ini.

Aurora finds art on XboxUnity by Title ID, and XboxUnity has no entry for homebrew apps unless its admins add one, so Aurora leaves NetDisc360's own tile (Title ID FFFF4E49) and FastFTP360 (FFFF4646) without a cover. The server fills those in: when Aurora has scanned either app, its empty art files in Aurora's Data\GameData folder get the cover, background, icon and banner from art/aurora. Restart Aurora to see them. Art that is already there is left alone.

Aurora's Xbox 360 category

Aurora files the launchers under Unsigned, because they aren't retail-signed, so its Xbox 360 category doesn't show them. The server edits Media\Scripts\Content\FilterFunctions.lua in Aurora's folder once, so that the category also lists games in the NetISO folder, and keeps the original next to it as FilterFunctions.lua.before-netiso. If an Aurora update puts the original back, the server makes the same edit again. A filter it doesn't recognise is left alone, and --no-category turns this off.

The server also adds two filters of its own to Aurora (Filters, User), as files in User\Scripts\Content\Filters that it keeps up to date: Hide install discs (below) and Recently added, the games that came into your game folders in the last 30 days (games already there when you first ran this version count as old). Aurora reads them when it starts, so restart Aurora to see new games in Recently added.

Aurora's scripts

NetDisc360 keeps two Lua scripts up to date in Aurora's User\Scripts folder:

  • NetDisc360 Cleanup (Aurora's Utilities). Aurora keeps a game on its list after its folder is gone, so a game you removed from your PC can stay in Aurora as a tile that starts nothing. The script finds the games listed from Hdd1:\NetDisc360\Games whose folder isn't there any more, asks, and takes them off Aurora's list, along with their place in recent games, favourites and hidden games. It deletes no file. (Don't delete such a game from Aurora's own menu: that deletes files on the console's drive.)
  • Hide PC games while NetDisc360 is off (Aurora's filters, under User). With this filter on, Aurora lists the PC games only while NetDisc360 runs, and the console's own games always. NetDisc360 keeps a file named online.txt in Hdd1:\Apps\NetDisc360 while it runs and deletes it when it quits; the filter looks for it as Aurora starts. When Aurora is on screen and the list no longer matches (Aurora started before the PC did, or NetDisc360 quits), NetDisc360 restarts Aurora so the list follows. It never restarts Aurora during a game. Restart Aurora when the PC games come or go under Settings > Xbox & Aurora turns that off.

--no-aurora-scripts (or Aurora extras on the dashboard) stops writing them; scripts already there stay until you delete them.

Extracted games and Games on Demand

Besides ISOs, the server serves Xbox 360 games extracted to a folder (default.xex at the top) and Games on Demand packages (<Title ID>\00007000\<package> with its .data folder). Nothing is converted or written next to them: the NetISO plugin only reads a disc as sectors, so the server answers with the disc image the folder or package came from, put together as it's read.

  • A folder is listed as <folder name>.iso, a package as <game folder>.iso (or the package's own title when it isn't in a folder of its own). A Disc 2 folder with its own default.xex inside a game's folder is a disc of its own, <game> - Disc 2.iso. A name that is already taken gets a number.
  • An extracted game is a GDF (XDVDFS) disc built in memory when it's mounted. A disc can't hold a file of 4 GB or more.
  • A GOD package is the disc's game partition cut into Data0000, Data0001, ... with hash blocks between; reads skip them.
  • A folder given on the command line is never taken as a game itself, even with a default.xex at its top; only what is inside it counts.

Compressed games

An ISO, or an ISO inside a .7z or .zip archive, can be compressed once into a .cso file next to it, which plays like the ISO and usually takes much less room. Archives in your game folders show on the dashboard's Games page with a Compress to play button; an ISO has a Compress button in its details. The same from a command line: NetDisc360.exe --compress <file> ... (netdisc --compress in Docker).

  • Retail Xbox 360 discs fill the space no file uses with random bytes, which don't compress. The compressed copy keeps every file of the disc and writes that space as zeros, as an extracted game or a Games on Demand package also leaves it out. A disc whose file table can't be read is kept whole (--whole keeps it whole anyway).
  • The file is a standard CSO (CISO version 1: the disc in 32 KB blocks, each deflated on its own, with a table of where each starts), so the server unpacks only the blocks a read touches. CSO files made by other tools, such as maxcso --format=cso1, play too.
  • The new file is written as <name>.cso.part, read back and checked, then renamed. Nothing is ever deleted: while the ISO is still next to its .cso, the ISO plays, and once you delete the ISO the .cso takes over with the same tile in Aurora. An archive's discs are checked against the archive's own CRCs.
  • .7z archives packed with LZMA, LZMA2 or no compression are read as they stream, so a disc never has to fit in memory; ones with filters (BCJ, Delta) or encryption need extracting with 7-Zip first. .zip archives can be stored or deflated, Zip64 included.
  • The .cso is written next to the original, so in Docker the games folder must be mounted writable to compress.

Install discs

Some games come on two discs, one of which only installs content: GTA V's second disc (8.3 GB in 4 packages) and Forza Motorsport 4's (car packs). The server reads the packages each disc carries for its game (content\0000000000000000\<Title ID>\ on an extracted folder, ISO or GOD package) and writes install.ini into the game folder of each other disc of that game, naming the install disc and its packages. Before such a game starts, the launcher looks for each package under Content on the hard drive (and USB storage set up for the console) at its full size, and offers to start the install disc if one is missing. A disc you swap to during a game, such as Red Dead Redemption's second disc, carries no packages and gets no install.ini.

Copy to Xbox on the install disc's page (or the game's) sends each package to Hdd1:\Content\0000000000000000\<Title ID>\<type>\ over Aurora's FTP. A package already there at its full size is skipped, and one cut short by a stop or a lost connection is deleted, so the launcher never takes it for installed. When you copy a game that has an install disc, its packages come along. The console has to be in Aurora while it copies.

Bonus discs and discs with arcade games, demos or DLC work the same way: each package goes where its own header says (its Title ID and content type), so a disc carrying another game's DLC puts it under that game. Avatar items, profiles, gamer pictures, themes and saves on a disc are left alone.

Copy to Xbox

Copy to Xbox on a game's page puts the whole game on the console's hard drive, so it plays without the server or the network. Like TinyXbox360BackupManager, it makes the game a Games on Demand package and sends it to Hdd1:\Content\0000000000000000\<Title ID>\00007000\ over Aurora's FTP, where Aurora finds GOD games by itself. ISOs, extracted folders and GOD packages all work. The server builds the package while it sends it, so nothing is written on the PC or NAS: it reads the game once for the hashes ("Getting it ready"), then sends the Data files and the header last. Data files already there at full size are skipped, so a stopped copy goes on where it was. The package is made as iso2god-rs makes one (MIT, third_party/iso2god).

  • A game on several discs: Copy all N discs puts every disc on the console, install discs last.
  • Original Xbox games are copied as their files to Hdd1:\Games\<game>\, and Aurora is asked to scan that folder.
  • One at a time. Aurora's FTP mixes up two uploads that run at once, so each console has a line: a copy you start while another runs waits its turn. The Consoles page shows the line, and a waiting copy can be taken out of it (POST /api/copy, POST /api/install/stop with id, progress in /api/state under installs).
  • Remove from the console: the game's Installed on row has a Remove button for each console. It deletes only that game's GOD package (or its folder under one of your game folders), after you confirm (POST /api/console/remove).

Title updates

The Title updates page, and each game's page, look up the game's updates on XboxUnity and put the right one on your consoles: the update made for the disc's own Media ID, newest first, with older versions to pick from. Update every console puts each game's newest update on every console that has the game (as a tile or installed). The server downloads each update once to TitleUpdates\ next to its settings, checks its size, its Content ID (the checksum XboxUnity lists) and that it is for this game, and sends it where Aurora loads it: Hdd1:\Content\0000000000000000\<Title ID>\000B0000\, or Hdd1:\Cache\ for a TU_ file. An older update of the same game is moved to NetDisc360\Title updates\<Title ID>\ on the console, never deleted, so Aurora loads only the new one. Each console's Check reads which updates it already has (GET /api/titleupdates?game=, POST /api/titleupdates/install, POST /api/titleupdates/scan).

Like Aurora's title update manager, each console's row lists every update of the game it has: the one it loads (On), ones moved aside, and the copies Aurora keeps in its own store (Data\TitleUpdates, only read). Use this one makes another version the one the game loads: one moved aside is moved back, one in Aurora's store is copied (Aurora's copy stays). Turn updates off moves the game's updates aside, so it starts as it is on the disc. Nothing is deleted, and only this computer goes online: the consoles get the files over Aurora's FTP (POST /api/titleupdates/use, POST /api/titleupdates/off).

Aurora keeps its own list of the update each game has on, and each time it starts a game it puts that one in place and deletes the others. So every install, Use this one and Turn updates off also changes Aurora's list. Aurora can't be changed from outside while it runs, so NetDisc360 writes a small script (User\Scripts\Content\Filters\NetDiscTitleUpdates.lua) that Aurora runs once as it starts. That script switches the update on in Aurora's list, adding the update to the list (with a copy in Aurora's store) if Aurora hasn't seen it yet. Aurora reads its list before its scripts run, so it uses the change from the start after that. NetDisc360 therefore restarts Aurora twice when Aurora is on screen and the settings allow it. If the console is in a game, NetDisc360 does the second restart once Aurora is back; if restarts are turned off, the job asks you to restart Aurora twice before you start the game. A change you make later in Aurora's own title update screen stays: the script runs only once for each change. Updates kept in Cache (TU_ files) aren't on Aurora's list, so for those Aurora is set to have none on.

Security

  • Change Aurora's FTP login. Aurora's default login (xboxftp / xboxftp) lets anyone on your network read and write the console's drives. Set your own in Aurora's settings and enter it on the dashboard's Settings page (or NETDISC_FTP_USER/NETDISC_FTP_PASSWORD in Docker, or --ftp-user/--ftp-password). FTP sends the login unencrypted, so keep the console on a network you trust. On Windows the settings file keeps the password encrypted for your Windows user. On Linux and in Docker it is kept as plain text in netdisc.ini, which only the server's user can read, so keep the /config folder private. The dashboard never shows the password again, and the server never writes it to its log.
  • Change Aurora's web server login too, if you use it (Aurora's settings, HTTP server; xboxhttp / xboxhttp by default): it can start any program on the console. Enter yours under Settings > Xbox & Aurora > Aurora's web server. It is kept like the FTP password. NetDisc360 never asks it for the console's system information, which holds the console's CPU and DVD keys.
  • The console's debug monitor (xbdm.xex) has no login at all: anything on your network can reach port 730 on a console that loads it, and NetDisc360's Turn off uses that. Load it only on a network you trust.
  • Keep the NetISO server on your home network. The NetISO protocol has no login: anything that can reach port 4323 can list and read the games you serve. Don't forward that port from the internet. When Windows Firewall asks, allow NetDisc360.exe on private networks only. The Docker image runs as an unprivileged user and only needs read access to your games.
  • Give the dashboard a password when other devices can open it. On Windows only the PC itself can open it until you turn on Other devices can open it, which needs a password. In Docker it is open to your network, so set one. The password is kept only as a salted hash; logging in gives the browser a cookie for 30 days, and changing the password logs every browser out. Without a password the dashboard only answers to addresses and local names (like nas.local), so a web site can't reach it through your browser, and it only takes requests from its own page. The login cookie is signed with a random key kept next to the settings file (session.key), not with anything a backup holds. Don't forward port 8360 from the internet either.
  • Covers on the dashboard. Your browser downloads them from GitHub (the XboxUnity-Scraper archive), asking only for each game's Title ID. Turn them off under Settings > Dashboard. Latest releases (in the sidebar) asks GitHub for the newest version of NetDisc360, FastFTP360 and NetUsb360 only when you open it. Apart from the update check below, the server itself never goes online.
  • Backups hold Aurora's FTP login and the dashboard password's hash, like the settings file (the FTP password is encrypted on Windows, so a backup restored on another PC or in Docker keeps the FTP password already set there). Keep downloaded backups where only you can read them.
  • Updates come only from this project's GitHub releases. On Windows the server asks GitHub's API for the newest release and, when you install it, downloads its NetDisc360.exe over HTTPS and installs it only if it comes from this project's releases and its size and SHA-256 match what GitHub lists for the release. Builds that carry an update key also need the release's signature, NetDisc360.exe.sig, to match that key, so not even a release put up by someone else on this GitHub page gets installed. Turn off Look for updates under Settings > Updates to stop it. In Docker the dashboard asks GitHub from your browser instead.
  • The server only reads your game folders; it never writes to them. On the console it writes only inside --xbox-folder, unless --no-category the one Aurora script above, and the empty art files of the two apps above in Aurora's Data\GameData.

Limitations

  • Original Xbox games (default.xbe folders, .xiso images and full disc images in Redump's format) are experimental. They stream and start in the console's original Xbox emulator, which needs the community's hacked emulator files in HddX:\Compatibility. Halo: Combat Evolved and Burnout 3 have been tested over the console's own network port, and Halo also over a USB network adapter. Over the adapter, use NetUsb360 1.1.2 or newer: 1.1.1 and older (and CUsbEnet) freeze the console or keep showing "Fatal Crash Intercepted!" as soon as an original Xbox game starts.
  • For System Link in original Xbox games, every console needs the NetDisc360 plugin (NetDisc360.xex) in launch.ini, with Aurora's LiNK off. Aurora's Nova.xex takes over the emulator's LAN traffic for LiNK and, with LiNK off, never hands the game anything, so no console finds another's game. When an original Xbox game starts, the plugin takes this over from Nova: the game gets only the System Link packets, and everything else, such as the disc streamed from NetDisc360, stays with the console. Nova stays installed for everything else. Tested with Halo: Combat Evolved and Halo 2 streamed to two consoles. xbox_link=nova in NetDisc360.ini leaves it all to Nova, and xbox_link_log=1 writes what the plugin sees to the game's log.
  • Each original Xbox game starts in the emulator version it plays best on. The console picks a version only for the games Microsoft supported and starts xefu.xex for the rest, so NetDisc360 has a list of about 570 games from the ConsoleMods compatibility list: Crazy Taxi 3 starts in xefu7, and a game with a fix in the Hacked Xefu Pack's Configs folder in config_loader_xefu7. The NetDisc360 plugin starts that version when the console starts the emulator, and the game's page on the dashboard shows which one. To pick another for a game, add xefu=xefu2021c under its [Title ID] in discs.ini (xefu= with nothing for the console's own pick). The emulator files stay as they are, except that xefutitle.xex becomes a copy of xefutitle2019.xex or xefutitle2021.xex before one of the Xbox One versions (xefu2019, xefu2021a to c) starts, as Xefu Spoofer does. Once Xefu Spoofer has set one version for every game, the others aren't there, and every game starts in that one.
  • Disc swaps work for a game started from its tile, with every disc in your game folders. They have been tested with GTA V.
  • The launcher has no title name of its own; Aurora names each game from its online lookup by Title ID.
  • With NetISO.xex loaded first, NetDisc360.xex patches NetISO.xex 1.0 in memory and checks that its code is exactly where it expects; with any other NetISO version it leaves the plugin alone, so the Guide fix and the speed-up are off. Its own drive has neither problem.

NetISO Sync (for other NetISO servers)

If your PC runs another NetISO server (netiso-srv, server.exe) instead of NetDisc360, NetISO Sync makes the game folders from the console. build\NetISO Sync\ is the launcher without a game: copied to Hdd1:\Apps\NetISO Sync and started from Aurora, it asks the NetISO server for its ISOs, writes and removes game folders the way NetDisc360.exe does, and returns to Aurora. It reads ISOs only (no extracted folders or GOD packages, which only NetDisc360.exe serves) and doesn't change Aurora's category or start a scan.

server= in its netiso.ini names the server if netiso.xex.txt doesn't, and after= names what to start when it's done (to run it at every boot as DashLaunch's Default, set after= to Aurora's XEX). tools\netiso_aurora.py makes the same folders on a PC, for copying by hand.

How it works

Each game's folder in Hdd1:\NetDisc360\Games holds a small launcher with the game's own Title ID and Media ID, so Aurora scans it as that game. When you pick it, the launcher draws the loading screen, asks NetDisc360.xex's drive (\Device\NetDisc360) to mount the game, waits until the disc in the drive is that game, and boots it the way Aurora's own disc entry does. The drive answers the console's disc reads from the server, fakes the tray opening and closing so the console reads the new disc, and gives games the disc's media ID, as cOz's NetISO.xex did, so games and Aurora see a real disc. With NetISO.xex loaded first, the plugin patches it in memory instead, so the Guide keeps working, reads go out in bigger pieces, and a game's disc swaps reach the server.

docs/how-it-works.md has the details: the disc drive, why the Guide died with NetISO, disc swaps, read speed, and the logs.

Build

You need Visual Studio 2022 with the "Desktop development with C++" workload, and the Xbox 360 SDK integration for Visual Studio (the same setup as FastFTP360), and Python 3. The SDK is not included and can't be redistributed.

.\build.ps1 -Tests

This makes build\NetDisc360.exe (with the launcher built in), build\NetDisc360.xex, build\NetISO Sync\ and build\NetISO-Sync.zip (the launchers, as the release and the Docker image use them). The Docker image builds the server for Linux from the same source; see the Dockerfile.

After a build, .\store\package.ps1 (needs 7-Zip) makes build\NetDisc360-<version>.7z for the Xbox 360 Homebrew Store, with NetDisc360.xex, store\readme.txt and the license, which the store unpacks into Apps\NetDisc360\, and build\NetDisc360-<version>.ini, the store entry made from store\consolemods.ini.

Pull requests go to the dev branch, not main: each change there is published as the dev Docker image for testing, and main only gets dev merged into it for a release. To make a release, see RELEASING.md.

Tests

  • python tests\test_server.py builds netdisc for Linux and checks the NetISO protocol (listing, mounting, reading, new ISOs without a restart, reads past the end), the push to tests/aurora_ftp.py, a stand-in for Aurora's FTP server (folders, removal, repair, each original Xbox game's emulator, and the category edit), and the dashboard's web API (games, consoles and bandwidth, settings kept in the settings file, the password, and changes only from its own page).
  • python tests\test_discs.py checks extracted folders and GOD packages: every file of a folder's disc reads back as it is on disk, walked as the console walks it; GOD packages in iso2god's and Microsoft's layouts read back across hash groups and Data files; duplicates are served once and reported once; original Xbox folders and ISOs are served with the Title ID from default.xbe, and a full original Xbox disc image as its game partition alone; a file over 4 GB is refused.
  • python tests\test_sync.py builds Sync's core for Linux and runs it against tests/netiso_server.py.
  • python tests\test_generator.py builds small XGD ISOs (XSF, XGD2 and XGD3 layouts) and checks the launcher folders made from them.
  • tests/ui_preview.cpp draws the loading screen on a PC into a BMP, for each step and error.

Credits

  • NetISO and its plugin NetISO.xex by cOz, whose protocol and drive behaviour NetDisc360.xex follows with its own code. This project doesn't include or modify NetISO's file; with it loaded, NetDisc360.xex patches it in memory at run time.
  • netiso-srv by tuxuser, whose protocol behaviour the server follows.
  • Aurora by Phoenix.
  • Dear ImGui (MIT, third_party/imgui/LICENSE.txt) and the Roboto font (Apache 2.0, third_party/fonts/LICENSE-Roboto.txt) for the loading screen.
  • iso2god-rs (MIT, third_party/iso2god/LICENSE): the Games on Demand layout and header template for Copy to Xbox.
  • miniz (MIT, third_party/miniz/LICENSE) for compressed games and .zip archives, and the LZMA SDK by Igor Pavlov (public domain, third_party/lzma/lzma-sdk.txt) for .7z archives.
  • Lucide icons (ISC, third_party/lucide/LICENSE) for the dashboard. Its covers come from XboxUnity, through the XboxUnity-Scraper archive.

Xbox and Xbox 360 are trademarks of Microsoft. This project is not affiliated with Microsoft, cOz or Team Phoenix. Use it only with games you own.

License

MIT, see LICENSE. The files in third_party/ keep their own licenses.

About

Play your whole Xbox 360 library from your PC or NAS, straight from Aurora, without filling the console's drive, even with 2,300 games. Open-source NetISO server for RGH, JTAG and BadUpdate: ISOs, extracted games and GOD as virtual discs, per-game launchers Aurora scans as real titles (art, TUs, DLC), Guide stays working. Windows or Docker.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages