Pscx Work Item Rss Feed

Closed Issue: Write-Zip -Append does not support -FlattenPaths [17794]

oisin — Thu, 16 May 2013 11:57:57 GMT

write-zip -append should have parity with archives created with plain write-zip. if not, it would be difficult to freshen files that have been flattened.

Closed Issue: Read-Archive fails on bz2 file [26955]

oisin — Thu, 16 May 2013 11:57:49 GMT

archive contains one large file - fails as below:

Read-Archive -Verbose -Path .\planet-100414.osm.bz2
VERBOSE: 1 item(s) in archive.
Read-Archive : Error reading index 0
At line:1 char:13
+ Read-Archive <<<< -Verbose -Path .\planet-100414.osm.bz2
+ CategoryInfo : ReadError: (:) [Read-Archive], ArgumentException
+ FullyQualifiedErrorId : ArchiveReadFail,Pscx.Commands.IO.Compression.ReadArchiveCommand

downloaded file planet-100414.osm.bz2and ran md5 check from http://planet.openstreetmap.org/

thread on http://pscx.codeplex.com/Thread/View.aspx?ThreadId=67087

Closed Issue: write-zip bug: -flattenpaths has no effect when used with -append [27848]

oisin — Thu, 16 May 2013 11:57:49 GMT

Hi,

I'm trying to use the write-zip cmdlet and find the following odd behavior:

When I use the -append switch, files get added with path information, even when specifying the -FlattenPaths switch....

write-zip $files $outputFile -level 9 -FlattenPaths -append

Anybody come across this, or even better, found a work around?

Cheers!

Closed Issue: -EntryPath switch of Expand-Archive is non-functional [28313]

oisin — Thu, 16 May 2013 11:57:48 GMT

Steps to reproduce: Run the following script:
"hello world" | sc a.txt
Write-Zip -Path a.txt -OutputPath a.zip
Expand-Archive -path a.zip -OutputPath . -EntryPath a.txt

Expected Behaviour: a.txt file is extracted from a.zip archive into the current path.

Observed behaviour: Error message is displayed:
Expand-Archive : Object reference not set to an instance of an object.
At line:1 char:15
+ Expand-Archive <<<< -path a.zip -OutputPath . -EntryPath @("a.txt")
+ CategoryInfo : NotSpecified: (:) [Expand-Archive], NullReferenceException
+ FullyQualifiedErrorId : System.NullReferenceException,Pscx.Commands.IO.Compression.ExpandArchiveCommand

Additional information: The stack trace is like this:
at Pscx.Commands.IO.Compression.ExpandArchiveCommand.ProcessArchive(FileInfo fileInfo) in C:\Users\Keith\Pscx\Trunk\Src\Pscx\Commands\IO\Compression\ExpandArchiveCommand.cs:line 175
at Pscx.Commands.PscxPathCommandBase.ProcessRecord() in C:\Users\Keith\Pscx\Trunk\Src\Pscx.Core\Commands\PscxPathCommandBase.cs:line 127
at System.Management.Automation.CommandProcessor.ProcessRecord()

Examination of the source code hints that EntryPath switch value is never used during the extraction process.

Workaround: Use -Index switch instead of -EntryPath switch

Closed Issue: Large Write-zip files cannot be extracted with 7zip 9.20 [32514]

oisin — Thu, 16 May 2013 11:57:45 GMT

The Write-Zip cmdlet appears to write zip files okay, but on large files (typical zip is 800MB or more), the files cannot be extracted when using later version of 7zip (e.g. 9.20, 9.22 etc), which gives an error "Unsupported compression method". I suspect this is because pscx is using quite an old version of the 7zip.dll files (v4.65), but simply replacing those DLLs in the pscx module folder has not resolved the issue (are the 7zip dlls embedded into the pscx dlls?).

Closed Issue: Expand-Archive fails with TAR file format [32847]

kevinsmotherman — Thu, 16 May 2013 11:57:45 GMT

The Expand-Archive cmdlet fails to extract the Tape Archive (TAR) file format.

Steps to reproduce:
1. Create TAR of image files (or any files of your choice):
Get-ChildItem *.img | Write-Tar -output archive.tar
2. Extract file:
Expand-Archive -Path archive.tar -Format Tar

Notes:
- No issues with Zip archive format using Expand-Archive cmdlet
- According to Expand-Archive documentation, the supported formats are:
SevenZip, Arj, BZip2, Cab, Chm, Compound, Cpio, Deb, GZip, Iso, Lzh, Lzma, Nsis, Rar, Rpm, Split, Tar, Wim, Z, Zip

Closed Issue: Pscx 2.1 beta on PowerShell 3 -- errors [32948]

r_keith_hill — Thu, 16 May 2013 11:57:44 GMT

