Possible increase the memory allocation to solve the "insufficient virtual memory" problem?

[Jason]

When submit to run a case using FDS5 under PC win-xp system, I got the
following error.
My PC has a physical memory of 3.25GB, Intel(R) Xeon(R) CPU 5160 @
3.00GHz.


forrtl: severe (41): insufficient virtual memory
Image PC Routine Line Source
fds5.exe 00679F9A Unknown Unknown Unknown
fds5.exe 00677855 Unknown Unknown Unknown
fds5.exe 0062560A Unknown Unknown Unknown
fds5.exe 005FE11B Unknown Unknown Unknown
fds5.exe 005EF2C9 Unknown Unknown Unknown
fds5.exe 005E9ED1 Unknown Unknown Unknown
fds5.exe 0067DFE9 Unknown Unknown Unknown
fds5.exe 006698B5 Unknown Unknown Unknown
kernel32.dll 7C816FD7 Unknown Unknown Unknown


However, If I use less obstruction creation/removal, it works, But I
really need all of them. Can I increase the memory allocation like did
with FDS4?

Running Big FDS4 Jobs Under Windows, the editbin Utility
When compiling FDS4 under Windows, a maximum stack size must be
declared. The stack is a region of memory used to store variables
local to an FDS subroutine. Unfortunately under Windows you are forced
to decide when building a program how much memory to set aside for the
stack. By default, FDS is built with a 50 MB stack size, plenty of
space for most jobs. Larger jobs, however, may need more stack space.
Fortunately, you can increase the stack size used by FDS without
having to recompile it. From the command prompt change to the
directory containing the FDS executable (usually c:\nist\fds ) and run
the following command:

editbin /stack:100000000 fds4.exe


Here we are using 100000000 bytes (100 MB) just as an example. You
might have to experiment with the number to get what you need.
Remember that we compiled with 50 MB.

Editbin is distributed with the FDS4/Smokeview installation files.

Part of my input file is a following:

!----------OBSTRUCTIONS of Trains----------

&OBST XB= 178.5,303.5, 14.5, 17.3,0,3.85, SURF_ID='WALL', COLOR='STEEL
BLUE', SAWTOOTH=.FALSE., DEVC_ID='timer 01'/TrainA
&OBST XB= 162.5,287.5, 14.5, 17.3,0,3.85, SURF_ID='WALL', COLOR='STEEL
BLUE', SAWTOOTH=.FALSE., DEVC_ID='timer 02'/TrainA-16m
&OBST XB= 162.5,287.5, 14.5, 17.3,0,3.85, SURF_ID='WALL', COLOR='STEEL
BLUE', SAWTOOTH=.FALSE., DEVC_ID='timer 03'/TrainA-16m
&OBST XB= 116.5,241.5, 14.5, 17.3,0,3.85, SURF_ID='WALL', COLOR='STEEL
BLUE', SAWTOOTH=.FALSE., DEVC_ID='timer 04'/TrainA-62m
&OBST XB= 116.5,241.5, 14.5, 17.3,0,3.85, SURF_ID='WALL', COLOR='STEEL
BLUE', SAWTOOTH=.FALSE., DEVC_ID='timer 05'/TrainA-62m
&OBST XB= 49.5,174.5, 14.5, 17.3,0,3.85, SURF_ID='WALL', COLOR='STEEL
BLUE', SAWTOOTH=.FALSE., DEVC_ID='timer 06'/TrainA-129m
&OBST XB= 49.5,174.5, 14.5, 17.3,0,3.85, SURF_ID='WALL', COLOR='STEEL
BLUE', SAWTOOTH=.FALSE., DEVC_ID='timer 07'/TrainA-129m

&DEVC ID='timer 01',XYZ=0.2,0.1,0.1, SETPOINT=125.0, QUANTITY='TIME',
INITIAL_STATE= .TRUE./ 0m
&DEVC ID='timer 02',XYZ=0.2,0.1,0.1, SETPOINT=125.0, QUANTITY='TIME',
INITIAL_STATE=.FALSE./-16m
&DEVC ID='timer 03',XYZ=0.2,0.1,0.1, SETPOINT=130.0, QUANTITY='TIME',
INITIAL_STATE= .TRUE./-16m
&DEVC ID='timer 04',XYZ=0.2,0.1,0.1, SETPOINT=130.0, QUANTITY='TIME',
INITIAL_STATE=.FALSE./-62m
&DEVC ID='timer 05',XYZ=0.2,0.1,0.1, SETPOINT=135.0, QUANTITY='TIME',
INITIAL_STATE= .TRUE./-62m
&DEVC ID='timer 06',XYZ=0.2,0.1,0.1, SETPOINT=135.0, QUANTITY='TIME',
INITIAL_STATE=.FALSE./-129m
&DEVC ID='timer 07',XYZ=0.2,0.1,0.1, SETPOINT=140.0, QUANTITY='TIME',
INITIAL_STATE= .TRUE./-129m

----------------------------------

[dr_jfloyd]

Stack space is not the same as memory. Stack is a subset of memory.
The error message you are getting suggests that you do not have enough
RAM. You can still use editbin and try to see if stack helps, but I
think it may be RAM. Editbin is in the utilities folder off the FDS
directory (default is C:\Program Files\NIST\FDS\Utilities).

Before running FDS open the task manager (CTRL-ALT-DEL) and look at
how much memory you have available to run FDS (Performance tab the
down at the bottom under physical memory). Now click the Process tab
and then click on the memory usage column to sort by memory usage.
Start your FDS calc and monitor its usage. If its usage gets close to
the available memory before it dies, then you lack enough RAM.