- A -
Apple CoreStorage/FileVault/Fusion Drive Volumes
- B -
Bad Sectors settings
Binary (byte to byte copy)
BitLocker System Drive Encryption
Broken File Name
Rename and change all invalid symbols to:
Broken File Name options
Button
Buttons
Create virtual volume sets or RAIDs
- C -
Connect to R-Studio settings
Contact information and technical support
Find Previous Versions of the File
Find Template Signature Previous
Remove All Scanned Information
Contextt menu
Create menu
Creating and saving your own RAID configuration
Creating Startup Disks for Mac and Linux Computers
- D -
Data Copy in Text/hexadecimal editor
Data Recovery on HFS/HFS+ File System
Description Files for Various RAID Configurations
Devices to Store Recovered Files
Dialog box
Dialog boxes
Edit Block RAID Layout Presets
Please configure R-Studio Agent for Mac
Please configure R-Studio Agent for Windows
R-Studio Agent for Linux Configuration
There is not enough space on the disk
Drive menu
- E -
Edit menu
Find Template Signature Previous
Editor tabs
Exclusive Region options
- F -
Fast Search for Lost Partitions
File Already Exists
File Information (R-Studio Technician/T80+)
File mask options
File menu
File Systems settings
Default encoding for Ext2/Ext3/Ext4/UFS volumes
Default encoding for HFS volumes
File Type Signature Specification
File Types
Find options
Find/Mark options
Find/mark objects only in real paths, ignore links to folders
Finding Previous File Versions
Forensic Data Collection Audit Log
- H -
Hidden Attribute
- I -
Image options
Image type:
Byte to byte image to a physical disk
Compressed image (R-Drive Image compatible)
VMDK (VmWare Virtual Machine Disk)
- K -
Known File Types settings
- L -
Log settings
Maximum messages in the Event Log
- M -
Main settings
Reset all hidden notifications
Messages
Double-click a logical disk...
- N -
Nested and Non-Standard RAID Levels
- O -
Opening several disks/partitions in one tab
- P -
Panels
Panes
Properties tab
- Q -
- R -
Recover options
Condense successful restoration events:
Open local folder (folders) when done
Recover alternative data streams:
Recover real folders structure
Region options
Contact information and technical support
Installing R-Studio Agent Emergency Startup Media Creator
Starting a Computer with the R-Studio Agent Emergency Startup Disk
R-Studio Agent for Mac main panel
R-Studio Agent for Windows main panel
Contact Informaiton and Technical Support
Installing R-Studio Emergency Startup Media Creator
Properties and Text/Hexadecimal Viewer
Starting a Computer with the R-Studio Emergency Startup Disks
R-Studio Emergency Startup Media Creator
- S -
Scan options
Search options
Settings
Shortcut menu
Smart drive copy
Copy all partitions onto original places
Expand/Shrink partition to whole disk
Smart partition copy
Startup Media Troubleshooting Options
Symbolic Links
Automatic recovery without symlink object path conversion
Don't show symbolic links by default (Technician version)
Recovery as it is (Technician version)
Show folder symbolic links as links to their targets, without target content (Technician version)
Show symbolic links as links to their targets, without target content
Symbolic links display settings
Symbolic links recovery options
Syntaxis of a Description File for RAID Configurations
- T -
Tabs
Technical Information and Troubleshooting
Tools menu
- U -
- V -
Various Disk and Volume Managers
View menu
Volume Sets, Stripe Sets, and Mirrors
- W -
Window
Working with RAID 6 Presets
You may create your own patterns yourself.
An example of a commented pattern parsing an AVI file.
The syntax of pattern description is similar to that of the XML language. The folder where the files should be placed is specified on the Main tab of the Settings dialog box.
Pattern header
Each pattern starts with a standard header
<?xml version="1.0" encoding="utf-8"?>
Section template
Each pattern starts with a section giving to the pattern a name that will be shown in the parsed data pane.
Attributes :
name |
Specifies the pattern name shown in the parsed data pane |
<template name="AVI File LIST">
........
</template>
Section signature
Attributes :
align <positive integer> |
Specifies if the data structure address is aligned (i.g., by a sector: 512) |
This section contains elements field with hex-codes of the signature. The attribute offset specifies their offset from the start of the record. Field length is equal to the number of hex-codes.
<signature align="1">
<field offset="0">46 49</field>
<field offset="2">4c 45</field>
</signature>
Section section
Such sections contain all expressions and operations needed for the pattern to parse the data. A section name is shown in the parsed data pane. In fact, sections are virtual objects used to group logically connected field s. Sections can be nested.
The main section is not shown in the parsed data pane.
Section contain elements field which are actual data objects. field names are shown in the parsed data pane with their values.
Attributes :
name |
Specifies the pattern name shown in the parsed data pane |
<section name="JUNK">
....
</section>
Data types (in field )
• integer
Sub-types:
int8
int16
int32
int64
uint8
uint16
uint32
uint64
uintX
Attributes:
endian: (be | le | system) |
Optional. Default: system . |
base: (decimal | hex | octal) |
Optional. Specifies data representation. Default: decimal . |
as-offset: <expression> |
Optional. Specifies that this field is an offset and its value should be evaluated using the expression. A special variable this returns the value of this field. |
purpose: (offset | rsector |sector | cluster | rcluster) |
Optional. Specifies the type of the as-offset expression result . If this attribute is present, the attribute is necessary if the offset value should differ from the value of this field (variable this ). rsector and rcluster are offsets relative to the absolute position of the pattern beginning. |
assigned-template: <TemplateName> |
Specifies the pattern name linked with this field. Ignored if the as-offset or purpose attributes are not specified. |
var: <Name> |
Optional. Specifies the name under which the value of this field can be accessed in expressions. |
• binary
Attributes:
display-encoding: (hex | binary) |
Optional. Default: hex . |
size: <bytes> |
Mandatory. |
• char
Attributes:
size: <bytes> |
Mandatory. |
codepage: (ansi | oem | utf8 | utf16) |
Optional. Specifies which codepage is used. Default: ansi . |
• filetime
Shows time in the Win32 format (64 bits)
• unixtime
Shows time in the Unix format (seconds from 01/01/1970)
• filetime
Shows time in the DOS format (date: hiword, time: loword)
• bits
Attributes:
size: <bytes> |
Mandatory. |
pos: <comma separated list of bit positions> |
Mandatory. Specifies bit positions in a data block. |
Commands
• goto
Specifies a jump to a specified offset (either absolute or relative one)
Attributes:
address: <expression> |
Specifies an absolute address to jump to. |
offset: <expression> |
Specifies a relative offset to jump by. |
One and only one of the attributes should always be specified.
• if
Evaluates a condition specified in the test attribute and, if the condition is true, reads fields specified in this tag.
Attribute:
test: <expression> |
Sets a condition to test against. |
• repea t
Reads the fields specified in the tag until the exit condition is equal to 0 or specified times
Attributes:
count: <expression> |
<expression> is evaluated one time upon entering the block. Internal elements are read the specified number of times. |
test: <expression> |
<expression> is evaluated upon entering the block. Similar to the C++ construction while(...) {} . |
test: <expression> |
<expression> is evaluated upon exiting the block. Similar to the C++ construction do {} while(...) . |
• setvar
Sets the value of an internal variable. As an example, this command is convenient to store the current offset. The value of the current offset is stored in a predefined variable offset .
Attributes:
var: <string> |
Specifies the name of the variable. |
expr: <expression> |
Specifies an expression which result will be assigned to the variable. |
Expressions
Expressions in the patterns are arithmetic expressions which syntax is similar to that of the C language, including operation preceding.
The following operations are supported:
+ - */ & | > < <= >= != == || &&
Predefined variables
• offset
An offset in bytes from the pattern beginning data is currently read at.
• start_position
An absolute position of the pattern beginning. offset + start_position = absolute offset.
• this
This variable exists only within the context of the ass-offset expression evaluation and is the current value of the data field for which that expression is specified