Method invocation failed because [System.Management.Automation.TypeAccelerators] doesn't contain a method named
'AddReplace'.
At C:\Users\rogerl\Documents\WindowsPowerShell\Modules\pscx\Modules\Wmi\Pscx.Wmi.psm1:17 char:9
+ $acceleratorsType::AddReplace($name, $type)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MethodNotFound

Import-Module : The specified module
'C:\Users\rogerl\Documents\WindowsPowerShell\Modules\pscx\Modules\Wmi\Pscx.Wmi.psm1' was not loaded because no valid
module file was found in any module directory.
At C:\Users\rogerl\Documents\WindowsPowerShell\Modules\pscx\Pscx.psm1:197 char:4
+ Import-Module $path -DisableNameChecking
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (C:\Users\rogerl...i\Pscx.Wmi.psm1:String) [Import-Module], FileNot
FoundException
+ FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand

Closed Issue: PowerShell 3.0 RC [32949]

r_keith_hill — Thu, 16 May 2013 11:57:44 GMT

Pscx modul WMI failed to load with error "Property 'Get' not available for this object'
Error is in Pscx\Modules\Wmi\Pscx.Wmi.psm1:8 Char:6: if (!$acceleratorsType::Get.ContainsKey($name))
See also : http://connect.microsoft.com/PowerShell/feedback/details/721443/system-management-automation-typeaccelerators-broken-in-v3-ctp2

Closed Issue: Invoke-Elevated / su error [33094]

r_keith_hill — Thu, 16 May 2013 11:57:44 GMT

When I run an Invoke-Elevated command the resultant elevated PS window reports an error which implies that the command line has been repeated without the initial letter.

e.g.:
Invoke-Elevated Get-ChildItem

reoprts

nvoke-elevated : The term 'nvoke-elevated' is not recognized as the name of a
cmdlet, function, script file, or operable program. Check the spelling of the
name, or if a path was included, verify that the path is correct and try again.
At line:1 char:143
+ ... .ProviderPath; nvoke-elevated Get-ChildItem}
+ ~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (nvoke-elevated:String) [], Comm
andNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Closed Issue: Property 'Get' cannot be found on this object. Make sure that it exists. [33100]

r_keith_hill — Thu, 16 May 2013 11:57:43 GMT

Property 'Get' cannot be found on this object. Make sure that it exists.
At C:\Windows\system32\WindowsPowerShell\v1.0\Modules\Pscx\Modules\Wmi\Pscx.Wmi.psm1:8 char:6
+ if (!$acceleratorsType::Get.ContainsKey($name))
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : PropertyNotFoundStrict

Import-Module : The specified module 'C:\Windows\system32\WindowsPowerShell\v1.0\Modules\Pscx\Modules\Wmi\Pscx.Wmi.psm1
' was not loaded because no valid module file was found in any module directory.
At C:\Windows\system32\WindowsPowerShell\v1.0\Modules\Pscx\Pscx.psm1:197 char:4
+ Import-Module $path -DisableNameChecking
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (C:\Windows\syst...i\Pscx.Wmi.psm1:String) [Import-Module], FileNot
FoundException
+ FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand

Closed Issue: Importing Pscx breaks help [33486]

r_keith_hill — Thu, 16 May 2013 11:57:42 GMT

After importing PSCX then get-help is broken for any topic. e.g.PS M:\> get-help about_CommonParameters...SEE ALSO about_Preference_Variables Write-Debug Write-Warning Write-Error Write-VerbosePS M:\> import-module pscxPS M:\> get-help about_CommonParametersProperty 'HelpUri' cannot be found for type 'System.Management.Automation.CmdletBindingAttribute'.At C:\windows\system32\WindowsPowerShell\v1.0\Modules\pscx\Modules\GetHelp\Pscx.GetHelp.psm1:407 char:19+ [CmdletBinding <<<< (DefaultParameterSetName='AllUsersView', HelpUri='http://go.microsoft.com/fwlink/?LinkID=113316')] + CategoryInfo : InvalidOperation: (:) [], RuntimeException + FullyQualifiedErrorId : PropertyAssignmentExceptionNote, This is for the 2.1 Production release of PSCX and occurs on both Win7 Desktop and Win2008 virtual server.

Created Issue: Paths with Spaces when using Invoke-Elevated [34019]

alzadude — Tue, 30 Apr 2013 13:14:45 GMT

Hi there,

When I use Invoke-Elevated (from PSCX 2.1.1) like this:

```
su dir 'C:\Program Files'
```

The launched process gives the following error:

```
Get-ChildItem : Cannot find path 'C:\Program' because it does not exist.
At line:1 char:37
+ & {Set-Location 'C:\Users\xxxx'; dir <<<< C:\Program Files}
+ CategoryInfo : ObjectNotFound: (C:\Program:String) [Get-ChildItem], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand
```

