Windows

It's %systemroot%\repair. See here for details:

http://support.microsoft.com/support/kb/articles/q130/0/29.asp

Like the last guy says, its in %systemroot%\repair folder. I never experience that problem so i don't know if it copies only the files that has not been copied to the floppy disk. However, if you double check and compare the files with the ones in the repair folder you should know which has been copied and which has not. The format in the repair folder is not usable in its current format, to be able to use it, you need to run the command expand <file> at the command prompt. for instand to make the files sam._ usable you first need to run expand sam._ at the command prompt and it will make a usable version of sam in the current folder.

See TechNet Q122857
(RDISK /S and RDISK /S- Options in Windows NT) on running rdisk without asking for a floppy disk. This is especially useful for remote servers. Move the %systemroot%\repair\*._ + *.nt files to a safe place. Make sure the %systemroot%\repair folder is cleaned up and/or ntfs secure. The sam._ is the crown jewels for hackers. However the setup.log file is needed for any reinstall of service packs so leave this file alone.

Hi! How did you make out with this?