MS-DOS VS Wekan

This 4.0 code contains references to 4.00, though: https://github.com/microsoft/MS-DOS/blob/main/v4.0/src/BOOT/...

I recently stumbled across the MS-DOS 1.25 and 2.0 source code [1].

[1] https://github.com/microsoft/MS-DOS

“Despite this reduction in scope for MS-DOS 2.0, it did carry many bits of XENIX. The system adopted I/O redirection via less-than and greater-than symbols, piping, a hierarchical directory tree, file handles […]”

The source code for MSDOS 2 is available and the file descriptor stuff appears to be in https://github.com/microsoft/MS-DOS/blob/master/v2.0/source/... and XENIX2.ASM. It stands in contrast to the File Control Block API which MSDOS 1 (née 86-DOS) modeled after CP/M’s API.

Asynchronous I/O figures in prominently in Windows NT. I was really surprised to see[0]:

Each driver in the chain defines two entry points; the strategy routine and the interrupt routine. The 2.0 DOS does not really make use of two entry points (it simply calls strategy, then immediately calls interrupt). This dual entry point scheme is designed to facilitate future multi-tasking versions of MS-DOS. In multi-tasking environments I/O must be asynchronous, to accomplish this the strategy routine will be called to queue (internally) a request and return quickly. It is then the responsibility of the interrupt routine to perform the actual I/O at interrupt time by picking requests off the internal queue (set up by the strategy routine), and process them. When a request is complete, it is flagged as "done" by the interrupt routine. The DOS periodically scans the list of requests looking for ones flagged as done, and "wakes up" the process waiting for the completion of the request.

I didn't realize that kind of forwarding-looking perspective was going into the design of MS-DOS.

[0] https://github.com/microsoft/MS-DOS/blob/master/v2.0/source/...

>Any others I'm missing?

I would suggest MS-DOS: https://github.com/microsoft/MS-DOS

Looks nice, I selfhosted https://github.com/wekan/wekan for a while, which is a MIT licensed heavily Trello-inspired alternative, does someone know both Wekan and Plankanban and can tell their differences?

Where can I get info, how to make required changes to get software running on s390x? For example, some software requires CPU-specific assembler code. I can not get some code to compile correctly:

https://github.com/wekan/wekan/wiki/s390x

Thanks for writing this.

I have added and removed about 4 million lines of code:

https://github.com/wekan/wekan/graphs/contributors

to WeKan Open Source kanban:

https://wekan.github.io

You are not dumb. It is normal to feel frustrated, when figuring out, step by step, how something works, and what to do. It is like labyrinth. Having enough breaks, taking a walk when needed, having enough coping skills or adding more of them, having patience to keep notes of what is current position in that rabbit hole. If some way does not work, try some other way.

It is always about the basics. Many programming languages change syntax often. Some dependencies change.

For example, when writing some for database export:

1) There was no working code examples at documentation

2) Google etc searches had old info, did not work

3) I did not find from source code how it did work

4) ChatGPT, Bing AI etc examples did not work

5) So I tried with trial and error, what is correct syntax, character by character

For some error messages, sometimes Google search shows somebody having same problem, or even a fix. But if not, it's about reading source code of the software.

But this works when code is available, like in Open Source.

If something is binary executeable, then there is need to decompile, read assembler, deobfuscate, etc. That means even more required, I have not gone there yet. That is why I use and develop FOSS, when it is possible to more easily fix something, when it is broken.

Hi Wekan,

looks cool but IHMO suffers from confusing documentation and onramp.

It took me multiple attempts, days apart, after initially stumbling upon this comment to get a better sense of it.

The project homepage (https://wekan.github.io/) stresses the different installers but at that point I didn't know if I want to install it or not.

Clicking on the Features link (https://wekan.github.io/#features) just takes you a few lines down on the same page which doesn't tell you much.

I tried to find a link to the Github repo but that wasn't obvious either. Eventually I stumbled upon it by following the Docs and API links at the bottom but those are very small and hidden compared to the rest of the content on the page.

From the Docs wiki there is a much better list of Features (https://github.com/wekan/wekan/wiki#:~:text=Calendar-,Featur...) that tells me more of what I was looking for.

However, I still don't know what database backends are supported or how configurable those are which I need to know in order to assess my backup strategy and how much work it will be for me to maintain this for our intranet site.

Thanks! I added issue about it:

https://github.com/wekan/wekan/issues/4930

Try to look at wekan. https://wekan.github.io/

Deck is very minimal and not really suited for anything beyond simple, personal stuff, in my opinion. As far as self-hosted, my favorite is still Kanboard, which has a lot of plugins and themes to choose from. Leantime is good too and a bit different. I also like Vikunja and Wekan.

Have a look at Kanboard. For Android it can be used with kandroid (available on F-Droid). There is also WeKan with official app on Google Play Store