AddEditFileToTransferDialog.1=File to transfer\:

AddEditFileToTransferDialog.10=No target path specified

AddEditFileToTransferDialog.11=All Files

AddEditFileToTransferDialog.12=Note\: Target file path has no extension

AddEditFileToTransferDialog.2=The absolute path on your PC of the file to transfer to the phone

AddEditFileToTransferDialog.3=Browse...

AddEditFileToTransferDialog.4=Select file to transfer

AddEditFileToTransferDialog.5=Target path\:

AddEditFileToTransferDialog.6=The directory on the phone to download the file to

AddEditFileToTransferDialog.7=File to transfer does not exist

AddEditFileToTransferDialog.8=No file to transfer specified

AddEditFileToTransferDialog.9=Invalid target path specified

AttachMainTab.NoConnectionError=A valid remote connection must be selected

ChooseProcessDialog.IDLabel=ID

ChooseProcessDialog.Message=Choose a process to attach

ChooseProcessDialog.NameLabel=Name

ChooseProcessDialog.Title=Attach to Process

DebuggerTab.0=Symbolics loading

DebuggerTab.1=Symbolics are what the debugger needs in order to debug an executable.  The debugger will have symbolics for the executable built by the project.  This let's you control what the debugger does with other dlls that get loaded by the emulator.

DebuggerTab.10=Create a console view to display the output of the executable being debugged.  This will contain RDebug\:\:Print's

DebuggerTab.11=View Windows system messages

DebuggerTab.12=Create a console view to display debug related messages from Windows OS such as dll loaded events and exceptions

DebuggerTab.14=Debugger

DebuggerTab.15=No break at entry symbol specified.

DebuggerTab.16=View emulator output

DebuggerTab.17=Create a console view to display the contents of the %TEMP%\\epocwind.out file

DebuggerTab.2=Attempt to load symbolics only when the module is being used

DebuggerTab.3=Attempt to load symbolics for all modules loaded into the debug process

DebuggerTab.4=Do not load symbolics for any modules loaded into the debug process

DebuggerTab.6=Break at entry point\:

DebuggerTab.7=When enabled the debugger will automatically set a breakpoint at the function specified.

DebuggerTab.9=View program output

EmulationMainTab.0=Executable\:

EmulationMainTab.1=The executable file generated when the project was built

EmulationMainTab.2=Process to launch\:

EmulationMainTab.3=The absolute path to the Symbian OS emulator or another .exe program to launch

EmulationMainTab.4=Browse...

EmulationMainTab.5=Select the Emulator

EmulationMainTab.6=Please specify an existing valid emulator executable (e.g. Epoc.exe).

EmulationMainTab.7=The project associated with this launch configuration.

ExceptionsTab.0=x86 Exceptions Panel

ExceptionsTab.1=Check the x86 exceptions that the want to debugger to halt on

ExceptionsTab.2=Halt the debugger on any x86 exceptions

ExceptionsTab.25=Exceptions to catch

ExceptionsTab.26=Check All

ExceptionsTab.27=Clear All

ExceptionsTab.28=x86 Exceptions

ExceptionsTab.3=Do not halt the debugger on any x86 exceptions unless it is unrecoverable

ExecutablesTab.1stColumnName=Enabled

ExecutablesTab.2ndCoumnName=Executable to debug

ExecutablesTab.TableToolTip=This table shows all the executables that are built as part of the project (i.e. part of the bld.inf file) excluding the executable specified for debugging in the main tab.

ExecutablesTab.Title=Executables

ExecutablesTab.0=Load symbols for these executables and target them for debugging:

ExecutablesTab.1=Executables in the workspace from this SDK

ExecutablesTab.2=Executables built by this project

ExecutablesTab.3=Executables selected below

ExecutablesTab.4=All executables (slows launch)

ExecutablesTab.5=Executables in the workspace from this SDK

ExecutablesTab.6=Add...

ExecutablesTab.7=Select an executable file

ExecutablesTab.8=Add Executable

