johna@moliman.MoliEnergy.BC.CA (John Altstadt) (05/02/89)
<our local backbone site was sick, so I don't think this got out> Hmmmm. There may be a problem with the binaries for zoo.ttp that were recently posted. (Then again, maybe it's a problem in the source, TOS, my brain, etc...) I was trying out zoo on the weekend, converting some old arc files to the zoo format to see if I could shrink the number of disks I have around. (Yes, I did un-arc the arc files before I tried zooing them.) The first one went great, a 60+k arc file became a 50+k zoo file, then I tried converting AIM (Atari Image Manager). AIM uses a directory for the help files, so I thought that it would be a good test case. Well, after running for a while, zoo came up with an "I/O error reading file" or some such error message. I figured that it probably filled my ram disk, so I re-booted the system without it, started MSH again and had my TMPDIR set to \TMP on my hard disk. I tried zooing the files again and zoo died with the same error message, on the very same file (the first .IM file). Then I zooed everything but the .IM file with no problem. Trying to add any of the .IM files to the zoochive always terminated the program. Then I arced the .IM files in one arc, and tried adding that to the zoochive. Same error. One last try... add the .IM files without compression (fast option). The program terminated on the first .IM file with a new error message: "I/O error on file, or disk full" or something similar. Now, with more than 2Meg free, I have my doubts that zoo was filling the disk. The only strange thing about .IM files are that they are exactly 64k bytes long (or is it 32k?). Does anybody else have this problem? Can it be fixed? I want the directory support features, but until this is fixed, I will live with .arc files in .arc files in... John