DOS ain't dead - not setting carry

not setting carry (Developers)

posted by kerravon , Ligao, Free World North, 17.10.2025, 19:05

> >
> > I think that's covered by this:
> >
> > Greater than 73H on MSDOS 7.0
> >
> > It's only 74H and above that I am expecting to have the "carry issue"
> > on that particular version of MSDOS.
>
> Indeed the maximum command is 73h, but the "high" functions aren't the only
> ones that use MS-DOS v1 style return. So it's a valid question to study
> what exactly it does for function 71h.

Thanks - I added that factoid to the comments in my code too.

And this is all in preparation for supporting PM16. In order for my startup code to detect the environment and adjust appropriately, I will need some extra DOS functions.

I made a change to my dos startup code today already in preparation for that. pdld was updated to provide some OMF16 support. I was able to produce a tiny memory model program, and .com file, with it. There's still some issues though. Also, he agreed to convert type 3 32-bit relocations into type 9, so that I could get an executable and be in a position to post-process it later. So even large memory model now links.

Post reply

Complete thread:

not setting carry - kerravon, 16.10.2025, 10:29
- not setting carry - ecm, 16.10.2025, 16:17
  - not setting carry - bretjohn, 16.10.2025, 23:59
    - not setting carry - ecm, 17.10.2025, 09:30
  - not setting carry - kerravon, 17.10.2025, 07:58
    - not setting carry - ecm, 17.10.2025, 10:29
      - not setting carry - kerravon, 17.10.2025, 10:55
        not setting carry - ecm, 17.10.2025, 11:31
        not setting carry - kerravon, 17.10.2025, 16:51
        not setting carry - ecm, 17.10.2025, 18:43
        not setting carry - kerravon, 17.10.2025, 19:05