AppWave Studio FAQs

AppWave Studio FAQs

Note: For the latest versions of AppWave documents and for information that will help you install and upgrade, see the Embarcadero documentation website. Always make sure to consult the README for late breaking updates at http://docs.embarcadero.com/products/appwave.

Q: When mastering an App, what is the best location for installing an App?

A: The recommended location for installing the App is C:\application_name_version. Avoid installing in the default Program Files location as problems might occur when launching the App on a 64-bit system.

Q: When I try to master as App, I get an error message if I have one or more AppWave Apps running on my system. How do I resolve this error?

A: Before mastering an App in AppWave Browser you must ensure that no other Apps are currently running. This is necessary to avoid adding unwanted artifact files such as files, registry entries, and/or environment variables. These unwanted artifacts could cause recording failures.

To close the Apps currently running:

1. In the AppWave Browser, click Activity and all Apps currently running are displayed.
2. To stop an App, right-click the app icon and select Stop Application(s).

Q: When mastering an App, can I use folders such as My Documents?

A: Folders that point to a network location should be avoided. It is recommended that you set the network folder to a local folder.

Q: How do I know, if during mastering, extra services related to the App I am mastering are launched?

A: Sometimes, at the end of the mastering process, Studio attempts to shutdown any services it detects. But in some cases Studio cannot detect those services and you must shut them down manually before broadcasting the App.

You must be logged on as an administrator or a member of the Administrator Group in order to complete this procedure. If your computer is connected to a network, network policy settings might also prevent you from completing this procedure.

1. To start, stop, pause, resume, or restart a service, open Control Panel > Administrative Tools > Services.
2. In the details panel, right-click the service, and then click Start, Stop, Pause, Resume, or Restart.

• Important
  • If you stop, start, or restart a service, any dependent services are also affected.
  • Changing the default service settings might prevent key services from running correctly. It is especially important to use caution when changing the Startup Type and Log On, as settings of services that are configured to start automatically.
  • To configure startup parameters for a service, right-click the service, click Properties, and then type the parameters in Start parameters before you click Start. These settings are used only once and are not saved. (A backslash [\] is treated as an escape character; type two backslashes for each backslash in a parameter.)

Q: Can I master an App using a template without installing?

A: Yes, however the AApp needs to already be on the system and installed with all the default options. If the App is installed in the Program Files folder and has this path in the configuration files for its usage or as part of other required components such as Java, there may be problems running the app on 64-bit systems.

Q: How do I master an App on Windows 7 or Vista?

A: You must launch the AppWave Browser as an Administrator. To do this, close the AppWave Browser, if it is running, and open it again by right-clicking the AppWave Browser shortcut on your desktop and selecting Run as Administrator.

Q: Why do I get the following error message when working with registry keys in the Windows 7 OS: "Failed to launch the App. Error code: APM_E_APP_CONFIG_INSTALL_REGISTRY. Please contact your administrator for more information." What does this error indicate?

A: This error is generated when you are mastering an AApp on the Windows 7 OS and create registry keys under HKEY_CLASSES_ROOT or in one of the subdirectories of HKEY_CURRENT_USER, HKEY_LOCAL_MACHINE, and HKEY_USERS.

If the properties for the key you created are set to "All Applications" and "Permanently Replace Host Version", then the error message will be generated. The application is trying to add registry keys in a location where writing is not allowed on the current OS. You may either set the registry key to default properties OR run the app on a compatible OS.

Q: Are there some applications that will not work as a streamed App because of their product architecture?

A: There are two different types of architecture that will not work:

• Applications that must run as a Windows service. Because they start automatically as a service when you start Windows, they cannot run on a different machine.

• Applications that are configured to run against a database or other service that is installed on the same machine. An example would be an application that locally installs a database and the database connection is hard coded. If an application has the option of installing as a network client and can be configured to access a database on the network, that configuration is more likely to work as a Studio App.

Q: If I have installed and uninstalled AppWave Studio several times, how do I ensure a clean install?

A: It is recommended that you fully remove all the files and directories installed by AppWave. This ensures a clean starting place for your next install. The following files should be removed for the AppWave Studio uninstall:

Windows XP

• C:\Documents and Settings\<user>\Local Settings\Application Data\Embarcadero\AppWaveBrowser\plugins
• C:\Documents and Settings\<user>\AppWaveStudio\Output\

Note that the default Output folder path can be changed by the user.

Windows 7

• C:\Users\<user>\AppData\Local\Embarcadero\AppWaveBrowser\plugins\
• C:\Users\<user>\Embarcadero\AppWaveStudio\Output\

Note that this directory can be changed by the user.

AppWave

