open in text mode (O_TEXT) (Developers)
Thanks for your thoughts.
What I can do is create additional Pos* calls, so
that instead of fopen() calling PosOpenFile() which
gets translated into the MSDOS interrupt, I can
instead get fopen() to call PosFopen() which has
identical parameters. And then gets translated into
an MSDOS extension (the same way that MSDOS 7 is an
extension of MSDOS 2).
Given that Microsoft is no longer extending MSDOS,
it's free for anyone (ie bttr or whoever) to extend
MSDOS.
But the definition of "MSDOS" gets hazier and hazier
in that process.
BFN. Paul.
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
- open in text mode (O_TEXT) - tkchia, 26.02.2025, 16:30
- open in text mode (O_TEXT) - kerravon, 24.02.2025, 04:24