top | item 38828007

86-DOS Version 0.11 Found

43 points| xeeeeeeeeeeenu | 2 years ago |virtuallyfun.com | reply

11 comments

order
[+] ksaj|2 years ago|reply
One of my favourite DOS things was the DEBUG.EXE command. As far as I know, it was the only debugger that allows for the creation of debug files where you could do things like debug.exe < script.dbg to do low level things like replacing a disk partition table.

It was a very handy method of passing around binaries in text-oriented chat systems.

[+] drwu|2 years ago|reply
debug.exe did not like non-DOS EOL, which caused some problems when copying texts.

If I remembered correctly, debug was only capable of writing 64kB (mono-segment) data? Though one can always create an in-RAM program inside debug to output larger files.

[+] wingman-jr|2 years ago|reply
Yeah, I went looking for debug.exe on the listing as well. There was something just so visceral and direct about its usage that I enjoyed.
[+] tschak|2 years ago|reply
I made a very in-depth video that shows 86-DOS version 0.11 being used in-context to port a piece of code from CP/M-80 2.2, to 86-DOS using RDCPM, TRANS, and the ASM. I also directly address the elephant in the room "Was CP/M code stolen for MS-DOS?" https://www.youtube.com/watch?v=Zd7T5euID1E
[+] RetroTechie|2 years ago|reply
WordPress: "There has been a critical error on this website."

HN hugged? lol

[+] scruffyherder|2 years ago|reply
Nah, it was wp-mail-smtp. It completely crashed out on me.

> PHP Fatal error: Uncaught TypeError: ActionScheduler_Action::set_schedule(): Argument #1 ($schedule) must be of type ActionScheduler_Schedule, ActionScheduler_NullSchedule given

I've been able to take 2 million hits a day, so it's not that!