Remembering Those Ancient VSTs That Actually Worked
I dug through some old hard drives last week while cleaning out a storage folder labeled "2003-ish stuff" and found a handful of installers I hadn't touched in nearly two decades. Among them were two plugins — Technoboy and Tuneboy — originally bundled or sold together under what some people still call TNT back in the forum threads from way back. I figured I'd write this up before I lose the actual files myself. Technoboy and Tuneboy were virtual instruments / sample players aimed at people making dance, techno, and Eurodance stuff. The concept was straightforward: instead of sequencing individual hits or layering your own samples, these plugins came pre-loaded with patterns, basslines, and synth stabs that you could drag, tweak, and stack together. Think of it as a pattern-based instrument rather than a traditional sampler where you have to map every single hit yourself. The interface looked exactly like you'd expect from 2003 — a bunch of dropdown menus, a small piano roll area, a pattern grid, and a handful of knobs for filter cutoff, decay, and volume. There wasn't much visual polish to it. It worked.
Here's what I remember about using them in a real session. You'd open your DAW — I was running Cubase SX at the time — load Technoboy on one channel and Tuneboy on another, pick a pattern from each, and start muting and unmuting sections to build a track. The patterns weren't endless; each voice had maybe four to eight variations you could cycle through. That limitation actually forced you to make decisions faster instead of getting lost in sixteen bars of the same loop. One thing people didn't talk about enough back then was the audio quality. The default output was fine for demos and club tracks, but if you pushed the saturation knob too far or layered too many voices, the mix became muddy fast. I learned the hard way that low-cutting every track below 120 Hz on the Tuneboy bass voices and keeping the Technoboy pads high-passed around 250 Hz made the whole mix clearer. Without that, you just got a wall of mid-bass mud that sounded great at half volume and terrible once you played it loud.
How To Get Them Working Today
Download links for these are scattered across old forum archives and random file-hosting sites. The honest answer is that official support ended years ago, so anything you find is essentially abandoned shareware. That said, they still run as 32-bit VST plugins in older DAWs and through compatibility layers in modern hosts. If you're on a modern 64-bit system, you'll need a bridge like iZotope VMPRO or a dedicated 32-to-64-bit VST host such as Caribou or TAL-NotePad sitting inside your main DAW. I use Bridson for this kind of thing — it's lightweight, stable, and handles single-instance plugins without issue. Technoboy and Tuneboy don't play well as multi-instance plugins; they tend to crash or desync when you load more than one copy of the same instrument in the same session. For the actual install, extract the ZIP, run the setup executable, and point it to your VST plugins folder. Most people put it in Program Files\VSTPlugins or wherever their DAW looks. After installation, rescan your plugin list and you should see both Technoboy and Tuneboy listed separately. They don't come with a library manager or preset browser, so you'll just open them and start clicking through the built-in presets.
Get the Full Details
Common Problems And What Actually Fixes Them
One issue I ran into repeatedly was CPU usage spiking when you opened the plugin window. The GUI isn't lightweight, and the waveform displays refresh constantly even when you're not touching anything. I solved it by minimizing the plugin window as soon as I loaded a pattern and only bringing it back up when I needed to adjust something. It sounds trivial but it cut my CPU load noticeably on an old dual-core machine. Another problem is MIDI mapping. These plugins don't ship with any factory MIDI controller mappings, and they don't save them either. If you assign a knob to a hardware fader one day, close your DAW, and come back the next day, the mapping is gone. I ended up writing down my most-used mappings on a sticky note next to my desk. That's how long ago this was. The biggest edge case I hit involved velocity sensitivity. Tuneboy's kick patterns respond to incoming MIDI velocity, but only in certain pattern slots. If you're programming drums and your kicks sound weak in one bar but strong in the next, check which pattern you're on — some slots are velocity-sensitive and some are fully static. There's no indicator in the UI telling you which is which. I figured it out by trial and error over about two hours of testing.
What They Were Good For And Where They Fall Apart
Technoboy and Tuneboy were useful for sketching ideas quickly. If you needed a techno track from zero to a basic arrangement in thirty minutes, these plugins could do it. The patterns were decently programmed, and the synth voices had character — especially the bass lines on Tuneboy, which had that early-2000s European techno growl to them. Where they fail is in production-quality mixing. The internal effects are primitive by today's standards. The reverb on Technoboy is a single delay-verb hybrid with no damping control. The EQ on Tuneboy is a fixed three-band with resonance that tends to ring out if you push it past 12 o'clock. You will end up routing these through external EQs and compressors anyway, which defeats part of the point of using them as all-in-one instruments. They also don't support automation export in a reliable way. If you automate a filter cutoff inside Technoboy and then bounce your track, the automation may or may not carry over depending on your DAW version and whether the plugin was running in sync or standalone mode. I learned this the hard way on a project I was submitting to a label in 2005 — the final master had completely different filter movements than what I'd written because the plugin dropped its automation data during rendering. I had to re-record those automations manually from memory, which took another afternoon.
Should You Use Them Now?
If you're making music in a genre that draws from early 2000s techno, Eurodance, or hard dance, these have a specific sonic signature that's hard to replicate exactly with modern plugins. The saturation character, the pattern phrasing, the way the bass voices distort — there's something about it that feels period-specific in a useful way. But if you're looking for a modern production workflow, you'll be frustrated. No MIDI Learn, no 64-bit native support, no updates, no documentation. It's basically archaeology at this point. I treat them like a vintage gear piece — fun to experiment with, limited in scope, and best used for specific color rather than as a foundational tool. If you want to track them down, search for the original software names along with "VST download" and look on archive-style forums. The files are out there. Just be aware you're working with abandoned software from over twenty years ago, and some of those downloads may contain unwanted bundled content if you aren't careful about where you grab them from. I stuck to known community sources and double-checked file hashes against what others had posted back in the day.
