Search the Community
Showing results for tags 'scancodes surface'.
Found 1 result
I was using BB to type in a Base64 encoded executable. (By the way, after start up, the BB types 1.5 times faster than Ducky) After completion I had it save to %userprofile%\mypath\myfile.mim This worked fine on a Win 7 older tower. On a new Windows Surface Book running Win 10, the save failed becasue "%" was output as "5", i.e. unshifted. Further testing demonstrated that the entire top row of number/symbol keys would not output their shifted values, no " !@#$%^&*() I need to do some more testing, but is it possible that the surface uses different scan codes? (Everything is US). Could Hypervisor make a difference? If I can figure out the corrections, maybe I can make a Lang_US_Surface as a fix, or force out key codes. Insights?