Windows NT Resource Limit?

I have an app running on a 400 Mhz, 256M hp machine which starts up many smaller apps.  The smaller apps however top out at 44.  I cannot open any other apps until I close one of the smaller apps.  Is this a resource limit in NT as I thought this only applied to 95? Is there some registry setting to expand this limit?
richpAsked:
Who is Participating?
 
nilosCommented:
Heve you tried this?

PSS ID Number: Q125752
-------------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Win32 Application Programming Interface (API) included with:

    - Microsoft Windows NT version 3.5
-------------------------------------------------------------------------

SUMMARY
=======

Sometimes, it may be necessary to increase the amount of memory that
Windows NT will make available for the system and desktop heaps. This can
be accomplished by editing an entry in the registration database. System
heap items are things like desktops and one-time-allocated items like
system metrics. The items that come out of the desktop heap are items such
as windows, menus, hook structures, queues, and some thread information.

MORE INFORMATION
================

The entry to be edited is under:

HKEY_LOCAL_MACHINE\
   System\
   CurrentControlSet\
   Control\
   Session Manager\
   SubSystems\
   Windows

Under this entry, you will find a string similar to the following (the
slash (/) is a line continuation charater):

%SystemRoot%\system32\csrss.exe /
   ObjectDirectory=\Windows /
   SharedSection=1024,512 /
   Windows=On /
   SubSystemType=Windows /
   ServerDll=basesrv,1 /
   ServerDll=winsrv:GdiServerDllInitialization,4 /
   ServerDll=winsrv:UserServerDllInitialization,3 /
   ServerDll=winsrv:ConServerDllInitialization,2 /
   ProfileControl=Off /
   MaxRequestThreads=16

By changing the SharedSection values, you can affect the heap sizes. The
first number (1024 as shown above) is the maximum size of the system wide
heap in kilobytes. The second number (512 as shown above) is the maximum
size of the per desktop heap in kilobytes. A desktop value of 512K can
support approximately 2,500 windows.

The memory you allocate needs to be backed up by paging space. It should
not have much effect on performance if you create the same number of items
with different heap sizes. The main effect is overhead in heap management
and initialization.

Additional reference words: 3.50
KBCategory: kbui
KBSubcategory: UsrWndw

0
 
paynCommented:
There is no set resource limit. However, a number of other things can limit you--file handles, memory (although 256MB should allow more than 44 apps--but try increasing your virtual memory to see if it has help), temp space on the hard drive, etc.

What exactly happens when you launch the 45th app? Do you get an error message? Nothing at all?

0
 
richpAuthor Commented:
Virtual memory is 250MB.  The 45th app's InitInstance fails when trying to create the main view.  This has to be a resource limit because when I pull up Task Manager I see only the Applications and Processes tab but not the Performance tab (I assume it didn't have the resources to create that tab).  Shutting down one of the apps then gives me all the tabs on the Task manager.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.