I'm trying to write a code that "blinks" the lock key leds really fast (using -comObject to sendkeys). The code run really slow on Powershell (from CMD) and miss some keypress, but seems to work great on Powershell_ise.
The code reads a file to binary and then transfer each bit to num/scroll lock. This needs to run really fast - as fast as I can.
This is the code:
$wsh = New-Object -ComObject "WScript.Shell"
$bytes = [Byte[]] (Get-Content $env:temp\temp1536.txt -Encoding Byte -ReadCount 0) | ForEach-Object {[System.Convert]::ToString($_,2)}
##($i=0; $i -le $byte.length; $i++){
foreach ($byte in $bytes) {
#$byte;
while($byte.length -ne 1 ){
if($byte[1] -eq '1'){
#echo "1";
$wsh.SendKeys('{SCROLLLOCK}');
[System.Threading.Thread]::Sleep(40);
$wsh.SendKeys('{SCROLLLOCK}');
} Else {
#echo "0";
$wsh.SendKeys('{NUMLOCK}');
[System.Threading.Thread]::Sleep(40);
$wsh.SendKeys('{NUMLOCK}');
}
$byte=$byte.Substring(1);
[System.Threading.Thread]::Sleep(50);
}
#echo " ";
#echo "1";
$wsh.SendKeys('{CAPSLOCK}');
[System.Threading.Thread]::Sleep(55);
$wsh.SendKeys('{CAPSLOCK}');
[System.Threading.Thread]::Sleep(20);
}
Anyone knows why this happens?
EDIT: I added a video showing the lag of the lock key blinking on Powershell Console Vs. Powershell_ISE http://youtu.be/OnOmr50OBhs
I tried this on Powershell V3.0/4.0 on Windows 7
I used this text file name -'temp1536.txt' in %temp% folder The file is imported to binary and then light the led accordingly.
$bytes = [Byte[]] (Get-Content $env:temp\temp1536.txt -Encoding Byte -ReadCount 0) | ForEach-Object {[System.Convert]::ToString($_,2)}
I couldn't get your code working (it never steps into if($byte[1] -eq '1')
), but here is the version using keybd_event \\ GetKeyState Win32 API that works fine in my ISE and console. Adapted from code posted here .
$Keyboard = @'
using System.Runtime.InteropServices;
namespace My
{
public class Keyboard
{
private const byte VK_SCROLL = 0x91;
private const byte VK_NUMLOCK = 0x90;
private const byte VK_CAPITAL = 0x14;
private const uint KEYEVENTF_KEYUP = 0x2;
[DllImport("user32.dll", EntryPoint = "keybd_event", SetLastError = true)]
static extern void keybd_event(byte bVk, byte bScan, uint dwFlags, uint dwExtraInfo);
[DllImport("user32.dll", EntryPoint = "GetKeyState", SetLastError = true)]
static extern short GetKeyState(uint nVirtKey);
// SCROLLLOCK
public static void SetScrollLockKey(bool newState)
{
bool scrollLockSet = GetKeyState(VK_SCROLL) != 0;
if (scrollLockSet != newState)
{
keybd_event(VK_SCROLL, 0, 0, 0);
keybd_event(VK_SCROLL, 0, KEYEVENTF_KEYUP, 0);
}
}
public static bool GetScrollLockState()
{
return GetKeyState(VK_SCROLL) != 0;
}
// NUMLOCK
public static void SetNumLockKey(bool newState)
{
bool scrollLockSet = GetKeyState(VK_NUMLOCK) != 0;
if (scrollLockSet != newState)
{
keybd_event(VK_NUMLOCK, 0, 0, 0);
keybd_event(VK_NUMLOCK, 0, KEYEVENTF_KEYUP, 0);
}
}
public static bool GetNumLockState()
{
return GetKeyState(VK_NUMLOCK) != 0;
}
// CAPSLOCK
public static void SetCapsLockKey(bool newState)
{
bool scrollLockSet = GetKeyState(VK_NUMLOCK) != 0;
if (scrollLockSet != newState)
{
keybd_event(VK_CAPITAL, 0, 0, 0);
keybd_event(VK_CAPITAL, 0, KEYEVENTF_KEYUP, 0);
}
}
public static bool GetCapsLockState()
{
return GetKeyState(VK_CAPITAL) != 0;
}
}
}
'@
Add-Type -TypeDefinition $Keyboard -ErrorAction Stop
$Bytes = Get-Content -Path '.\led.txt' -Encoding Byte
foreach ($byte in $Bytes) {
if($byte)
{
[My.Keyboard]::SetScrollLockKey($true)
[System.Threading.Thread]::Sleep(40)
[My.Keyboard]::SetScrollLockKey($false)
}
else
{
[My.Keyboard]::SetNumLockKey($true)
[System.Threading.Thread]::Sleep(40)
[My.Keyboard]::SetNumLockKey($false)
}
[My.Keyboard]::SetCapsLockKey($true)
[System.Threading.Thread]::Sleep(55)
[My.Keyboard]::SetNumLockKey($false)
[System.Threading.Thread]::Sleep(20)
}
It seems to be a problem in some PCs only. Can't really understand why. But I got it to work fine on some computers.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.