Member Avatar for Phenylfairy

Hi there!

This is my first post, so hello :).

I'm having problem with my Appleworks. I was working on a document last night, typing away etc, doing Command-S every so often as usual. Then I wanted to go to bed, so I just went to "shut down" and left it to it. I came back and it was fussing because "did I want to save changes to ThisOtherDocument?". So I said yes and it shut down and all was well.

However, I got up this morning, opened the file... and it obviously hadn't been saving :|.

I'd written over 2000 words last night, now I have less than 200. This is highly distressing, as it was an essay that was in for today (hence me getting up at 5am to finish it, heh heh).

I don't have Norton Utilities (got it at home but I'm in Uni) which I seem to recall can help with getting stuff back, but I was wondering if you could advise if there is any way to recover my work?

Oh yeah, I made the filename longer than Appleworks likes by changing it in the finder, could this have confused it enough to not save? The filename is "E. coli transcription regulation.cwk" but Appleworks is apparently calling it "E. coli transcription#E01D0.cwk".

Thanks very much in advance!

Phenyl Fairy

(X Posted elsewhere)

  • 2 Contributors
  • 1 Reply
  • 127 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by yellow

Dani AI

Generated

A focused recovery checklist and a few causes to check (ordered, low risk first).

Make a copy of every AppleWorks (.cwk) file you can find before doing anything else. Work from the copies so you never overwrite a possible recovery candidate. As suggested, filename/attachment issues are a common trigger — if the document arrived as an email attachment, reopen the original message and re-save the attachment before doing anything else.

Search for alternate copies and temporary files:

  • Look in the Trash and in any folders where the mail program stores attachments or temporary downloads.
  • Use Finder to search the whole home folder for AppleWorks documents (search by kind or by extension).
  • If comfortable with Terminal, search your home folder first (safer and faster) and only escalate to whole-disk searches if needed:
    find ~/ -type f -iname '*.cwk' -mtime -2 2>/dev/null

    If you find candidates, duplicate them to a safe folder (Desktop or external drive) before opening.

If a candidate file looks corrupt or AppleWorks refuses to open it, try extracting readable text rather than letting other apps write to it:

cp /path/to/candidate.cwk ~/Desktop/candidate-copy.cwk
strings ~/Desktop/candidate-copy.cwk | less

That can recover chunks of typed text if the document content survived in the file.

If the above yields nothing, restore from backups (Time Machine or other backup snapshots) or consider a disk-recovery product (DiskWarrior, Data Rescue) or professional recovery. Preserve the drive as-is (avoid extensive writes) if you plan to use recovery tools. Finally, when you get the document back, use short, simple filenames without legacy-reserved characters — older Mac apps sometimes create alternate filenames or temp copies when they hit problematic names.

Member Avatar for yellow

Oh yeah, I made the filename longer than Appleworks likes by changing it in the finder, could this have confused it enough to not save? The filename is "E. coli transcription regulation.cwk" but Appleworks is apparently calling it "E. coli transcription#E01D0.cwk".

Because the name of the file is too long. Sounds like this is possibly an email attachment that you were working on?

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.