I've never done it that way, but it might be possible with a little manipulation. A problem is that because of a registry bug you can only log into w2k if its drive letter comes up the same as that on which it was installed. However, if, say, your current w2k drive letter is C:, you can do that by adding a third HD that is, say, SCSI (or ATA66/100), which when booted from BIOS will then come up as C:. Then, you'd use the minimal w2k install that I mentioned to copy drive C: directly to the SCSI drive. You might have to edit its boot.ini to account for the change in controller, but that's easily done - or, if you're unsure how to do that, you could find out by simply installing w2k on the SCSI and seeing how w2k configures its line in boot.ini. Of course, there would be the hardware change (w2k finding itself running on a hard drive whose configuration has changed), but overall I've found that w2k adjusts well to hardware changes and makes the necessary registry adjustments, sometimes querying you in the process and sometimes not. The duplicated drive and other security IDs might present a problem - on a domain it would for sure, but maybe not on a standalone or workgroup computer - you'd have to try it and see. If you try it, let us know how it works. I'm curious. I wouldn't bother trying it myself since, unlike a DOS program like Ghost, w2k can copy a large disk in about 10 to 15 minutes. Fifteen minutes for a backup, or fifteen minutes for a restore, is not bad. Certainly a lot faster, I've found, than playing with Recovery Consoles, repair installs, and the like. I've used this system on my wife's computer so she wouldn't have a long downtime if things needed to be fixed.