4 ms·
> Super slow because for every frame every necessary image is read from the hard disk and for every calculation involving a lookup table the hard disk is also a
by MBCook 3y ago
> Super slow because for every frame every necessary image is read from the hard disk and for every calculation involving a lookup table the hard disk is also accessed
The 8086 was limited to 640k, a 286 could actually do 16MB with paging.
Is the problem simply the ram limit on the 8086? Is that why assets have to be reloaded off disk constantly?
Couldn’t a 286 with enough memory handle it (if you were emulating that processor)?
I’m curious what the issue is.
- Narishma 3y agoEven an 8088 could use more than 640kB through paging with EMS add-on cards. A 286 doesn't even require paging to use up to 16MB.
- basementcat 3y agoAdding EMS support is on the issue list. https://github.com/FrenkelS/Doom8088/issues/1 https://github.com/FrenkelS/Doom8088/issues/1
- whaleofatw2022 3y agoEMS only let's you have a 64kb frame, I don't think it matters if it's 286 or not.
- Narishma 3y agoA 286 doesn't need EMS though. You can use XMS or a 16-bit DOS extender and run in protected mode to access all memory.
- whaleofatw2022 3y agoYou mentioned EMS that's why I brought it up. On a 286 sure you can go to protected mode but AFAIK that tended to be more involved than most people would like. In the case of XMS, that could help but still requires moving data to/from EMB. Frankly EMS would be the best option to keep it workable on an 8088. At the very least the 64k frames could be used for some of the data that I'm guessing are streamed (belched?) from disk.
- mikeytown2 3y agoQEMM was created for the 286 (see QRAM) https://en.wikipedia.org/wiki/QEMM https://en.wikipedia.org/wiki/QEMM