From ce08c38843cadd338d133eda22157cc933e21bc9 Mon Sep 17 00:00:00 2001 From: bitform Date: Sun, 20 Jan 2013 18:41:22 -0500 Subject: Renamed Usage.txt to Usage.md to apply markdown. --- PETools/Usage.md | 12 ++++++++++++ PETools/Usage.txt | 12 ------------ ReverseEngineering/Usage.md | 12 ++++++++++++ ReverseEngineering/Usage.txt | 12 ------------ ScriptModification/Usage.md | 12 ++++++++++++ ScriptModification/Usage.txt | 12 ------------ 6 files changed, 36 insertions(+), 36 deletions(-) create mode 100644 PETools/Usage.md delete mode 100644 PETools/Usage.txt create mode 100644 ReverseEngineering/Usage.md delete mode 100644 ReverseEngineering/Usage.txt create mode 100644 ScriptModification/Usage.md delete mode 100644 ScriptModification/Usage.txt diff --git a/PETools/Usage.md b/PETools/Usage.md new file mode 100644 index 0000000..6c96b10 --- /dev/null +++ b/PETools/Usage.md @@ -0,0 +1,12 @@ +To install this module, drop the entire PETools folder into one of your module directories. The default PowerShell module paths are listed in the $Env:PSModulePath environment variable. + +The default per-user module path is: "$Env:HomeDrive$Env:HOMEPATH\Documents\WindowsPowerShell\Modules" +The default computer-level module path is: "$Env:windir\System32\WindowsPowerShell\v1.0\Modules" + +To use the module, type `Import-Module PETools` + +To see the commands imported, type `Get-Command -Module PETools` + +For help on each individual command, Get-Help is your friend. + +Note: The tools contained within this module were all designed such that they can be run individually. Including them in a module simply lends itself to increased portability. \ No newline at end of file diff --git a/PETools/Usage.txt b/PETools/Usage.txt deleted file mode 100644 index 6c96b10..0000000 --- a/PETools/Usage.txt +++ /dev/null @@ -1,12 +0,0 @@ -To install this module, drop the entire PETools folder into one of your module directories. The default PowerShell module paths are listed in the $Env:PSModulePath environment variable. - -The default per-user module path is: "$Env:HomeDrive$Env:HOMEPATH\Documents\WindowsPowerShell\Modules" -The default computer-level module path is: "$Env:windir\System32\WindowsPowerShell\v1.0\Modules" - -To use the module, type `Import-Module PETools` - -To see the commands imported, type `Get-Command -Module PETools` - -For help on each individual command, Get-Help is your friend. - -Note: The tools contained within this module were all designed such that they can be run individually. Including them in a module simply lends itself to increased portability. \ No newline at end of file diff --git a/ReverseEngineering/Usage.md b/ReverseEngineering/Usage.md new file mode 100644 index 0000000..dcfae6d --- /dev/null +++ b/ReverseEngineering/Usage.md @@ -0,0 +1,12 @@ +To install this module, drop the entire PETools folder into one of your module directories. The default PowerShell module paths are listed in the $Env:PSModulePath environment variable. + +The default per-user module path is: "$Env:HomeDrive$Env:HOMEPATH\Documents\WindowsPowerShell\Modules" +The default computer-level module path is: "$Env:windir\System32\WindowsPowerShell\v1.0\Modules" + +To use the module, type `Import-Module ReverseEngineering` + +To see the commands imported, type `Get-Command -Module ReverseEngineering` + +For help on each individual command, Get-Help is your friend. + +Note: The tools contained within this module were all designed such that they can be run individually. Including them in a module simply lends itself to increased portability. \ No newline at end of file diff --git a/ReverseEngineering/Usage.txt b/ReverseEngineering/Usage.txt deleted file mode 100644 index dcfae6d..0000000 --- a/ReverseEngineering/Usage.txt +++ /dev/null @@ -1,12 +0,0 @@ -To install this module, drop the entire PETools folder into one of your module directories. The default PowerShell module paths are listed in the $Env:PSModulePath environment variable. - -The default per-user module path is: "$Env:HomeDrive$Env:HOMEPATH\Documents\WindowsPowerShell\Modules" -The default computer-level module path is: "$Env:windir\System32\WindowsPowerShell\v1.0\Modules" - -To use the module, type `Import-Module ReverseEngineering` - -To see the commands imported, type `Get-Command -Module ReverseEngineering` - -For help on each individual command, Get-Help is your friend. - -Note: The tools contained within this module were all designed such that they can be run individually. Including them in a module simply lends itself to increased portability. \ No newline at end of file diff --git a/ScriptModification/Usage.md b/ScriptModification/Usage.md new file mode 100644 index 0000000..ddff666 --- /dev/null +++ b/ScriptModification/Usage.md @@ -0,0 +1,12 @@ +To install this module, drop the entire PETools folder into one of your module directories. The default PowerShell module paths are listed in the $Env:PSModulePath environment variable. + +The default per-user module path is: "$Env:HomeDrive$Env:HOMEPATH\Documents\WindowsPowerShell\Modules" +The default computer-level module path is: "$Env:windir\System32\WindowsPowerShell\v1.0\Modules" + +To use the module, type `Import-Module ScriptModification` + +To see the commands imported, type `Get-Command -Module ScriptModification` + +For help on each individual command, Get-Help is your friend. + +Note: The tools contained within this module were all designed such that they can be run individually. Including them in a module simply lends itself to increased portability. \ No newline at end of file diff --git a/ScriptModification/Usage.txt b/ScriptModification/Usage.txt deleted file mode 100644 index ddff666..0000000 --- a/ScriptModification/Usage.txt +++ /dev/null @@ -1,12 +0,0 @@ -To install this module, drop the entire PETools folder into one of your module directories. The default PowerShell module paths are listed in the $Env:PSModulePath environment variable. - -The default per-user module path is: "$Env:HomeDrive$Env:HOMEPATH\Documents\WindowsPowerShell\Modules" -The default computer-level module path is: "$Env:windir\System32\WindowsPowerShell\v1.0\Modules" - -To use the module, type `Import-Module ScriptModification` - -To see the commands imported, type `Get-Command -Module ScriptModification` - -For help on each individual command, Get-Help is your friend. - -Note: The tools contained within this module were all designed such that they can be run individually. Including them in a module simply lends itself to increased portability. \ No newline at end of file -- cgit v1.2.3