Page 1 of 1
SheepShaver crashes when WriteNow opens recovered files
Posted: Sat May 04, 2019 1:38 pm
by meyori
Has anyone gotten WriteNow 3 or 4 to work in SheepShaver? I'm running 9.0.4 and both crash immediately when trying to read files I recovered from a zip drive. Both produce the following error output:
Code: Select all
SIGSEGV
pc 00452147
ea 51D80000
r0 00000000 r1 1ece6988 r2 00000000 r3 68fff400
r4 eb800103 r5 68fff740 r6 000000a0 r7 00068414
r8 00000000 r9 0000ffff r10 0000ffff r11 00000002
r12 00000000 r13 00000000 r14 ffff80a3 r15 000080a3
r16 1ece6b36 r17 1ece6c68 r18 1ece7ae5 r19 00000000
r20 1ec56924 r21 1ece7bbc r22 1ece6a30 r23 00000000
r24 4b7ff0d7 r25 00000000 r26 00000000 r27 00000000
r28 001aeb04 r29 40d80000 r30 40c60000 r31 68fff000
f0 0.00000 f1 0.00000 f2 0.00000 f3 0.00000
f4 0.00000 f5 0.00000 f6 0.00000 f7 0.00000
f8 0.00000 f9 0.00000 f10 0.00000 f11 0.00000
f12 0.00000 f13 0.00000 f14 0.00000 f15 0.00000
f16 0.00000 f17 0.00000 f18 0.00000 f19 0.00000
f20 0.00000 f21 0.00000 f22 0.00000 f23 0.00000
f24 0.00000 f25 0.00000 f26 0.00000 f27 0.00000
f28 0.00000 f29 0.00000 f30 0.00000 f31 0.00000
lr 40d80000 ctr 00000000 cr 00000200 xer 00000000
pc 40d80000 fpscr 00000000
0x40d7ffe0:
This doesn't happen if you save a file and open it with WriteNow inside the emulation. The potentially only happens with files that aren't immediately identifiable via their file type, since the backup didn't encode that. However, WriteNow4 seems to recognize WriteNow3 files for a moment before the crash, because it says it's converting the file.
Re: SheepShaver crashes when WriteNow opens recovered files
Posted: Sat May 04, 2019 4:56 pm
by Ronald P. Regensburg
You do not mention your host system, I suppose it is OSX/macOS, and you do not mention which SheepShaver version/build you use.
1. Did you make sure to enable "Ignore Illegal Memory Accesses" in SheepShaver preferences > Miscellaneous tab?
2. Are you sure the old files are complete and intact, including their resource forks? If the files have been saved on a non-Mac files system and/or were compressed by a zip utility that does not include the classic Mac file properties, they may be damaged beyond repair.
3. If they were compressed with a Mac zip utility while residing on a Mac file system, which zip utility on which MacOS/MacOSX/OSX/macOS version?
Re: SheepShaver crashes when WriteNow opens recovered files
Posted: Sat May 04, 2019 5:29 pm
by meyori
Sorry, I completely forgot to include those details. I'm on Windows 10, but have Mac Drive to read HFS disks. I'm using the 01-03-2015 version.
To answer your questions:
1. Yes, I have, no change.
2. They were never saved or compressed in a non-Mac system. These backups are intact from 1997.
3. I do not believe they were compressed; when I say "zip drive", I mean an Iomega Zip Drive. The files do seem to be intact, because if you open them in a NotePad++ you can actually read the original text of the file interspersed with the binary information (presumably about font, document type, etc.)
EDIT: After some additional searching I just had the idea to try opening the files in LibreOffice, which seems to do a fairly good job at preserving the original formats. I would still like to see what they look like in the original program if possible, tho.
Re: SheepShaver crashes when WriteNow opens recovered files
Posted: Sat May 04, 2019 6:31 pm
by Ronald P. Regensburg
meyori wrote:I'm on Windows 10, but have Mac Drive to read HFS disks. I'm using the 01-03-2015 version.
[...]
They were never saved or compressed in a non-Mac system. These backups are intact from 1997
[...]
I mean an Iomega Zip Drive.
So you use Mac Drive to read the files on the Zip drive. How do you transfer those files from the Zip drive into OS9 in SheepShaver?
The files do seem to be intact, because if you open them in a NotePad++ you can actually read the original text of the file interspersed with the binary information (presumably about font, document type, etc.)
NotePad++ is a Windows application. It will read only the data fork of a classic Mac file. The resource fork could still be lost.
In your first post you wrote:
The potentially only happens with files that aren't immediately identifiable via their file type, since the backup didn't encode that.
How come? A backup made with a Mac from a Mac on a HFS (or HFS+) volume should have kept type and creator codes intact. They should be there with the files on the Zip drive. Those metadata (and probably the resource forks) may have been lost by the way the files were moved from the Zip drive into SheepShaver.
Re: SheepShaver crashes when WriteNow opens recovered files
Posted: Sun May 05, 2019 10:31 am
by Ronald P. Regensburg
I am mainly a Mac user and I do not have much experience with Windows. I think someone with experience with SheepShaver in Windows can better instruct you how to get files from the backup on your Iomega Zip drive into SheepShaver with their specific Mac file properties intact.
Re: SheepShaver crashes when WriteNow opens recovered files
Posted: Sun May 05, 2019 1:05 pm
by Cat_7
Hi,
Perhaps HFV explorer can read your zip drive directly? Does it show up as a drive in Windows?
If HFV explorer can read the drive, you can copy the files directly to a disk readable by SheepShaver.
Or perhaps Mac drive can also open a SheepShaver disk image?
Best,
Cat_7