Hiya!
This is a known problem, which is due to the way Director saves its work. I
have personally lost nearly an entire project this way. I have earlier
requested from macromedia that they'd give the user the option to select
between using the current incremental save (quick but risky) and a full
save, which would not replace the original file until the save process has
completed successfully. Another case of macromedia sweeping a problem under
the carpet in the hope of making it go away.
Anyway, the first rule of thumb is to make backups. I personally made a
small app, which at the end of the day makes backups of all new files in a
specific folder. This has given me the security that I never lose more than
(at a max) one day's work.
Now in your case, I recommend the following.
As Director froze during saving there is no guarantee of how much of the
file it had time to save, If you're lucky, It might infact have been able to
save the entire contents (scripts) of the castlib, but not the header or
ender info (happened to me a copule of times). Now for the data in your
castlib, everything except the scripts will probably be gone, To recover
those scripts which were saved, you can try to open the corrupted castlib
with a plaintext editor (not Word or Appleworks) like BBEdit (even
simpletext might do it) or similar. Then you have to do some detective work,
in trying to decipher the contents of the text. The scripts are plainly
viewable and you can copypaste them into a script window, but you need to be
careful of where the script cast member begins and where it ends, as in some
cases that is not entirely apparrent.
This is as much general info as I have on the topic, if you need more help,
please contact me. Preferrably offlist.
Pekka Buttler
GMT+2
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Katagiri, Junichi
> Sent: 14. elokuuta 2001 16:40
> To: '[EMAIL PROTECTED]'
> Subject: <lingo-l> corrupted castLib
>
>
> This problem of mine is a rather devastating case where director
> froze while
> quitting. The result is an external castLib, where I used to store all
> parent scripts and linked my movies to, cannot be opened with director. My
> question is, obviously, "Is there a way to retrieve a castLib corrupted in
> such a way?" I know this sounds dumb, but losing it all will pull
> me back a
> few weeks. So I take the embarrassment and am hoping for your support.. I
> use Director Shockwave Stuido 8.5 on Mac OS9.1
>
> Thanks
>
> JunK
>
>
>
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
>
> This footnote also confirms that this email message has been swept by
> MIMEsweeper for the presence of computer viruses.
>
> www.mimesweeper.com
> **********************************************************************
>
> [To remove yourself from this list, or to change to digest mode, go to
> http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
> email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
> Lingo-L is for learning and helping with programming Lingo. Thanks!]
>
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
