tuning heap space in Windows 2000 server

I am moving a database from SCO to Windows. For some reason this
database accesses an independent connection to cmd.exe for each
individual workstation, terminal, or user that connects to it. For
example, I (at my workstation) open the app (programmed in JAVA) which
accesses my database (CQCS or Cyberscience) and a cmd.exe process is
opened on the server. This happens for every instance the app is
opened. I do not know why it is programmed this way or the logic
behind it, but it is what it is.

The problem this causes me is that my noninteractive desktop heap
maxes out at 28 connections, and I have 80 users. Here is a microsoft
doc that explains the scenario:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;184802

Under the registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session
Manager\SubSystems\Windows

I have tuned down my noninteractive heap setting from the default of
512 to 128. This allows me 120 connections for now, but I haven't
tested the server under a full load yet to verify that those settings
will hold up. Also, I may be adding more clients soon and need more
growth room. My software vendor has promises of a fix, but I'm not
holding my breath. The microsoft doc refers to a 48-mb buffer that
all heap needs to fit under. What I am wondering is if there is any
way to increase that buffer size beyond 48mb. Or, if anybody has any
other solutions, I am all ears at this point.

Thanks,
Heath