[BugReport] Keyboard Issue

[webdirector]

I am a little frustrated that nothing is happening to solve this keymap issue of the Ducky.

It would be a great product but at the moment I can't use it because of this.

I hope this gets fixed soon.

Some guys started work on German keyboard but that has stopped and they encode it to German (IBM) but most used keyboard is German (standard)

If not I have a very expensive light weight brick ;-)

I hope that the developers pick this up and find a solution.

Edited March 7, 2012 by webdirector

[NetFalcon]

Hey,

i just bought a ducky (really seconds ago) and will be developing for German standart. (If by the time the ducky arrives, its not yet completed.

What keys are currently not working ?

regards

[NetFalcon]

Hey,

i just bought a ducky (really seconds ago) and will be developing for German standart. (If by the time the ducky arrives, its not yet completed.

What keys are currently not working ?

regards

Weird, that i cant edit.

I dont have a ducky so, maybe I'm missing the point.

What happens when switching the keyboard layout. EN is preinstalled on my laptop with DE Layout. And switching would be quite easy.

GUI r

STRING Rundll32 Shell32.dll,Control_RunDLL Intl.cpl,,2

ENTER

ENTER

DOWN

ENTER

ALT+F4 // dont know if that is even right

but any new console etc then as standart has an english layout

or, am I missing the point and the issue can only be fixed inside the encoder (or firmware)?

[NetFalcon]

What i also dont get, you could tr to modify the encoder yourself ?!

take a look at the uk enoder:

			case ' ':
				return 0x2C;
			case '!':
				return 0x1e;
			case '"':
				return 0x1f;
			case '£':
				return 0x20;
			case '$':
				return 0x21;

and now the german beta from Snake & PCFreak

			switch (c) {
			case 'y':
			case 'Y':
				return 0x1D;
			case 'z':
			case 'Z':
				return 0x1C;
			case ' ':
				return 0x2C;
			case '°':
				return 0x35;
			case '^':
				return 0x35;
			case '!':
				return 0x1e;
			case '"':
				return 0x1f;
			case '\\':
			case 'ß':
			case '?':
				return 0x2d;

So for every Key e.g. case '?' - it would be nice to find the corresponding Hex Value e.g. (0x2d) (0x does only mean its a Hex Value - explain it at the bottom)

And in both decoders they try to find them: e.g. ß in the german has no hex value (there's none ? / they couldnt find it)

So "all" you have to do is: find the corresponding Hex Value for your keyboard (sadly theres also the chance that theres none)

So you make a test file (like the bart simpson) and the change some of the hex values and find some that fit your keybord.

you can do it the hard way by trying it:

case '?':
				return 0x20;

then

case '?':
				return 0x21;

then

case '?':
				return 0x22;

until you find it... (as i said, maybe theres no corresponding hex value - but maybe you should try anyways)

btw: hex value range:

0-9 then A-F

so 0-F:

e.g.

0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F
11,12,13,14,15,16,17,18,19,1A,1B,1C,1D,1E,1F
31,32,..,3A,3B...
A1,A2,..,AA,AB

in this case there is hex value = write

0x

in front of it

e.g.

0x1D

regards

Edited March 7, 2012 by NetFalcon

[webdirector]

Hi,

I also thought it would be that easy.

But I used Snakes German IBM on my Backtrack machine and encoded and the result you can see here

You can see below (The Bart simpson picture) where I posted the output.

So you can see it is not working for me ( see the Y is Z and so on)

I was looking at the UK and German Java files and there are some more differences.

But if you want I would be willing to support you in anyway I can

Rgds