I'm quite sure that's a issue with 10.3.9 (Java surely) and 4.10pro.

I have 4.10pro runningon my daughter's G3 running 10.3.8 without any problem

Other things that can be done:

(1) repair permissions
(must be admin)
Launch Applications/Utilities/DiskUtility
On the left pane, select the drive
On the right, select the First Aid (or SOS) tab
Then click on repair permissions and let run; don not worry about messages like " new permissions...."
Quit DiskUtility
Shutdown and reboot

(2) manually run maintenance scripts through Macjanitor
http://personalpages.tds.net/~brian_...acjanitor.html
and use it to run the maintenance scripts
The maintenance scripts are Unix scripts which are automatically ran on your
Mac between 02Am and 04 am..if your Mac is on at this moment.
I can advice you to run, through Macjanitor, the daily script each day, the week script each week, ..and so on

(3) and last but not least the Unix repair function: fsck
To run fsck, you first need to start up your Mac in single-user mode. Here's how:
1. Restart your Mac.
2. Immediately press and hold the Command and "S" keys.
You'll see a bunch of text begin scrolling on your screen. In a few more seconds, you'll see the Unix command line prompt (#).
You're now in single-user mode.

Now that you're at the # prompt, here's how to run fsck:
1. Type: "fsck -y" (that's fsck-space-minus-y).
If the 1st pass says that nothing has to be repaired, try "fsck -fy"
Option "-y" forces a "yes" response to every question of the system, which is very important because answering "no" to a fsck question will stop the process !
Option "-f" forces fsck to chack a system that this command seems to have find "clean"
2. Press Return.
The fsck utility will blast some text onto your screen. If there's damage to your disk, you'll see a message that says:

***** FILE SYSTEM WAS MODIFIED *****

If you see this message--and this is extremely important-- repeat running fsck. It is normal to have to run fsck more than once -- the first run's repairs often uncover additional problems..

When fsck finally reports that no problems were found, and the # prompt reappears:
3. Type: "reboot" to restart,
or type "exit" to start up without rebooting.
4. Press Return.

Your Mac should proceed to start up normally to the login window or the Finder.

Phil