Re: Possible hardpressed bug

[fadden@uts.amdahl.com (Andy McFadden)]

In article <1993Jul13.214130.26003@vpnet.chi.il.us> vagrant@vpnet.chi.il.us (Guy Umbright) writes:
>On a semi-related note, when you copy and the target is full, you get the
>dialog box telling you that a problem occured and HP is going to restrict
>access  until you free up some space.
[...]
>                                               Would it be possible to
>give the option to tell HP to just abandon the operation?

Yeah, I suppose so.  I think a better option is to turn HP off, compress
the files, and then copy them over without compression (yes, the Finder
extension stuff still works regardless of HP's state), but I guess if you're
doing some sort of back-up thing that's not much of an option.

BTW, because of the way it works, you never end up with "stuck" files when
just compressing with the FExt... it's able to recover.  It's only when
copying files to a disk that's about out of space that you have problems.

Out of curiosity, did any of the files that complained about bad headers
have resource forks?  More importantly, did ALL of them have resource forks?
I discovered (to my great surprise) that bytes $10-$ff of the resource fork
are marked as "reserved" on the Macintosh... so if you tried to compress a
file over AppleShare, the Mac Finder would overwrite the HP header right
after the HP header finished overwriting the Mac Finder info.  In short, it
was a mess, but v1.0.1 will fix it.  I'm curious to know if what you're
seeing is related.

-- 
fadden@uts.amdahl.com (Andy McFadden)
[ Above opinions are mine, Amdahl has nothing to do with them, etc, etc. ]