On Fri, 27 Jul 2001, Lance Costanzo wrote: But since some think that the "drivers" (GUEST.EXE) will not work with an 8088, the value of your drive that does work just doubled. When using GUEST.EXE, it doesn't even need to be rebooted. In a surprisingly sensible move, Iomega actually wrote it so that it inserts itself into the device driver chain without rebooting! Unless you want WINDOZE, I think that it just needs GUEST.EXE. /V !!!!!! One 100M disk will be way more than adequate for a 251. But if you want to use disks that are already half full, or do larger drives, then you can do an ATTRIB C:\*.* /S +A to set the attribute bytes on all files and add a /M to the XCOPY command. That way, it will copy all files, including sub directory contents and structure, reset the archive bits on the files that it copies, and when the destination disk fills up, another XCOPY C:\*.* D: /E/S/V/M will cause it to continue from where it left off. (The /V is because I CARE whether the copy was successful) The biggest problem with XCOPY /e/s/v/M is that if you encounter a file that is too big to fit on an empty destination disk (such as WINDOZE swap file), it will hang there, and you will have to manually (ATTRIB) reset the archive bit of that file even to skip it. Use XCOPY32 if WIN9x file nicknames (LFN) matters to you. -- Grumpy Ol' Fred cisin(a)xenosoft.com