You forgot all the annoying issues that crop up when trying to get a game to even run. Sound, memory, other drivers. Back then you spent more time configuring shit then actually playing your damn game >:E

Also Windows 3.1 sucked, did anyone actually use that thing?

I used 3.1, but mainly to play Tetris and Ski Free.

But yeah, I remember spending hours trying to clear 512kb of lowmem to get a game to run, some of them required even more memory IIRC, and those could be a real bitch to get running even if you had a total of 2mb of RAM available because of the way it was split between low, high and extended memory.

There were lots of cool programs for Windows 3.1.

- SkiFree
- Neko
- and many more.


Edit: Oh, right, and Johnny Castaway.

You know, it’s at times like this, when weird people on the internet are waxing nostalgic about horribly obsolete operating systems that sometimes were quite shitty even back then that I really wish I’d listened to what my mother told me when I was young.

You can still run DOS as main OS if you want. Knock yourself out.

Did Sarcasm escape you, God of Sarcasm?

EVERYTHING was inaccessible on Windows 8, or seemed that way.

I have no doubt they have ways to start the commandline in windows 10, but it's not going to be one of the base applications like it used to be where it was under the base program files listing. Worse probably if you have a laptop or tablet that runs windows 10, since it's useless to you overall.
I don't know if i'd want to. I'll take a commandline only linux install.

Far Manager
Batch files work
It's stable when you know your gpedit.msc
File searching works, lrn2index
vmware for 3.11
isn't spyware, go and learn some networking then log all network traffic and check it yourself, nothing that suspicious going on, when you turn everything off, cortana and bing integration isnt supported (aint missing that shit either) in my country so maybe i get some connections less?
Powershell is awesome compared to old cmd (although it's on older versions aswell, but not so integrated that you can switch cmd with powershell)

And CMD.EXE, in turn, is quite a bit better than COMMAND.COM was.
Oh? I just hit the Windows key, type "CMD", and hit return. (Same method as how I've launched every application since Vista and the start menu search appeared. In 2000 and XP I, of course, had to hit WinKey-R, then type "CMD" and hit return. Why bother messing around with a pointing device when the keyboard is much more efficient?)

I liked how DOS games were always self-contained. All the needed parts were there in the game directory (+ the CD if it used one).

It didn't fail because you had installed MS Visual Studio C++ 2009, not 2008, or because the new Quicktime installed on your system somehow clashed with the Quicktime version the game was expecting, or the audio codecs installed to your system made the whole game silent, or you having a wrong version of NVidia PhysX...

If the game needed e.g. certain video player to play the game videos, then it was included with the game, and that's that. No fuss, and absolutely no problem different games requiring different versions of the same software, as each would have its own copy of it inside the game directory.

Other than that though, I can think of only drawbacks to DOS, compared to DirectX/Windows 9x gaming. I especially liked that we didn't have to depend on certain HW manufacturers anymore, like needing a 100% Soundblaster compatible sound card to get sounds (just to be sure, even if many games also supported some of its competitors), or 3D acceleration being all about 3Dfx Voodoo series. Getting rid of that dependency opened up the flood gates for HW competition, meaning more performance for less money. Otherwise we would still be using 3Dfx Voodoo 12 which has merely a faster framebuffer than Voodoo 11.

Alternatively, right click the start menu, click "Command Prompt" or "Command Prompt (Admin)". Or Win+R, cmd, though I can never recall how to run it elevated from there.

Runas? Of course, it's not quite as simple as *nix' "sudo" as it needs do know which user you want to run the command as, but it has some other switches to set which environment and access you need.

From what I recall, there is a modifier to enter for the Win+R dialog that will result in the command being run elevated. I always look for it if/when needed, then promptly forget about it.

Pre-post edit: Looked for it. On Win7, Ctrl-Shift-Enter in the Win+R dialog will run it elevated. On Win8 and Win10, it will not through the Win+R dialog, but Ctrl-Shift-Enter will run it elevated from the start search screen, no matter the program.

This Windows 10 F/U/D is getting tiring.

It's far more stable than Windows Vista ever was and has far less issues than I've seen in an OS.