DosTips.com

Agreed, goto is an immediate change of program flow. If you wanted to recast that script to do something and then come back and do something else, use functions:

If the source and destination have different file systems, eg NTFS and FAT or NTFS and some NAS running Linux/Samba, the date-stamp granularity is different and so Robocopy will always copy the file again. The remedy is to use /FFT which takes into account the tiny date-stamp differences. Also be ca...

In the Start command, the first parameter is the title of the window being spawned, but actually it hardly ever shows up. Nevertheless I find it more reliable to have an actual title, eg Start "" is unreliable I think.

Depending on what "over and over" means, one possibility is that the source has a junction point which refers to something in its own parent. So Robocopy just follows forever in a loop. To stop this, use the /XJ switch.

Generally speaking, you can't rely on the idea that writing new data to a file will replace the existing data. A 'file' consists of some metadata such as the name, and a linked list of pointers to clusters on the disk which the file system uses to construct the contents. NTFS is a transactional data...

The issue is that NTFS and FAT/FAT32 have timestamps of different accuracy so whenever Robocopy checks the time stamps between the source and the destination, it looks like they're different, whereas all that's happened is the high-resolution time stamp from NTFS has been rounded to the lower-resolu...

Just on the general topic of registry backup. Microsoft sort of created a problem here since they've never had a simple method to manage registries. On Windows NT 4 there was a tool called rdisk which supposedly made a sort of 'rescue disk' with boot information and a copy of the registry. Never act...

This is two questions, really. In Windows 2000, Microsoft changed the default profiles root from C:\Winnt\Profiles to "C:\Documents and Settings" and the folders were called "My Documents", "My Pictures" etc and then in Vista they changed it to C:\Users with folders called "Documents" and "Pictures"...

On my system Opera is in Program Files so I wrote this to start at the root:
Otherwise could be:

The glitch is that I should never have used exclamation marks cosmetically. But it used to work, and now doesn't. So either Microsoft has fixed a bug in Windows 11, or introduced one. Anyway I've just removed the exclamation marks. My point is that it's weird to find some changed behavior in CMD.EXE...

Just found one of my scripts broke on Windows 11. I had something like this: SetLocal EnableDelayedExpansion <do some stuff> if defined Result (echo Success) else (echo Failure!!) EndLocal This has always worked, but on Windows 11 it glitches. You can probably guess the !! in the echo command is the...