Datel Keyboard: Sticky keys, argh!!!, Anyone with a remedy? Options

[Kazicht]

Hey guys, I need some help...

I just recently recieved my Datel KB from codejunkies after waiting 2 freaken weeks for it to come and right out of the box I'm having problems...
Oftentimes, whenever I press a key it won't read unless I hit it mulitple times or jam on it real hard, causing my typing speed to slow down to a mere crawl. hell I could use the in-game KB faster then this thing *sigh*

Actually I've been able to break it down to the root of the problem; its the PS/2 to GC converter thats included with the KB thats causing this malfunction...atleast thats what I've concluded by taking the datel KB and plugging it into my PC and it works perfectly. Then I took my SONY VAIO KB and plugged it into the converter and guess what; STICKY KEYS!! Argh!!!

Anyway, I was just wondering if any of you here at AT have had this problem and if you figured out a way to get passed it. Preferably without having to buy a whole new KB altogether. Maybe a garenteed to work converter (USB or PS/2 will be fine) that I can get for cheap.

Well, any help is appreciated. Thanks.

[DivA]

perfect timing - i just received mine yesterday afternoon.. =. before i get into that, i'll say this for the record: the folks at Datel should have sold the GC adapter without the KB - blessed moon, that KB looks as if they acquired it from the manufacturer for a $1.00 - yes, folks - it's that flimsy.. =p

ok, i tested both devices & here is what i learned thus far; i'm beginning to see that perhaps some of the cross-wiring was not set properly.. example: the "=" sign is at the hyphen key when shifted.. -.O also, i'm trying to locate where the colon key actually is.. -.-

i plugged my friend's mini-keyboard into the system, that worked rather well (actually, i like that one far better than the one that came with adapter..) but the same problems arose when searching for certain symbols.. =. it should also be noted that once in a while, the Datel KB slows down - perhaps because the adapter was designed with certain limits where data transfer is concerned? =? but when i used the mini-KB, typing works fine, so perhaps it's the KB?