Discussion:
MSDOS 1.0
(too old to reply)
muta...@gmail.com
2021-04-04 15:10:38 UTC
Permalink
I would like to know if the MSDOS executables I
produce are capable of running on MSDOS 1.0
or whether I used some functions it doesn't
support.

I don't care if MSDOS 1.0 doesn't support
subdirectories etc. So long as my executable
doesn't rely on that, and just calls open(), I
should be fine.

I'm using these functions:

public ___open
public ___creat
public ___read
public ___write
public ___seek
public ___close
public ___remove
public ___rename
public ___allocmem
public ___freemem
public ___setj
public ___longj
public ___exec
public ___datetime

I have seen a lot of applications cite MSDOS 2.0
as the minimum they support, and at the moment
I don't actually know what my minimum is.

Also, if my minimum happens to be 2.0 also, is
there anything I can do for my executables to
support both 2.0 and 1.0?

Thanks. Paul.
Alexei A. Frounze
2021-04-04 17:02:44 UTC
Permalink
Post by ***@gmail.com
I would like to know if the MSDOS executables I
produce are capable of running on MSDOS 1.0
or whether I used some functions it doesn't
support.
I don't care if MSDOS 1.0 doesn't support
subdirectories etc. So long as my executable
doesn't rely on that, and just calls open(), I
should be fine.
Well, your beloved file-handle-based functions (open, read, write,
close, seek) first appeared in 2.0. Put 1.0 back to the grave.
Post by ***@gmail.com
public ___open
public ___creat
public ___read
public ___write
public ___seek
public ___close
public ___remove
public ___rename
public ___allocmem
public ___freemem
public ___setj
public ___longj
public ___exec
public ___datetime
I have seen a lot of applications cite MSDOS 2.0
as the minimum they support, and at the moment
I don't actually know what my minimum is.
2.0 it is. Only date/time functions can be used from 1.0.
You can't even exit your program with function 4C in 1.0.
Post by ***@gmail.com
Also, if my minimum happens to be 2.0 also, is
there anything I can do for my executables to
support both 2.0 and 1.0?
Write your own DOS 1.0-2.0 compatibility layer.
But seriously, just don't.

Alex
JJ
2021-04-04 18:59:03 UTC
Permalink
Post by Alexei A. Frounze
Post by ***@gmail.com
I would like to know if the MSDOS executables I
produce are capable of running on MSDOS 1.0
or whether I used some functions it doesn't
support.
I don't care if MSDOS 1.0 doesn't support
subdirectories etc. So long as my executable
doesn't rely on that, and just calls open(), I
should be fine.
Well, your beloved file-handle-based functions (open, read, write,
close, seek) first appeared in 2.0. Put 1.0 back to the grave.
Post by ***@gmail.com
public ___open
public ___creat
public ___read
public ___write
public ___seek
public ___close
public ___remove
public ___rename
public ___allocmem
public ___freemem
public ___setj
public ___longj
public ___exec
public ___datetime
I have seen a lot of applications cite MSDOS 2.0
as the minimum they support, and at the moment
I don't actually know what my minimum is.
2.0 it is. Only date/time functions can be used from 1.0.
You can't even exit your program with function 4C in 1.0.
Post by ***@gmail.com
Also, if my minimum happens to be 2.0 also, is
there anything I can do for my executables to
support both 2.0 and 1.0?
Write your own DOS 1.0-2.0 compatibility layer.
But seriously, just don't.
Alex
You forgot that DOS v3+ are based on v2 and v1. You can't throw away the
specification for the DOS services.
Alexei A. Frounze
2021-04-04 20:19:52 UTC
Permalink
Post by JJ
You forgot that DOS v3+ are based on v2 and v1. You can't throw away the
specification for the DOS services.
I'm not following. What are you trying to convey?
Alex
muta...@gmail.com
2021-04-04 21:02:27 UTC
Permalink
Post by Alexei A. Frounze
Well, your beloved file-handle-based functions (open, read, write,
close, seek) first appeared in 2.0. Put 1.0 back to the grave.
Ok, thanks.

I'm guessing that MSDOS 1.0 provided CP/M and
that's about it?

BFN. Paul.
muta...@gmail.com
2021-04-05 00:15:38 UTC
Permalink
Post by ***@gmail.com
I'm guessing that MSDOS 1.0 provided CP/M and
that's about it?
I probably just need an 8086 CP/M target for PDPCLIB.
To mimic those tiny memory model assembler programs
that were auto-converted from the 8080.

And then target the 8080 CP/M with more-or-less the same
code base.

BFN. Paul.

Loading...