ExecutablesTab.9=Select All

ExecutablesTab.10=Unselect All

ExecutablesTab.12=Get Executables

FileTransferTab.1=File Transfer

FileTransferTab.10=Select All

FileTransferTab.11=Deselect All

FileTransferTab.Tooltip=Table is initially empty for Application TRK configurations because files are installed on the device. \nUse this table to transfer additional files if needed.

FileTransferTab.2=Enabled

FileTransferTab.3=File to transfer

FileTransferTab.4=Target path

FileTransferTab.5=Add...

FileTransferTab.6=Edit...

FileTransferTab.7=Remove

FileTransferTab.8=Add File to Transfer

FileTransferTab.9=Edit File to Transfer

FileTransferTab.HostFilesDontExist=One or more files to transfer do not exist.

InstallationTab.1=Installation file\:

InstallationTab.10=You can either interact with the installer UI on the phone when installing the .sis file, or you can choose which drive you want to install to and bypass any UI on the phone.  This is quicker but may not be suitable for more advanced installers.

InstallationTab.11=Install to drive\:

InstallationTab.12=The installation drive on the phone. 'C\:' is normally internal RAM while 'D\:' or 'E\:' typically refer to a memory card.

InstallationTab.13=Installation

InstallationTab.14=Note\: No installation file specified.

InstallationTab.15=Installation file specified does not exist.

InstallationTab.16=Download directory not specified

InstallationTab.17=Download directory must be an absolute path.

InstallationTab.18=The installation drive does not match the drive of the process to be launched.

InstallationTab.2=The absolute path on your PC of the installation file (.sis, .sisx) to install on the phone.

InstallationTab.27=Installation Files

InstallationTab.28=All Files

InstallationTab.3=Browse...

InstallationTab.4=Select installation file

InstallationTab.5=Download directory\:

InstallationTab.6=The directory on the phone to download the installation file to.

InstallationTab.7=Install each launch even if installer file has not changed

InstallationTab.8=This forces the installer to run each time you launch, even if the timestamp of the installation file on the PC and phone are the same.

InstallationTab.9=Do not show installer UI on the phone

InstallationTab.puLabel=Partial upgrade sis/sisx path:

InstallationTab.puTooltip=The partial upgrade sis/sisx path.  This will be downloaded and installed instead of the full sis file specified above.

InstallationTab.puHyperlink=Open SIS Builder settings

InstallationTab.puNotEnabled=Partial upgrade feature not enabled.  Click link below to go to SIS Builder settings.

InstallationTab.puNotAvailable=No partial upgrade installer currently available.

RomImageTab.0=ROM Image

RomImageTab.1=Startup Options

RomImageTab.10=Specify the Symbian OS image that can be downloaded starting at the specified download address.

RomImageTab.11=Symbian ROM Image\:

RomImageTab.12=Specify the Symbian OS image which needs to be downloaded onto the target.

RomImageTab.13=Browse...

RomImageTab.14=Select Symbian ROM image

RomImageTab.15=Symbian ROM Image

RomImageTab.16=All files

RomImageTab.17=Download Address (hex)\:

RomImageTab.18=Specify the download address where the OS image can be downloaded to.

RomImageTab.19=Ask for download at the start of each debug session

RomImageTab.2=Specify the options such as start address and whether to stop the target at the start address during the start of debug session or not.

RomImageTab.20=This option will allows the user to specify whether to ask for download or not at the start of the debug session.

RomImageTab.21=Invalid start address, start address should be specified in hex like "0x10000000".

RomImageTab.22=Invalid download address, download address should be specified in hex like "0x10000000".

RomImageTab.23=Symbian ROM image file not specified

RomImageTab.24=Specified Symbian ROM image file does not exist

RomImageTab.25=Same as start address

RomImageTab.26=This option allows the user to specify whether to make the download address same as the start address or not.

RomImageTab.27=Soft attach option is chosen in the debugger tab, download rom image option will be ignored.

