AppleWorks 6.2.9 crashes on save in OS 10.6.8

I am trying to save old ClarisWorks v4 docs into AppleWorks v6 to then convert to either Numbers or Excel. Whether I try to Save or Save As to AW6 or to convert to Excel 98/2001 within AppleWorks it crashes before saving. Nothing else opens the CW v4 docs other than AW6, but it crashes no matter what I try - shorten file name, try direct conversion to Excel 98/2001 format - trashed pref & cache files - nothing works.


From one of the crash reports the problem is:


Crashed Thread: 0 Dispatch queue: com.apple.main-thread


Thread 0 Crashed: Dispatch queue: com.apple.main-thread

0 LaunchCFMApp 0xb80c56d0 0xb8000000 + 808656

1 LaunchCFMApp 0xb80c0037 0xb8000000 + 786487

2 LaunchCFMApp 0xb80dd8e8 0xb8000000 + 907496

3 LaunchCFMApp 0xb8145397 spin_lock_wrapper + 1791

4 LaunchCFMApp 0xb801ceb7 0xb8000000 + 118455


Thanks,


MartyP


This full crash report below if someone can see where I might be able to change something to prevent problem.



Process: AppleWorks [10109]

Path: /Applications/AppleWorks 6/AppleWorks 6.2.9.app/Contents/MacOS/AppleWorks 6

Identifier: com.apple.appleworks

Version: 6.2.9 (6.2.9)

Build Info: AppleWorks-1~0

Code Type: PPC (Translated)

Parent Process: launchd [274]


Date/Time: 2012-01-17 20:31:44.519 -0500

OS Version: Mac OS X 10.6.8 (10K549)

Report Version: 6


Interval Since Last Report: 147360 sec

Crashes Since Last Report: 7

Per-App Interval Since Last Report: 24475 sec

Per-App Crashes Since Last Report: 5

Anonymous UUID: 02CE7EDF-E270-4CF0-9081-C1A8E52172DD


Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x000000000000000e

Crashed Thread: 0 Dispatch queue: com.apple.main-thread


Thread 0 Crashed: Dispatch queue: com.apple.main-thread

0 LaunchCFMApp 0xb80c56d0 0xb8000000 + 808656

1 LaunchCFMApp 0xb80c0037 0xb8000000 + 786487

2 LaunchCFMApp 0xb80dd8e8 0xb8000000 + 907496

3 LaunchCFMApp 0xb8145397 spin_lock_wrapper + 1791

4 LaunchCFMApp 0xb801ceb7 0xb8000000 + 118455


Thread 1:

0 libSystem.B.dylib 0x80142afa mach_msg_trap + 10

1 libSystem.B.dylib 0x80143267 mach_msg + 68

2 LaunchCFMApp 0xb819440f CallPPCFunctionAtAddressInt + 206231

3 libSystem.B.dylib 0x80170259 _pthread_start + 345

4 libSystem.B.dylib 0x801700de thread_start + 34


Thread 2:

0 LaunchCFMApp 0xb815acc0 spin_lock_wrapper + 90152

1 LaunchCFMApp 0xb8179c5b CallPPCFunctionAtAddressInt + 97763

2 LaunchCFMApp 0xb80e88cb 0xb8000000 + 952523

3 ??? 0x8ac08d56 0 + 2327874902


Thread 3:

0 LaunchCFMApp 0xb815a8ff spin_lock_wrapper + 89191

1 LaunchCFMApp 0xb8176e5d CallPPCFunctionAtAddressInt + 85989

2 LaunchCFMApp 0xb80c6b13 0xb8000000 + 813843

3 LaunchCFMApp 0xb80c0037 0xb8000000 + 786487

4 LaunchCFMApp 0xb80dd8e8 0xb8000000 + 907496

5 LaunchCFMApp 0xb8145397 spin_lock_wrapper + 1791

6 LaunchCFMApp 0xb801ceb7 0xb8000000 + 118455


Thread 4:

0 LaunchCFMApp 0xb815a8ff spin_lock_wrapper + 89191

1 LaunchCFMApp 0xb8176e5d CallPPCFunctionAtAddressInt + 85989

2 LaunchCFMApp 0xb80c6b13 0xb8000000 + 813843

3 LaunchCFMApp 0xb80c0037 0xb8000000 + 786487

4 LaunchCFMApp 0xb80dd8e8 0xb8000000 + 907496

5 LaunchCFMApp 0xb8145397 spin_lock_wrapper + 1791

6 LaunchCFMApp 0xb801ceb7 0xb8000000 + 118455


Thread 5:

0 LaunchCFMApp 0xb815aa8b spin_lock_wrapper + 89587

1 LaunchCFMApp 0xb818c3eb CallPPCFunctionAtAddressInt + 173427

2 LaunchCFMApp 0xb818eeec CallPPCFunctionAtAddressInt + 184436

3 LaunchCFMApp 0xb80e88cb 0xb8000000 + 952523

4 ??? 0x8aba92c1 0 + 2327483073


Thread 6:

