🚀 go-pugleaf

I am developing on NT4.0 system with 96M RAM and 200MHZ Pentium CPU.
The JBuilder I use is JB2.0 Pro. During the course of my development, I
often found
that JB takes a lot of more memory than I expected. Here is an example:

Today I was trying some java bean examples. I created a JApplet and put
some of the demo beans from Sun's BDK. The beans I used were "molecule",
"button" and some beans I created based on the bean tutorial: "WaterSource",
"Pipe", "Valve". Then I created another bean which uses a JScrollPane and a
JTree inside it. When I tried to add the last bean to my applet design panel
and trying
to run it, the computer went into a long time of memory swapping. I checked
the
Task Manager and it reads:
                      Mem Usage     Page Faults      VM Size      Threads
    jbuilder      70300K              411566           140432K       243

I don't know what is going on here. How can a program takes 140MB memory?
How can you do serious developping if the
tool uses this much memory. I have to restart JB each time I wanted to test
my
application to free up the memory JB uses. Is this typical? I don't think I
am doing
anything fancy here.  This is just one of the typical situations during my
everyday
developing. How much memory is considered enough for JB? The manual states
that 48MB is recommended but I have 96MB. Or is it because of NT?

Also, when I uses the Deployment wizard to package the java bean I just
built,
the wizard automatically includes all JFC class files. As a result, I had to
manually build the bean using a makefile to include only the bean java file
I wanted.
 Is there any way to make the wizard not to include JFC class files?

Mark X. Yang