Tech Support Blog · Chapter 1
From DOS Prompts to the Cloud:
A Career Built on Every Generation of Tech
Over three decades of hands-on experience with every major operating system — from blinking cursors to virtual machines.
Series: From DOS to the Cloud · Chapter 1 of 5 · Publish: June 1, 2026
There's a certain pride that comes from knowing your craft inside and out — not from a certification exam, but from thousands of hours in the trenches, fixing real problems for real people. When I tell you I've been doing this for over 30 years, I don't say it to brag. I say it because every OS I've ever supported lives in my hands like muscle memory. This is the story of every major operating system I've worked with — and what each one taught me about great tech support.
// CHAPTER ONE: THE COMMAND LINE ERA
C:\>_1981 – 1995
MS-DOSMicrosoft Disk Operating System · 1981 – 1995
Before mice and windows, there was the blinking cursor. MS-DOS was the backbone of personal computing throughout the 1980s and early 90s. Every command was typed by hand — no icons, no menus, no guardrails. You either knew your way around
AUTOEXEC.BAT, CONFIG.SYS, and HIMEM.SYS, or you didn't get far.C:\> echo "This is where I learned to think like a machine."
My first day on the job, a user couldn't print. No error message — just silence. I spent an hour tracing IRQ conflicts and manually editing CONFIG.SYS. That hour taught me more about troubleshooting methodology than any textbook ever could.
DOS taught me to read error codes, write batch scripts, manage memory with HIMEM.SYS and EMM386, and understand exactly what a computer was doing at every step. When you have no GUI to hide behind, you learn fast.
C:\> That foundation still shapes how I diagnose problems today.
My first day on the job, a user couldn't print. No error message — just silence. I spent an hour tracing IRQ conflicts and manually editing CONFIG.SYS. That hour taught me more about troubleshooting methodology than any textbook ever could.
DOS taught me to read error codes, write batch scripts, manage memory with HIMEM.SYS and EMM386, and understand exactly what a computer was doing at every step. When you have no GUI to hide behind, you learn fast.
C:\> That foundation still shapes how I diagnose problems today.
Program Manager1992 – 1995
Windows 3.1Microsoft Windows · 1992 – 1995
Windows 3.1 was the first glimpse most users had of a graphical desktop. It ran on top of DOS rather than replacing it — which meant tech support had to know both worlds simultaneously. Program Manager, File Manager, and Print Manager became daily destinations. General Protection Faults (GPFs) were a constant companion, and 16-bit application crashes tested everyone's patience.
> General Protection Fault. That phrase still makes me smile.
Windows 3.1 was where I learned the art of user communication. Suddenly, people who had never touched a computer before were sitting in front of them — and calling me when the magic stopped working. I became fluent in two languages: the technical language of the machine, and the calm, clear language of the end user.
I also became an expert in WIN.INI and SYSTEM.INI — the configuration files that governed everything Windows 3.1 did. That attention to detail in configuration management is something I still bring to every engagement.
Windows 3.1 was where I learned the art of user communication. Suddenly, people who had never touched a computer before were sitting in front of them — and calling me when the magic stopped working. I became fluent in two languages: the technical language of the machine, and the calm, clear language of the end user.
I also became an expert in WIN.INI and SYSTEM.INI — the configuration files that governed everything Windows 3.1 did. That attention to detail in configuration management is something I still bring to every engagement.
Windows 3.1 taught me that great tech support isn't just about fixing the machine — it's about calming the person sitting in front of it.
Citrix WinFrame / MetaFrame1993 – present
Citrix WinFrame / MetaFrameCitrix Systems · 1993 – present
Long before 'the cloud' was a buzzword, Citrix was doing it. WinFrame allowed multiple users to run Windows sessions on a single server, accessing applications remotely over thin clients and dial-up connections. It was virtualization before virtualization had a name. Managing a Citrix environment required deep knowledge of server resources, session management, printing, and network protocols.
> Citrix was the first time I saw the future — and I didn't even know it.
Supporting Citrix environments in the mid-90s meant thinking about computing in an entirely new way. Instead of one user, one machine — you had dozens of users sharing a single server's resources. Printer mapping, session shadowing, ICA protocol tuning — complex, demanding, and I loved every second.
What Citrix taught me then is precisely what powers cloud VDI today. When I support Microsoft Azure Virtual Desktop for clients today, I'm drawing on fundamentals I built back in the WinFrame days.
> That's the value of deep roots: they grow into tall trees.
Supporting Citrix environments in the mid-90s meant thinking about computing in an entirely new way. Instead of one user, one machine — you had dozens of users sharing a single server's resources. Printer mapping, session shadowing, ICA protocol tuning — complex, demanding, and I loved every second.
What Citrix taught me then is precisely what powers cloud VDI today. When I support Microsoft Azure Virtual Desktop for clients today, I'm drawing on fundamentals I built back in the WinFrame days.
> That's the value of deep roots: they grow into tall trees.
// COMING NEXT IN THIS SERIES
This is just the beginning. In the next installment, I'll walk through the game-changing release of Windows 95, the reliability of Windows 98, and the enterprise power of Windows NT 4.0.
30+ Years of Experience.
One Call Away.
From your first DOS batch file to your last cloud migration — we've seen it all and fixed it all. Let's talk about what we can do for your business.
Get In Touch →- By: James Phillips
- Date: May 24, 2026
- Contact US
