A quick note on how to copy files and folders over without overwriting existing files. It's easy to say "Yes" and replace all files. What I need is something that synchronizes files on an internal hard drive to an external one. I wanted it to copy only the files that were new in the original folder and only copy those over (reason being, the archive is 4 terabytes and backing up only the changed files would speed things up).
- Microsoft Windows XP
- Microsoft Windows 7
- Microsoft Windows 8
- for Vista and Windows 2008 without XCOPY, try ROBOCOPY.
We're going to use MS-DOS because I'm that old.
A quick note for myself as I'd forgotten how to do this (we're talking technology belonging to the 90s - MS-DOS v6.22). The example wants to loop through a directory and then loop through the line it finds.
I use another technology for automation but sometimes the simpler solution is the one I make for other people to use. Explaining MS-DOS batch programs is a lot easier and colleagues trust these more than my all-in-one GUI applications.
Note: we're using the code in a DOS Batch program so our variables have to be prefixed with a double-percent rather than just the one:
- Microsoft Windows XP
I keep having to do this every year as I reghost all my machines (=restore to sorta factory settings), so instead of googling it and going through other websites that work and don't; I thought I might as well post the way I do it:
- Open up windows explorer
- Go to Tools -> Folder Options
- Click on the File Types tab
- Scroll down and select (NONE) Folder as file type
- Click on Advanced
- Click on New...
- For the Action type what ever you want the context menu to display, I use Command prompt from here
- For the Application value type c:\windows\system32\cmd.exe (this will be different on winnt, browse if unsure to your cmd.exe program)
- Click on OK > OK > Close
- Added by default since Microsoft Windows 7
During a critical business period, we monitor the use of a program which only one user can be using at a time. We encountered the issue where the user who would go in to check for any errors, would forget to tell everyone else that they are no longer using the program when they are done.
The program is on a server to which our standard credentials cannot use the "OPENFILES" command on the server to determine who is using a specific program. We wanted IT staff to be able to check for this without disrupting other staff, all our IT staff are admins on standard workstations.
We don't have access to the server but what we do have is admin access to the workstations connected to that server. In order for the following to work, we had to pass the following criteria:
- Administrator rights on remote workstation.
- Need to know the computer name or IP address of the remote workstation.
Open a command prompt
tasklist /s <computername>