Too much virtual memory?

[Dean]

I am having problems viewing content on a cd with
extended features such as videos,pictures etc.that was
created with Macromedia's Director program.This appears
to be a known issue as I have investigated Google and
found several posts with the same issue. Macromedia posts
a work around that requires lowering the maximum amount
of virtual memory to less than 200 MB's. Currently I have
1 gig. of ram and I let Windows manage the virtual memory
which gives me I believe 1536 MB's.The problem according
to Macromedia is cd's created with older versions of
Director don't recognize this large amount and return a
negative value there-by not allowing the application to
play. When I try to play the cd an information box pop's
up saying that "This application requires at least 3 MB's
of free virtual memory to run".
The problem is these cd's used to run problem free until
I did an in place repair to reload the operating system.
Everything else works fine and I have re-downloaded all
up dates to all programs including XP.I am technically
right back where I started except for this one issue.
I have tried SFC /SCANNOW with no results. This is
driving me nuts trying to figure out why they worked
before but wont work now. I have checked various virtual
memory info sites including Jim Elshemans but can't find
the right answer. If I try the work around that
Macromedia suggests,(lowering the max amount of virtual
memory to less than 200 MB's),an info box pop's up saying
that with that low of an amount, Windows wont be able to
record pertinent data in the event of a crash.
Has anyone else experienced this and/or is there a
better solution to this than the one Macromedia suggests?
Thanks for all responses and suggestions.

 

[Alex Nichol]

I am having problems viewing content on a cd with
extended features such as videos,pictures etc.that was
created with Macromedia's Director program.This appears
to be a known issue as I have investigated Google and
found several posts with the same issue. Macromedia posts
a work around that requires lowering the maximum amount
of virtual memory to less than 200 MB's. Currently I have
1 gig. of ram and I let Windows manage the virtual memory
which gives me I believe 1536 MB's.

No program should be asking you to *reduce* the amount of virtual
memory. That being said, on a 1GB machine the page file is probably
doing nothing, and I would set the initial size down to 100 MB. But I
would leave the maximum quite high - say 800 MB, because this allows the
potential space to be assigned to memory space that has been assigned
to programs but never taken up. Otherwise these addresses have to be
assigned to actual RAM, and lock it out , maybe to the tune of hundreds
of MB

Read more at www.aumha.org/win5/a/xpvm.htm

 

[Dean]

Thanks for the info. Ron. I'll give it a try. I'm still
puzzled though, as to why they worked before and now they
don't. I'm sure this is probably one of those strange
anomolies that you can spend many hours/days pondering
and never come up with a sollution.
Thanks again Ron.