The Complete Guide to Powershell Punctuation

Total Page:16

File Type:pdf, Size:1020Kb

The Complete Guide to Powershell Punctuation The Complete Guide to PowerShell Punctuation Does not include special characters in globs (about_Wildcards) or regular expressions (about_Regular_Expressions) as those are separate “languages”. Green items are placeholders indicating where you insert either a single word/character or, with an ellipsis, a more complex expression. Symbol What it is Explanation Symbol What it is Explanation <enter> line break Allowed between statements, within strings, after these <#... Multi-line Everything between the opening and closing tokens— carriage separators [ | , ; = ] and—as of V3—these [ . :: ]. comment which may span multiple lines—is a comment. return Also allowed after opening tokens [ { [ ( ' " ] . #> Not allowed most anywhere else. call operator Forces the next thing to be interpreted as a command statement Optional if you always use line breaks after statements; & even if it looks like a string. So while either Get- ; required to put multiple statements on one line, e.g. semicolon separator ampersand ChildItem or & Get-ChildItem do the same thing, $a = 25; Write-Output $a "Program Files\stuff.exe" just echoes the string name variable prefix $ followed by letters, numbers, or underscores specifies a literal, while & "Program Files\stuff.exe" will $ variable name, e.g. $width. Letters and numbers are not execute it. dollar sign limited to ASCII; some 18,000+ Unicode chars are eligible. (a) line As the last character on a line, lets you continue on the variable prefix To embed any other characters in a variable name enclose ` continuation next line where PowerShell would not normally allow a ${...} it in braces, e.g ${save-items}. See about_Variables. back tick; line break. Make sure it is really last—no trailing spaces! grave accent See about_Escape_Characters path accessor Special case: ${drive-qualified path} lets you, e.g., ${path} store to (${C:tmp.txt}=1,2,3) or retrieve from (b) literal Precede a dollar sign to avoid interpreting the following character characters as a variable name; precede a quote mark ($data=${C:tmp.txt}) a file. See Provider Paths. inside a string to embed that quote in the string instead of (a) grouping Wrap any single statement (or single command-stream ending the string. See about_Escape_Characters (...) expression connected by pipes) to override default precedence rules. (c) special Followed by one of a set of pre-defined characters, allows See the subexpression operator for multiple $() character inserting special characters, e.g. `t = tab, `r = carriage commands. return, `b = backspace. See about_Special_Characters Group at the front: access a property from the result of an operation, e.g. (get-process -name win*).name '...' literal string String with no interpolation; typically used for single-line Group at the end: pass the result of an operation as an single quote strings but can be used for multi-line as well. argument: write-output (1,2,3 -join '*') "..." interpolated String with interpolation of variables, sub-expressions, (b) grouping Override operator precedence: double quote string escapes, and special characters (e.g. `t). See operator e.g. 8 + 4 / 2 vs. (8 + 4)/2 about_Escape_Characters and about_Special_Characters (c) .NET Unlike when calling native PowerShell functions, calling @' literal A multi-line string with no interpolation; differs from a function arg .NET functions require parentheses: ... here-string normal string in that you can embed single quotes within container $hashTable.ContainsKey($x) '@ the string without doubling or escaping. $(...) (a) sub- Wrap multiple statements, where the output of each interpolated A multi-line string with interpolation; differs from a normal expression contributes to the total output: $($x=1;$y=2;$x;$y) @"... here-string string in that you can embed double quotes within the (b) sub- Interpolate simple variables in a double-quoted string with string without doubling or escaping. expression just $, but complex expressions must be wrapped in a "@ inside a string subexpression. Ex: $p = ps | select –first 1 then command Pipe output of one command to input of next, "proc name is $($p.name)" | pipe connector e.g. ps | select ProcessName array sub- Same as a sub-expression, except this returns an array divert to file / Redirects & overwrites (if file exists) stdout stream to a file @(...) expression even with zero or one objects. Many cmdlets return a > overwrite (e.g. ps > process_list.txt). See about_Redirection array collection of a certain type, say X. If two or more, it is greater than returned as an array of X whereas if you only get one It’s a “greater than” symbol but it doesn’t do comparisons: object then it is just an X. Wrapping the call with this for algebraic operators use -gt or -lt, e.g. ($x -lt $y). operator forces it to always be an array, e.g. $a = @(ps divert to file / Redirects & overwrites (if file exists) numbered stream (2 | where name -like 'foo') See about_Arrays n> overwrite thru 5) or all streams (use *) to a file e.g. ps 4> hash initializer Defines a hash table with the format process_list.txt @{...} @{ name1=value1; name2=value2; ...}. Example: divert to file / Redirects & appends stdout stream to a file, e.g. hash $h = @{abc='hello'; color='green'}. You can >> append ps >> process_list.txt. See about_Redirection then access values by their keys, e.g. $h['color'] or divert to file / Redirects & appends numbered stream (2 thru 5) or all . See about_Hash_Tables $h.color n>> append streams (use *) to a file, e.g. ps *>> out.txt {...} script block Essentially an anonymous function. Ex: output redirect Redirects an output stream (2 thru 5) to stdout stream, $sb = {param($color="red"); "color=$color"} n>&1 to stdout effectively merging that stream with stdout. Ex: to merge braces then . See about_Script_Blocks & $sb 'blue' errors with stdout: Do-SomethingErrorProne 2>&1 (a) array indexer returns the 5th element of the array. [...] $data[4] $data assignment Assign a value to a variable, e.g. $stuff = 25 or brackets (b) hash indexer $hash['blue'] returns the value associated with key = operator $procs = ps | select -first 5. Use -eq or -ne for 'blue' in the hash (though you could also use $hash.blue) equals equality operators: ("ab" -eq $x) or ($amt -eq 100). (c) static type Use to call a static methods, e.g. [Regex]::Escape($x) ! Logical not Negates the statement or value that follows. Equivalent to (d) type cast Cast to a type just like C# ([int]"5.2") but in PS you can exclamation the -not operator. if ( !$canceled ) ... also cast the variable itself ([xml]$x='<abc/>'). Also (a) add Adds numbers, e.g. ($val + 25). applies for function args: function f([int]$i) {...} + plus (b) concatenate Concatenates strings, arrays, hash tables, e.g. ('hi'+'!'). (e) array type Cast to an array type—use with no content inside: (c) nested class Typically best practice says not to have public nested designator function f([int[]] $values) {...}. access classes but when needed you need a plus to access, e.g. pipeline object This special variable holds the current pipeline object (now [Net.WebRequestMethods+Ftp] See Plus (+) in .NET $_ with a more friendly alias as well, $PSItem), Class Names e.g. ps | where { $_.name -like 'win*' } add & store Common shorthand identical to that in C#: $x += 5 is splatting prefix Allows passing a collection of values stored in a hash table += shorthand for $x = $x + 5. Can also be used for @name or in an array as parameters to a cmdlet. Particularly compound concatenation as described under plus and concatenation splat useful to forward arguments passed in to another call with assignment direct to a path: ${c:output.txt) += 'one','two' or . See about_Splatting @Args @PsBoundParameters (a) negate Negate a number (-$val). alias for Instead of you Get-Stuff | Where-Object { ... } - (b) subtract Subtract one number from another ($v2 - 25.1). ? Where-Object can write the oft-used cmdlet with the terse alias: hyphen question Get-Stuff | ? { ... } (c) operator Prefixes lots of operators: logical (-and, -or, -not), mark prefix comparision (-eq, -ne, -gt, -lt, -le, -ge), %{...} Alias for Instead of 1..5| ForEach-Object { $_ * 2 } you bitwise (-bAND, -bOR, -bXOR, -bNOT), and more. ForEach-Object can write the oft-used cmdlet as: 1..5| % { $_ * 2 } (d) verb/noun Separates the verb from the noun in every cmdlet, e.g. (a) alias for Special case of above for a single property of pipeline separator Get-Process. % ForEach-Object input: ls| % name is equivalent to ls| % { $_.name} percent subtract & Common shorthand identical to that in C#: $x -= 5 is (b) modulo Returns the remainder of a division e.g. (7 % 2) returns 1. -= store shorthand for $x = $x - 5. modulo & store Common shorthand identical to that in C#: $x %= 5 is (a) multiply Multiply numbers, e.g. ($val * 3.14). %= shorthand for $x = $x % 5. * (b) replicate Replicate arrays, e.g. ('a','b' * 2). (a) drive Just like conventional Windows drives ( , etc.) you asterisk dir C:\ Common shorthand identical to that in C#: is : designator can use dir alias: to see the contents of the alias drive multiply & $x *= 5 colon *= store shorthand for $x = $x * 5. Can also be used for or $env:path to see the $path variable on the env drive. replication as described under asterisk and replication (b) variable An undecorated variable, e.g. $stuff implicitly specifies direct to a path: ${c:output.txt) *= 3 scope specifier the current scope. But you can also reference divide Divide numbers, e.g. ($val / 3.14). $script:stuff or $global:stuff to specify a / different scope. See about_Scopes virgule divide & store Common shorthand identical to that in C#: $x /= 5 is static member Specify a static .NET method, e.g. [String]::Join(...) /= :: shorthand for $x = $x / 5. accessor or [System.IO.Path]::GetTempFileName(), or a increment Auto-increment a variable: increment then return value double colon static property [System.Windows.Forms.Keys]::Alt ++ (++$v) or return value then increment ($v++).
Recommended publications
  • Configuring UNIX-Specific Settings: Creating Symbolic Links : Snap
    Configuring UNIX-specific settings: Creating symbolic links Snap Creator Framework NetApp September 23, 2021 This PDF was generated from https://docs.netapp.com/us-en/snap-creator- framework/installation/task_creating_symbolic_links_for_domino_plug_in_on_linux_and_solaris_hosts.ht ml on September 23, 2021. Always check docs.netapp.com for the latest. Table of Contents Configuring UNIX-specific settings: Creating symbolic links . 1 Creating symbolic links for the Domino plug-in on Linux and Solaris hosts. 1 Creating symbolic links for the Domino plug-in on AIX hosts. 2 Configuring UNIX-specific settings: Creating symbolic links If you are going to install the Snap Creator Agent on a UNIX operating system (AIX, Linux, and Solaris), for the IBM Domino plug-in to work properly, three symbolic links (symlinks) must be created to link to Domino’s shared object files. Installation procedures vary slightly depending on the operating system. Refer to the appropriate procedure for your operating system. Domino does not support the HP-UX operating system. Creating symbolic links for the Domino plug-in on Linux and Solaris hosts You need to perform this procedure if you want to create symbolic links for the Domino plug-in on Linux and Solaris hosts. You should not copy and paste commands directly from this document; errors (such as incorrectly transferred characters caused by line breaks and hard returns) might result. Copy and paste the commands into a text editor, verify the commands, and then enter them in the CLI console. The paths provided in the following steps refer to the 32-bit systems; 64-bit systems must create simlinks to /usr/lib64 instead of /usr/lib.
    [Show full text]
  • Command Line Interface Specification Windows
    Command Line Interface Specification Windows Online Backup Client version 4.3.x 1. Introduction The CloudBackup Command Line Interface (CLI for short) makes it possible to access the CloudBackup Client software from the command line. The following actions are implemented: backup, delete, dir en restore. These actions are described in more detail in the following paragraphs. For all actions applies that a successful action is indicated by means of exit code 0. In all other cases a status code of 1 will be used. 2. Configuration The command line client needs a configuration file. This configuration file may have the same layout as the configuration file for the full CloudBackup client. This configuration file is expected to reside in one of the following folders: CLI installation location or the settings folder in the CLI installation location. The name of the configuration file must be: Settings.xml. Example: if the CLI is installed in C:\Windows\MyBackup\, the configuration file may be in one of the two following locations: C:\Windows\MyBackup\Settings.xml C:\Windows\MyBackup\Settings\Settings.xml If both are present, the first form has precedence. Also the customer needs to edit the CloudBackup.Console.exe.config file which is located in the program file directory and edit the following line: 1 <add key="SettingsFolder" value="%settingsfilelocation%" /> After making these changes the customer can use the CLI instruction to make backups and restore data. 2.1 Configuration Error Handling If an error is found in the configuration file, the command line client will issue an error message describing which value or setting or option is causing the error and terminate with an exit value of 1.
    [Show full text]
  • Mac Keyboard Shortcuts Cut, Copy, Paste, and Other Common Shortcuts
    Mac keyboard shortcuts By pressing a combination of keys, you can do things that normally need a mouse, trackpad, or other input device. To use a keyboard shortcut, hold down one or more modifier keys while pressing the last key of the shortcut. For example, to use the shortcut Command-C (copy), hold down Command, press C, then release both keys. Mac menus and keyboards often use symbols for certain keys, including the modifier keys: Command ⌘ Option ⌥ Caps Lock ⇪ Shift ⇧ Control ⌃ Fn If you're using a keyboard made for Windows PCs, use the Alt key instead of Option, and the Windows logo key instead of Command. Some Mac keyboards and shortcuts use special keys in the top row, which include icons for volume, display brightness, and other functions. Press the icon key to perform that function, or combine it with the Fn key to use it as an F1, F2, F3, or other standard function key. To learn more shortcuts, check the menus of the app you're using. Every app can have its own shortcuts, and shortcuts that work in one app may not work in another. Cut, copy, paste, and other common shortcuts Shortcut Description Command-X Cut: Remove the selected item and copy it to the Clipboard. Command-C Copy the selected item to the Clipboard. This also works for files in the Finder. Command-V Paste the contents of the Clipboard into the current document or app. This also works for files in the Finder. Command-Z Undo the previous command. You can then press Command-Shift-Z to Redo, reversing the undo command.
    [Show full text]
  • Attacker Antics Illustrations of Ingenuity
    ATTACKER ANTICS ILLUSTRATIONS OF INGENUITY Bart Inglot and Vincent Wong FIRST CONFERENCE 2018 2 Bart Inglot ◆ Principal Consultant at Mandiant ◆ Incident Responder ◆ Rock Climber ◆ Globetrotter ▶ From Poland but live in Singapore ▶ Spent 1 year in Brazil and 8 years in the UK ▶ Learning French… poor effort! ◆ Twitter: @bartinglot ©2018 FireEye | Private & Confidential 3 Vincent Wong ◆ Principal Consultant at Mandiant ◆ Incident Responder ◆ Baby Sitter ◆ 3 years in Singapore ◆ Grew up in Australia ©2018 FireEye | Private & Confidential 4 Disclosure Statement “ Case studies and examples are drawn from our experiences and activities working for a variety of customers, and do not represent our work for any one customer or set of customers. In many cases, facts have been changed to obscure the identity of our customers and individuals associated with our customers. ” ©2018 FireEye | Private & Confidential 5 Today’s Tales 1. AV Server Gone Bad 2. Stealing Secrets From An Air-Gapped Network 3. A Backdoor That Uses DNS for C2 4. Hidden Comment That Can Haunt You 5. A Little Known Persistence Technique 6. Securing Corporate Email is Tricky 7. Hiding in Plain Sight 8. Rewriting Import Table 9. Dastardly Diabolical Evil (aka DDE) ©2018 FireEye | Private & Confidential 6 AV SERVER GONE BAD Cobalt Strike, PowerShell & McAfee ePO (1/9) 7 AV Server Gone Bad – Background ◆ Attackers used Cobalt Strike (along with other malware) ◆ Easily recognisable IOCs when recorded by Windows Event Logs ▶ Random service name – also seen with Metasploit ▶ Base64-encoded script, “%COMSPEC%” and “powershell.exe” ▶ Decoding the script yields additional PowerShell script with a base64-encoded GZIP stream that in turn contained a base64-encoded Cobalt Strike “Beacon” payload.
    [Show full text]
  • Powershell Integration with Vmware View 5.0
    PowerShell Integration with VMware® View™ 5.0 TECHNICAL WHITE PAPER PowerShell Integration with VMware View 5.0 Table of Contents Introduction . 3 VMware View. 3 Windows PowerShell . 3 Architecture . 4 Cmdlet dll. 4 Communication with Broker . 4 VMware View PowerCLI Integration . 5 VMware View PowerCLI Prerequisites . 5 Using VMware View PowerCLI . 5 VMware View PowerCLI cmdlets . 6 vSphere PowerCLI Integration . 7 Examples of VMware View PowerCLI and VMware vSphere PowerCLI Integration . 7 Passing VMs from Get-VM to VMware View PowerCLI cmdlets . 7 Registering a vCenter Server . .. 7 Using Other VMware vSphere Objects . 7 Advanced Usage . 7 Integrating VMware View PowerCLI into Your Own Scripts . 8 Scheduling PowerShell Scripts . 8 Workflow with VMware View PowerCLI and VMware vSphere PowerCLI . 9 Sample Scripts . 10 Add or Remove Datastores in Automatic Pools . 10 Add or Remove Virtual Machines . 11 Inventory Path Manipulation . 15 Poll Pool Usage . 16 Basic Troubleshooting . 18 About the Authors . 18 TECHNICAL WHITE PAPER / 2 PowerShell Integration with VMware View 5.0 Introduction VMware View VMware® View™ is a best-in-class enterprise desktop virtualization platform. VMware View separates the personal desktop environment from the physical system by moving desktops to a datacenter, where users can access them using a client-server computing model. VMware View delivers a rich set of features required for any enterprise deployment by providing a robust platform for hosting virtual desktops from VMware vSphere™. Windows PowerShell Windows PowerShell is Microsoft’s command line shell and scripting language. PowerShell is built on the Microsoft .NET Framework and helps in system administration. By providing full access to COM (Component Object Model) and WMI (Windows Management Instrumentation), PowerShell enables administrators to perform administrative tasks on both local and remote Windows systems.
    [Show full text]
  • Linux-PATH.Pdf
    http://www.linfo.org/path_env_var.html PATH Definition PATH is an environmental variable in Linux and other Unix-like operating systems that tells the shell which directories to search for executable files (i.e., ready-to-run programs ) in response to commands issued by a user. It increases both the convenience and the safety of such operating systems and is widely considered to be the single most important environmental variable. Environmental variables are a class of variables (i.e., items whose values can be changed) that tell the shell how to behave as the user works at the command line (i.e., in a text-only mode) or with shell scripts (i.e., short programs written in a shell programming language). A shell is a program that provides the traditional, text-only user interface for Unix-like operating systems; its primary function is to read commands that are typed in at the command line and then execute (i.e., run) them. PATH (which is written with all upper case letters) should not be confused with the term path (lower case letters). The latter is a file's or directory's address on a filesystem (i.e., the hierarchy of directories and files that is used to organize information stored on a computer ). A relative path is an address relative to the current directory (i.e., the directory in which a user is currently working). An absolute path (also called a full path ) is an address relative to the root directory (i.e., the directory at the very top of the filesystem and which contains all other directories and files).
    [Show full text]
  • Where Do You Want to Go Today? Escalating
    Where Do You Want to Go Today? ∗ Escalating Privileges by Pathname Manipulation Suresh Chari Shai Halevi Wietse Venema IBM T.J. Watson Research Center, Hawthorne, New York, USA Abstract 1. Introduction We analyze filename-based privilege escalation attacks, In this work we take another look at the problem of where an attacker creates filesystem links, thereby “trick- privilege escalation via manipulation of filesystem names. ing” a victim program into opening unintended files. Historically, attention has focused on attacks against priv- We develop primitives for a POSIX environment, provid- ileged processes that open files in directories that are ing assurance that files in “safe directories” (such as writable by an attacker. One classical example is email /etc/passwd) cannot be opened by looking up a file by delivery in the UNIX environment (e.g., [9]). Here, an “unsafe pathname” (such as a pathname that resolves the mail-delivery directory (e.g., /var/mail) is often through a symbolic link in a world-writable directory). In group or world writable. An adversarial user may use today's UNIX systems, solutions to this problem are typ- its write permission to create a hard link or symlink at ically built into (some) applications and use application- /var/mail/root that resolves to /etc/passwd. A specific knowledge about (un)safety of certain directories. simple-minded mail-delivery program that appends mail to In contrast, we seek solutions that can be implemented in the file /var/mail/root can have disastrous implica- the filesystem itself (or a library on top of it), thus providing tions for system security.
    [Show full text]
  • An Incremental Path Towards a Safer OS Kernel
    An Incremental Path Towards a Safer OS Kernel Jialin Li Samantha Miller Danyang Zhuo University of Washington University of Washington Duke University Ang Chen Jon Howell Thomas Anderson Rice University VMware Research University of Washington LoC Abstract Incremental Progress Tens of Linux Safe Linux Linux has become the de-facto operating system of our age, Millions FreeBSD but its vulnerabilities are a constant threat to service availabil- Hundreds of Singularity ity, user privacy, and data integrity. While one might scrap Thousands Biscuit Linux and start over, the cost of that would be prohibitive due Theseus Thousands RedLeaf seL4 to Linux’s ubiquitous deployment. In this paper, we propose Hyperkernel Safety an alternative, incremental route to a safer Linux through No Type Ownership Functional proper modularization and gradual replacement module by Guarantees Safety Safety Verification module. We lay out the research challenges and potential Figure 1: Our vision and the current state of systems. solutions for this route, and discuss the open questions ahead. security vulnerabilities are reported each year, and lifetime CCS Concepts analysis suggests that the new code added this year has intro- duced tens of thousands of more bugs. ! • Software and its engineering Software verification; While operating systems are far from the only source of se- ! • Computer systems organization Reliability. curity vulnerabilities, it is hard to envision building trustwor- Keywords thy computer systems without addressing operating system correctness. kernel safety, verified systems, reliable systems One attractive option is to scrap Linux and start over. Many ACM Reference Format: past works focus on building more secure and correct op- Jialin Li, Samantha Miller, Danyang Zhuo, Ang Chen, Jon Howell, erating systems from the ground up: ones based on strong and Thomas Anderson.
    [Show full text]
  • Simple File System (SFS) Format
    Simple File System (SFS) Format Version SFS-V00.01 The SFS is a simple file system format optimized for writing and for low overhead.. The advantages of this format are: • Event navigation is possible using simple content-independent file system like functions. • Very low overhead. No loss due to block size granularity • Entire valid file system can be created by appending content On the other hand, random access directory navigation is rather slow because there is no built-in indexing or directory hierarchy. For a 500MB file system containing files with 5k bytes this represents an initial search overhead of ~1-2 sec (~100,000 seeks). SFS Structure The structure of a SFS file is as follows VolumeSpec Head File1 File1 Binary Data File2 File2 Binary Data ... ... Tail VolumeSpec: This is simply a 12 byte character string representing filesystem version. For example: “SFS V00.01” Head: This is a short header record. The byte order only applies to the time field of this record. type = “HEAD” byte_order = 0x04030201 time File: The File records are a variable length record containing information about a file. type = “FILE” byte_order = 0x04030201 Sz head_sz attr reserved name.... name (continued).... “byte_order” corresponds only to this header. The endiness of the data is undefined by SFS “sz” corresponds to the datafile size. This may be any number, but the file itself will be padded to take up a multiple of 4 bytes “head_sz” this must be a multiple of 4 “attr” SFS_ATTR_INVALID: file deleted SFS_ATTR_PUSHDIR: push current path to path stack SFS_ATTR_POPDIR: pop current path from path stack SFS_ATTR_NOCD: this record doesn’t reset the basedir “name” the name of the file.
    [Show full text]
  • A Plethora of Paths
    A Plethora of Paths Eric Larson Seattle University [email protected] Abstract A common static software bug detection technique is to use path simulation. Each execution path is simulated using symbolic variables to determine if any software errors could occur. The scalability of this and other path-based approaches is dependent on the number of paths in the pro- gram. This paper explores the number of paths in 15 differ- ent programs. Often, there are one or two functions that contribute a large percentage of the paths within a program. A unique aspect in this study is that slicing was used in dif- ferent ways to determine its effect on the path count. In par- ticular, slicing was applied to each interesting statement individually to determine if that statement could be analyzed without suffering from path explosion. Results show that slic- ing is only effective if it can completely slices away a func- tion that suffers from path explosion. While most programs had several statements that resulted in short path counts, slicing was not adequate in eliminating path explosion occurrences. Looking into the tasks that suffer from path explosion, we find that functions that process input, produce stylized output, or parse strings or code often have signifi- Figure 1. Sample Control Flow Graph. cantly more paths than other functions. a reasonable amount of time. One technique to address path 1. Introduction explosion is to use program slicing [11, 20] to remove code not relevant to the property being verified. Static analysis is an important tool in software verifica- Consider the sample control flow graph in Figure 1.
    [Show full text]
  • Path Howto Path Howto
    PATH HOWTO PATH HOWTO Table of Contents PATH HOWTO..................................................................................................................................................1 Esa Turtiainen etu@dna.fi.......................................................................................................................1 1. Introduction..........................................................................................................................................1 2. Copyright.............................................................................................................................................1 3. General.................................................................................................................................................1 4. Init........................................................................................................................................................1 5. Login....................................................................................................................................................1 6. Shells....................................................................................................................................................1 7. Changing user ID.................................................................................................................................1 8. Network servers...................................................................................................................................1
    [Show full text]
  • File Manager
    File Manager 2016.12 Rev. 1.0 Contents 1.Introduction....................................................................................1 1-1.Overview .........................................................................................................1 1-2. System Requirements and Restrictions .......................................................1 2.Installation on Windows PC ...........................................................2 2-1.Installation......................................................................................................2 2-2.Uninstallation.................................................................................................4 3.How to use RSD-FDFM ..................................................................5 3-1.How to proceed with format CF media..........................................................6 3-2.How to proceed with writing data to CF media ............................................8 3-3.How to create files/folders at CF media.......................................................11 3-4.How to delete files/folders at CF media.......................................................14 3-5.How to save files/folders at CF media .........................................................15 3-6.A list of error messages of RSD-FDFM .......................................................16 *All trademarks and logos are the properties of their respective holders. *The specifications and pictures are subject to change without notice. 1.Introduction Thank you for purchasing file
    [Show full text]