J
Jonathan Kirwan
It depends exactly what finite resources the 'Dozy operating system is
running out of. My copy of Win98SE has no trouble at all managing 192MB
of ram and would probably go slightly faster with 256MB if I could be
bothered.
It's running out of those I posted about:
16-bit User heap 64K
32-bit User window heap 2M
32-bit User menu heap 2M
16-bit GDI heap 64K
32-bit GDI heap 2M
How these are specifically accounted for by the summarized display of the
program called RSRCMTR.EXE, I can't exactly say. But it is typically controls
added to sheets that cause such memory leaks (when they aren't properly returned
to the system, as the visual page changes and is updated.)
In any case, these limitations have nothing whatever to do (generally) with
management or mismanagement of the totality of memory, such as the 192M or 256M,
etc. That memory isn't about the above memory limitations. Those regions I
listed above have their own special limitations that are unrelated to the
overall RAM available in the system.
The typical sorts of things that Windows trashes resources for are
multiple (redundant) loading of fonts when drawing graphs. You can force
an error reported as "not enough memory" in Excel for example by drawing
around 50 charts in one spreadsheet (no matter how much ram is free).
Interesting. I haven't tried that, of course.
In the case of Mathcad, I've tried to keep to VERY SIMPLE processes of
documenting my thought processes for applications I write, without getting fancy
about using features. Font types for text I type are limited to one, with
perhaps some italics. Mathematics is as Mathcad uses, so whatever that means.
Other than that, basic stuff.
Doesn't matter. Unusable because I can just simply watch that resource meter
memory bar drop and drop and drop. And when I close the program entirely,
saving my work, very little comes back in reply. When I restart, I restart from
a much lower starting position and I have far less time left "on the clock," so
to speak. So I have to reboot.
Doing that every hour or half-hour or hour-and-a-half just isn't my idea of a
workable program. And, sadly, I'd applied this program and patches onto four
machines, all with varying versions of Win98 on them with varying drivers. But
after long talks with Mathcad folks about these problems, I finally broke down
and reformatted a disk and completely rebuilt Win98 as a clean system, applied
Microsoft's "critical updates" onto the system, did nothing else, and then ran
Mathcad. Same results.
The several copies of Mathcad I have now sit on a shelf.
I suspect the problem here is similar. It is a bit careless to ship
software with gratuitous and large memory leaks. A better choice of OS
may help.
As I also said earlier, my work habits preclude that. I didn't get into
details, but the issue is that I have several machines -- one at my electronics
workbench that includes several ISA slots in it for old hardware cards I need to
support, one in my library area, and a laptop. I keep all my projects on
separate disks -- they are cheap to buy and I use removable drive enclosures for
the drives so that I can just slap them in. So, if I work on a product under
Linux for project A today and work on a product under Win98 for project B
tomorrow, I simply grab the project A disk and boot today and grab the project B
disk tomorrow and reboot on it.
This allows me to work on clean operating system environments for all projects,
without the required installations of software for one project causing me
problems for a different and unrelated project, allows me to operate under any
number of operating systems, etc. But the upshot of all this is that I place
copies of Win98 on many different mountable disks. Microsoft doesn't support
this mode of operation with XP, for example. I'd be calling and begging from
them every time I needed to configure a new project using their OS.
So Win98 it is.
There are registry tweaks to fix some of these flaws....
Well, Mathcad support had me doing some of those. No help there.
Anyone with the tools to say if v12 has serious memory leaks or not?
And specifically under Win98 or Win98SE???
Much obliged if anyone can say!
Jon