|
Prev: Replacement software for Authorware
Next: Quiz
From: Steve Howard on 9 Jan 2008 13:41 > Are there any known memory issues with AW 6.5 webplayer running on XP? Not that I can recall. But to be frank, I've not used 6.5 for years. > I > haven't upgraded to V 7 yet because it would require the retesting of the > webplayer (the rules on what gets installed on the desktops here are very > strict about that here) and the repackaging of all the online courses and > that > would take months. The only repeatable but inconsistent (that you don't encounter at the same point each time) that I recall cropping up for Authorware content have been when different versions of Xtras somehow get mixed in. For the sake of argument, AW 6 and AW 6.5 might have slightly different versions of the JPG Xtra. If you use the wrong one when you package/deliver, then you might see occasional errors. But I doubt that's your problem since you are more than likely using the same packaged files you always have ... ??? Steve
From: sc_honeydo on 9 Jan 2008 13:57 Erik, thank you so much. I am not using Jump File/Jump File Return and I have not seen the multiple property inspector panels that you describe. PFTW, I'm not running the web piece either. This error occurs, not when running the built and published end-product, but rather when running authorware itself.
From: PFTW on 9 Jan 2008 14:05 Well then that is worrisome because I'm getting the exact same errors running a web-packaged piece and I was hoping there was something different that can be done while publishing (ie: an easy fix). But the fact that we're both using different versions of AW and the errors are occurring under different circumstances, tells me this isn't going to be so easy.
From: Erik **AdobeCommunityExpert** on 9 Jan 2008 15:37 Rats. Well, along with my reply to PFTW, are you using any third-party XTras? Those are less likely to be the cause, though, because your piece seems to be crashing as soon as you start Authorware. If you can start the program before you load in a project, close that Property Panel immediately if it's open, then close Authorware. Then open it again, then your project... What happens? Erik sc_honeydo wrote: > Erik, thank you so much. I am not using Jump File/Jump File Return and I have > not seen the multiple property inspector panels that you describe. > > PFTW, I'm not running the web piece either. This error occurs, not when > running the built and published end-product, but rather when running authorware > itself. > > -- Erik Lord http://www.capemedia.net Adobe Community Expert - Authorware http://www.adobe.com/communities/experts/ ------------------------------------------------------------------------ http://www.awaretips.net - samples, tips, products, faqs, and links! *Search the A'ware newsgroup archives* http://groups.google.com/group/macromedia.authorware
From: Erik **AdobeCommunityExpert** on 9 Jan 2008 15:35
Are you using BuddyAPI? I recall an issue like this when using an older version of it that had the Xtra and a DLL. Newer versions use just the Xtra. If not that, then any third-party Xtras you're using would be worth looking into and seeing if there's a newer version... Otherwise, do the errors seem to generate from a consistent place in the piece? IF so, examine what's going on in that section... Erik PFTW wrote: > Well then that is worrisome because I'm getting the exact same errors running a > web-packaged piece and I was hoping there was something different that can be > done while publishing (ie: an easy fix). > > But the fact that we're both using different versions of AW and the errors are > occurring under different circumstances, tells me this isn't going to be so > easy. > -- Erik Lord http://www.capemedia.net Adobe Community Expert - Authorware http://www.adobe.com/communities/experts/ ------------------------------------------------------------------------ http://www.awaretips.net - samples, tips, products, faqs, and links! *Search the A'ware newsgroup archives* http://groups.google.com/group/macromedia.authorware |