home *** CD-ROM | disk | FTP | other *** search
- ZipOff: A third party PKZIP(*) extender
- ----------------------------------------
-
- A .ZIP backup program
- Written and Copyright (c) 1990-1991
- by Morgan Schweers
-
- INTRODUCTION
- The ZipOff program is designed primarily for taking large .ZIP
- files and splitting them among multiple disks. The goal here,
- however, was to make each disk have a valid and readable .ZIP file.
- (As opposed to simply splitting the file at some point, and having
- to recombine before use.)
-
- HISTORY
- There are many ZIP splitters already available. Given this,
- you might wonder why I released this one. In my experience, all
- the .ZIP splitters out so far either require there to be large
- amounts of drive space available, or they do not produce readable
- ZIPs.
- Many of the ZIP splitters already out there require two to
- three times the space used by the .ZIP for their buffering. Since
- none of the splitters came with source, I was unable to determine
- the reason for this usage.
- In the mean time, I had a 15Meg long .ZIP file created as a
- backup of one of my drives. I wished to split this off onto
- seperate disks, yet still have access to the data that was in it.
- That's how this program came into existance.
-
- HOW TO USE
- The program is designed for ease of use, really. The standard
- means of operation is the default, and requires no options. The
- command line format is as follows:
-
- zipoff {source file}[.ZIP] {destination path} [options]
-
- The destination path *MUST* include a drive specification,
- if operating in standard mode. Both the source file and the
- destination path *MUST* be in the command, and *MUST* be in that
- order. The options can be spread among the commands, and
- accept both the dash and the forward slash as delimiters.
-
- Options cannot be stacked on one delimiter, and each parameter
- and option must be seperated by at least one space.
-
- Values which go along with options *MUST* be flush against the
- option letter.
-
- The options are as follows:
-
- -m#### The #### is the maximum size for the
- output ZIPfiles in bytes.
-
- -bNAME This makes 'NAME' the default six-character
- base for the output ZIPfiles.
-
- -n Non-Interactive mode. (Works only with -m)
-
- The -m#### option was mainly designed for splitting a large ZIPfile on
- disk into many smaller ZIPfiles. It expects that you have the space available
- and will eventually die if you don't.
-
- If you are splitting to a non-removable media, or a removable media with
- enough space to hold the files, you can give the -n option. This is, however,
- only valid with the -m#### option. The program (by default) calculates the
- disk space available before starting a copy. If it stops, then it has filled
- the disk. Then -m#### option simply creates the files with that size. It
- stops once it has reached that size limit, and prompts you to continue. This
- usually isn't necessary, thus the -n option.
-
- The option you're most likely to be using is the -bNAME option. It sets
- the six character basename from NEWZIP to whatever you specify. If you
- specify a NAME longer than six characters, it truncates and warns you that it
- has done so.
-
- If an incorrect number of parameters are given (such as none), the
- program will display a help screen with the information on how to run it.
-
- To do backups, my recommeded procedure is to clear off a good 20-25
- Megs of space on one drive. Then do a
-
- PKZIP -arpwHS cdrive.zip c:\*.*
-
- This will ZIP up the entire C drive, into a zipfile named CDRIVE.ZIP
- in your current directory.
-
- Then, after thats done, you can use the ZipOff program as follows:
-
- ZIPOFF CDRIVE.ZIP A:
-
- It will load in the ZIPfile, sort it, and you'll take it from there!
-
- This program works really well in conjunction with programs like
- MaxiFormat and FDFormat. These programs format more space on disks than
- DOS normally does, adding as much as 400K to the floppies.
-
- I would recommend, BTW, that you register PKZIP. It's a good thing
- to do, and it'll give you this warm fuzzy feeling. :-) Read the section
- on registration for info on my opinion about registering this program.
-
- SUPPORT
- I'm willing to provide whatever support I can, but I'm not a company.
- If you want support, there are two main ways I can give it. One is if you
- are on the Internet, you can send me mail at the address listed at the
- bottom of the document. I respond to those usually very quickly.
- The other option isn't all that wonderful. If you're not on the
- network, all I can offer is a bug-reporting service. Write me at my home
- address (listed at the bottom) and I'll check out and try to fix the bug.
- If you include a Self Addressed Stamped Disk Mailer, I'll try to send you
- a disk back when it gets fixed. No guarentees, however.
-
- Read the disclaimer, and be warned! I am *NOT* liable for any damages
- caused by this program to your machine. I have tried VERY hard to make
- everything work right, but your machine may be just that touch different
- that makes something go wrong. Moreover, it's impossible for me to test
- the program in all situations, and on all files. Bugs may have slipped
- through. Nothing *SHOULD* be critical, since it's a reasonably careful
- program. However, that bug is not dead which can eternal lie, and with
- strange electrons, even this code may die.
-
- Once upon a time, I wouldn't have bothered to include a disclaimer,
- but with the litigation I've seen recently, I feel I have to. Down with
- Lawyers and Insurance companies!
-
- DISCLAIMER
- This program is Copyright (c) 1990-1991 Morgan Schweers.
- This disclaimer is Copyright (c) 1983 Regents of the University of
- California. All rights reserved. They neither endorse, nor promote this
- product, however.
-
- Redistribution and use in source and binary forms are permitted
- provided that the above copyright notice and this paragraph are duplicated
- in all such forms and that any documentation, advertising materials, and
- other materials related to such distribution and use acknowledge that the
- software was developed by Morgan Schweers. My name may not be used to endorse
- or promote products derived from this software without specific prior written
- permission. THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
- IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
- MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
-
- REGISTRATION
- There is none.
-
- The program is, essentially, freeware. I would really appreciate some
- donation (around $5.00 would be great!) if you use the program much. (For
- example, if you back your HD up with this.) My network connection costs
- me around $15.00 per month, so you'd be paying 1/3 of my connection for a
- month.
-
- If you're not willing to send $5.00, though, I'd appreciate a postcard
- if you found the program of use. Really. I collect them. (No, my name's not
- Craig Shergold. ;) ) Just mention on it that the program was Zipoff, and
- write any comments you'd like to make!
-
- If, however, you're looking to use this on a company scale (I.E. It's
- important to your business, or some-such) I'd expect some reasonable
- compensation. I leave it up to you, really.
-
- You may NOT sell this program. You may NOT SELL this program. You
- may NOT SELL THIS PROGRAM. (Get the picture?) It is my code, and I want
- all people to feel free to use it. Shareware distributors may include it
- on Shareware disks, as long as the disks are priced reasonably. (Under
- $5.00 each.)
-
- If you wish to use any of my code in a commercial application, please
- get in touch with me.
-
- VALIDATION
- The program has had a validation code added to it with the ViruScan
- package from McAfee Associates. Here also are the validation values using
- the VALIDATE program.
-
- File Name: ZIPOFF.EXE
- Size: 28,777
- Date: 7-4-1991
-
- File Authentication:
- Check Method 1 - 787B
- Check Method 2 - 00E7
-
- FEEDBACK
- I appreciate feedback, and would be happy to hear of suggestions for
- features, or warnings of bugs. Bugs especially! I supply the source,
- because I think it's a neat hack, and so anyone else interested in writing
- ZIP-handlers can check it over. Furthermore, if you find a bug *AND* fix
- it (AND send me the source, the bugfix appropriately commented with your
- name) I'll leave it in there, when it's re-released. I do ask, though, that
- you send bugfixes through me rather than just redistributing them.
-
- I strongly recommend that you 'PKUNZIP -t' the .ZIP files that result
- after a split. The test feature of the PKUNZIP is your security that the
- archives are okay. If there's a problem, try doing the split once more.
- If the problem persists, please do a
- PKUNZIP -V {original-zipname} > BUG.TXT
- and mail it to me at my network address, or (if you want to) at my home
- address. Also tell me which version of the product you are running.
-
- I tried to make the program bullet-proof. I'm rarely successful in that,
- since bullets are so ingenious. ;) If you do come across a problem, please
- feel free to drop me a line either on the postcard, in a letter, or by Internet
- mail.
-
- My addresses follows. Thanks muchly for taking the time to read the
- documentation! (It's more than I usually do, I admit...)
-
-
- Morgan R. Schweers
- 400 Riverside Court #210
- Santa Clara, CA 95054
-
- mrs@netcom.com (Preferred)
- ms@gnu.ai.mit.edu (Will do in a pinch)
-
-
- (*) PKZIP, PKUNZIP, ZIP, and PKWare are probably all copyright PKWARE INC.
-
-