<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>EditVoicepack User's Guide</title>
<meta content="http://schemas.microsoft.com/intellisense/ie5" name="vs_targetSchema">
<meta content="Microsoft Visual Studio .NET 7.1" name="GENERATOR">
<meta content="VisualStudio.HTML" name="ProgId">
<meta content="Microsoft Visual Studio .NET 7.1" name="Originator">
<LINK title="default" href="main.css" type="text/css" rel="stylesheet">
</head>
<body onload="OnLoad()">
<script language="javascript">
function OnLoad()
{
if (window.location.href.toLowerCase().indexOf("http://www.editvoicepack.com") == 0)
{
var onlineRef = document.getElementById('OnlineReference');
onlineRef.style.display = "none";
}
var nodes = document.getElementsByTagName('body')[0].childNodes;
var tocList = new Array();
var tocHtml = "";
var createLinks = new Array();
var whiteSpaceRemover = /\s+/g;
for (var i = 0; i < nodes.length; i++)
{
var isTocEntry = true;
var nodeName = nodes[i].nodeName.toLowerCase();
if (nodeName.length != 2) isTocEntry = false;
if (nodeName.charAt(0) != "h") isTocEntry = false;
if (nodeName.charAt(1) != "2" && nodeName.charAt(1) != "3") isTocEntry = false;
if (isTocEntry && nodes[i].innerHTML.toLowerCase() == "table of content") isTocEntry = false;
if (isTocEntry)
{
var marginStyle = "margin-left:0;";
if (nodeName.charAt(1) == 3) marginStyle = "margin-left:16;";
var tocLinkName = "ToC" + tocList.length;
//alert(nodes[i].innerHtml);
tocList.push(nodes[i].innerHTML.replace(whiteSpaceRemover, " "));
tocHtml += "<div style='" + marginStyle + "'>" + nodes[i].innerHTML + "</div>";
nodes[i].innerHTML = "<a name='" + tocLinkName + "'></a>" + nodes[i].innerHTML;
}
else createLinks.push(nodes[i]);
}
var tocSpan = document.getElementById("TableOfContent");
tocSpan.innerHTML = tocHtml;
for (var i = 0; i < createLinks.length; i++)
{
if (createLinks[i].innerHTML)
{
var innerHTML = createLinks[i].innerHTML.replace(whiteSpaceRemover, " ");
var insertPosition = new Array();
var insertLink = new Array();
var insertTextLength = new Array();
for (var j = 0; j < tocList.length; j++)
{
var tocHTML = tocList[j];
var index = 0;
while (index >= 0)
{
index = innerHTML.indexOf(tocHTML, index);
if (index >= 0)
{
insertPosition.push(index);
insertLink.push("ToC" + j);
insertTextLength.push(tocHTML.length);
index += tocHTML.length;
}
}
}
for (var j = insertPosition.length - 1; j >= 0; j--)
{
var endPos = insertPosition[j] + insertTextLength[j];
innerHTML = innerHTML.substr(0, endPos) + "</a>" + innerHTML.substr(endPos);
var startPos = insertPosition[j];
innerHTML = innerHTML.substr(0, startPos) + "<a href='#" + insertLink[j] + "'>" + innerHTML.substr(startPos)
}
if (insertPosition.length > 0) createLinks[i].innerHTML = innerHTML;
}
}
document.getElementById('TableOfContentHeader').style.display = "inline";
}
</script>
<H1 style="MARGIN-BOTTOM: 0px">EditVoicepack User's Guide</H1>
<P style="MARGIN-TOP: 0px" align="right">
Version 3.1 - Released 2004-10-17<BR>
For <EM>Microsoft Flight Simulator 2004: A Century of Flight</EM></P>
<P class="OnlineReference" id="OnlineReference">Please read the <a href="http://www.editvoicepack.com/DeepLink/dl.aspx?page=evpReadme31">
online version</a> of this document to ensure you have the latest version.</P>
<H3 style="DISPLAY: none" id='TableOfContentHeader'>Table of content</H3>
<span id="TableOfContent"></span>
<H2>What is EditVoicepack</H2>
<P>EditVoicepack offers a simple interface to edit the file containing the ATC
communication used in <EM>Microsoft Flight Simulator 2004: A Century of Flight</EM>.
It is possible to change the phraseology as well as add airline callsigns,
airports, and aircraft types. EditVoicepack already contains thousands of ready
made entries; and is able to download new entries from a central server. It
also allows you to accelerate the existing voices for a more realistic
experience and better handling of traffic dense environments.</P>
<H2>Installing EditVoicepack</H2>
<H3>System Requirements</H3>
<P>EditVoicepack can be installed on any system supporting the .NET Framework
version 1.1 and <EM>Microsoft Flight Simulator 2004: A Century of Flight. </EM>This
includes Windows 98, ME, 2000, XP, and 2003.</P>
<H3>First time users</H3>
<P>To install EditVoicepack run Setup.exe. If you do not have the .NET Framework
version 1.1 installed you will be directed to a download page at Microsoft. The
recommended .NET Framework package for EditVoicepack is <EM>.NET Framework Version
1.1 <EM>Redistributable</EM></EM>. After installing the .NET Framework it
is recommended to perform a Windows Update to ensure you have the latest
security patches for the framework installed.</P>
<P class="info">Please notice that newer versions of the .NET Framework might not
be able to run EditVoicepack (it will then allow you to install both version
1.1 and the newer version).</P>
<H3>Upgrading from version 3.0</H3>
<OL>
<LI>
If you have made or imported any custom modifications it is recommended you
make a backup from version 3.0 before installing version 3.1.<BR>
This backup will normally not be needed unless a problem occurs doing
installation.
<LI>
Run Setup.EXE and let it uninstall the existing version.
<LI>
When you start EditVoicepack 3.1 the first time, select “Yes” to preserve the
custom modifications and settings you had in version 3.0. If you select “No”
EditVoicepack 3.1 will use the default settings.</LI></OL>
<P>Please notice that not all custom modifications for <EM>Microsoft Flight Simulator
2002</EM> are compatible with <EM>Microsoft Flight Simulator 2004: A Century of
Flight</EM> and you might have to delete some of them. You will be notified
of any problems when you run Update Voicepack.</P>
<H3>Upgrading from version 2.x</H3>
<OL>
<LI>
Install EditVoicepack to a new directory as outlined under “First time users”.
<LI>
Create a backup from version 2.x
<LI>
Restore the backup into version 3.1
<LI>
You can now delete version 2.x, unless you want to use it for <EM>Microsoft Flight
Simulator 2002</EM>.</LI></OL>
<H3>Upgrading from version 1.x</H3>
<OL>
<LI>
Export your custom modifications from EditVoicepack 1.x
<LI>
Install EditVoicepack to a new directory as outlined under “First time users”.
<LI>
Import the custom modifications into EditVoicepack 3.1</LI></OL>
<H3>Uninstalling EditVoicepack</H3>
<P>If you want to uninstall EditVoicepack simply use the Add or Remove Programs
feature of the Control Panel (see Windows help for details).</P>
<H2>Running EditVoicepack the first time</H2>
<P>After installation the following steps must be performed to apply the voicepack
modifications to the <EM>Microsoft Flight Simulator 2004: A Century of Flight</EM>
data files:</P>
<OL>
<LI>
Close <EM>Microsoft Flight Simulator 2004: A Century of Flight</EM>
if you have it running.
<LI>
Run EditVoicepack (the installer placed an icon in your start menu).
<LI>
If a dialog opens informing you of new updates, you can install them at this
time (EditVoicepack will attempt to connect to a server at this stage to
determine if any updates are available, so personal firewalls or dial-up
dialogs might appear at this stage).
<LI>
Select "Update Voicepack" from the "File" menu. You can change the settings in
the dialog or simply go with the default.
<LI>
You are done - close EditVoicepack by selecting "Exit" from the "File" menu.<BR>
If you installed any updates at step 3 or changed the settings under step 4,
you should save when prompted.</LI></OL>
<P>You might want to read the sections “Making callsigns selectable in Flight
Simulator” and “Locate aircraft configuration errors” to take full advantage of
EditVoicepack.</P>
<P>
<H2>Keeping EditVoicepack updated</H2>
<P>EditVoicepack can automatically download modifications from a central server.
This means that you will not have to search various Flight Simulator download
sites for additional modifications – they are all delivered directly to your
computer. EditVoicepack will automatically attempt to download updates from the
server each time you start it. If an update is available a dialog will open
allowing you to install the update. You will also be notified of new program
versions this way. You can manually check for updates using the functions
available in the about box. In the about box you can also disable the automatic
check at startup if you prefer to have full control over when the updates are
downloaded.</P>
<P>If your Flight Simulator system is not connected to the Internet you can visit
the <A href="http://www.editvoicepack.com">EditVoicepack homepage</A> to
download an offline update package.</P>
<P class="info">You must run Update Voicepack before the updates are available in
Flight Simulator. Saving is not enough as it only saves the data file
EditVoicepack stores the modifications in. Update Voicepack is the only
function that applies the modifications to Flight Simulator.</P>
<P>If you look at the tree to the left you will find all the modifications
controlled though the EditVoicepack server under the “Standard Modifications”
branch. You can not delete or change these modifications, but you can exclude
them so they will not be written to Flight Simulator (see Determining which
modifications to include).</P>
<H2>Determining which modifications to include</H2>
<P>When you run Update Voicepack you can select which regions you want to include
modifications for. This should be sufficient for most users, but in some
situations it can be desirable to control inclusion or exclusion of groups of
modifications, or even a single modification. This is done by selecting the
checkboxes in the tree view to the left. Most checkboxes have three states:
Explicit Included (white with a green checkmark), Explicit Excluded (white
without any checkmark), or Default (gray with or without a green checkmark).</P>
<P>Notice a single modification can be inserted several places in the tree.</P>
<P>If a checkbox is set to Default, it will be included if any of its direct parent
nodes in the tree are included (either because it is explicit included or if it
is included by default as well).</P>
<P class="info">The presence of a green checkmark always indicates the node is
included while the lack off a green checkbox will indicate the node is
excluded.</P>
<H2>Creating modifications</H2>
<P>Creating your own modifications is fairly simple task once you get used to it.
Please complete the tutorial
outlining the process with screenshots before</P>
<H3>Creating a new callsign</H3>
<P>This is covered by the tutorial.</P>
<H3>Creating a new airport</H3>
<P>There are two different types of modifications for airports: ICAO and Agent. The
ICAO modification is used when ATC refers to the airport itself – for example
as destination in an IFR clearance or when it is used to determine the position
of the aircraft. The Agent code is used when communicating with a specific
radio service (clearance, tower, ground, approach, or departure). While ICAO
modifications can simply be added and will work right away Agent modifications
require a matching agent in the Airport Facilities Data (typically created with
AFCAD).</P>
<P>In most cases it is enough to create an ICAO modification as EditVoicepack
automatically will write an agent modification. The agent will use the phrase
as identifier, meaning the Com Frequency Name in AFCAD must match the phrase in
EditVoicepack to work. Agent modifications are typically only created if you
wish to change an existing entry in the default Microsoft voicepack.</P>
<H3>Creating a new aircraft</H3>
<P>In Flight Simulator aircrafts are typically identified as a combination of a
manufacturer (for example Airbus) and a model (for example 340). Please see
“Locate aircraft configuration errors” for details on how the aircraft type and
model are specified in the aircrafts configuration files.</P>
<H3>Creating new Phraseology</H3>
<P>The phraseology modifications allow you to change the sentences spoken by ATC
and pilots. Notice that you can only change existing phrases – you can not
insert new procedures in the ATC procedures. It is for example not possible to
insert a phrase for requesting pushback – as there is no pushback sentence to
replace. It is not possible to change the numbers spoken by ATC either, and
hence it is not possible to change altimeter pressure to be given in millibar.</P>
<P>Initially phrases are created as all other modifications, except you can insert
markers where other sound bits will be inserted when ATC places the
modification. You insert the positions in the phrase by enclosing a keyword in
<> brackets. Try typing “<” (without the double quotes) in the filter
to see samples of this in the default Flight Simulator voicepack. This will
also give you an idea which identifiers you can override as well as which
keywords you can use in the markers. The Voicepack SDK from Microsoft can
provide further details on possible identifiers and keywords.</P>
<P>Each marker in the phrase must be matched by a marker with the same name in the
wave file. Right click the wave file display in the Markers section (above the
sound segments) to insert a marker in the wave file. Select the marker by
clicking it to assign the name to it. Notice that markers are copied with the
sound segments, so it can be an advantage to add the markers to the first voice
before copying the segments.</P>
<H2>Correcting a default Flight Simulator entry</H2>
<P>You must be able to create modifications before proceeding with this section.</P>
<P>Flight Simulator allows up to 16 variations of each entry in the voicepacks (so
16 identical identifiers). Each variation will be assigned a unique number.
This is used to make ATC less monotone. For example when flight Cimber 123 is
handed off to the tower on frequency 121.0 the pilot can respond “Going to
121.0, Cimber 123”, “121.0 for Cimber 123”, or simply “121.0, Cimber 123”. When
looking at existing entries in the default Flight Simulator voicepack using the
filter display of EditVoicepack you will notice that some of the identifiers
are followed by a number in brackets. This is the identifier. If no number is
present only one variation exist for the specific identifier.</P>
<P>The default behavior of EditVoicepack is to add the modifications as additional
variations in case the identifier is already present in the default Flight
Simulator voicepack. This means pilots and ATC will randomly choose between the
default entry in Flight Simulator and your modification. To make sure your
modification replaces the default Flight Simulator entry select “Force
Variation” and indicate the variation to replace.</P>
<H2>Uploading to the server</H2>
<P>One of the strong points of EditVoicepack is that you do not have to create all
the modifications you would like to the voicepack, neither do you have to
search various sites to find them. EditVoicepack lets the users upload their
modifications to the server, where they will be automatically distributed to
all other users of EditVoicepack.</P>
<P>Please notice that there are very strict requirements to the format used in the
modification as well as doing the upload. Please check the upload tutorial for details before attempting to upload a modification.</P>
<P>To upload your modification, right click it and select “Send to server..." or
“Update Server..." (only one will be present, depending on which node you right
clicked). A wizard will now open and guide you though the process. After you
have uploaded the update, you can visit <A href="http://www.editvoicepack.com">http://www.editvoicepack.com</A>
to track the review process of the modification.</P>
<P>Besides your own modifications, you can also upload requests to have the
standard modifications changed (as before, right click and select “Send to
server...”. It is however only possible to request that the modification is
deleted or to change the groups the modification is assigned to. If you would
like to make further changes (for example improving the sounds), please copy
the modification first (right click it and select “Copy”). You can now make
your changes in the new modification and upload it to the server.</P>
<P>If you upload a new callsign it will automatically be moved from the custom
section of EditVoicepack to the standard section. Any changes you have done
after the modification was uploaded will be lost. In case the modification was
changed by the reviewer, you will loose your original data as well. If you want
to preserve your data, please export the modification after uploading it to the
server. If you are changing an existing modification, only the copy in your
standard section will be updated, the copy in the custom section will remain
unmodified, and you should delete it as soon as your modification has been
accepted</P>
<P>The server tracking the uploaded modifications uses the Identifier to check if
you are updating an existing modification. If the identifier needs to be
changed, the server can not match the uploaded modification with the existing
modification. Please use the comments field to specify the original Identifier
that should be deleted. If the reviewer still fails to delete the wrong
identifier, you can upload a request to have it deleted after your new
identifier has been accepted.</P>
<H2>Making callsigns selectable in Flight Simulator</H2>
<P>When selecting an aircraft in Flight Simulator you can also change the callsign
though a dropdown list. The entries available in the list are found in a file
named “airlines.cfg” in the “aircraft” folder of <EM>Microsoft Flight Simulator
2004: A Century of Flight</EM>. Notice that a callsign do not need to be in
this file for ATC to pronounce it (ATC will work fine if the file is completely
missing) neither will ATC necessarily be able to pronounce a callsign simply
because it is listed “airlines.cfg”.</P>
<P>If you want to be able to be able to select all available callsigns run “Update
airlines.cfg” from the “Tools” menu each time you run “Update Voicepack”.</P>
<H2>Locate aircraft configuration errors</H2>
<P>ATC use settings in the aircraft.cfg files found in the folder of each aircraft
to determine the manufacturer and type of the aircraft, as well as the callsign
to use. Please consult the Microsoft SDK’s for details on the general format of
the aircraft.cfg file (information can probably also be found on various Flight
Simulator web sites).</P>
<P>Each line listed below must be set to match an existing identifier of the
specified type (callsign, aircraft manufacturer, or aircraft type) – either
from the default voicepack or a modification added by EditVoicepack.</P>
<P>You can use the function “View Missing…” from the “Tools” menu to locate
aircraft.cfg files referring to non-existing identifiers. Please remember that
a missing entry do not necessarily mean you should immediately download or
create a modification – it could as well indicate the aircraft.cfg file is
wrong and can simply be changed.</P>
<P>Under the [General] section of the aircraft.cfg file you should find two lines
related to ATC:</P>
<UL>
<LI>
atc_type<BR>
This is the Aircraft Manufacturer. Unfortunately Microsoft where not consistent
between the ATC and aircraft system, hence “type” refers to two different
things. EditVoicepack follows the definition used in the ATC system.<BR>
Notice that deleting this line (or leaving the setting empty) will result in
ATC using “Experimental”. If you want to ensure ATC does not include a
manufacturer (as the manufacturer is included in some aircraft types in the
default voicepack) set it to a non-existing identifier (for example “silent”).
<LI>
atc_model<BR>
This is the Aircraft Model in EditVoicepack.</LI></UL>
<P>For each livery (or model) entry you will find four lines related to ATC:</P>
<UL>
<LI>
atc_id<BR>
This is the registration number and will be used if no flight number is
selected (for user aircrafts) or if specified in the flight plan (for AI
aircrafts)
<LI>
atc_airline<BR>
This is the Callsign in EditVoicepack
<LI>
atc_flight_number<BR>
The flight number is used in combination with the callsign. If the flight
number isn’t specified ATC will refer to a user aircraft by the registration
number. This entry is ignored for AI aircraft as the flight number is specified
in the flight plan.
<LI>
atc_heavy<BR>
If set to 1 “Heavy” will be appended to the callsign.</LI></UL>
<H2>Importing and exporting modifications</H2>
<P>While the automatic update will be sufficient for most users some will have the
need to share specific callsigns not accepted on the official server (for
example unofficial callsigns used in real life but not recognized by ICAO). You
can export a modification to a file by right clicking the modification in the
tree to the left and the selecting “Export”.</P>
<P>To import a modification select “Import” from the “File” menu. Please read the
warning dialog displayed the first time you select import. Please be very
careful what you import. A bad modification can render EditVoicepack unstable
and force you to restore a backup of the data file loosing any changes you made
after the backup.</P>
<H2>Creating and restoring a backup</H2>
<P>You can use the backup functionality to ensure you do not loose any custom
modifications or inclusion settings. Select “Create Backup” from the “File”
menu to create a backup. Select “Restore Backup” to restore the backup into
EditVoicepack. Notice that restoring the backup will also affect the
modifications controlled by the EditVoicepack server, and a new update from the
EditVoicepack server is most likely needed to bring them up to date.</P>
<H2>Troubleshooting</H2>
<H3>Which files does EditVoicepack modify?</H3>
<P>EditVoicepack only modifies two files in the <I>Microsoft Flight Simulator: A
Century of Flight</I> directory. One is airlines.cfg (see “Making callsigns
selectable in Flight Simulator” for details).</P>
<P>The other (and more important) file modified is named <I>usenglishbig.gvp</I> and
contains all spoken language used by the ATC, as well as the text displayed in
the ATC window. This file can be found in the <EM>Sound</EM> directory of <I>Microsoft
Flight Simulator: A Century of Flight</I> In case you selected the compact
installation of <I>Microsoft Flight Simulator: A Century of Flight</I>, the
file might be called <I>usenglishsmall.gvp</I>. Localized (translated) versions
of <I>Microsoft Flight Simulator: A Century of Flight</I> will have different
file names. EditVoicepack is designed to recognize the files in any language;
however it has mainly been tested on the English version.</P>
<P>If you do not use the accelerated voicepack <EM>usenglishsmall.gvp</EM> will be
modified directly. If you use the accelerated voicepack the file will be
renamed to <EM>USEnglishBig.gvp.evpOrg</EM> and a new file named <EM>Evp_Accelerated.gvp</EM>
will be created.</P>
<H3>Will EditVoicepack work with additional or changed voicepacks?</H3>
<P>No, EditVoicepack will only work with the unmodified default voicepacks supplied
with <I>Microsoft Flight Simulator: A Century of Flight</I>. If you have
manually changed the voicepack using the Microsoft SDK (or any other mean than
EditVoicepack) can give one of the following problems:
</P>
<UL>
<LI>
EditVoicepack might refuse to load
<LI>
EditVoicepack might not be able to complete Update Voicepack
<LI>
Update Voicepack might complete, but some of the modifications no longer
produce the intended result.</LI></UL>
<P>If this happens, please follow the instructions in the section “EditVoicepack
won’t start (Microsoft Voicepack damaged)”.
</P>
<H3>I can no longer select a reply to ATC instructions
</H3>
<P>This problem will typically occur if you have applied or removed voicepak
acceleration. Please chose Settings/ATC in Flight Simulator and ensure you have
a pilot voice assigned.
</P>
<H3>Some of the nodes in the tree on the left are colored red</H3>
<P>This indicates a problem with one or more modifications. Drill down the tree
until you locate the problematic modification (following the red nodes in the
tree). When you select it, it will display a red text below the Author field
where you can see what the problem. If more than one error exists the text will
change every few seconds. Correct the error and the color will change back to
black. In a few cases where you do not want to make any changes you can ignore
the error (press the Ignore Errors button and set a checkmark for the errors
you would like to ignore).
</P>
<H3>I can’t select the new callsigns in Flight Simulator?
</H3>
<P>Most likely you did not update airlines.cfg. Please see “Making callsigns
selectable in Flight Simulator”.
</P>
<H3>I can’t hear the new modifications I added
</H3>
<P>First of all ensure you did run Update Voicepack whenever you change anything in
EditVoicepack. If you do not run Update Voicepack the Flight Simulator file
containing the wave files used by ATC will not be changed. Secondly please
ensure all voices have a sound segment defined. Finally check that you do not
have a copy of the gvp file located in the Sound directory (some people do this
to make a backup of the original file not realizing that Flight Simulator will
still load it even though the name is changed).
</P>
<H3>My plane is referred to by registration number instead of callsign.
</H3>
<P>Please ensure you have a flight number assigned.
</P>
<H3>AI traffic is referred to by registration number instead of callsign.
</H3>
<P>This is due to a setting in the flight plan used by the AI plane. Please refer
to the documentation of the utility you use to create or install the flight
plans.
</P>
<H3>ATC says “Fokker Fokker Jet” or similar duplicates.
</H3>
<P>For unknown reasons Microsoft included the manufacturer in the wave file for
some of the aircraft model entries. Please see “Locate aircraft configuration
errors” for a solution to this problem.</P>
<H3>ATC calls my Airbus 319 an A320, my Beech 1900D a Beech 1900, etc</H3>
<P>Basically it does this because nobody cares about the exact model of your plane
(nope, the serial number and your shoe size should not be included when you
contact ATC either). The type used must give some ideas of the capabilities of
the plane as well as visual appearance. Are these two largely identical it is
not really relevant which specific aircraft model it is.</P>
<H3>The changes I make in aircraft.cfg are ignored
</H3>
<P>Changes you make in the user interface of flight simulator (typically changing
callsign) are not written to the aircraft.cfg file, but to a user specific file
in C:\Documents and Settings\<username>\Application
Data\Microsoft\FS9\AIRCRAFT (this is the location on Windows XP and it will
most likely be different on Windows 98/ME - in this case you can either search
for the files, or upgrade to XP - needles to say I recommend upgrading to XP).
</P>
<P>This is done as a modern computer is a multi-user system, and several people
must be able to run the same application using different settings.
</P>
<H3>EditVoicepack won’t start (Microsoft Voicepack damaged)</H3>
<P>Typically this happens when the voicepack files of <EM>Microsoft Flight Simulator
2004: A Century of Flight</EM> has been changed by another program than
EditVoicepack (like MyTraffic) but it can also happen in a few other
situations.</P>
<P>Please restore the original file from your <I>Microsoft Flight Simulator 2004: A
Century of Flight</I> CD number 2. The file is inside the file
"MSGame4.cab" for the 10 voice setup, and inside the "MSGame5.cab" file for the
three voice setup. Copy the file to the Sound directory under the Flight
Simulator directory. In case the <EM>Sound</EM> directory contains files named <EM>*.evpOrg</EM>
or <EM>Evp_Accelerated.gvp</EM> they should be deleted.</P>
<H3>EditVoicepack won’t start (Missing registry key)</H3>
<P>When you install Flight Simulator a registry key is created pointing to the
location <I>Microsoft Flight Simulator 2004: A Century of Flight</I> is
installed. If you move <I>Microsoft Flight Simulator 2004: A Century of Flight</I>
to another directory you should update the registry key to reflect the new
location. If you are not comfortable editing the registry you should follow the
following procedure:</P>
<OL>
<LI>
Rename the directory you installed <EM>Microsoft Flight Simulator 2004: A Century
of Flight</EM>
in (the name does not matter)
<LI>
Install <EM>Microsoft Flight Simulator 2004: A Century of Flight</EM>
in the intended location
<LI>
Delete the directory of the newly installed <EM>Microsoft Flight Simulator 2004: A
Century of Flight</EM>
<LI>
Rename the directory from step 1 back to the intended name</LI></OL>
<H3>EditVoicepack won't start (Unhandled Exception)</H3>
<P>This can be a serious problem and I can't provide a bullet proof solution. I
recommend following the following procedure:</P>
<OL>
<LI>
Uninstall EditVoicepack
<LI>
Uninstall the .NET Framework version 1.1
<LI>
Reboot
<LI>
Install the .NET Framework version 1.1
<LI>
Run Windows Update - reboot if required
<LI>
Install EditVoicepack</LI></OL>
<P>If you haven't done so already, installing the latest service pack for Windows
might also solve the problem.</P>
<H2>Distribution</H2>
<P>Beta versions of EditVoicepack can not be distributed to any site without
permission (please see feedback section for contact information). A beta
version will have the word Beta after the version number at the top of this
file - the word Beta will not be present in the software itself - it is only
this readme file that can be used to determine if a package is a beta version.</P>
<P>Release versions can be freely distributed on any media (online or CD etc) as
long as the package is not modified in any way, and no payment is directly
required for the file. A reasonable indirect payment (for example a fee for
fast access to a file library, or payment for a magazine containing the program
on a cover CD) is acceptable. If you have any questions, please contact me on <A href="mailto:[email protected]">
[email protected]</A>. If you intent to distribute EditVoicepack on a
CD please contact me - I might be able to supply an installable version
containing the latest updates as well as the .NET Framework.</P>
<P>EditVoicepack can be bundled with commercial products, as long as I receive a
copy of the finished product - please contact me for details. Commercial addon
authors that recommends users to use EditVoicepack with their products but do
not include EditVoicepack directly with their product (download or other form)
are requested - but not required - to provide me with a free version as well.</P>
<H2>Conditions of Use</H2>
<P>This software is provided "as is", and usage of it is the responsibility of the
user - I accept no responsibility for any damage this program might course.
</P>
<H2>Feedback</H2>
<P>If you have constructive criticism or any other form of feedback, please send me
an email on <A href="mailto:[email protected]">[email protected]</A>.
Please notice any email mentioning missing or low quality callsigns, will be
ignored - most of the callsigns shipped with this package can easily be
improved - it just takes more time than the author had available. Use the build
in functionality to send an improved or additional callsign instead.</P>
<H6>Copyright © 2002-2004 Lars Mшllebjerg, All rights reserved.</H6>
</body>
</html>