DOS ain't dead

open in text mode (O_TEXT) (Developers)

posted by tkchia , 03.03.2025, 15:09
(edited by tkchia on 03.03.2025, 15:24)

Hello kerravon,

> identical parameters. And then gets translated into
> an MSDOS extension (the same way that MSDOS 7 is an
> extension of MSDOS 2).

Well, that sounds like an idea.

Fun fact: some configurations of MS-DOS actually allow the backslash character code (0x5c) within a filename.
Under DOS/V (Japanese), a 0x5c byte may occur as part of a double-byte character code.
Some time back I tweaked my libi86 library to handle such cases.

Another fun fact (just discovered): MS-DOS apparently has some support (?) for using an EBCDIC character set as its global code page (via int 0x21, ax = 0x6602).
I am not sure how exactly it works though.
I suspect -- as with DOS/V -- this support is mainly useful for dealing with oddball character sets in file names.

> How come the original was able to be posted?

I used a HTML entity code to enter the double arrow.
I suppose the forum still has a bit of a problem dealing with some Unicode characters.

Thank you!

---
https://gitlab.com/tkchia · https://codeberg.org/tkchia · 😴 "MOV AX,0D500H+CMOS_REG_D+NMI"

Complete thread:

• open in text mode (O_TEXT) - kerravon, 24.02.2025, 04:19 (Developers)
  • open in text mode (O_TEXT) - kerravon, 24.02.2025, 04:24
    • open in text mode (O_TEXT) - tkchia, 26.02.2025, 16:30
      • open in text mode (O_TEXT) - Rugxulo, 27.02.2025, 00:29
      • open in text mode (O_TEXT) - kerravon, 02.03.2025, 01:30
        • open in text mode (O_TEXT) - kerravon, 02.03.2025, 01:33
        • open in text mode (O_TEXT) - tkchia, 03.03.2025, 15:09
      • open in text mode (O_TEXT) - kerravon, 02.03.2025, 01:35