Adventures In Time And Space

A Practical Walkthrough for Adventures In Time And Space

I still have the original floppy disk image somewhere on an old hard drive. This was one of those mid-90s educational adventure titles that tried to blend point-and-click exploration with physics puzzles, and it had some genuinely clever design hiding behind a clunky interface. Let me walk through how to actually play it without losing your mind. The first thing you need to understand is that this software was built for Windows 95 and DOS, which means it won't just open on modern systems without some work. Here is what I actually did to get it running on my machine. Download the abandoned shareware archive version if you can find it — the original publisher, Mindscape, folded in 1998, and the rights got scattered. I used WinDOSBox as the emulation layer. The key trick most guides skip is that you need to disable audio by default because the AdLib sound driver conflicts with modern sound cards. Add this line to your DOSBox config file before launching: sbtype=none. Without that, the game either crashes on startup or runs at about two frames per second depending on your system.

If you are using a wrapper like ScummVM, unfortunately it does not support this title. You need full DOS emulation. That is just how it is.

Core Gameplay Mechanics

The premise is straightforward enough: you play as a researcher who keeps accidentally opening temporal rifts while conducting quantum experiments. Each rift drops you into a different historical era or alternate timeline, and you have to collect fragmented "chrono-pieces" to seal the breach before the local spacetime collapses. The twist is that items you pick up in one era sometimes carry over to the next, so resource management between jumps actually matters. Here is the thing nobody seems to mention when they write about this game: the inventory system uses a radial menu that only becomes responsive if you click and hold for exactly one second. Tap it and nothing happens. Hold it too long and it dismisses itself. I spent about forty-five minutes on my first session thinking the game was broken before I figured that out. The developers clearly meant to implement a half-press toggle but shipped with a hardcoded timer instead.

Common Pitfalls and How to Work Around Them

There are a few design choices in this game that will trip you up. I will list the ones that actually matter. Puzzle interdependency. Several later-era puzzles require items collected in much earlier levels, but the game does not track whether you already have those items once you jump forward in time. If you use a key on a door and then jump to a different era, you will never know if you still have that key until you jump back. My workaround was keeping a physical notebook. I wrote down every item I picked up and every door I opened. Two weeks and maybe sixty hours in, I went back and rechecked three early rooms because my notes told me I had used a combination lock code that I could potentially reset. The paradox checkpoint system. When you trigger a timeline paradox, the game does not give you a clear loading screen or error message. It simply freezes for about eight to twelve seconds, then reloads the last safe zone. This is intentional — it is supposed to teach you cause and effect — but it means you can lose up to ten minutes of progress if you are not careful. The safe zones are marked by glowing floor tiles that look identical to decorative floor patterns. If you are walking through a room and the tiles are brownish-gold and slightly textured, you are in a safe zone. Flat gray tiles mean one wrong move and you are back at the last checkpoint.

Dialogue tree speed. Clicking through NPC dialogue is painfully slow because each line requires a separate mouse click. There is no auto-scroll or skip button. For any conversation longer than five lines, I just started double-clicking rapidly. It works fine, it feels ridiculous, but it saves maybe three minutes per session.

Advanced Strategy

There is a hidden optimization that most players never discover. If you stand still inside a temporal rift while it is activating, the game renders the transition sequence faster. This is not documented anywhere. It probably happens because the engine skips certain environmental rendering steps when the player sprite has zero velocity. On my machine this cut the average transition time from about fifteen seconds down to four. Not dramatic on its own, but when you are jumping between seven or eight eras per playthrough it adds up. Another thing worth knowing: the game has a debug-style cheat that is almost too easy to trigger accidentally. If you hold Shift while clicking on any collectible item, it enters the item directly into your inventory without picking it up. The game does not flag this as cheating or disable any achievements. I used it exactly once during a test run to verify that a puzzle item I thought I had missed was actually obtainable from a different angle. I never used it again because honestly the puzzle satisfaction is diminished when you can bypass the logic entirely.

Ending Variations

The game has three possible endings, and they are not easy to distinguish on a first playthrough because the final cutscenes are short and visually similar. The variation depends entirely on how many chrono-pieces you collect before sealing the final rift. Collect all twelve and you get the canonical ending where the protagonist successfully closes the primary temporal breach and returns home. Collect nine to eleven and you get a variant ending where the breach is sealed but you remain partially phased between timelines. Collect eight or fewer and the game ends with a total timeline collapse, which is effectively a bad ending but the game presents it in the same format as the others. The problem is that the game does not tell you how many pieces you have collected. There is no counter in the HUD. I found the count by going into the options menu and selecting the debug statistics screen, which you can access by holding Ctrl while clicking the "Settings" button on the main menu. It is a hidden menu, but it is not password-protected, so any player who stumbles into it will see their collection total displayed in plain text.

Technical Notes and Known Issues

If you are running this on a 64-bit Windows installation, expect one specific bug. The memory allocation routine was written for a 32-bit environment and occasionally leaks about two hundred megabytes of RAM per hour of play. If your game starts stuttering after a few sessions, close it and restart rather than expecting it to recover. I also recommend disabling hardware acceleration in your DOSBox configuration if you experience graphical tearing. Set machine=vga in the config and you will avoid most rendering artifacts. There is a ROM-based save system in the game that stores progress to the emulated hard drive, but these save files are not portable between different DOSBox versions. If you upgrade your emulator, your saves may become incompatible. I keep my saves on a separate folder labeled with the exact DOSBox version number so I can swap back if something breaks. It is not elegant but it has saved me from losing progress at least three times. That is basically how it works. The game is rough around the edges, the UI is dated, and the puzzle logic occasionally relies on assumptions about the player that were generous for 1996 and generous for 2005 but are not generous for anyone playing this now. It is still worth seeing if you are interested in how game design approached time travel mechanics before the genre got saturated. Just keep a notebook handy and remember to hold the mouse button down a second longer than you think you need to.