I wouldn't have commented except you said that. First, you can turn it off any number of ways, like SET CAUSEWAY=NOVM, or reassemble without the option enabled, or there is programmatic support to do it. Second, CauseWay doesn't use the hard disk until you run out of physical memory, which means it's more powerful than those lame extenders which don't support virtual memory. Third, one of the primary enhancements of a 386+ chip over earlier chips is that it DOES support virtual memory -- I can't believe how many extender developers act proud about not supporting it. That's like bragging your dog can run faster if you cut off its tail for streamlining and weight-reduction. Those developers are lazy is what it is. That's right: lazy. Lazy, lazy, lazy. Even lazier than me; no mean feat.

Actually I'm not saying that Causeway is bad. The problem is that I write DOS applications that are time critical so I can not have virtual disk swapping. Since operational information is stored in memory until it is downloaded via network, the system often uses all remaining memory for this information. With causeway it ends up using the disk.

If it weren't for this I would definatly be using causeway, in fact I already use it during development. I simply do not deploy with it. Michael, you say that there is a programmatic way to disable this feature; can you tell me how. Ideally it would be disabled by default and enabled either programmatically or during complile/link time. But if I can disable it programmatically it's ok. I don't like to use the environment since users do tend to have access to this.



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to