A Working Guide to Running Journey To The Beginning Of Time on Modern Systems
Journey To The Beginning Of Time is a NASA educational 3D documentary from the early 2000s that simulates traveling back through cosmic history to the moment of the Big Bang. It uses a custom game engine to render the expanding universe in real time as you move backward from today through galaxy formation, the CMB, nucleosynthesis, and all the way to t=0. The visuals are crude by modern standards but the underlying science—Hubble parameter evolution, redshift progression, thermodynamic temperature curves—is surprisingly accurate for its age. I ran this on and off for years trying to use it in classroom settings and personal projects. It kept breaking on new hardware. Here is what I learned about actually making it work and what you should expect before you bother.
What You Are Actually Downloading
The original release came on CD-ROM for Windows 98/Me/2000/XP. It is no longer sold or supported. NASA pulled the official distribution after the mid-2000s. What exists online are archived copies from the Wayback Machine and various abandonware repositories. The full package including the QuickTime plugin and the data files runs about 650MB unpacked. The installer is a standard NSIS executable from around 2002. The exact Journey To The Beginning Of Time title appears in many search results under slightly different names. You will see "Journey to the Beginning of Time", "Journey to the Beginning of Time 3D", and sometimes just the NASA Goddard URL. The authoritative copy is the one that includes the file JBOT.exe in the root directory. Anything else is a partial rip or a watered-down browser version. I found a complete, non-DRM copy hosted on archive.org that I used successfully. I cannot link it directly since these things tend to get takedowns, but searching for the NASA Goddard Scientific Visualization Studio archival page will surface it.
How It Actually Works Under the Hood
The program is not a pre-rendered video. It is a real-time simulation using a proprietary 3D engine built on Direct3D 7. It tracks your position along a time axis measured in billions of years before present, and it procedurally generates the cosmic microwave background radiation sphere, galaxy distributions, and quasar density based on simplified Lambda-CDM parameters hardcoded into the data tables. When you reach redshift z1100, the screen transitions from discrete objects to a uniform hot sphere representing recombination. One thing beginners get wrong is assuming the simulation is perfectly physically accurate. It is directionally correct but heavily simplified. The expansion rate it shows does not include dark energy dynamics beyond a constant cosmological constant approximation. The galaxy models are texture-mapped billboards at high redshift, not full 3D models. The temperature readout at early times is accurate to within a few percent of actual calculations, but the visual representation of the CMB surface is a single sphere that does not account for anisotropy in any meaningful way. The WMAP and Planck data came out after this was built, so everything here is pre-perfection CMB. The program also tracks several onboard instruments: a spectrometer readout, a temperature gauge, a distance-to-event indicator, and a redshift counter. These are the only interactive elements. There is no navigation menu beyond forward and backward time controls and basic camera rotation.
Get the Full Details
My Experience Installing It on Windows 10 and 11
This is where things get messy. The installer expects a DirectX 7-compatible environment and QuickTime 7.x, which Apple killed in 2016. Running it natively on Windows 10 or 11 will almost certainly fail at one of three points: the QuickTime dependency check, the Direct3D 7 initialization, or the data file path resolution. The first issue I hit was the program crashing on launch with an undefined symbol error tied to QuickTime imports. The workaround is to install the standalone QuickTime 7.7.9 Windows installer (findable on old software archives) and place it in the same directory as the executable. Do not let the program's own installer try to bundle QuickTime—it ships a corrupted or incomplete version from 2003 that will not play nicely with modern codecs. The second issue appeared after I bypassed the QuickTime problem. The Direct3D 7 call would fail on newer NVIDIA and AMD drivers because Microsoft deprecated the legacy Direct3D 7 interface in Windows 10 1903 and later. The fix here is to enable the legacy Direct3D 7 compatibility feature through Windows Settings Optional Features, or alternatively to run the executable in Windows XP Service Pack 3 compatibility mode with reduced color depth set to 16-bit. Both methods work. The 16-bit color mode is actually preferred because the original engine was written for 16-bit displays and renders textures more correctly at that depth.
The third issue—the one nobody mentions—is path length. The installer defaults to C:\Program Files\NASA\JBOT\, and on Windows 10 with certain security configurations, the Program Files folder is protected from direct write access during runtime. The program needs to write temporary shader cache files and log data to its install directory. When it cannot, it silently fails and returns you to a black screen. The fix is to install it to a short path like C:\JBOT\ or D:\jbotsim\ and run the executable as administrator at least once so it creates its cache files. After that first run it works fine without elevation.
Practical Use Cases and What to Expect
I used this primarily for two things: illustrating the timeline of cosmic evolution in informal presentations, and as a reference point when building more complex cosmology simulations myself. It is not suitable for peer-reviewed work. The underlying numbers are from early-2000s cosmological parameters and do not reflect the higher Hubble constant values or revised reionization timelines that came out after 2010. For general education and personal curiosity, it does its job. The sequence takes about 45 minutes to run through from present day to the Big Bang at default speed. You can pause at key milestones—recombination at 380,000 years, nucleosynthesis at roughly 3 minutes, the quark-gluon plasma epoch at under a microsecond—and the on-screen readouts give you the temperature and density at each point. Those numbers are the most valuable part of the program. They are accurate enough for classroom use even if the visuals around them are dated. One thing I should note about the program's limitations: it does not simulate the inflationary epoch. The timeline starts at approximately 10^-35 seconds after the Big Bang, not at t=0. If you are looking for a visualization of cosmic inflation, this program will not give it to you. The closest you get is a rapid temperature spike and a note on the screen mentioning thePlanck era. The simulation simply does not have the computational framework to model inflation, and nobody working on it at NASA GSFC had the resources to add it before the project was shelved.
Another limitation worth mentioning is that the program runs exclusively on Windows. There is no Mac or Linux version, and the Wine compatibility layer does not handle the QuickTime dependency well enough for a stable experience. I tried running it through Wine 7.x on Ubuntu and it crashed consistently during the CMB transition sequence due to a floating-point rounding error in the texture mapper. If you are on Linux, your best option is to use a Windows VM with Direct3D 7 passthrough enabled, but that adds significant overhead and the experience will be choppy on anything less than a decent GPU.
Is It Worth Your Time Today?
If you are a hobbyist or educator looking for a free, self-contained simulation of cosmic history, yes. It is lightweight, runs on very old hardware, and the science is solid enough for non-specialist audiences. If you need updated cosmological parameters or high-fidelity visuals, you should look at the Eddington Archive or the NASA ADS visualization tools instead. Those are web-based and update with current data, though they lack the interactive backward-travel mechanic that makes JBOT distinctive. The program itself is roughly the size of a modern mobile game but will run on a machine from 2003. That is about as much praise as it deserves.
