Interesting... I'd assumed that #FreePascal's 16-bit #DOS cross-compiler was just ignoring the memory model I was setting. Turns out it wasn't, and I hadn't been reading the error messages properly. They're all failing for different reasons!
Surely I must be doing something wrong?
I'm struggling to find any information on issues like this, largely because hardly anyone uses it.
I might end up switching to the 32-bit DOS compiler, just to get something working.
I'm a masters postgrad studying #criminology with research interests in #cybercrime, digilantism (hacktivism, etc), and online deviance.
I also love #retrogaming (mostly #DOS games), #movies, and watching a lot of #tv. Sunlight burns but I sometimes go for little hikes and take camping trips with my dog.
1984, January 24th., Steve Jobs presented the first Macintosh Computer. We are glad to share our MAC POP Art, in tribute, in this Fediverse, to celebrate the 40th anniversary of that milestone with You, today.
Since the #MS & #IBM#DOS wasn't much more than a terminal with local CPU, floppy/hard disk support, the operating system was a "pirated" clone of #CPM. Even when IBM teamed up with Microsoft to break copyrights of Digital Research & Gary Kildall's IP on CP/M, #MSDOS wasn't up-to-date since there was no GUI available. #portrait@art work made in #SVG with @inkscape
Just released dos2ansi v0.4, with lots of #DOS#codepage s supported and a testmode to display them.
The next nice feature would be to use the actual terminal capabilities if output goes there. Very simple on *nix-like systems (#Linux, #FreeBSD, ...), just link #curses and use the termcap functions.
Thinking about #Windows again, either I keep relying on #UTF8 support (since #win7 IIRC? and still a bit buggy) and #ANSI sequences support (since #win10) .... OR I attempt to use the native #Console#API there (using special functions to write in #UTF16 and other special functions to set colors, which would require a major refactoring first 🙄)
Never really knew or thought about this, but DOS applications running under Windows were running in a virtual machine. Either emulated or on the Intel 80386 processor also with hardware virtualization.
This should boot up on your run of the mill S-100 based system with an 8086. Maybe an 8080 too? Also, it reportedly runs under #simH as a virtual machine. According to some, this is the earliest known version of #86-DOS, not long after replacing #QDOS as its successor....
I stumbled across this the other day - Old DOS Never dies... (ia801209.us.archive.org)
This should boot up on your run of the mill S-100 based system with an 8086. Maybe an 8080 too? Also, it reportedly runs under #simH as a virtual machine. According to some, this is the earliest known version of #86-DOS, not long after replacing #QDOS as its successor....