It would involve rewriting zipdll (and has a number of holes - keeping files stored on same path together, large files mixed with small ones) but I have in mind ways to try (when I get a chance) Russell Peters http://www.users.bigpond.com/russellpeters/delphizip.html ----- Original Message ----- From: "Alistair George" <bigal@xxxxxxxxxx> To: <delphizip@xxxxxxxxxxxxx> Sent: Sunday, December 08, 2002 5:43 AM Subject: [delphizip] Re: Spanned SFX > > Hello James, et all > JT> The problem with using a generic file splitter is that if you only want one > JT> file from a large diskset, you still have to load all the disks. The > > And that is the most disconcerting problem - imagine you have backed up 15Gb > hard drive data and only want zipmastr.pas off it. It is most inconvenient > having to replace all the disks to eventually get the one file. > The only practical easily done solution I place at the end of these > comments.... > > Not only, but also, maybe the users hard drive does not have sufficient space to > hold the temporary zipfile (what happens in that instance?) Makes me ask also, > during the current building process for spanning are not the whole zipfile built > on hard disk THEN broken into parts and sent to destination. Once again, if the > hard disk does not have the temporary storeage size what happens then?? > > JT> approach I outlined earlier would require no temporary file and no > JT> unnecessary disk swaps. It would also be smaller. > Sounds good. > > >Yes, the way disk apnning is handled at this moment is rebuilding a > >temporary zip file and then start extracting. > However, if it were possible, and no requirement (for loading all the disks to > build a complete zipfile) before extraction were possible, that would be > desireable too?? Sorry for my lack of knowledge. > > > My suggestion to get an interum approach would be: > Maxdisksize, NoSpan. > The user selects their desired files for inclusion. I am writing a wee > calculator to show approximate filespace (compressed) for the current file > selection. > User presses 'Write Archive' dll progress archive till mazfilesize, the archive > is closed as a single archive and if files omitted those missed are returned > as per usual error format. > Thus we have a single zip with slightly inconvenient management, but no problem > getting desired restore file. > I would guess that most users having a full backup would require a maximum of > say five CDR disks. They are not spanned and the management is a little less fluid, > but in restore easier and much faster than the current spanning system. > Can this Maxdisksize Nospan be done in the interum please? > -- > Regards, > Alistair+ > > >