RS> If you dont have enough free space, its quite possible for that
RS> to just fail to unzip one of the largest PKTs out of the archived
RS> PKT without a single hint of a problem, just silently carrys on
RS> regardless and a whole chuck of mail goes straight into the bin
RS> forever.

PE> If you don't have enough free space to unzip your mail, I think
PE> it's time for you to either spring for a 1.4 meg floppy disk, to
PE> be used exclusively for unzipping mail,

Its fucking medieval to use a floppy in that situation instead of a
decent check for running out of free space.

PE> and you are not likely to run out of space on it,

Thats wrong too, quite a bit of the time thats not enough free space.
It was in with that specific set of PKTs which fucked up for starters.

PE> or (heaven forbid), spring out for a bit of hard disk space, since
PE> it only costs 70c per meg brand new.

Missing the point again, I have the free space, it just didnt happen
to be free where it needed to be.

PE> Crikey, you could set up a partition exclusively for unzipping mail.

Also fucking medieval.

There is only one sensible approach, code which behaves gracefully
when something goes wrong. And by far the worst thing is code which
just carries on regardless when things fuck up, never says a word,
gives the illusion that its worked fine, with half the fucking mail
silently filed in the bin.

PE> Why do you run important disks so low?

There is stuff which I dont particularly need to keep, which is handy
to have if I'm not short of space. If more space is needed, that stuff
can be dumped. Corse its handy if the software actually bothers to tell
you if its had a problem with lack of free space.

--- PQWK202