Page 2 of 3
Posted: 24 Feb 2010 04:02
by anotegen
I have the same problem here in Switzerland with a Dell GX280 and Keyboard S/N 3AKxxxxxxBJC
Posted: 02 Mar 2010 10:46
by anotegen
Does anyone have a solutions?
In the meantime i have this problem with 3 differents keyboards S/N ...BAA and ....BJB
Has it anything to do with a Windows Update?
What version of the keyboard driver are you using?
I have the software 5.0.4
cheers,
andy
Posted: 03 Mar 2010 12:20
by Bjarne
The primary suspect at the moment is static electricity...
Seems like you have to ground the lady ( ermm..or dude ) behind the keyboard somehow ;0)
Posted: 05 Mar 2010 02:24
by Eliott
Explain this to a "lady" behind a welcome desk / reception which moves around the whole day.
A pad on the floor caused no improvement for my customer.
And it's not possible to explain to the customer that the staff has to wear special clothing and the carpets and chairs have to be replaced...
A comment of one our customers was that it is maybe better to replace the Alcatel-Lucent system by another one e.g. Siemens after several months of heavy disturbance without any improvement.
Posted: 16 Mar 2010 15:00
by Eliott
Problem was fixed in one site now. We replaced the chair. (no joke)
It was reproducible when sit down on the chair.
Posted: 16 Mar 2010 19:30
by knightrider
very slightly off topic but still related...
Many years ago we had a problem on a site using an SDX (latterly known as Avaya IP Office) system where always one user (a pretty youg lady) kept blowing the board her phone was connected to. My boss got so pissed off one day he told me to tell her to go change her knickers because she must be wearing some nylon ones or something. Anyway - after she left the company - the problem went away - 8 boards later (32 port Digital board)!!!
so, moral of that story - you guys better start checking these chicks knickers out
)
Posted: 17 Mar 2010 00:56
by Bjarne
Lets just hope that ALU comes up with a knicker-proof keyboard then, labeled and all
If the solution turns out to be down to new hardware it will be quite interesting to see if ALU replace the existing ones for free...
Posted: 19 Mar 2010 12:01
by mninghetto
Hi everybody,
I opened a case for the problem "ThreadWaitkbdNotif IOCTL_KEYBOARD_PAC_GET_KEY_INFO failled 5" two weeks ago. This problem is a main issue at Alcatel - Lucent. Observation sheet is created. Here is the official answer from R&D site.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Currently we’ve found a potential workaround that consist to use an USB hub without external power supply between the PC and the 4059 Keyboard; please try it on your customer site.
This workaround is applied on a customer site and it solves the issue up to 90%.
Be careful HUB must be USB Powered, not Self Powered.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Posted: 08 Apr 2010 10:53
by anotegen
there is a USB Keyboard Patch out there for version 5.1.5
just installed it. will report back if successfull
Posted: 09 Apr 2010 01:02
by Reinoud
anotegen wrote:there is a USB Keyboard Patch out there for version 5.1.5
just installed it. will report back if successfull
I have the same patch, but because it is a hardware problem it doesn't solve the root cause. It reinitializes the driver in some way that the keyboard is found again. Unfortunately I use sourcetech operator software, which talks directly to the driver, and the patch does not apply for sourcetech.
At the other hand, because I do use the sourcetech software, the customer is able to use an ordinary keyboard making this issue less urgent.