Earlier quoted context omitted.
"He was the designer of the MS-DOS executable file format, and the headers of that file format start with his initials: the ASCII characters 'MZ' (0x4D, 0x5A)" Ref: https://en.wikipedia.org/wiki/Mark_Zbikowski
> In 2006, he was honored for 25 years of service with the company, the third employee to reach this milestone, after Bill Gates and Steve Ballmer. He retired the same year from Microsoft Considering he "only" joined MS in 1981 (which was found in 1975?), I'm surprised no more people between him and Bill stayed at MS. Also shouldn't Paul Allen still count (from Wikipedia, "Allen resigned from his position on the Micr…
Open Sourcing DOS 4
361–370 of 382 posts
Re: Open Sourcing DOS 4
#362It looks like "brain damaged" was the developer's go-to insult when frustrated :D 2024-04-25 19:35 ~/sort/dl/MS-DOS % grep -nri 'brain[ -]damage' . ./v4.0/src/DOS/STRIN.ASM:70:; Brain-damaged TP ignored ^F in case his BIOS did not flush the ./v4.0/src/DOS/PATH.ASM:24:; MZ 19 Jan 1983 Brain damaged applications rely on success ./v4.0/src/DOS/FCBIO.ASM:28:; MZ 15 Dec 1983 Brain damaged programs close FCBs multiple ./v4…
Looks as if someone did an s/retarded/brain damaged/g before making the code public :)
Re: Open Sourcing DOS 4
#363I appreciate the work in getting this open sourced but I find it telling that this had to be done through an outside motivator. There seems to be no internal "ticking clock" to get some of these things out in to the open. That's fine no one is owed the source code for this stuff or anything, but it would be nice if there was more interest on the side of the companies to get some of their formative history out so peop…
For some insight, look how people are combing for curse words/ devs making jokes about people being brain damaged etc. There is no upside for the company, and all that has to happen is some unsavory politically incorrect joke to get missed from sanitization and the are on the cancelled chopping block.
Re: Open Sourcing DOS 4
#364Earlier quoted context omitted.
For some insight, look how people are combing for curse words/ devs making jokes about people being brain damaged etc. There is no upside for the company, and all that has to happen is some unsavory politically incorrect joke to get missed from sanitization and the are on the cancelled chopping block.
I think I lost it when they suggested we stop using the term 'sanity check' or 'sane defaults' because they might offend, well, brain damaged people. I am close to writing a browser extension that does a find and replace to reverse change these imposed, humourless, coddled changes.
Re: Open Sourcing DOS 4
#365Earlier quoted context omitted.
As someone who recently asked our QA team to change the name of one of our test suites from "sanity test" to "quick test", maybe I can provide some perspective. Many software developers like me have faced challenges to our mental health. Indeed, there has been a time or two when I questioned my own sanity. And perhaps the sanity of some of my colleagues! It's not so much that there is something inherently wrong with…
1. Other terms are neither more descriptive nor more neutral. 2. If someone has a problem with the term "sanity check", they are overly sensitive and they need to adjust to the realities of life. It is unreasonable to expect everyone to coddle them.
Re: Open Sourcing DOS 4
#366Earlier quoted context omitted.
We have literally no idea what the 'sanity test' involved actually did, and the common use in computing has little connection to any such use in psychology. https://en.wikipedia.org/wiki/Sanity_check informs me: "A sanity check or sanity test is a basic test to quickly evaluate whether a claim or the result of a calculation can possibly be true." ... "In computer science, a sanity test is a very brief run-through of…
I cannot cop to "smoke test" being interchangeable with "sanity test," in any way. Smoke tests are obvious crashes, often before any real input. I had a friend on the build team of Windows NT 5.0 (until it was called Windows 2000) and their version of smoke test was "can it boot up to the login screen," and that's similar to working in electronics, where powering up your machine or circuit is all you do and you hope…
Describe the difference between a test and a "sanity test?"
Re: Open Sourcing DOS 4
#367Earlier quoted context omitted.
I cannot cop to "smoke test" being interchangeable with "sanity test," in any way. Smoke tests are obvious crashes, often before any real input. I had a friend on the build team of Windows NT 5.0 (until it was called Windows 2000) and their version of smoke test was "can it boot up to the login screen," and that's similar to working in electronics, where powering up your machine or circuit is all you do and you hope…
We do not know if what was described as a "sanity test" actually meets your definition of a sanity test, or was used for some other purpose like a smoke test. A quick look using Google Scholar finds people using "sanity test" for smoke testing, like "Typical behavior is to allocate any special resource requirements it needs, map the device into virtual address space, initialize the device and perform a brief “sanity…
I think this even is contradictory for what a lot of people think a "sanity test" means. A "test" may check that something is correct, where a sanity test would be a lower fidelity test that simply checks that something is not obviously wrong.
Re: Open Sourcing DOS 4
#368Earlier quoted context omitted.
As someone who recently asked our QA team to change the name of one of our test suites from "sanity test" to "quick test", maybe I can provide some perspective. Many software developers like me have faced challenges to our mental health. Indeed, there has been a time or two when I questioned my own sanity. And perhaps the sanity of some of my colleagues! It's not so much that there is something inherently wrong with…
> Many software developers like me have faced challenges to our mental health. It's a stressful industry at times, probably almost everyone has had crap times at one point or another. And then there's Covid, which affected everyone. Doesn't mean every mention of the word "sanity" needs to be expunged from our language though. :( :( :( That way lies er... madness. (!) ;)
Re: Open Sourcing DOS 4
#369Earlier quoted context omitted.
> My brain is rusty It is. Because: > but I feel like MSDOS 5.11 was where things finally just worked There was no MS-DOS 5.11. It went 4, 4.01, 5, 6, 6.2, 6.21, 6.22. IBM had a few extra versions as the divorce was occurring at the time.
> There was no MS-DOS 5.11. There was Windows 3.11 which ran on top of MS-DOS 5.0, the two numbers probably got mixed in their memory.
But neither of them ran on any particular version of DOS. They ran on PC DOS, MS-DOS and DR-DOS -- although Microsoft tried very hard to block the latter:
https://en.wikipedia.org/wiki/AARD_code
They ran on DOS 3.3, 4, 5, 6, and 7.
There's nothing at all that links them especially to MS-DOS 5.
Re: Open Sourcing DOS 4
#370Earlier quoted context omitted.
I think I lost it when they suggested we stop using the term 'sanity check' or 'sane defaults' because they might offend, well, brain damaged people. I am close to writing a browser extension that does a find and replace to reverse change these imposed, humourless, coddled changes.
How dare people attempt to be more empathetic towards others.
I empathise with myself first, and will use what ever word feels right in the situation. I'd rather speak my mind than please everyone. That's sanity for me and for many others.