RomImageTab.3=Start Address (hex)\:

RomImageTab.4=Specify the start address from where the OS can be started.

RomImageTab.5=Debug from start address.

RomImageTab.6=This radio button will stop the target at start of the debug session so the user can debug from the start address.

RomImageTab.7=Run from start address.

RomImageTab.8=This radio button will start the OS without stopping the target at the start address of the debug session. 

RomImageTab.9=Download ROM Image 

RomLogFileTab.0=ROM Log

RomLogFileTab.1=Parse Rom Log File

RomLogFileTab.10=Specify the Symbian OS kit Epoc32 directory to resolve the full paths for the various modules in the ROM log file

RomLogFileTab.11=Select Epoc32 directory

RomLogFileTab.12=Epoc32 dir

RomLogFileTab.13=Log unresolved modules

RomLogFileTab.14=This check box allows the user to see the list of unresolved modules from the log file

RomLogFileTab.15=Debug non-XIP executables

RomLogFileTab.16=This check box enables the debugging of non-XIP modules i.e. modules from ROFS image 

RomLogFileTab.17=Symbian ROM log file not specified

RomLogFileTab.18=Specified Symbian ROM log file does not exist

RomLogFileTab.19=Epoc32 directory not specified

RomLogFileTab.2=Rom log file is necessary for finding out the address for each module in the ROM log file. Please specify the ROM log file and epoc32 directory for the Symbian OS kit

RomLogFileTab.20=Specified epoc32 directory does not exist

RomLogFileTab.21=Rom log file is not specified. You need to specify the ROM log file for debugging Symbian modules

RomLogFileTab.3=Symbian Rom Log File\:

RomLogFileTab.4=Specify the ROM log file generated when building the ROM image

RomLogFileTab.5=Browse...

RomLogFileTab.6=Select Symbian Rom Log file

RomLogFileTab.7=Symbian Rom Log files

RomLogFileTab.8=All files

RomLogFileTab.9=Symbian Epoc32 Directory\:

RunModeDebuggerTab.0=Default instruction set

RunModeDebuggerTab.1=When viewing memory or setting breakpoints in a range of memory\r\nfor which there are no symbolics there is no way for the debugger to\r\ndetermine the processor mode.  Please choose the default instruction set for these cases.

RunModeDebuggerTab.10=Message retry delay (ms)\:

RunModeDebuggerTab.11=This is the time the debugger will wait for a response from TRK before resending the message.  Most users will not need to change this value.

RunModeDebuggerTab.12=Debugger

RunModeDebuggerTab.13=No break at entry symbol specified.

RunModeDebuggerTab.14=Message retry delay not specified.

RunModeDebuggerTab.15=Message retry delay should be between 100 and 10000 ms.

RunModeDebuggerTab.16=Invalid message retry delay specified.

RunModeDebuggerTab.17=Auto (examine code at current PC location)

RunModeDebuggerTab.2=ARM (32 bit)

RunModeDebuggerTab.3=Thumb (16 bit)

RunModeDebuggerTab.4=Break at entry point\:

RunModeDebuggerTab.5=When enabled the debugger will automatically set a breakpoint at the function specified.

RunModeDebuggerTab.6=View program output

RunModeDebuggerTab.7=Create a console view to display any data from the communications port that TRK does not understand, such as the output of the executable being debugged

RunModeDebuggerTab.8=View messages between Carbide and debug agent

RunModeDebuggerTab.9=Create a console view to display all communications between the Carbide debugger and TRK on the phone (this can be useful in debugging communications problems)

RunModeMainTab.0=Executable\:

RunModeMainTab.1=The symbolics file (.sym) generated when the project was built

RunModeMainTab.2=Remote process to launch\:

RunModeMainTab.3=The absolute path to the executable on the phone to launch

RunModeMainTab.4=Command line arguments\:

RunModeMainTab.5=Whatever is specified here will be passed to the remote process as command line arguments

RunModeMainTab.6=Remote process to launch not specified.

