back | content | forward

1.2 Frequently Asked Questions

1.2.1 What information is backed up with Install-Backup?

Install-Backup saves all files which is necessary to restore Windows® and the installed software on a blank hard disk. It does not matter if these files are located on only one or on different drives. This is a significant advantage over conventional backup programs which are forced to always back up complete drives.

Example
SystemRoot C:\WINDOWS
Profiles C:\Users
ProgramFiles C:\Program Files
ProgramData, beginning with Vista™ C:\ProgramData
Boot, ab Vista™ C:\Boot
ProgramFiles (x86), only 64 bit systems C:\Program Files (x86)

Folders like the Recycle Bin are not required by Windows® and the installed software. They will not be backed up.

On the other hand, personal data is excluded, because it is not required by the Windows® environment to work correctly. Folders with personal data may be backed up regularly with Private Backup.

Install Backup does not save the content of these directories:

beginning with Vista™ XP, Server™2003
Documents My Documents
Pictures
Music
Videos
Downloads

The default folder for Google Drive is excluded from backup and restore, because it contains only personal files.

Each backup contains all Reuschtools files for the recovery. This means that the restore process can be started directly from the backup record. Installing Reuschtools is not necessary.

InstallRestore32.exe Launches Install Restore on 32 bit systems.
InstallRestore64.exe Launches Install Restore on 64 Bit Systems.

The subfolder 'data' contains Zip archives and the Reuschtools software. In addition there are the following files:

RtConfig.ini important information for Install Restore
HardRestore.txt List with components that have to be adapted to dissimmilar hardware.
A user can edited this file.
NotToRestore.txt List of folders that are backed up but will not be overwritten when restoring.
A user can edited this file.

If you would like to exclude software from backup and restore, you can install it outside the designated folders.

1.2.2 Are there incremental backups?

No, because the risk of failure increases with every new backup. But there is something better. The template technique can update an existing backup. Runtime corresponds to incremental backup but you allways get full backups.

1.2.3 How often should I run Install Backup?

Install Backup saves the Windows® environment. You should run it if the Windows® environment has changed.

  • New software has been installed and you want to keep it permanently.
  • Settings have been changed. This could, for example, be a wireless connection with password to automatically connect to the Internet each time the computer gets started.

At best, Install backup never needs to be executed after a PC has been set up and everything is working properly.

Important, what you back up is what you get back. You should not overwrite a good backup if you are not sure that your Windows® is clean.

1.2.4 How do I get a clean Windows® environment?

Congratulations on your purchase of a new PC or notebook. Many "apps" are already installed. Evan more software which has to be payed after 30 days of testing. Regulary pop ups tell you how unsafe your computer is without paying. It's best to buy a smart phone to do your tasks, quickly and safely.

A Windows® environment which is very busy in the background does not only slow down your Windows®. It also reduces the life of the hardware. Rule of thumb: 18 degrees Fahrenheit higher reduce life expectancy to the half. This is rather important for notebooks since heat dissipation is more difficult. The fan should be silent if a machine is idle.

Often there is only one solution. To reinstall a clean Windows® environment. Be sure that a Windows® installation medium is included when you by a new computer. If you like you can additionaly keep the original Windows® environment.

Hold down left Shift + Ctrl and press Esc to open the Task Manager. Here you can see a clean 64-bit Windows® 8.1 environment at idle:

clean

  1. 25 processes running in the background (Defender and Firewall disabled)
  2. The CPU starts the Task Manager
  3. The CPU is idle

To install a clean environment, proceed in 3 steps. Write down your action with keywords to a text file. After each step, you should create a backup with Install Backup. Use the name of the respective step (Basic, Soft, Run). The backups can be stored on the Windows® drive. You take no risks, as soon as something goes work you can rapidely get back to the previous step with Install Restore.

1. Basic

  • Install Windows® from the installation media. When you first start Windows®, you will be prompted for the settings. Turn off what you can.
  • If Windows® is newer than the hardware componets, all drivers should run correctly at this point. An exception forms the driver for the graphic card. It has often to be installed manually.
  • Connect the computer to the Internet and activate Windows®. The activation is done automatically beginning with Windows® 8. Hold down the Windows® key and press Pause to verify the activation.
  • Install Reuschtools and its' license key.

2. Soft

It is time to install the required software. Here is a list that has proven itself in practice. Always make sure to select only components that are really needed.

  • Open Office
  • VLC media player to play DVDs and BluRays
  • Printer software

In addition, the following programs may be usefull for Windows® versions older than Windows® 8:

  • Adobe® Reader® to view and print PDF files.
  • Adobe® Flash® Player to watch streams.
  • Firefox, modernen websites sometimes dislike older versions of the Internet Explorer®.

3. Run

In the last step you should make all personal settings and the tuning.

  • Replace the toasts on the Start Menu with such that you need for your daily work.
  • Disable Windows® functions that are not needed. You can use TuneUp.cmd to do this. It is located in the Reuschtools\scrips\WinSetup folder.