0 LaunchCFMApp 0xb815aa8b spin_lock_wrapper + 89587

1 LaunchCFMApp 0xb818c3eb CallPPCFunctionAtAddressInt + 173427

2 LaunchCFMApp 0xb818eeec CallPPCFunctionAtAddressInt + 184436

3 LaunchCFMApp 0xb80e88cb 0xb8000000 + 952523

4 ??? 0x8aba92c1 0 + 2327483073


Thread 7:

0 LaunchCFMApp 0xb815a93a spin_lock_wrapper + 89250

1 LaunchCFMApp 0xb8176f67 CallPPCFunctionAtAddressInt + 86255

2 LaunchCFMApp 0xb80e88cb 0xb8000000 + 952523

3 ??? 0x8ade5c96 0 + 2329828502


Thread 8:

0 LaunchCFMApp 0xb815aa8b spin_lock_wrapper + 89587

1 LaunchCFMApp 0xb818c3eb CallPPCFunctionAtAddressInt + 173427

2 LaunchCFMApp 0xb818eeec CallPPCFunctionAtAddressInt + 184436

3 LaunchCFMApp 0xb80e88cb 0xb8000000 + 952523

4 ??? 0x8aba92c1 0 + 2327483073


Thread 9:

0 LaunchCFMApp 0xb815a93a spin_lock_wrapper + 89250

1 LaunchCFMApp 0xb8176f67 CallPPCFunctionAtAddressInt + 86255

2 LaunchCFMApp 0xb80e88cb 0xb8000000 + 952523

3 ??? 0x8ade5c96 0 + 2329828502


Thread 10:

0 LaunchCFMApp 0xb815a8ff spin_lock_wrapper + 89191

1 LaunchCFMApp 0xb8176e5d CallPPCFunctionAtAddressInt + 85989

2 LaunchCFMApp 0xb80c6b13 0xb8000000 + 813843

3 LaunchCFMApp 0xb80c0037 0xb8000000 + 786487

4 LaunchCFMApp 0xb80dd8e8 0xb8000000 + 907496

5 LaunchCFMApp 0xb8145397 spin_lock_wrapper + 1791

6 LaunchCFMApp 0xb801ceb7 0xb8000000 + 118455


Thread 11:

0 LaunchCFMApp 0xb815aa8b spin_lock_wrapper + 89587

1 LaunchCFMApp 0xb818c3eb CallPPCFunctionAtAddressInt + 173427

2 LaunchCFMApp 0xb818eeec CallPPCFunctionAtAddressInt + 184436

3 LaunchCFMApp 0xb80e88cb 0xb8000000 + 952523

4 ??? 0x8af41ff6 0 + 2331254774


Thread 12:

0 LaunchCFMApp 0xb815a8ff spin_lock_wrapper + 89191

1 LaunchCFMApp 0xb8176e5d CallPPCFunctionAtAddressInt + 85989

2 LaunchCFMApp 0xb80e88cb 0xb8000000 + 952523

3 ??? 0x8bc50da2 0 + 2344947106


Thread 13:

Posted on Jan 17, 2012 5:49 PM

Reply
4 replies

Jan 17, 2012 7:01 PM in response to MartyP

I have no clue about crash reports so I can't say what it does or doesn't reveal.


It's quite possible that the spreadsheet is corrupt. I suggest copying & pasting the data into a new AppleWorks spreadsheet or even a word processing document (it will be tab-delimited text). If you already have Numbers or Excel, you could paste the data directly into one of those documents.


User uploaded file

Jan 19, 2012 2:12 AM in response to MartyP

Thanks for replies Peggy & Fruhulda. I had tried to copy from the old SS to a new one, but AW6 quit the second I selected "New SS." When pasting into another app most of the formatting was gone (no font color, style or size carried over - no borders, etc. Why, I don't know. Luckily, the rare time AW6 didn't quit (when going from AW to Excel 98/2001), I noticed the MacLinkPlus progress bar flash on and off. I have MacLinkPlus 13 and haven't used it separately in 6 or 7 years. Once it was reinstalled (something I can no longer do with AW6 since OS9 isn't supported) all the CW or AW docs and even old MS Works 2 and 3 spreadsheets converted to Excel instantly.

Now if I could find something to convert old MacWrite 4.5 docs to something current I'd be ecstatic. Thanks again.

Jan 19, 2012 3:14 AM in response to MartyP

Hello MartyP

>Now if I could find something to convert old MacWrite 4.5 docs to something current I'd be ecstatic.

> Thanks again.

Normally, MacLinkPlus seems to be able to convert MacWrite 4.5 documents ( see for instance http://www.techrepublic.com/article/translating-files-using-the-maclinkplus-util ity/5033391 ). So if you still have it, it may be the better option.


If not, one solution can be to use a emulator ( for instance, minivmac http://minivmac.sourceforge.net/ ).


Note: as I am trying to create some filters for old documents, you can also try http://sourceforge.net/projects/libmwaw/files/ , if you want.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

AppleWorks 6.2.9 crashes on save in OS 10.6.8

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.