It would be great if Invoke-Elevated could support paths with spaces.

Thanks

Created Issue: Working Directory when using Invoke-Elevated [34018]

alzadude — Tue, 30 Apr 2013 09:07:58 GMT

Hi there,

When I use Invoke-Elevated like this:

su dir

The launched process (correctly?) re-uses my current working directory.

However, if I create a simple bat file 'show_dir.bat' containing the command 'dir', and place this bat file on the system path, and use Invoke-Elevated on it:

su show_dir.bat

The launched process doesn't seem to use my current working directory; instead, the directory listing is for 'C:\Windows\system32'. (As an aside, the window for the launched process doesn't stay open, unlike the behaviour for 'su dir')

I can work around this issue (and the window not staying open) by using the following command, instead of Invoke-Elevated:

Start-Process powershell -Verb RunAs -ArgumentList "-noexit","-command set-location $pwd; show_dir.bat"

However, it would be great if Invoke-Elevated could support this case directly.

Thanks

Commented Issue: Import-Module extremely slow in 32-bit window on x64 system [27246]

schallm — Tue, 02 Apr 2013 17:49:47 GMT

The command "Import-Module pscx" takes an extremely long time in a 32-bit window on a 64-bit computer. This problem exists on all computers available for me to test, running Windows 2008 R2, Windows 2008, and Windows Vista.

I have tried, using pscx.UserPreferences.ps1, to limit the number of modules imported. With the default values in that file, load time is about 110 seconds. The Net, DirectoryServices, and FileSystem modules each use 20-30 seconds of that time, but most troubling is that with ALL the modules set to false the import time is still about 20 seconds.

Remove-module takes about 10-30 seconds longer than import-module.

NOTE: Import-module with all default modules takes only a few seconds in a 64-bit Powershell window, on all the same machines and operating systems. Remove-module is likewise quite fast in a 64-bit window.

Why the big difference between 64bit and 32bit on the same machine? Is there anything that can be done to resolve this?
Comments: ** Comment from web user: schallm **

I noticed that this is a fairly old work item... Hoping that someone has a solution...

I am seeing this slow down on a Windows 2008 R2 64bit machine with PowerShell 3.0 and Pscx 3.0 installed that is a TS server. My dev machine Windows 7 64bit machine with PowerShell 3.0 and Pscx 3.0 installed loads in ~2 seconds.

Any pointers would be great.

Created Issue: Write-Zip overwriting zip files when -WhatIf is specified. [33670]

zaf0 — Wed, 16 Jan 2013 20:22:04 GMT

When using the -whatif parameter with write-zip, if there is an existing archive with the same name it is overwritten. I've included a brief transcript.

I'm running PSCX 2.1.1 under PowerShell 3.0 on Server 2008 R2.

Commented Issue: get-filetail does not work with files being used [32689]

KeithF — Thu, 10 Jan 2013 22:57:53 GMT

Hello,
 
One of the most important uses for system administration of the get-filetail command is to monitor log files, like the Windows Update log file. But this does not work:
 
PS C:\Windows\System32> tail -wait -count 10 C:\Windows\System32\LogFiles\Firewa
ll\pfirewall.log
Get-FileTail : The process cannot access 'C:\Windows\System
32\LogFiles\Firewall\pfirewall.log' because it is being used by another process
 
Line: 1 Character: 5
+ tail <<<< -wait -count 10 C:\Windows\System32\LogFiles\Firewall\pfirewall.lo
g
 + CategoryInfo : NotSpecified: (:) [Get-FileTail], IOException
 + FullyQualifiedErrorId : System.IO.IOException,Pscx.Commands.IO.GetFileTa
 ilCommand
 
(Note: actual messages in Spanish, translated by hand by me, for helping you).
 
 
In the source code of the file GetFileTailCommand.cs, we see:
 
var stream = new FileStream(filePath, FileMode.Open, FileAccess.Read, FileShare.ReadWrite)
 
 
The share mode is restricting access to files being concurrently written.
Comments: ** Comment from web user: KeithF **

I've experienced the same problem and fiddled with the source code a bit. What I discovered is that the other process generating the logs is requesting DELETE access on the log file, which get-filetail is denying.

If the line mentioned above:
var stream = new FileStream(filePath, FileMode.Open, FileAccess.Read, FileShare.ReadWrite)

is altered so that we have FileShare.ReadWrite | FileShare.Delete, it then works correctly.

I haven't tested how get-filetail will behave if a log file being is deleted while being monitored

Created Issue: Import-Module gives errors after calling Test-ModuleManifest [33639]

matty2013 — Thu, 03 Jan 2013 22:17:29 GMT

I call Test-ModuleManifest, passing in the full path to the pscx.psd1 file:

