Skip navigation
FVMF
Currently Being Moderated

Corrupt erase icons

Jun 20, 2012 7:54 AM

Tags: #erase #icon #corrupted #cb1 #_500

Hi all,

 

Lately, I'm experiencing problems with corrupt erase icons. I'm running Authorware 7.0 on Windows 7. When I copy a questionnaire from one authorware file to another, one of the erase icons becomes corrupt. When I want to delete the erase icon, I get the internal error 'cb1, 300' (like that is informative...). Saving and compacting results in the error 'Unable to save this file because of the following error: computer memory is full.' The solutions of the thread http://forums.adobe.com/thread/897544?tstart=0 did not solve the problem. It would be nice to know why this error occurs, and how to prevent it in the future. Copying all the non-corrupted icons to a new file and creating a new, uncorrupted erase icon will also do the trick, but becomes quite tedious in the long run. So if anyone has a solution or a suggestion other than those already suggested, I would be happy to hear!


Regards,
Frank

 
Replies
  • Currently Being Moderated
    Jun 20, 2012 8:12 AM   in reply to FVMF

    There was an issue involving erase icons and corrupted backpointer lists which was corrected in the 7.0.2 free update. I see that the other thread you mentioned already references that update. Simply updating Authorware and opening the file won't fix the issue, however. The backpointer list is rebuilt when you 'touch' the icon. You have to move it on the flowline for the backpointer scan to take place. When I put in the fix I just dragged the icon to the right a bit and let it go. That should rebuild the backpointer list. You may wind up with something that used to be erased that isn't but you shouldn't have a backpointer that points to something that's non-existent or an icon without a display component, which is where we get into trouble.

     

    HTH,

    Mike

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 20, 2012 8:14 AM   in reply to FVMF

    Why icons become corrupted, no known reason. Theories are between files that grow to large and/or are edited so much with a lot of add/edit/deleted icons that internal 'pointers' just get out of whack.

     

    You have applied the latest Authorware update, 7.02, right?

     

    Primary way to avoid such issues: Use 'Save and Compact' often. When creating an Authorware project, any time I make a significant update to the code, I save-and-compact to a new file. A good habit to get into.

     

    Working off a network location as opposed to a local drive also is suspected of contributing to corrupted icons and/or files. I've not had that problem in many, many years...but if it's something you experience, work locally and copy up to the fileshare when done for the day.

     

    With the icon issue itself, copy around the icon, as you suggest - everything before it, copy, paste into a new file - everything after it, copy, paste into a new file, then create a new erase icon and fix up any broken linkages.

    Save and Compact the file and use that new one as your new 'master'.

     

    If Save and Compact, or Save As, doesn't work on your current master file due to these corruption issues, it's time to abandon that file before the problems get worse.

     

    Oh, one trick I think is likely useless but some hace said it works - .zip the Authorware source file, move it to a new location, and unzip it, then test that source file. There are old claims this can help rebuild a file and nix the problem code. I doubt it, but can't hurt to try.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 20, 2012 9:33 AM   in reply to FVMF

    Once the file is corrupted by updating it to AW 7 or 7.01, that corruption

    is not fixable.

     

    Do you have an older version of the file?

     

    Steve

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 21, 2012 11:58 AM   in reply to FVMF

    Perhaps try making a copy of the original Authorware file you're pulling pieces from, then updating that copy to 7.02.

    All work fine? Save and compact... All good?

    Then copy pieces out and paste into a new A'ware 7 project. All ok?

     

    Prevention - as has been mentioned before... oh, and karma... Hubris has been shown to have a direct effect on Authorware source code stability.

    ;-)

    Once corrupt though, no way to solve other that to cut around the bad parts...

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points