Mail Archives: djgpp/2000/10/26/19:30:27
> When playing with CWSPARAM to find optimal settings for my application,
> I often experienced, that (unnoticed) the application loaded an other CWSDPMI
> from the path (or from it's stub info, or an other DPMI server was already
> loaded) than that one I just had modified.
Those are good suggestions for future enhancements. In particular, if there
is one in the current directory and one on your path you should be aware of it.
> Also I always had my difficulies with pages and paragraphs sizes to remember :-)
I got rid of pages with r5 - only paragraphs were left. If I had thought
about it, I would have make Kb the natural measure for the DOS memory. I doubt
anyone is trying to configure to the nearest 16 bytes anyway.
> If you all like it, we could ask Mr. Charles Sandman to take my modifications
> over to his r5 distribution. Thanks for comments or even more "enhancements".
I would consider new changes for r6, but I have no plans to change the r5
distribution since it's been through a beta period and final release.
> BTW please don't take this as a critisism of Charles' great work.
I don't ... many of the features were suggested by users. Some of the
memory diagnosis features you mention are actually in a image I use for
debugging:
ftp://clio.rice.edu/djgpp/meminfo.exe
Which tells me how much DOS memory, raw memory, XMS memory or VCPI memory is
available, the CPU mode, hardware type, and if DPMI is present. This
image causes some Windows versions to want to force it into a raw DOS
mode, so I wouldn't want to put it inside cwsparam, however.
- Raw text -