Caution, avoid the World Wide Web before creating a backup. Even legitimate sites can install malware and cookies on your computer via on-screen advertising. If you have visited websites to download software or drivers, you should perform Install Restore. Make the desired settings and create a final backup which is guaranteed to be clean.

1.2.5 Why does Window® slow down over time?

A Windows® environment seems to be subject to a natural aging process. The operating system gets slowly and sometimes malfunctional.

  • Unnecessary software has been installed by the user or unattended (trojans, viruses, spyware). These programs run in the background and burden working memory and CPU.
  • Software has been uninstalled, but has left files or registry entrys.
  • Regular updates increased the mass of data that must be loaded into memory and managed by Windows®.

A well-configured Windows® system should start in less than a minute. Windows® 8 in 8 seconds after the hardware has been initialized. Shut down should be much faster.

A clean installation can provide better performance than a faster microprocessor would do. Install Backup preserves the installation. After Install Restore a computer is running as quickly and safely as on the first day.

1.2.6 Automatic Updates On or Off?

Experts seem to agree, automatic updates should allways be switched on. But the question must be allowed, if this is right in every case.

Benefits:

  • Known vulnerabilities get fixed as soon as an update is avaliabe.
  • Bugs in the software will be fixed automatically.

Disadvantages:

  • Automatic updates are a back doors. The provider of the software can take over complete control of the computer, read personal files and monitor the users behaviour.
  • Windows® is getting larger. An update being installed today may be obsolete two weeks later. Old updates often remain in the Windows® system.
  • The user is habited to regular update windows that appear suddenly. That is why he may click on OK if it was a Trojan Horse that wants to get full control of the computer this way.
  • Updates can cause errors that were not there before the update.

The argumentation is similar for antivirus software. Both, antivirus and automatic updates can not guarantee protection against unknown vulnerabilities.

If someone would decide against automatic updates he could use Install Restore to put the computer back to a clean state at regular intervals. If necessary, updates could be installed manually, and added to the previous backup with Install Backup.

1.2.7 How do I get multiple Windows® environments onto one drive?

Any Windows® version beginning with Windows® XP can installed side by side on the same partition. It does not matter whether it is a 32 or 64 bit version.

Vorteilhaft ist die Neuinstallation von relocated. Die Windows® Installationsdateien können dann auch vom Netzwerk gelesen werden.

Nicht immer kann Setup.exe von einem laufenden Windows® gestartet werden. Ein 64 Bit Windows® kann nicht mit einer 32 Bit Windows® Version installiert werden und umgekehrt. Das Windows® Installationsprogramm mag keine älteren Versionen, weshalb es besser ist, zuerst Windows® 7 und danach Windows® 8 zu installieren.

Lässt sich Setup.exe nicht von einem laufenden Windows® starten, kann der Rechner mit der Windows® Installations-DVD gebootet werden. Oder Sie starten Setup.exe mit einer Reuschtools Recovery Umgebung.

Vor einer Neuinstallation sollten eventuell vorhandene Zielordner gelöscht werden. Nutzen Sie dazu InstallClean.cmd, das sich im Ordner Reuschtools\Scrips\WinSetup befindet. Vor der Ausführung dieses Scrips sollten Dateien, die sich im alten Dokumente Ordner befinden, gesichert werden.

Manchmal funktioniert Setup.exe im Stammverzeichnis der Windows® Installations DVD nicht richtig. Nutzen Sie in diesem Fall Setup.exe aus dem Unterverzeichnis 'Sources'.

1.2.8 What does the log file tell us?

If a template is used, the logfile will only show changes since the last backup. A Private Backup log sector will be created for each generated Zip File.

The upper part of the log shows the command lines to automate Install Backup or to create a shortcut.

Log example:

RtCmd64 3.09    OK  Wednesday, May 7, 2014  9:44:55 PM
Install Backup      -o1 tf5=*HD\*ARCH\ tof5=*NET\*ARCH\ to=*RD\*ARCH\ to=*CD\*ARCH\
  
      link command  c_u -xp          rtcmd ib -o t=R:\*ARCH\run.ib
  schedule command  c_e.exe -hi      rtcmd ib -i t=R:\*ARCH\run.ib
    script command                   rtcmd ib -i t=R:\*ARCH\run.ib
       new archive  R:\RtArch\_PC\Win81_64\run.ib
          template  R:\RtArch\_PC\Win81_64\BasicE90.ib
              INFO  Bootstrap code has been read
analysing
       shadow copy  R:\

backup acl          R:\Windows\
          6791.805  mb
template            R:\RtArch\_PC\Win81_64\BasicE90.ib\data\_SYSTEM_.zip
             #      AppCompat\Programs\Amcache.hve
             *      bootrepair\Bootfiles\Boot\BCD.bak
             *      bootrepair\Start\BCD
             *      debug\PASSWD.LOG
                    .
                    .
                    .
Dataset             3941.537 mb

Harddisk      13+1  R:\RtArch\_PC\Win81_64\run.ib


SUCCESS!            Logtime 00.03.34.328

back | content | forward


Manual RT_3.99