• Install directory = C:\Program Files (x86)\Embarcadero\AppWave
• Application repository (only if you want to delete existing binaries) = C:\ProgramData\Embarcadero AppWave\Products

The following files should be removed for the AppWave Browser uninstall:

Windows XP

• Install directory = C:\Documents and Settings\<username>\Local Settings\Application Data\Embarcadero\AppWaveBrowser
• Repository = C:\Documents and Settings\<username>\Local Settings\Application Data\Embarcadero\Product Repository
• Streaming Core additional locations:
  • C:\Documents and Settings\<username>Application Data\Embarcadero\Product Repository
  • C:\Documents and Settings\All Users\Application Data\Embarcadero\StreamingCore

Windows 7

• Install directory = C:\Users\<username>\AppData\Local\Embarcadero\AppWaveBrowser
• Repository = C:\Users\<username>\AppData\Local\Embarcadero\Product Repository
• Streaming Core additional locations:
  • C:\Users\<username>\AppData\Roaming\Embarcadero\Product Repository
  • C:\Users\All Users\Embarcadero\Product Repository
  • C:\Users\All Users\Embarcadero\StreamingCore

Q: What folders are created in AppWave Studio when mastering an App?

A: The created directories are listed below:

Win7

• C:\Users\<user>AppData\Local\Embarcadero\AppWaveBrowser\plugins\
• C:\Users\<user>\Embarcadero\AppWaveStudio\Output\

Note that this can be changed by the user.

Win XP

• C:\Documents and Settings\<user>\Local Settings\Application Data\Embarcadero\AppWaveBrowser\plugins
• C:\Documents and Settings\<user>\ AppWaveStudio\Output\

Note that this is the default Output folder path and can be changed by the user.

Q: What log files are generated and saved by AppWave Browser and Studio?

A: The AppWave logs are: aaserver.log; error.log, and info log. The paths for these logs are:

• C:\Documents and Settings\<user>\Local Settings\Application Data\Embarcadero
• C:\Documents and Settings\<user>\Local Settings\Application Data\Embarcadero\AppWaveBrowser
• C:\Program Files (x86)\Embarcadero\AppWave\2.0\logs

• Streaming core locations can be in a variety of places depending on the OS:
  • XP 32 bit - C:\Documents and Settings\<user>\Local Settings\Application Data\Embarcadero\Product Repository\StreamingCore
  • Vista 32 bit - C:\Users\<user>\AppData\Local\Embarcadero\Product Repository\StreamingCore\Log\StreamingCore.log
  • Win 7 32 bit - C:\ProgramData\Embarcadero\Product Repository\StreamingCore\Log
  • The following registry entry has the location:
    • HKEY_LOCAL_MACHINE\software\Embarcadero\StreamingCore\Settings\Logging

Note that you should set the hidden files and folders to visible in order to access the StreamingCore.log:

1. On the current folder, select Tools > Folder Options...
2. In the Folder Option window, select Show hidden files and folders as shown below.

Q: What variables can I use that will be replaced with the correct path when the App is loaded on a machine?

A: Please refer to the Variable Path Substitution lists in the AppWave Studio User Guide's Appendix. The topic is Predefined Virtual Folders.

Q: I get an error message if I try to broadcast an App that has the same name, version, and edition of an existing App. How do I correct this problem?

A: Before you can complete the mastering process, you must contact your Administrator to delete the existing App. When you click OK, you are returned to the Broadcast page.

Q: What are the required mastering criteria of an App?

A: The mastering criteria are listed below:

1. No beta versions of applications are accepted. The only exception is if the beta version is the only version ever released, for example WinZip.
2. All Apps must be mastered using the Prefetch option.
3. The vendor must provide the .msi installer of the application being mastered. If the application has an installer with any other file extension, then the vendor must convert that installer into an unattended .msi installer and provide that one. The vendor has the obligation to check that the converted installer works properly on Windows XP, Windows 7 32-bit and Windows 7 64-bit operating systems.
4. The App mastering process must always be done with the original installer of the application and not with the converted one.

Q: How do I use the prefetch option when mastering an AApp?

A: The steps for using the prefetch option are outlined below:

• Open the Broadcast page. Notice that a Task appears at the bottom of the screen. This task indicates that "in order to record the launch of the application for faster start-up time, you need to master the App from the Test tab before broadcasting. Once the launch data was recorded, remastering before broadcast will not remove this information." Only some key blocks of application data from AppWave are necessary for the application to launch and perform basic functions.

Note: There is also an indicator next to the Broadcast step showing that there is a task that needs to be fixed.

• Click Fix and a dialog appears instructing you on how to record prefetch information. Prefetch is the process of streaming application blocks in anticipation that those blocks are needed by an application.

