|
|
|
|
|
by kerravon86
1175 days ago
|
|
Source or binary? In both cases - it depends. PDOS/86 will certainly run some binaries. But if you say "what about xyz" the answer is likely "probably not". I don't have a lot of interest in 16-bit, so it's there for demonstration purposes mainly. My interest is 32-bit. The biggest genuine task I do is getting GCC to compile itself with full optimization, which requires something like 23 MB of memory on the mainframe and something like 37 MB on a PC. Far far below the 4 GiB barrier (or even 2 GiB barrier), but above even 16 MiB, nevermind 640k. If it is source code you have, then it will require recompilation at a minimum. I made use of that fact to provide a C-defined API to wrap the INT calls, so at least nominally you need to use those C functions. But you may be able to get away with an existing int86x call (or even assembler instruction), as the interrupts do exist (ie even in 32-bit). If your MSDOS program is C90-compliant then that should work unchanged - but that is the case for any environment, not just MSDOS or PDOS/386. |
|