this post was submitted on 26 Apr 2024
833 points (97.7% liked)

Open Source

30984 readers
470 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 256 points 6 months ago (1 children)

I love that they specify that they're not accepting pull requests.

[–] [email protected] 21 points 6 months ago

Even funnier when it's their own platform and it has been missing the feature to disable them for so long afaik

[–] [email protected] 150 points 6 months ago (2 children)

The MS-DOS v1.25 and v2.0 files were originally shared at the Computer History Museum on March 25th, 2014 and are being (re)published in this repo to make them easier to find[.]

[–] [email protected] 129 points 6 months ago

In 2014, MS-DOS 1.25 and 2.0 were released under a Microsoft shared-source license (Microsoft Research License) which forbids redistribution

In 2018, both versions were published to GitHub and relicensed as MIT, making them properly open-source

Today, MS-DOS 4.00 was added to that repo, also under MIT.

load more comments (1 replies)
[–] [email protected] 131 points 6 months ago (10 children)

Ignore them. Send a pull request with the full source of Arch Linux.

[–] [email protected] 53 points 6 months ago* (last edited 6 months ago) (1 children)

Nah, just a giant compiled binary blob. That's what all the cool hackers do these days.

load more comments (1 replies)
load more comments (9 replies)
[–] [email protected] 97 points 6 months ago (1 children)

LOL, some of the comments in the source are gold.

https://github.com/microsoft/MS-DOS/blob/main/v4.0/src/DOS/ABORT.ASM

Note:  We do need to explicitly close FCBs.  Reasons are as follows:  If we
; are running in the no-sharing no-network environment, we are simulating the
; 2.0 world and thus if the user doesn't close the file, that is his problem
; BUT...  the cache remains in a state with garbage that may be reused by the
; next process.  We scan the set and blast the ref counts of the FCBs we own.
;
; If sharing is loaded, then the following call to close process will
; correctly close all FCBs.  We will then need to walk the list AFTER here.
;
; Finally, the following call to NET_Abort will cause an EOP to be sent to all
; known network resources.  These resources are then responsible for cleaning
; up after this process.
;
; Sleazy, eh?~
[–] [email protected] 17 points 6 months ago (1 children)

This is what people mean when they say hostile to users damn wow

load more comments (1 replies)
[–] [email protected] 86 points 6 months ago (12 children)

i remember writing .bat files and pretending they were really fancy update scripts when i was like ten they did nothing but it was still fun :)

[–] [email protected] 59 points 6 months ago (6 children)

Like half of my job is writing .bat files to automate stuff locally and not tell my boss that all I do anymore is double click the right things in the right order...

[–] [email protected] 24 points 6 months ago (3 children)

You can put in a timeout command at the end, and then call the next .bat file.

For example "TIMEOUT /T 60" waits for 60 seconds before resuming, or you can override it by pressing any key.

So if you know how long the wait time between scripts is, just write a master.bat and call them in order, with adequate waiting time in between.

[–] Tja 17 points 6 months ago

This guy is a master bat-er

load more comments (2 replies)
[–] [email protected] 17 points 6 months ago (8 children)

Next step, bind them to unused keys on your keyboard and press them in the right order

load more comments (8 replies)
[–] [email protected] 13 points 6 months ago (5 children)

Do you ever list your job title as Batman?

load more comments (5 replies)
load more comments (3 replies)
load more comments (11 replies)
[–] [email protected] 78 points 6 months ago (1 children)

I guess we now have a timeframe in which to expect the release of Windows.

[–] onlinepersona 54 points 6 months ago

30+ years after death. Better than 70+ years of copyright 🤷

Anti Commercial-AI license

[–] [email protected] 64 points 6 months ago* (last edited 6 months ago) (2 children)
[–] [email protected] 18 points 6 months ago (6 children)

I wonder if this is of any use to them or if they're already too far ahead.

[–] [email protected] 29 points 6 months ago

To my knowledge, FreeDOS has been a fairly complete implementation of DOS for a very long time, so this is probably not useful to them.

load more comments (5 replies)
load more comments (1 replies)
[–] [email protected] 54 points 6 months ago

MS-DOS, Source public available on March 25 2014 with MS Research License, released with as Free Software MIT license in 2018, this yer released as Open Source MS-DOS 4.0. Anyway, the Source code was available since 2014, only different licenses since then.

[–] [email protected] 38 points 6 months ago (2 children)
[–] Tja 17 points 6 months ago

Look at me, I AM FREE DOS now

load more comments (1 replies)
[–] [email protected] 35 points 6 months ago (3 children)

Cool, but why's that all of a sudden?

[–] [email protected] 18 points 6 months ago (1 children)

Laundering their reputation by open sourcing defunct historical code

load more comments (1 replies)
load more comments (2 replies)
[–] [email protected] 35 points 6 months ago (2 children)

What's the use case that would upset Microsoft the most?

[–] [email protected] 98 points 6 months ago (1 children)

Idk, maybe fork it under the name MS-DOSNT

load more comments (1 replies)
load more comments (1 replies)
[–] SuperNerd 32 points 6 months ago

So cool, thanks. As a kid I spent so much time in DEBUG, stepping through DOS's executables, and especially the Interrupt handlers. It's so neat to see the actual source code-- way easier to read and follow. I didn't know it was all written in assembly, from within Debug it sometimes seemed so messy and convoluted that I just assumed more was written in C.

[–] [email protected] 32 points 6 months ago (4 children)

Look at them, embracing open source like this, how wonderful.

[–] [email protected] 37 points 6 months ago

I'm sure the only reason why they waited this long is that they needed to make sure it's old enough that the companies they stole code from can't sue.

[–] [email protected] 14 points 6 months ago (4 children)

Can't wait for the OSS community to fork it and build some cool shit on top of this /s

load more comments (4 replies)
load more comments (2 replies)
[–] [email protected] 31 points 6 months ago (5 children)
load more comments (5 replies)
[–] [email protected] 24 points 6 months ago (1 children)

Where is the ctrl+alt+del function defined? I just want to see what made that sequence work. I'd also be interested in where ctrl+break is defined.

[–] [email protected] 36 points 6 months ago (3 children)

Ctrl+alt+delete was a separate interrupt line direct from the keyboard. That is, when you pressed the three keys, the interrupt signal was asserted, causing the CPU to jump to the interrupt service routine, which should be in the source code package.

load more comments (3 replies)
[–] [email protected] 22 points 6 months ago

Woah MIT license. That’s a lot more permissive than I expected.

[–] [email protected] 20 points 6 months ago (1 children)

!remind 10 years when they will release the source code of Windows 3.0 for non-commercial use

(3.11 will take another 10 years)

load more comments (1 replies)
[–] [email protected] 18 points 6 months ago (7 children)

Wake me up when they open source Windows 10/11.

load more comments (7 replies)
[–] [email protected] 17 points 6 months ago (4 children)

Would this have Bill’s code in it ? Or was he off the shop floor by then ??

[–] [email protected] 27 points 6 months ago* (last edited 6 months ago) (4 children)

I'd be surprised if Windows 11 didn't still have bill's code in it

load more comments (4 replies)
load more comments (3 replies)
[–] [email protected] 15 points 6 months ago

6.22 or foff

[–] [email protected] 15 points 6 months ago* (last edited 6 months ago)

https://github.com/microsoft/MS-DOS/blob/main/v4.0/src/DOS/CTRLC.ASM
; The user has returned to us.
So ominous.
; Well... time to abort the user.
Goodbye

[–] [email protected] 15 points 6 months ago

How much you wanna bet that a select few turbo-nerds are racing to debug it or something.

load more comments
view more: next ›