>>>Yup - that fixed it. Great!!!
>>>
>>>I noticed that if you use the multi-volume disk option, when it prompts for disk two or disk three and you don't change the floppy, it will overwrite the data you just entered. I have set the following properties to .t. (.lmv_wipe, .lmv_SubDir, .lmv_SysHide ). I didn't find a property that would check for this and warn the user. Any suggestion other than issue a strong warning in the users procedure manual.
>>
>>There is nothing you can do about that. That problem even exists in earlier DOS versions of PKZip. There are somethings you just can not overcome, and two of those are user apathy and stupidity.
>
>Well, why not check if this disk contains files already or not? Presumably this should be a "clean" disk.

When you are spanning diskettes, the ZIP program is still in control. If you set the property to wipe the disk before creating the zip file, the diskette will be erased before the zip file is written regardless if the user has switched diskettes. The user is prompted to switch the dsikettes, but there is no gun to the user's head to force them to change diskettes. The Zip program will not look to see if the actually switched diskettes. We have no control over this.

Conversely, if the wipe disk property is false, the diskette is not erased first. However, if the diskette is full, the user keeps getting prompted to insert the next disk until a disk is provided that has some space on it. If disk 2 is full, you get prompted for disk 3, if disk 3 is full, you get prompted to insert disk 4, etc. Now the user has disks that are totally irrelevant to the current zip file, but for consistency, will be required if an unzip operation is permormed on them.