🚀 go-pugleaf

In article <10797@wehi.dn.mu.oz> BAXTER_A@wehi.dn.mu.oz writes:

[lots of other stuff deleted]

>You know how big the space is, yes? So you want to know how big the file is.
>Copy it to Nil:/Null: and cout the bytes on the way. It will be quick enough
>to not make much difference (Unless the file is enormous, in which case, you
>will have some idea of if it will fit :-)

Or you can just seek to the end of the file with OFFSET_END and then find
the size...  (Why copy it)  Or you could get the information by doing an
Examine() on the file.  The real question here is how to figure out if a file
will fit on a device.  This can not be done without trying.  That is, the
device may be running a filing system that uses different allocation units
or block sizes etc.  Plus the system, being multi-tasking, could end up using
some of the space while you are writing the file.  (Some other application also
writing a file) and thus mess you up.  The only real method is to try the copy
and see if it worked.

>Regards Alan> 
>>  -- 
>> UUCP:  kim@uts.amdahl.com   -OR-   ked01@juts.ccc.amdahl.com
>>   or:  {sun,decwrl,hplabs,pyramid,uunet,oliveb,ames}!amdahl!kim
>> DDD:   408-746-8462
>> USPS:  Amdahl Corp.  M/S 249,  1250 E. Arques Av,  Sunnyvale, CA 94086
>> BIX:   kdevaughn     GEnie:   K.DEVAUGHN     CIS:   76535,25


/----------------------------------------------------------------------\
|      /// Michael Sinz -- CATS/Amiga Software Engineer                |
|     ///  PHONE 215-431-9422  UUCP ( uunet | rutgers ) !cbmvax!mks    |
|    ///                                                               |
|\\\///       Quantum Physics:  The Dreams that Stuff is made of.      |
| \XX/                                                                 |
\----------------------------------------------------------------------/