In this series of articles, I'm going to explain how to build and manage SVS layers. The first article was how to take the registration key out of Office 2007. You can read it on here.

In this article I will explain to you how to capture a software program with SVS that needs a reboot. All articles in this series are by request. People always ask how to accomplish these difficult tasks.

Packaging Daemon Tools

Many requests I receive are about packaging software with a driver in it. It is difficult, but it can be done. I use a nice piece of freeware ( yes, you can download this on the internet for free) many of us use: Daemon Tools. The download is available at http://www.daemon-tools.cc It's a neat little tool and once you've used it you'll never want to be without it.

So first of all, I have my packaging machines ready to rumble. Windows XP without Office. You won't need Office for this. So when you have downloaded Daemon Tools, go to your packaging machine, and start SVS admin.

Follow all steps below:

• Click on File.
• Click on Create new layer.
• Click on install application.
• Name the package whatever you wish. I named it Daemon.
• Do a single program capture.
• Select the location where you placed the executable.

  I have mine located on the desktop with version 410-x86.

• Click Next and then Finish

  The installation of Daemon Tools 4.10 will start. You can choose different setup paths and everything, but I use the standard ones.

• Select Next
• Select "I Agree" to agree with the license terms.
• Now Windows likes a restart. If you do this, the capturing will stop, and you will encounter a error. So select Cancel
• Go to the layer, and De-activate the layer.
• Double click on the layer to see its files, and go to [WINDIR] system32\drivers, and copy the driver sptd.sys out of the layer into c:\windows\system32\drivers

The driver is not virtualized anymore. Now you are ready for step two.

Reboot your machine and follow the steps below.

• Start SVS admin, and go to file update existing layer.
• Update the layer you created with the initial installation.
• Start the install again, and now when you get the message to reboot, select YES.
• Reboot your machine.
• A screen will popup with the installation.

  DO NOT CLICK ON IT OR IN IT

• Start SVSadmin, and go to file, update layer. Do a global capture.
• Click Next and then finish to start the capture.
• Click Next in the installation wizard of daemon tools.
• Agree again with the license.
• Now you see a screen with four choices.
  1. Daemon tools core files. These are required.
  2. Daemon tools search bar (UNMARK THIS) (If you wish to use this, go to the bottom and read further to get this in.
  3. Desktop shortcuts
  4. Start menu shortcuts. Select what you wish to have.
• Select the path you want to use to install it in.
• Click Install
• Now you have finished the install. BUT DO NOT CLICK FINISH.
• There is a checkmark for Run Daemon Tools. Unmark it and click Finish
• Go to the taskbar, and click on the turning svs icon, and stop the capture.
• Go to the layer and mark Automatically start Layer.
• Reboot your machine.

Now you have one task left.

De-activate the layer. It will give an error message that there is a file open. Yes, one is. The driver will stay resident. Click yes, and it will close the driver for you.

Now go to c:\windows\system32\drivers, and delete the local, not virtualized sptd.sys.

The first time around you have to place the driver in the right place, because daemon tools install will need it to get to the second part of the installation.

This is only for those who want the toolbar

If you wish to have the toolbar inside the package, then you have to de-activate the layer and follow the steps below:

• Go to file update existing layer.
• Select the layer.
• Do a global capture.
• Start daemon tools.
• It will now ask you to install the toolbar.

Yes, you managed this and you build yourself a very difficult package. Congratulations!

Regards ErikW
http://www.dvs4sbc.com

Handling Office 2007 License Keys with SVS

SVS Packaging Best Practices, Part 3: Update Existing Layer