CompuServe Messages

Perhaps I don't understand how PharLap works. I assumed that it replaced malloc/free with its own heap management. But you're saying that an IPAS links in the standard Metaware malloc/free, which trickle down to the regular DOS memory allocation calls, which get intercepted by PharLap, which is also managing all of protected mode memory, so the app doesn't know the difference, as long as it is good 32-bit code. Did I get that right? Except does DOS reall have 32-bit-friendly memory allocation calls? (Or 48 bit, etc.) So DMPI fits in here somewhere, too, for the big memory handling. PharLap is bound into 3DS.EXE, and since IPASes run only when 3DS.EXE has already run, it all works. I think my misunderstanding was that PharLap replacement functions were getting linked into replace some low-level OS calls…