Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "ms-dos"
I wrote a Student Information system for my midterm project back in 94 written in Clipper and runs on MS-DOS.
I demoed & explained to the panel of professors how it tracks enrollments, payments, class schedules, grades and attendance of each and every student. Has user authentication, auditing and reporting functionalities.
It has a lite version also written in Clipper that can be installed on a Professor's laptop so that he/she can update records even at home, and would be able to sync with the db at school via a BBS. Telix for DOS (self-taught) was my choice for the BBS as it was shareware, has built-in Zmodem support and comes with it's own programming language called SALT (Script Application Language for Telix) that can be used for automating tasks. The lite version of my project would dump the updates on an ASCII file, compress the file using PKZIP, use the laptop's modem to dial-up the number to the school's BBS and send the file across using Zmodem protocol.
The main version would then download the file(s) from the BBS and proceed to do a sync.
After the doing the demo and answering all their questions the panel asked me to wait outside the room, called me back in after 15mins and told me that I don't have to attend that class for the remainder of the term. The happiness as the my classmates outside of the room gawked at me felt like King Midas himself gave my balls his golden touch.
Then in 97, 2yrs after I graduated, I accompanied my cousins to a different campus of the same school for their enrollment and right there on the bottom of the screen were my initials on a very very familiar UI! They actually used, and were still using, my school project. Needless to say my cousins didn't believe that it was written by me.15
I really, honestly, am getting annoyed when someone tells me that "Linux is user-friendly". Some people seem to think that because they themselves can install Linux, that anyone can, and because I still use Windows I'm some sort of a noob.
So let me tell you why I don't use Linux: because it never actually "just works". I have tried, at the very least two dozen times, to install one distro or another on a machine that I owned. Never, not even once, not even *close*, has it installed and worked without failing on some part of my hardware.
My last experience was with Ubuntu 17.04, supposed to have great hardware and software support. I have a popular Dell Alienware machine with extremely common hardware (please don't hate me, I had a great deal through work with an interest-free loan to buy it!), and I thought for just one moment that maybe Ubuntu had reached the point where it just, y'know, fucking worked when installing it... but no. Not a chance.
It started with my monitors. My secondary monitor that worked fine on Windows and never once failed to display anything, simply didn't work. It wasn't detected, it didn't turn on, it just failed. After hours of toiling with bash commands and fucking around in x conf files, I finally figured out that for some reason, it didn't like my two IDENTICAL monitors on IDENTICAL cables on the SAME video card. I fixed it by using a DVI to HDMI adapter....
Then was my sound card. It appeared to be detected and working, but it was playing at like 0.01% volume. The system volume was fine, the speaker volume was fine, everything appeared great except I literally had no fucking sound. I tried everything from using the front output to checking if it was going to my display through HDMI to "switching the audio sublayer from alsa to whatever the hell other thing exists" but nothing worked. I gave up.
My mouse? Hell. It's a Corsair Gaming mouse, nothing fancy, it only has a couple extra buttons - none of those worked, not even the goddamn scrollwheel. I didn't expect the *lights* to work, but the "back" and "Forward" buttons? COME ON. After an hour, I just gave up.
My media keyboard that's like 15 years old and is of IBM brand obviously wasn't recognized. Didn't even bother with that one.
Of my 3 different network adapters (2 connectors, one wifi), only one physical card was detected. Bluetooth didn't work. At this point I was so tired of finding things that didn't work that I tried something else.
My work VPN... holy shit have you ever tried configuring a corporate VPN on Linux? Goddamn. On windows it's "next next next finish then enter your username/password" and on Linux it's "get this specific format TLS certificate from your IT with a private key and put it in this network conf and then run this whatever command to...." yeah no.
And don't get me started on even attempting to play GAMES on this fucking OS. I mean, even installing the graphic drivers? Never in my life have I had to *exit the GUI layer of an OS* to install a graphic driver. That would be like dropping down to MS-DOS on Windows to install Nvidia drivers. Holy shit what the fuck guys. And don't get me started on WINE, I ain't touching this "not an emulator emulator" with a 10-foot pole.
And then, you start reading online for all these problems and it's a mix of "here are 9038245 steps to fix your problem in the terminal" and "fucking noob go back to Windows if you can't deal with it" posts.
It's SO FUCKING FRUSTRATING, I spent a whole day trying to get a BASIC system up and running, where it takes a half-hour AT MOST with any version of Windows. I'm just... done.
I will give Ubuntu one redeeming quality, however. On the Live USB, you can use the `dd` command to mirror a whole drive in a few minutes. And when you're doing fucking around with this piece of shit OS that refuses to do simple things like "playing audio", `dd` will restore Windows right back to where it was as if Ubuntu never existed in the first place.
Thanks, `dd`. I wish you were on Windows. Your OS is the LEAST user friendly thing I've ever had to deal with.28
It were around 1997~1998, I was on middle school. It was a technical course, so we had programing languages classes, IT etc.
The IT guy of our computer lab had been replaced and the new one had blocked completely the access on the computers. We had to make everything on floppy disks, because he didn't trusted us to use the local hard disk. Our class asked him to remove some of the restrictions, but he just ignored us. Nobody liked that guy. Not us, not the teachers, not the trainees at the lab.
Someday a friend and me arrived a little bit early at the school. We gone to the lab and another friend that was a trainee on the lab (that is registered here, on DevRant) allowed us to come inside. We had already memorized all the commands. We crawled in the dark lab to the server. Put a ms dos 5.3 boot disk with a program to open ntfs partitions and without turn on the computer monitor, we booted the server.
At that time, Windows stored all passwords in an encrypted file. We knew the exact path and copied the file into the floppy disk.
To avoid any problems with the floppy disk, we asked the director of the school to get out just to get a homework we theorically forgot at our friends house that was on the same block at school. We were not lying at all. He really lived there and he had the best computer of us.
The decrypt program stayed running for one week until it finds the password we did want: the root.
We came back to the lab at the class. Logged in with the root account. We just created another account with a generic name but the same privileges as root. First, we looked for any hidden backup at network and deleted. Second, we were lucky: all the computers of the school were on the same network. If you were the admin, you could connect anywhere. So we connected to a "finance" computer that was really the finances and we could get lists of all the students with debits, who had any discount etc. We copied it to us case we were discovered and had to use anything to bargain.
Now the fun part: we removed the privileges of all accounts that were higher than the trainee accounts. They had no access to hard disks anymore. They had just the students privileges now.
After that, we changed the root password. Neither we knew it. And last, but not least, we changed the students login, giving them trainee privileges.
We just deleted our account with root powers, logged in as student and pretended everything was normal.
End of class, we went home. Next day, the lab was closed. The entire school (that was school, mid school and college at the same place) was frozen. Classes were normal, but nothing more worked. Library, finances, labs, nothing. They had no access anymore.
We celebrated it as it were new years eve. One of our teachers came to us saying congratulations, as he knew it had been us. We answered with a "I don't know what are you talking about". He laughed and gone to his class.
We really have fun remembering this "adventure". :)
PS: the admin formatted all the servers to fix the mess. They had plenty of servers.4
My dad's old MS-DOS computer (can't remember specs) when I was 5 or 6 years old. This got me into gaming. I always had to ask him to execute the games I wanted to play cause I didn't know how to do it. One of the first games I ever played was Wolfenstein 3D. Was so scary I didn't want to exit the first room :D4
Microsoft are getting a lot of pats on the back today for open sourcing MS-DOS. It might have meant something before FreeDOS was so well established and mature, but now... really, who gives a shit? Even more significant, they already "open sourced" it before, just not hosted on GitHub.
Here's the thing. Going open source is like losing your virginity. You only get to do it once, you can't take it back, and you certainly can't claim to be doing it again just because you're using a different host.9
I seriously do not understand the rants against Windows.
I love Windows 10 (got as free upgrade from MS), and have no issues with MacOS or Linux OS. I use them as well but do all serious work on Windows.
All my life, I have worked on business / commercial side and picked up Web development in last couple of years. I started using computers on DOS in 1992, and shifted to Windows 3.0 in 1995. There was no Mac or MacOS back then.
For serious work, I purchased a old Dell Precision M4700 workstation grade laptop with quad-core i7, at throwaway price, got 32GB RAM, 2.4TB (1x2 TB + 400gb) of SSD on super sale online, and installed it myself. It easily supports dual 4k monitors.
Git-bash on windows allows all the necessary linux command line on windows. Though not tried, Windows 10 allows embedded Ubunutu with linux terminal. Web development tools like - VSCode, git, github / bitbucket clients, NVM/Node, React / Redux / Webpack / Gatsby / Jest, REST clients, GraphQL client and server, Graph Server, Chrome PWA / Chrome Dev Tools, http/Websocket/WebRTC interception, Google Firebase SDKs, AWS sdks, cloud utilities, CI/CD tools work flawlessly. Windows even has its own package manager for applications.31
Oh look MS-DOS on GitHub?!
Time to run through more code I don't understand and see what I can learn and potentially port :-D1
"I’ve noticed lately that the paranoid fear of computers becoming intelligent and taking over the world has almost entirely disappeared from the common culture. Near as I can tell, this coincides with the release of MS-DOS." - Larry DeLuca
The initial version of DOS was called QDOS – Quick and Dirty Operating System. The bullshit they tel you about DiSk oPeRaTinG sYsTeM is a lie. It was renamed when MS acquired it.7
That moment when you realize you're using a Hackintosh with VirtualBox and a CF card to install a Beta version of MS-DOS with DOS SHELL that your brother found on an old BBS forum; on an IBM 5150 from 1981.
A plain computer illiterate guy rings tech support to report that his computer is faulty.
Tech: What's the problem?
User: There is smoke coming out of the power supply.
Tech: (keeps quiet for the moment)
Tech: You'll need a new power supply.
User: No, I don't! I just need to change the startup files.
Tech: Sir, the power supply is faulty. You'll need to replace it.
User: No way! Someone told me that I just needed to change the startup and it will fix the problem! All I need is for you to tell me the command.
Tech support: 10 minutes later, the User is still adamant that he is right. The tech is frustrated and fed up.
Tech support: (hush hush)
Tech: Sorry, Sir. We don't normally tell our customers this, but there is an undocumented DOS command that will fix the problem.
User: I knew it!
Tech: Just add the line LOAD NOSMOKE <nosmoke> at the end of the CONFIG.SYS. Let me know how it goes.
10 minutes later.
User: It didn't work. The power supply is still smoking.
Tech: Well, what version of DOS are you using?
User: MS-DOS 6.22.
Tech: That's your problem there. That version of DOS didn't come with NOSMOKE. Contact Microsoft and ask them for a patch that will give you the file. Let me know how it goes.
1 hour later.
User: I need a new power supply.
Tech: How did you come to that conclusion?
Tech: (hush hush)
User: Well, I rang Microsoft and told him about what you said, and he started asking questions about the make of the power supply.
Tech: Then what did he say?
User: He told me that my power supply isn't compatible with NOSMOKE.4
I saw a rant about some department still using win98, and it reminded me, when I was in school the school library used MS-fucking-DOS, windows 10 was already out by that time...
The librarian lady was really surprised I even knew what it was, which meant she knew it was fucking ancient2
Instead of asking how old people are, how about this:
Post the specs of the first computer you regularly used. I will start.
Tandy 1000 SX. Not one, but TWO 5 1/4" floppy drives. An 8088 CPU and 640K of RAM. The operating system was MS-DOS 3.2, which was always in the A: drive.
We used it to make papers for school in Wordstar, and my parents made spreadsheets in Lotus 1-2-3. We learned to type on it. We played Space Quest, King's Quest, Carmen Sandiego, and Lords of Conquest on it. We transcribed BASIC programs from the, "BASIC Training" column in 3-2-1 Contact magazine.
We LOVED that computer.8
beginning to learn QBASIC as i'm looking to port my demoscene stuff from TI-BASIC (based on QB) to MS-DOS. Graphics are weird here and i can't just drop in Assembly snippets so scrollers are gonna be a bitch. However...
Screen mode 13's kinda nice, ngl.5
Wow, I would have to write a book to describe all of the positive ways coding and a long career in technology have impacted my life.
In short, it has provided me with a great life, career, passion and so many friends I can 'talk shop' with.
A great journey from punch cards to PC's to LAN's to a global network. From 8" platters to 10mb Bernoulli boxes to 5 1/4 to 3 1/2 to terabytes in your pocket!
From Brick size 'mobile' phones and 35 lb Compaq and Osborne 1 'laptops' (I know some of you remember those) to today's amazing miniaturization.
From MS DOS and Dr. DOS to lots of OS's. I had better stop as it seems I am writing a book in a rant 😀
Best of all... my son went into the family business and now we 'talk shop'!
It has been an amazing ride!1
My dad bought a computer when i was 6 or 7. Trying to launch games via ms-dos.
But we also had the “minitel” a french thing that connected you to a network. I played games on that too.1
On a 8088 Acer 500+ with a whopping 640KB RAM with Clipper and dBase III+ on MS-DOS 3.30 back in 1988.
Recently started computer science course at college. Linux user since 3 years.
Started to learn MS-DOS yesterday.
Teacher: To create a file use 'copy con <filename>'
Me (thinking): WTF, DOS doesn't have a seperate create command like 'touch'5
so i need a utility written in C because MS-DOS but i can't figure out how MS-DOS APIs work and there's no docs available so if anyone has used Borland C i'd be grateful if you could help me out on how the hell anything works7
So... My brother got his computer when I was 6 years old... It was a 286 with the new 64mb HD and the screen had 16 gray scale color...
Latter it was given to me when my brother got his 486dx2 and I did a course in ms-dos and batch scripting.
That's it, lots of sfigher, puzzle bubble, Dina blast, wolfeinstein 3D...1
Why so many people complain about Vim? Just drink Nuka Cola.
Anyway, my first scripts were done with edit, in MS-Dos...
Anyone who can't learn how to use a tool... Well there are so many IDEs...
Just use something else1
I was at school. Should be around 7 years old. They bought some new computers: XTs with green monitors.
I saw it as asked: how can I use one of there? They answered it was just to mid school to students, so I asked to have some typewriter classes.
A few years after, when I was finishing the typewriter classes, I used a IBM 286 for the first time at a friend's house. I've been using and studying it since that day. I just loved to use MS-DOS and the 5" disks.
When they decided to deprecate the old app that went back to early DOS, they decided to use VB.NET because they'd used some VBA and were familiar with it. Except they had a vague idea that C# was faster and decided to write the OpenGL code in that. Also they had some C++ code and decided to write more of it, accessed by the main program via COM.
I come in and the decision is made to integrate some third-party libs via a C++/CLI layer. On one hand screw COM, but on the other we're now using two non-standard MS C++ extensions. Then we decide we need scripting, so throw in some IronPython.
I'm the build engineer for all this, by the way. No fancy package managers since almost all the third-party dependencies are C++; a few of them are open source with our own hacks layered on top of the regular code, a few are proprietary. When I first started here you couldn't build on a fresh SVN checkout (ugh) without repeatedly building the program, copying DLLs manually, building again, ad nauseum. I finally got sick of being called in to do this process and announced that I was fixing it, which took a solid week of staring at failed compiler output.
Every so often someone wants to update that damn COM library and has to sacrifice a goat to figure out how the hell you get it to accept a new method. Maybe one day I'll do a whole rant just based on COM.
Dad brought home a i386 based desktop with MS-DOS and Windows 3.1 back in 1993.
Learned how to use basic command line to run video games like Commander Keen, Jazz Jackrabbit, Kilo Blaster, Wolfenstein, Doom, Raptor. All the classics. Good times.
I think we still have the computer somewhere.
i was around 10 year old. That time we used to use ms dos for drawing lines, traingle and stuff using commands that will print on execution . I was having hard time understanding it . I went to my father and asked for help. He taught me how it works and everything is logic only nothing else.That was life changing movement for me. Use to score very good in computers then on . Now a full time web developer
I was probably about 7 and my parents just bought their first computer.
It was on our living room table for at least a couple of weeks and the main attraction of the whole family.
I learned how to install MS DOS, some software and even games.
Tried to install MS-DOS 6.22. Was not fun at all. Tried 3 iso flashers in total. The closest that happened to DOS was unetbootin getting bootlooped on the 10 second countdown to automatic system start. I gave up on it eventually.
Alright, so i'm making an MS-DOS 6.22 box on a modern laptop: 80GB HDD (SATA 2), 2GB RAM (rip 9x, smallest stick I got,) AMD x64 CPU (they stuck a single-core 1GHz CPU in a laptop meant for Win8.0, with age it's slowed to around 600MHz effective, so it's more suited to being an XP box but I have no XP drivers...)
I'm not strapped for space at all (I could make 4 2GB partitions with no issue) but should I use DRVSPACE? I've never used DOS-era disc compression (and won't fucking touch DoubleSpace, for those that remember that and its issues) and i'm wanting to fuck with it some.
EDIT: fuck CSM, gotta use GRUB to load DOS...2