Nothing world changing. But a way to make your scripts do one thing if it's on and another if it's not... In other words, you don't need to sign the g*d d*mn fake driver, import it again and so on every time you need to do some trouble shooting since the config-file is part of the driver. *rant off* :P
Powershell:
VBS:
And yes, I'm well aware that the vbs function could be made in the same way as the powershell one by using, for an example
Set WSHShell = CreateObject("WScript.Shell")
set objEnv=WSHShell.Environment("PROCESS")
drive=(objEnv("SYSTEMDRIVE"))
But it works and I had harder things to struggle against once it was.
Коментарі