Table of contents
No headers
Welcome to the new PoshCode wiki, brought to you by the folks behind the PoshCode script repository. We're working on some exciting new things, and thought we'd kick things off by setting up a wiki which will be fair game for any PowerShell related content. Deki Wiki is exciting because it has a great API which is accessible from PowerShell (we've already published the first set of scripts for working with it), and is really user-friendly, with a great WYSIWYG editing interface and everything.
We've already started importing the help for PowerShell Cmdlets using scripts, so please sign up and start pitching in!
Some resources you may find useful:
Comments
================
With 64bit Windows being more the norm and 32 bit applications likely to be here for a very long time its very important to understand exactly which side of the OS your script is running in.
The main reasons I can think of is
1) The DLL whether it be a COM component, .NET assembly or native code must match the address space of the process
2) Starting with Vista the Registry is divided into a 32 and 64 bit section (this will need more work) For a 32 bit COM component for instance this will be registred in the HKCR\Wow6432Node node.
3) Similarly to for Powershell. Try this in both a 32 and 64 bit shell
Get-ItemProperty HKLM:\software\Microsoft\Powershell\1\ShellIds\Microsoft.PowerShell\
Both 32 and 64 bit executables see a different view of the world. This will apply in general to both types of processes.
So for you to determine for instnace whether to look aty System32, SysWOW64, Program Files, Program Files (x86) requires you to know both whether this is a 32 or 64 bit OS as well as what shell or process you are running in.
To detect whether you are running in 32-bit environment (on x86 machine or in WOW64 process):
[intptr]::size -eq 4
To detect whether you are running on x64 machine but in 32-bit process in WOW64:
([intptr]::size -eq 4) -and (test-path env:\PROCESSOR_ARCHITEW6432)
Actually, I guess we should put it under "How do I ... detect a 64 bit machine"
1) If I where to add a "comment" to in the link above FAQ would this have put the information in the location? Other than adding a comment to a section I don't see how one is able to add a topic to the FAQ.
2) Some parts of what I said didn't make it into the FAQ when you moved it. To be specific all of the code one would add to the script is missing i.e. click on
/content/body/div/pre[1]/@function, reference to undefined name 'syntax': line 1, column 1 (click for details)
I suspect that we need some instructions on how to use this correctly because I'm assuming you have other things to do than move posts from one spot to another.