So a soc member asked me in our Skype group the other day if it were possible to install EU to a flash drive and have it run on another computer. He has access to a faster computer, but isn't allowed to install anything on it (assuming a work PC). I've delved deeply into the registry entries that EU uses during my work on Entropia Tools, so I figured "this shouldn't be too hard" -- and I was right. I did a preliminary test on it today by copying over the game files (minus the dynamic content, participant content, and shader cache) and using this to "install" it on the target machine. I was somewhat worried by a couple of the methods called to then remove said registry entries, and tested it on a virtual install in VMware. I learned something quite valuable: the "installer" has to be run as Administrator to populate the registry to any great extent. Anyway, it's ready for some field testing if anyone's up to it. At this moment, it only supports initial setup with one planet (with a big enough flash drive you can expand it on your own from the client loader). It also requires you to download all content, though it does copy the settings-ce.cfg. Anyway, download link: http://www.adamh.us/entropia/EU_packager.zip (~2.85 MB) Windows XP Specific Build: http://www.adamh.us/entropia/EU_packager_XP.zip (~2.79 MB) Five files: EU_Packager.exe EU_Launcher.exe config.xml vcredist_x86.exe (Visual C++ 2005 Runtime files - installed by EU installation) dxwebsetup.exe (Updates for DirectX - installed by EU installation) Usage: Run EU_Packager.exe first to set it up the way you want it (planet, saved username, etc) or edit the config.xml file to match. In the Packager window, click "Begin Installation" on a computer that already has EU installed, making sure the paths are directed to the correct drive. Run EU_Launcher.exe from the external drive and click "Install" and then "Launch" (Alt+I and Alt+L, respectively) - Make sure config.xml is also present. When finished, click "Remove" to clear the registry entries. On first run (per "install") it will ask for the language to run in. One additional note: This is brand new. Just wrote it basically today. It lacks a lot of error handling, so incorrect values or attempting to overwrite existing files may produce some very lengthy error messages. You can choose Continue or Quit. You may have to close and then bring it back up, anyway. Also: Make sure you have .NET 4.0 installed. If this becomes a problem for XP users, I'll drop it back to 3.5. But 4.0 has run on XP before.