I really felt old when I found out our graduate student (physics) didn’t know how to use a DOS/Windows command line, but could use Python.
Absolutely no way. I’m older than dirt and remember when DOS was a thing, but I didn’t even use a computer in undergraduate classes. I saw one once. I took a beginning DOS class in 1989 and the only thing I remember about it is which building it was in.
This
Of the top of my gray head I recalled 4-5 commands like DEL and REM. With a bit of searching I could put something together.
Now if we expand to FORTRAN…
I can do it, that’s for sure. Whether I could do it on the first try in a matter of seconds or after a few shots to get the syntax right, I’m not sure. I spent my formative years in DOS, those commands are still there and, IIRC, typing /? after a command usually gives some half assed instructions.
And just for the record (becuase I saw some people not doing it this way), it would be way easier to CD a few times to get into the source files directory and then use the copy or move command than to try to type out the entire path in one shot.
One last tip that I used a lot of, the up arrow recalls the last thing you typed. It’s helpful for making small changes when you’re trying to work something out (like getting the syntax just right, so you can use it to bring back the last command with that giant path and just adjust a space or the command after a slash etc) .
Scenario more commonly referred to as ‘Tuesday’
My biggest issue is that post-college (which coincidentally was almost exactly the same time as the advent of Windows 95 and the decline of the command line on PCs), I’ve used UNIX/LINUX commands a lot more than Windows/DOS command line.
And I haven’t used either in a long time, so my thoughts were some sort of weird mishmash of UNIX/LINUX commands and DOS commands. I’d have to play with it a bit to be sure, but I’m pretty sure Happy Fun Ball was on target first, except that you’d have to do the dir /s part for every attached drive, not just C: until you found your file.
At any given time I have about 4 command prompt windows open. So yeah. 
I used to know. I learned on DOS. I wouldn’t have a clue now.
The answer is fdisk, right? Naw, I’d figure it out within a minute. I might mix up a UNIX and DOS command, but I’d figure it out without external help.
Yes. I’d have to play with it and it would take me a little while, but I did a lot of stuff on DOS, back in the day. Thanks to my ex, I guess.
Biggest pain in the ass is dealing with the ‘~’ for long file names in the post 8 character limit world. Other than that, I still write .bat and .sys scripts first before venturing into the dank basement of Visual Basic or C++
When I worked phone support for a small software company, the support techs had a standard fix for all users’ problems large and small: FDISK
That was always our solution of first resort! Never failed!
(Actually, that was just our inside joke among ourselves. We didn’t really tell users to FDISK. Well, not all that often anyway.)
I set up my boxes way back when with all sorts of stuff like Picnix (which appears to have been updated as recently as 2013!), aliases, etc., so I could use Un*x commands. While my memory of MS-DOS commands is hazy, at least I know enough to do the task in the OP (assuming the long file name was in error and a proper 8.3 name was intended). I’d be using the /? option a few times.
Now, if I had PowerShell or, even better, Cygwin, then we’re talking.
UNIX has been around longer than DOS, and it NEVER had drive letters!
I’m pretty good at DOS, and this gave me a nice head-start when I first started learning UNIX. The two resemble one another (for obvious reasons) rather a lot.
Love 'em both.
From memory, I know how to press <enter>. Beyond that I have to copy written directions, painfully slowly, so nervous you’d think I was defusing a nuculer weapon.
I tend to use Dos (FreeDos, not MS-Dos, but it’s pretty close) as a quick and dirty boot loader for embedded system development, so I’m very comfortable hacking around on a dos prompt.
As a kid, yes, I could have done this. Doubt I would remember now.
The hard part would be finding the directory, if there is a complicated directory structure. If it is a top directory, no sweat. Otherwise I would hope there was some sort of editor around and I would try dir c:\ /s > dirlist and then edit the file dirlist to find the directory I was looking for. What, the version of DOS is too old for output redirection? In that case I would be screwed, but so would everyone else.
I still use a command prompt for most of my work. A modern command prompt called TakeCommand which is a descendant of 4DOS. In that case, I would first index the directory tree (the command is cdd/s) and then type cd \someoldshit which would find it in the index and then the usual copy command copy oldfile a:.