Skip to main content

Featured

Health Supplements you should be taking

Hello once again! Here is a list of supplements you should likely be taking. Note that this is not medical advice, and some supplements are tolerated better by some people than others due to health / genetic factors. Generally, taking excessive amounts of supplements do not increase benefits, so stick to reasonable dosages. There is some variation between male and female in terms of requirements, I'm more familiar with male physiology and supplementing. There are some supplements I will mention that are not OTC, or are special prescription, which I may or may not take myself, and are not freely available. These supplement types are generally more expensive and less accessible, but I will discuss them also. Ideally you would start supplementing in your mid to late 20's. Most people only discover vitamins/supplements later in life when they begin to feel run-down, and by that point a lot of 'damage' has already been done to your body, which is accelerated with life
Post a Comment
Read more

Launching a Powershell script from the command-line


Launching a Powershell script from the command-line

This is assuming that Powershell is already in your path. This can be confirmed by performing:

C:\>echo %PATH%

Within that path, you should find something like this, if the Powershell executable location is missing from your PATH you should add it into into your path in Windows:

;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;

I'll often create a wrapper file (.cmd extension) called something meaningful like "launch_installer.cmd". This command file when executed, fires the Powershell command like so:

powershell -noprofile -executionpolicy bypass -command "& {C:\temp\Installer.ps1}"

You can also provide the full path to Powershell if you wish, remember that users could run different PATH variables. It's probably best to define this in it's own variable in the .cmd file if you choose that approach, and realise that you will need to update it, if ever required.

In the above example shown I've also set ExecutionPolicy to Bypass to avoid Powershell ExecutionPolicy errors, without having to actually change the ExecutionPolicy.
NoProfile tells the PowerShell console to not load the current user's profile.

-Command fires a command as if you were in the shell, in this case launching a PowerShell script with the & which instructs PowerShell to execute the command, and not to try to interpret it as a cmdlet or string.




Comments

Post a Comment

Popular Posts