conversations.from: human
conversations.value: What could be a title for a book about Windows, Leading with the genre: Computers & Technology, Operating Systems?
conversations.from: assistant
conversations.value: A title for this book could be 'Windows 7 Secrets'
conversations.from: human
conversations.value: Do you know the first three paragraphs for this book?
conversations.from: assistant
conversations.value: Windows 7 Secrets
  As a reminder, Table 24-1 outlines the backup technologies highlighted in this chapter and explains which are available in each mainstream Windows 7 product edition.
  Although various data recovery tools are available scattered through the Windows 7 user interface, a single interface—Backup and Restore—provides a handy front end to most of them. Shown in Figure 24-1, this application helps you backup and restore files on your PC, create and restore complete system image backups as well, and access the System Restore recovery utility.
  Because Backup and Restore basically sits in front of most of the other data recovery functions included in Windows 7, we will use this as the obvious starting point for most of the data, file, and system backup and restore features discussed in this chapter.
conversations.from: human
conversations.value: Do you know four more paragraphs?
conversations.from: assistant
conversations.value: In the introductory page of the wizard, shown in Figure 25-22, select Choose a different restore point and then click Next to choose a restore point.
  As shown in Figure 25-23, you will now see a list of restore points. Most of these were automatically created by the system and will include a description of what was going on when each restore point was created. If you manually created your own restore points from System Protection, those restore points will have "Manual:" appended to the front of the restore point name.
  When you select a restore point, Windows will move into the secure desktop and begin restoring your system to its previous state. This requires the PC to reboot. Note that any applications you have installed since that restore point will almost certainly need to be reinstalled.
  You can also access System Restore from the Windows Recovery Environment discussed earlier in the chapter. This is useful when an install has made Windows particularly unstable. As shown in Figure 25-24, accessing System Restore from this environment is similar to doing so from within Windows.
conversations.from: human
conversations.value: Swap the first and the last sentence.
conversations.from: assistant
conversations.value: As shown in Figure 25-24, accessing System Restore from this environment is similar to doing so from within Windows.
  As shown in Figure 25-23, you will now see a list of restore points. Most of these were automatically created by the system and will include a description of what was going on when each restore point was created. If you manually created your own restore points from System Protection, those restore points will have "Manual:" appended to the front of the restore point name.
  When you select a restore point, Windows will move into the secure desktop and begin restoring your system to its previous state. This requires the PC to reboot. Note that any applications you have installed since that restore point will almost certainly need to be reinstalled.
  You can also access System Restore from the Windows Recovery Environment discussed earlier in the chapter. This is useful when an install has made Windows particularly unstable.In the introductory page of the wizard, shown in Figure 25-22, select Choose a different restore point and then click Next to choose a restore point.
conversations.from: human
conversations.value: Do you know the last five paragraphs?
conversations.from: assistant
conversations.value: With Windows PowerShell, determining the size of a directory in bytes can be accomplished with just three lines of code. First, you define a variable, $bytesize, and set its initial value to zero. Next, you pipe the output of the Windows PowerShell cmdlet alias dir into the foreach alias and add up the bytes. Finally, you display the total. The whole thing looks like this:
  Instead of using the third line of this script, which simply outputs the total onscreen, you could feed the number into another process, write the total into a file for later analysis, or any other number of alternatives. For example, if the selected files were too large for a single CD-R, a script you wrote could show you the message "Whoa, boy! You'll need two CDs for those files," or three, or four, or whatever number was calculated.
  Notice that we've used the aliases dir and foreach to make the second line of the script concise. If we had used the non-alias name of each cmdlet, the script might look as follows:
  Because a percent sign (%) is also an alias for the for-eachobject cmdlet, you could also make the original script even shorter, at the expense of being less readable:
  The percent sign in this case doesn't have anything to do with calculating a percentage. It's just an alias for the command foreach-object. This use of symbols may be confusing, but it does reduce the amount of typing developers have to do, which is always a good thing.