I think this is the same problem as the one I ran into when trying to render some pretty large pic's. MS can't handle more then 2 gigs of ram/application.....in reality somewhere between 1,5 to 1,7 GB. I have 2Gig ram on both my machines and I hit the roof at about 1,5-1,7 >Gig ...then Sw tells me it doesn't obtain enough memory....and I almost taired my hair off before I understood what was happening.... many thanks to Edward T Eaton who helped me off......but that's the limit I believe
Jerry Steiger skrev i diskussionsgruppsmeddelandet:brt8dj$77jub$ snipped-for-privacy@ID-200869.news.uni-berlin.de...
> I recently spoke to Greg Jankowski from SW and he stated installing a > second
> > hard drive dedicated to virtual memory was one of the greatest payoffs for
> > performance per cost that most users overlook.
> This makes absolutely no sense to me. If you are hitting swap space at all,
> no matter how fast your disk is, you are going to be slowing down a lot.
> Buying more RAM is the answer, not a small, fast hard disk.
> Having said that, I still run into problems even though I have 1.5GB of RAM.
> Sometimes (say when trying to do a STEP translation of a relatively large
> assembly), SW will tell me it can't get any memory, even though I am at less
> than 1.5GB and have an additional 1.5GB of swap space available. >
> Jerry Steiger
> Tripod Data Systems