Authorware 5.2 and SP2
in [Authorware]
|
From: Amy Blankenship *TMM* on 18 Jul 2005 11:40 Maybe you had just enough other background processes running to keep it working, and SP2 improved memory handling and freed up enough memory to cause it to fail...? -Amy "Laust" <webforumsuser(a)macromedia.com> wrote in message news:dbgi03$6ic$1(a)forums.macromedia.com... >I know I haven't been back to post in a couple weeks since the last reply, >but > after a lot of research, i have one last question about this problem. The > previous admin had Authorware 5.2 working and these same machines last > semester > and the only thing that is different between now and then is that SP2 is > installed. I discussed this with him and he said he didn't do anything > special, > he just installed it and it worked. None of the systems specs have been > changed. So, i'm having a hard time accepting that Authorware doesn't > support > that much ram due to the fact that, it did work 1GB of ram in the first > place. > Hence my original question of if the program had a problem with SP2. > Currently, > I am going to suggest that we get an upgrade anyways, but this is the last > area > that I'm sure they will ask me about before upgrading. "It worked last > semester, why won't it work now?" If anyone can give me a little insight > to > this, I would greatly appreciate it. > Thanks >
From: Laust on 18 Jul 2005 13:39 Hey! Thanks for the info. I think I misunderstood the original post. That or it just clicked. I went in and changed the page file to keep it under 2GB. It worked for all but 2 machines. and those are because they have 2GB memory plus the page file. Not much I can do there. Thanks for the info and sorry I didn't catch it the first time.
From: jennyb_ga on 18 Jul 2005 20:35
hello friend, We have Authorware 5.2 and 6.5 running with SP2 and XP. Our experience with the error you have reported "computer memory full" was when we tried to run a file which contained a corrupted icon...this icon was usually a display or an erase. The error was not indicative of a true memory full problem just some code "gone bad". It seemed to be a result of copying files back and forth from the server. We were able to open the file and just start testing icons until we found the "bad" one. |