Hi,

We have these class software called "LanguEdge" installed in our lab
computers, and lately they have been getting random error messages of
Authorware's Memory is Full. I have searched Adobe's knowledgebase and found an
article regarding how Authorware 6.5 and lower would give that error message if
the combined Virtual Memory and physical RAM would exceed 2.0GB. I suspect that
is why our lab software is crashing, but I have found no way to verify the
version of the Authorware that LanguEdge was made with. Is there a way to check
the version? Also, if anyone has a solution to the "Memory is Full" error, I
would really appreciate your help. I did a search on this forum but I could not
find any solutions yet, but perhaps I am not looking hard enough...

Thanks for the help.

"po684" <webforumsuser@macromedia.com> wrote in message
news:ga29d5$lg2$1@forums.macromedia.com...
> I have searched Adobe's knowledgebase and found an article regarding how
> Authorware 6.5 and lower would give that error message if the combined
> Virtual Memory and physical RAM would exceed 2.0GB. I suspect that is
> why our lab software is crashing,

As far as I'm aware that's only a problem in authoring mode, it shouldn't be
an issue with a completed (packaged) product.

Chris Forecast

"po684" <webforumsuser@macromedia.com> wrote in message
news:ga29d5$lg2$1@forums.macromedia.com...
> I have searched Adobe's knowledgebase and found an article regarding how
> Authorware 6.5 and lower would give that error message if the combined
> Virtual Memory and physical RAM would exceed 2.0GB. I suspect that is
> why our lab software is crashing,

As far as I'm aware that's only a problem in authoring mode, it shouldn't be
an issue with a completed (packaged) product.

Chris Forecast

The particular message that related to memory over 2.0 GB always happened
when you first started up Authorware itself, not a program written in
Authorware. The message incorrectly reported "Not enough memory". The
"Memory Full" message comes up for a number of different things that are not
actually memory full. Sometimes it's Authorware's best guess about what
might have happened when it tried to do something and couldn't.
Debugging a program with errors that are seeminly random is a process of
elimination. You have run it over and over to discover what steps are being
taken that cause the problem. In my experience an error that is truly random
is more often hardware related. You mentioned that this has started
happening only recently. Is there a change to the systems that has happened
recently?

Mike
====================
Mike Baker
Adobe Community Expert
mike-baker at cox dot net

Thanks for the replies, I guess I will have to look at this from another angle
then, if the memory error only exists in authoring mode. We have recently
replaced the lab server and upgraded it from Windows 2000 to Windows Server
2003, could the fault have lied with the server? The thing about the error
messages is, they do not always show up (the error comes up about 30-40% of
times), and they occur at different phases; sometimes it is when the program is
showing a picture icon, sometimes it is during a text input, and sometimes it's
when an audio clip is being loaded. I have been accessing the program in the
morning at the same time, so that is consistent there. I will start checking
the Windows 2003 server FAQs and see if I can find anything there. Thanks again
for the help.

Thanks for the replies, I guess I will have to look at this from another angle
then, if the memory error only exists in authoring mode. We have recently
replaced the lab server and upgraded it from Windows 2000 to Windows Server
2003, could the fault have lied with the server? The thing about the error
messages is, they do not always show up (the error comes up about 30-40% of
times), and they occur at different phases; sometimes it is when the program is
showing a picture icon, sometimes it is during a text input, and sometimes it's
when an audio clip is being loaded. I have been accessing the program in the
morning at the same time, so that is consistent there. I will start checking
the Windows 2003 server FAQs and see if I can find anything there. Thanks again
for the help.

"po684" <webforumsuser@macromedia.com> wrote in message
news:ga3j9v$6lq$1@forums.macromedia.com...
> Thanks for the replies, I guess I will have to look at this from another
> angle
> then, if the memory error only exists in authoring mode. We have recently
> replaced the lab server and upgraded it from Windows 2000 to Windows
> Server
> 2003, could the fault have lied with the server? The thing about the error
> messages is, they do not always show up (the error comes up about 30-40%
> of
> times), and they occur at different phases; sometimes it is when the
> program is
> showing a picture icon, sometimes it is during a text input, and sometimes
> it's
> when an audio clip is being loaded. I have been accessing the program in
> the
> morning at the same time, so that is consistent there. I will start
> checking
> the Windows 2003 server FAQs and see if I can find anything there. Thanks
> again
> for the help.

Is this program web enabled or packaged as an executable?

"po684" <webforumsuser@macromedia.com> wrote in message
news:ga3j9v$6lq$1@forums.macromedia.com...
> Thanks for the replies, I guess I will have to look at this from another
> angle
> then, if the memory error only exists in authoring mode. We have recently
> replaced the lab server and upgraded it from Windows 2000 to Windows
> Server
> 2003, could the fault have lied with the server? The thing about the error
> messages is, they do not always show up (the error comes up about 30-40%
> of
> times), and they occur at different phases; sometimes it is when the
> program is
> showing a picture icon, sometimes it is during a text input, and sometimes
> it's
> when an audio clip is being loaded. I have been accessing the program in
> the
> morning at the same time, so that is consistent there. I will start
> checking
> the Windows 2003 server FAQs and see if I can find anything there. Thanks
> again
> for the help.

Is this program web enabled or packaged as an executable?

What usually comes up with Win server 2003 is MIME type configuration. The
server won't send down files that don't have MIME types set up. If the mime
types apply to files listed in the map then this usually winds up looking
like the download or the application just froze up. It may or may not show
an error message for timeout.
As you go through your testing you should show the task manager and watch
the memory. See if the amount used keeps climbing abnormally. Authorware is
known to have some leaks but this is usually minimal and only has an effect
on things that run for days at a time. If you see big spikes in memory usage
then there may be something that's not clearing correctly. Watch the memory
for these jumps to see if they match with a certain operation in the app.

Mike
====================
Mike Baker
Adobe Community Expert
mike-baker at cox dot net

What usually comes up with Win server 2003 is MIME type configuration. The
server won't send down files that don't have MIME types set up. If the mime
types apply to files listed in the map then this usually winds up looking
like the download or the application just froze up. It may or may not show
an error message for timeout.
As you go through your testing you should show the task manager and watch
the memory. See if the amount used keeps climbing abnormally. Authorware is
known to have some leaks but this is usually minimal and only has an effect
on things that run for days at a time. If you see big spikes in memory usage
then there may be something that's not clearing correctly. Watch the memory
for these jumps to see if they match with a certain operation in the app.

Mike
====================
Mike Baker
Adobe Community Expert
mike-baker at cox dot net