Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revisionLast revisionBoth sides next revision | ||
blog:pc98_devtools [2020/08/14 16:54] – [The Real Problem Is...] john | blog:pc98_devtools [2020/08/22 10:27] – [Troubleshooting on Real Hardware] john | ||
---|---|---|---|
Line 29: | Line 29: | ||
* https:// | * https:// | ||
* https:// | * https:// | ||
+ | * http:// | ||
+ | * https:// | ||
==== Graphics Hardware Differences ==== | ==== Graphics Hardware Differences ==== | ||
Line 522: | Line 524: | ||
===== Troubleshooting on Real Hardware ====== | ===== Troubleshooting on Real Hardware ====== | ||
- | First of all, **DPMI32.exe** (from the PC-98 DOS 5.00 disks) and **go32-v2.exe** (which we built from the patched sources, above) work on real PC-9821 hardware, just as they do within the NekoProject II Kai emulator, as long as you have a VCPI service running (either EMM386, VEMM486 or similar), the result is the same. | + | First of all, <del>**DPMI32.exe** (from the PC-98 DOS 5.00 disks)</ |
So boot with typical memory managers in place: | So boot with typical memory managers in place: | ||
Line 568: | Line 570: | ||
==== The Real Problem Is... ==== | ==== The Real Problem Is... ==== | ||
- | So, I figured out that there' | + | So, I figured out that there' |
{{: | {{: | ||
+ | |||
+ | The upside is that nothing else needs changing, just the single **make.exe** binary. | ||
+ | |||
+ | Here's an updated version of the GCC + DJGPP development environment, | ||
+ | |||
+ | * {{ : | ||
+ | |||
+ | Note that this version also includes renamed libreadline.a (libread.a), | ||
+ | |||
+ | ===== Next Steps ===== | ||
+ | |||
+ | Go forth, create code for another obsolete computer platform, and be merry! | ||
+ | |||
+ | Or, alternatively, |