From af7232fc9822669c12fa7718ad63188bb9def216 Mon Sep 17 00:00:00 2001 From: RadWolfie Date: Sun, 10 Feb 2019 20:41:11 -0600 Subject: [PATCH] Updated Cxbx Reloaded overview (markdown) --- Cxbx-Reloaded-overview.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Cxbx-Reloaded-overview.md b/Cxbx-Reloaded-overview.md index 35e7363..b1074a9 100644 --- a/Cxbx-Reloaded-overview.md +++ b/Cxbx-Reloaded-overview.md @@ -3,10 +3,12 @@ Here some technical details on how Cxbx-Reloaded works. # Executable launch modes Cxbx-Reloaded is a single executable which operates in two different modes: -1. If launched normally (without any command-line arguments), it will show a user-interface. +1. If launched normally (without any command-line arguments), it will show a user-interface then wait for user inputs. + * However, if drag and drop an xbe file on top of executable. It will automatic run xbe file. 2. To emulate Xbox software, Cxbx-Reloaded relaunches itself (with the path to the Xbox executable to run on the command-line). The emulated Xbox screen is then put over the user-interface. At the end of emulation, the second instance terminates and the user-interface reappears. + * If want to start standalone emulation. Then the following argument should be input `> cxbx.exe /load "path to xbe"` via command prompt. If another process launches Cxbx-Reloaded (for instance, a user starts a shortcut via Windows Explorer) with a command-line argument, there's no parent process, so when emulation ends in this scenario, the Cxbx-Reloaded process terminates entirely.