Test-ModuleManifest 'C:\Program Files (x86)\PowerShell Community Extensions\Pscx3\Pscx\Pscx.psd1'

Then I call:
Import-Module pscx

and the following errors are output:

Property 'ModulesToImport' cannot be found on this object. Make sure that it exists.
At C:\Program Files (x86)\PowerShell Community Extensions\Pscx3\pscx\pscx.psm1:141 char:11
+ $keys = @($Pscx:Preferences.ModulesToImport.Keys)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], PropertyNotFoundException
+ FullyQualifiedErrorId : PropertyNotFoundStrict

Property 'ShowModuleLoadDetails' cannot be found on this object. Make sure that it exists.
At C:\Program Files (x86)\PowerShell Community Extensions\Pscx3\pscx\pscx.psm1:142 char:5
+ if ($Pscx:Preferences.ShowModuleLoadDetails)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], PropertyNotFoundException
+ FullyQualifiedErrorId : PropertyNotFoundStrict

Property 'ShowModuleLoadDetails' cannot be found on this object. Make sure that it exists.
At C:\Program Files (x86)\PowerShell Community Extensions\Pscx3\pscx\pscx.psm1:227 char:5
+ if ($Pscx:Preferences.ShowModuleLoadDetails)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], PropertyNotFoundException
+ FullyQualifiedErrorId : PropertyNotFoundStrict

Commented Feature: ConvertTo-Metric [23611]

aaron_s — Sat, 22 Dec 2012 00:39:42 GMT

Implement a command to convert various U.S. units to metric. The first iteration will implement Length, Energy, Pressure and Mass structures. They will automatically choose the best SI unit multiple in ToString().
Any thoughts?
 
# ConvertTo-Metric [-Value] 1080 [-Unit] feet
329,184 m
 
# ConvertTo-Metric .452 in
11,480 mm
 
# ConvertTo-Metric 518 ftlb
702,313 kJ
 
# ConvertTo-Metric 21000 psi
144,789 MPa
 
# ConvertTo-Metric 200 gr
12,959 g
 
# ConvertTo-Metric 2.9 lb
1,315 kg

Comments: ** Comment from web user: aaron_s **

I like the cmdlet, but I think the types (length, mass, etc) should have a value property that returns a numeric value in SI units. That would allow me to use the length in calculations, write it to database etc.
eg
(ConvertTo-Metric 1 -Unit inch) * 5

Commented Issue: Importing Pscx breaks help [33486]

r_keith_hill — Sun, 16 Dec 2012 01:00:45 GMT

After importing PSCX then get-help is broken for any topic. e.g. PS M:\> get-help about_CommonParameters ... SEE ALSO about_Preference_Variables Write-Debug Write-Warning Write-Error Write-Verbose PS M:\> import-module pscx PS M:\> get-help about_CommonParameters Property 'HelpUri' cannot be found for type 'System.Management.Automation.CmdletBindingAttribute'. At C:\windows\system32\WindowsPowerShell\v1.0\Modules\pscx\Modules\GetHelp\Pscx.GetHelp.psm1:407 char:19 + [CmdletBinding <<<< (DefaultParameterSetName='AllUsersView', HelpUri='http://go.microsoft.com/fwlink/?LinkID=1133 16')] + CategoryInfo : InvalidOperation: (:) [], RuntimeException + FullyQualifiedErrorId : PropertyAssignmentException Note, This is for the 2.1 Production release of PSCX and occurs on both Win7 Desktop and Win2008 virtual server.
Comments: ** Comment from web user: r_keith_hill **

This is a duplicate of 33314 which has been fixed and will be made available in the next few weeks.
http://pscx.codeplex.com/workitem/33314

Commented Issue: 'less' clears the screen on exit [32522]

slumos — Tue, 11 Dec 2012 18:50:29 GMT

The less utility clears the screen when I exit. This makes it really hard to see options when using 'help', as the text disappears as soon as I quit help!
 
I tried various flags (--no-init, --dumb, --clear-screen) and none helped.
 
I am using the default console window that starts when you run powershell.exe. Windows 7 64-bit. 
 
Easy to reproduce, just type "help help", then "q" to exit. All the help disappears and your prompt returns. I would rather the text stayed in the window.
 
For now, I am setting the preference PageHelpUsingLess to false.
 
Can anyone else reproduce?

Comments: ** Comment from web user: slumos **

This must have something to do with the way that the bundled less was compiled. The --no-init switch is the usual way to prevent clearing the screen on Unix. The bundled less accepts this option ($env:LESS = "--no-init" then help help), but unfortunately mangles the text in that case.

I tried a different build of less (from DevKit bundled with RailsInstaller) like:

help help | c:\railsinstaller\devkit\bin\less --no-init

and that one works as expected.