MT> If that doesn't work, SPACEHOG might.  It actually fills the extra
 MT> space with a hidden file so that free space is <=2gb (no TSR req'd)
 MT> and resizes the hidden file as necessary on subsequent runs.  It is
 MT> circa 2000, so don't know if it might choke on multi-terabyte drives.

 DM> That's an interesting approach.  But I'd have to "waste" 15gb. 

this is what i also spoke of in my earlier post... but in my case, i created
the file(s) manually because i needed to "waste" about 8G of space on a 12G
drive...

as i recall, i had or created a 25M zip file which i simply copied together
four times to make a 100M file... then i just copied that several times so
that i was loosing 100Meg of space each time... its a trash file anyway so
doing this doesn't hurt anything and i still have the original which IS
important...

if file.foo is 25M...

  copy /b file.foo + file.foo + file.foo + file.foo file1.foo

then i could copy the 100M file1.foo 5 times, as above, for a .5G file... the
thing i was looking at was also being able to delete them as the drive space
was consumed and i needed more for the stuff that is 2G restricted... the most
i would do via the above copying routine to create a large file would be a 1G
file and then have several of them... just have to watch, as i say, when
deleting because you don't want to delete too much and end up back over the 2G
freespace line ;)

i've thinking of looking into the above mentioned spacehog tool... i knew
there was something else out there but couldn't remember what it was so i went
with what i already knew how to do ;)

)\/(ark

 * Origin:  (1:3634/12)