8086 rules (Miscellaneous)
> > This was not without its limitations. If an application utilized or
> relied
> > on any of the techniques below, it would not run:
> >
> > ...
> > Use of BIOS functions, due to the BIOS interrupts being reserved by
> > Intel[31]
>
> I would classify "Would not run" as a vast overstatement. Specifically
> regarding the BIOS functions, that is not actually a DOS problem -- it is a
> BIOS problem. And even then, the only BIOS interrupt problem I've come
> across that has any practical effect is INT 05, which used by both the BIOS
> PrintScreen function and by the CPU BOUND instruction (which didn't even
> exist until the 80286).
You can do BIOS calls from PM16?
ie read a disk?
edit: and into memory above 1 MiB?
Complete thread:
- 8086 rules - kerravon, 21.02.2024, 07:24 (Miscellaneous)
- 8086 rules - Japheth, 21.02.2024, 09:03
- 8086 rules - Rugxulo, 21.02.2024, 10:38
- 8086 rules - kerravon, 21.02.2024, 11:02
- 8086 rules - Ringding, 21.02.2024, 11:56
- 8086 rules - kerravon, 21.02.2024, 12:06
- 8086 rules - Japheth, 21.02.2024, 15:16
- 8086 rules - Ringding, 21.02.2024, 15:24
- 8086 rules - Ringding, 21.02.2024, 11:56
- 8086 rules - mceric, 21.02.2024, 11:07
- 8086 rules - kerravon, 21.02.2024, 12:02
- 8086 rules - kerravon, 21.02.2024, 13:36
- 8086 rules - CS writing, lDebugX - ecm, 21.02.2024, 14:57
- 8086 rules - bretjohn, 21.02.2024, 17:40
- 8086 rules - kerravon, 21.02.2024, 23:35
- 8086 rules - Japheth, 21.02.2024, 09:03