• Return to the Test page and click Master. The Master dialog appears.
• Select "Record the launch of the application for faster start-up time" and click Launch. This is to ensure that the application is completely loaded.

• Click Finished in the Master dialog and then click Next to advance to the Broadcast page.
• Make sure the option to Always remaster projects before broadcasting to the AppWave is selected.
• Click Broadcast and save the changes to your file. The Broadcast dialog appears where you can track the remastering and broadcast of your App with the prefetch recorded information included.
• Your App is now mastered with the prefetch information included.

Q: How do I master a DOS App so that is launched by the AppWave Browser on Windows 64-bit PC?

A: If the application is an actual MS-DOS executable, then it is theoretically possible via DOSBox. Include both DOSBox and the DOS executable that you need in the App. As a launch command set the DOSBox executable that takes as parameter your DOS executable.

If the App is not able to find Dosbox’s DLL, move those two to the same folder where TP7 was. The App is able to work in fullscreen mode as well. This was tested on Win 7 (32 and 64-bit) and Win XP (32 and 64-bit) as well.

Q: How do I master Microsoft Project and Visio on XP?

A: With AppWave you can master complex applications such as Microsoft Project or Visio. This mastering process provides a deep level of integration with the operating environment so common components are available and the Windows UI is exposed (i.e., executables, right-click menu extensions, and file associations).

Complete the following steps to successfully master these Apps:

A: Prerequisites

1. The latest Office PADE plugin and templates are provided by Embarcadero via Public update.
2. Mastering on Win XP requires the following applications be installed:
   • Windows Search 4.0: http://www.microsoft.com/download/en/details.aspx?id=23
   • Microsoft XML Paper Specification Essentials Pack: http://www.microsoft.com/download/en/details.aspx?displaying=en&displaylang=en&id=11816
   • .Net 3.5 SP1 or .NET 3.0
   • Microsoft Visual C++ 2005 Service Pack 1 Redistributable: http://www.microsoft.com/download/en/details.aspx?id=14431
   • Microsoft Visual C++ 2008 SP1 Redistributable Package: http://www.microsoft.com/download/en/details.aspx?id=5582
   • Windows Update service must be Disabled.
3. Download the installer from:
   • Microsoft Project (en_project_standard_2010_with_sp1_x86_x64_dvd_730334.iso): https://msdn.microsoft.com/en-us/subscriptions/securedownloads/default.aspx#searchTerm=&ProductFamilyId=386&Languages=en&PageSize=10&PageIndex=0
   • Microsoft Visio: (en_visio_2010_with_sp1_x86_x64_dvd_730325.iso): https://msdn.microsoft.com/en-us/subscriptions/securedownloads/default.aspx#searchTerm=&ProductFamilyId=388&Languages=en&PageSize=10&PageIndex=0
4. Use the MSP file provided by Embarcadero:
   • Need to extract the setup. For example, for Project and Visio run the Command Prompt: en_project_professional_2010_x86_515560.exe /extract:c:\OfficeSetup OR en_visio_2010_x86_516534.exe/extract:c:\OfficeSetup
     • Note: If the installer is an .iso or .bin file, mount and copy the files in a folder.
   • Copy the MSP file to Updates Folder in the extracted install. MSP files can be found in: http://altd.embarcadero.com/download/appwave2/apps/3rdparty/03262012/MSP.zip
     • Note: The MSP file is the Office administrative update file that updates the MSI file and copies files to the Administrative Installation Point. If you have more than one Office updte to install (more than one MSP file), you have to install them separately. You can't "chain" MSP file installs.
   • The .msp file you use depends on the Edition you are about to master:
     • If you are mastering the Project 2010 Standard Edition, copy the AppWave_Project2010Standard.MSP in the updated folder: E:\x86\Updates or c:\OfficeSetup\Updates.
     • If you are mastering Project 2010 Professional Edition, copy the AppWave_Project2010Pro.MSP in the updated folder: E:\x86\Updates or c:\OfficeSetup\Updates.
     • If you are mastering Visio 2010 Standard, Professional & Premium Editions, copy the AppWave_Visio2010Pro.MSP in the updated folder: E:\x86\Updates or c:\OfficeSetup\Updates.
       • Note: The .MSP file will make modifications in the config.xml and the application will install in a custom path, e.g., c:\Project2010.

B. Start Mastering:
Using the template, start a Record on Install process, and install in a custom path location. The MSP file from Step 4 changes the install path to a custom location and the user will no longer be able to choose from the Default install location and Custom location.

• Note: Make sure you uncheck the Attempt to automatically activate my product online option.

C. Launch the .app:
To launch the .app the user must have the same software installed as in Step A.2.