One more thing. Load the standalone of VI and as many samples as you can. Maybe this will help to remove Forte being the problem from the equation.

DG

OK, here is where to check:

Start
Run...
regedit
HKEY_LOCAL_MACHINE
SYSTEM
CurrentControlSet
Control
Session Manager
Memory Management

Now, double click on each of the next 4 D-words in turn. They should all be set to 0 for you to be running the XP default.

NonPagedPoolQuota
NonPagedPoolSize
PagedPoolQuota
PagedPoolSize

Report back as to your findings.

DG

Thanks for this.

Checked the registry settings - all four were zero.

Will load up the standalone VI as suggested and let you know what happens.

OK, I just checked using Chainer (which is not LAA) on my 4Gb machine. I loaded 20 instances and eventually Chainer crapped out at around 1.75GB. Maybe the Forte demo is not LAA. I have been told that the proper version is, so I don't understand why there would be a difference like this in the demo.

DG

I'm now using the full Forte version, not the demo. The demo is incredibly annoying because it times out after a certain amount of time, making it virtually impossible to load up all the patches and get everything the way I wanted it for a proper test. Grr. So I decided to risk it and buy the full version.

Your hunch in your last post was correct. I loaded up a similar set of matrices in the standalone, and it froze on me.

I've just loaded them all again, and checked the memory values in the Perform tab after loading each matrix. I got as far as

21760 samples
1360 Mb used
1925 Mb free

...sorry, tail end of my last post got truncated...

...which was further than I had got before, so I thought I'd check out saving/loading the setup. Saved OK, but when I came to reload, the machine rebooted without warning part way through.

Just to rule out a memory glitch I am currently running a memory check utility on the box!

Mike

OK, this is sounding more normal now. I would imagine that you don't have the /3Gig switch installed. Next thing to check (using Task Manager):

Load 1.2GB in Forte (so that you don't hit the end stop), then open a standalone instance of VI and load around the same amount. If you can do it, then it is likely to be a /3Gig switch problem. If not, then you need help from someone else, I'm afraid.

DG

I do have the /3GB switch set in boot.ini.

OK, I got 1.2Gb into Forte, and then tried to load a similar amount into the standalone VI. Once I got to around 811M (as reported by Task Mgr) VI froze.

Any ideas what this means? - you're a step or two beyond me here!

OK, FWIW the outcome of this was...

I ran some memory tests but nothing much came up, and VI kept crashing no matter what I did.

So I gave up on that machine, and took out my extra 2Gb of memory and installed it in my other Giga machine. Removed the GS3 memory tweak, added the /3GB switch, loaded VI and Forte.

And it works like a dream.

21 instances of VI, with 1527 samples loaded - and still over 1Gb of free memory. Clearly on this box CPU will top out before memory does.

As to why it didn't work on the other machine, I have no idea. I'm just grateful that I happened to have another reasonably beefy box standing by as a spare.

Mike

Glad you got it sorted. I really don't know what could be the problem on the other machine. Hopefully someone else will chime in before you get as far as an OS re-install.

DG

I think I'm going to stick to GS3 on the other machine - which worked fine - or maybe if I'm feeling brave, I might try GVI...!

Thanks for all your help.