RunModeMainTab.7=Remote process to launch must be an absolute path.

RunModeMainTab.8=The project associated with this launch configuration.

RunModeMainTab.NoConnectionError=A valid remote connection must be selected. If none exist, create a new one.

SophiaTargetInterfaceTab.0=Sophia Target Interface (WTI.dll) location

SophiaTargetInterfaceTab.1=Browse

SophiaTargetInterfaceTab.10=The absolute path on your PC of the Carbide C++ interface to Sophia JTAG emulator (wti.dll)

SophiaTargetInterfaceTab.11=EJ_Debug Type

SophiaTargetInterfaceTab.12=Select the type of your Sophia JTAG emulator

SophiaTargetInterfaceTab.13=Auto

SophiaTargetInterfaceTab.14=ARM9

SophiaTargetInterfaceTab.15=ARM11

SophiaTargetInterfaceTab.16=ARM9_11

SophiaTargetInterfaceTab.17=ARM7_9_11

SophiaTargetInterfaceTab.18=This lets you see the debug command messages between the Carbide debugger and Sophia JTAG emulator

SophiaTargetInterfaceTab.19=JTAG TCLK Frequency

SophiaTargetInterfaceTab.2=STI Target Configuration File

SophiaTargetInterfaceTab.20=Select desired JTAG TCLK Frequency (Some boards don't support highest or 'Auto' settings)

SophiaTargetInterfaceTab.22=33 MHz

SophiaTargetInterfaceTab.23=16 MHz

SophiaTargetInterfaceTab.24=8 MHz

SophiaTargetInterfaceTab.25=500 KHz

SophiaTargetInterfaceTab.27=View messages between Carbide and STI

SophiaTargetInterfaceTab.3=Browse

SophiaTargetInterfaceTab.4=Connection

SophiaTargetInterfaceTab.5=STI DLL not specified

SophiaTargetInterfaceTab.6=STI DLL specified does not exist

SophiaTargetInterfaceTab.7=Select Sophia Target Interface library (WTI.dll)

SophiaTargetInterfaceTab.8=Dynamic Link Libraries

SophiaTargetInterfaceTab.9=All Files

StopModeDebuggerTab.0=Break at entry point\:

StopModeDebuggerTab.1=When enabled the debugger will automatically set a breakpoint at the function specified.

StopModeDebuggerTab.10=Target Initialization files (*.cfg)

StopModeDebuggerTab.11=All files

StopModeDebuggerTab.12=Memory Configuration File\:

StopModeDebuggerTab.13=Specify the file which defines the memory configuration for the target.

StopModeDebuggerTab.14=Select Memory Configuration file

StopModeDebuggerTab.15=Memory Configuration files (*.mem)

StopModeDebuggerTab.16=Reset target at the start of each debug session

StopModeDebuggerTab.17=This check box allows the user to specify whether to reset the target at beginning of each debug session or not.

StopModeDebuggerTab.18=Default instruction set

StopModeDebuggerTab.19=When viewing memory or setting breakpoints in a range of memory\r\nfor which there are no symbolics there is no way for the debugger to\r\ndetermine the processor mode.  Please choose the default instruction set for these cases.

StopModeDebuggerTab.2=Target Options

StopModeDebuggerTab.20=ARM (32 bit)

StopModeDebuggerTab.21=Thumb (16 bit)

StopModeDebuggerTab.22=Auto (examine code at current PC location)

StopModeDebuggerTab.23=Debugger

StopModeDebuggerTab.24=Initialization file not specified.

StopModeDebuggerTab.25=Specified initialization file does not exist.

StopModeDebuggerTab.26=Memory configuration file not specified.

StopModeDebuggerTab.27=Specified Memory configuration file does not exist.

StopModeDebuggerTab.28=Startup Options

StopModeDebuggerTab.29=Specify the options such as start address and whether to stop the target at the start address during the start of debug session or not.

StopModeDebuggerTab.3=Specify the target options such as target initialization file, memory configuration file etc...

StopModeDebuggerTab.30=Debug from start address

StopModeDebuggerTab.31=This radio button will stop the target at start of the debug session so the user can debug from the start address.

StopModeDebuggerTab.32=Run from start address

StopModeDebuggerTab.33=This radio button will start the OS without stopping the target at the start address of the debug session. 

StopModeDebuggerTab.34=Soft attach

StopModeDebuggerTab.35=This radio button will attach to the target without restarting the target. 

StopModeDebuggerTab.36=Start Address (hex)\:

StopModeDebuggerTab.37=Specify the start address from where the OS can be started.

StopModeDebuggerTab.38=Invalid start address, start address should be specified in hex like "0x10000000".

StopModeDebuggerTab.4=Target Processor\:

StopModeDebuggerTab.5=Choose the processor for your reference board.

StopModeDebuggerTab.6=Target Initialization File\:

StopModeDebuggerTab.7=Specify the initialization file which is run after connecting to the target

StopModeDebuggerTab.8=Browse...

StopModeDebuggerTab.9=Select Target Initialization file

StopModeMainTab.0=Executable\:

StopModeMainTab.1=The symbolics file (.sym) generated when the project was built

StopModeMainTab.2=The project associated with this launch configuration.

Trace32ConnectionTab.1=Trace32 Executable\:

Trace32ConnectionTab.10=Select Trace32 Initialization Script

Trace32ConnectionTab.11=Trace32 Port\:

Trace32ConnectionTab.12=Port number for connecting to T32. This should be same as the port number in the config file.

Trace32ConnectionTab.13=View messages between Carbide and Trace32.

Trace32ConnectionTab.14=This lets you see the debug command messages between the Carbide debugger and Trace32.

Trace32ConnectionTab.15=Trace32 executable not specified.

Trace32ConnectionTab.16=Trace32 executable specified does not exist.

Trace32ConnectionTab.17=Trace32 config file not specified.

Trace32ConnectionTab.18=Trace32 config file specified does not exist.

Trace32ConnectionTab.19=Trace32 initialization script not specified.

Trace32ConnectionTab.2=The absolute path on your PC of the Trace32 executable file (t32marm.exe).

Trace32ConnectionTab.20=Trace32 initialization script specified does not exist.

Trace32ConnectionTab.21=Connection

Trace32ConnectionTab.22=Trace32 Initialization Script

Trace32ConnectionTab.23=Trace32 Executable

Trace32ConnectionTab.24=Trace32 Config Files

Trace32ConnectionTab.25=All Files

Trace32ConnectionTab.26=Specified Trace32 configuration file is invalid.

Trace32ConnectionTab.27=T32 path in the config file is different from specified T32 executable path. Please modify the T32 path in the config file to match the T32 executable path. 

Trace32ConnectionTab.3=Browse...

Trace32ConnectionTab.4=Select Trace32 Executable file

Trace32ConnectionTab.5=Trace32 Configuration File\:

Trace32ConnectionTab.6=The absolute path on your PC of the Trace32 config file (like config.t32).

Trace32ConnectionTab.7=Select Trace32 Config file

Trace32ConnectionTab.8=Trace32 Initialization Script\:

Trace32ConnectionTab.9=The absolute path on your PC of the Trace32 cmm file.

PartialUpgradeAlertDialog.title=Information

PartialUpgradeAlertDialog.text=The sis/sisx file you're downloading is rather large.  There is a builder option which will build\na partial upgrade sis/sisx file containing only the files that have changed since the last install.\nThis can potentially greatly reduce download and hence debugging time.\nClick the link below to go to the SIS Builder settings if you'd like to enable this feature.

PartialUpgradeAlertDialog.dontAskAgain=Don't ask me again

ChooseProcessDialog.NameFilterInitialText=type filter text

ChooseProcessDialog.NameFilterToolTip=Filter the visible items by name, using prefix, ? = any character, * = any string, or camel case initials

ChooseProcessDialog.ClearToolTip=Clear