If you open the task manger in Windows 2000 and select the processes tab the javaw.exe process shows the memory being used by further. Here it is 32,788 k at present with a single outbound active. I _think_ that the 9x/Me releases have something similar but honestly can't remember. Gave my 98 and NT 4 CD's away when I got 2K and haven't regretted it in the least. MS was targeting different user bases with 2000 and though it works great for a home system it isn't quite the multimedia/gamer system that the 9x/Me systems are (damn close though). Then again the 9x/Me platforms aren't as stable or efficient with memory as the NT based platforms so it's still a trade off whatever you choose.
For the Windows users having problems you may want to look at your Java
Virtual Machine (javaw.exe and whatever additional files are part of the
java run time environment). I have Borland's JBuilder, CBuilder, and Delphi
as well as MS Visual C++ and Basic installed for development tools as well
as version 6 of MSIE so somewhere in all of that I may have some files, file
classes, and file associations that are helping to stabilize Java operations
on my system. I really couldn't say as I'm not a big fan of interpreted
languages so Furthur is the first real Java app I've worked with here. I'm
sure there are still issues the development team needs to address but some
of what comes up sounds more system specific and having dealt with lousy
Java integration in Windows before when playing with JBuilder on Windows 95
the run time system is where I would start. The only difference in the
files used by further from operating system to operating system will be in
that particular computer's Java run time system (the Java Virtual Machine).
For the record I am not one Furthur's developers. I'm not familiar enough
with Java code to write it efficiently, but debugging software and
stabilizing new code from the user/tester side is pretty much the same
regardless of what language is being used so I'll do what I can to try and
assist anyone.
Hope some of that helps.
Later,
Rob
<<attachment: winmail.dat>>
