[FreeNX-kNX] Client reports keyboard dk instead of keyboard da to Windows...

[Verner Kjærsgaard]

Onsdag den 1. marts 2006 12:04 skrev Kurt Pfeifle:
> On Tuesday 28 February 2006 21:41, Verner Kjærsgaard wrote:
> > This is what I did:
> >
> > In VMware, I installed 3 machines, one MS-Windows2000 to run the client
> > from, one SuSE10 to act as the NX-server and proxy to one MS-2003
> > Terminal Server (the one onto which the client from the MS2000 machines
> > wants to connect to). I installed FreeNX version 0.4.4 on the SUSE box.
> >
> > With this setup, I was able to replicate the incorrect keyboard behavior
> > as well as the correct keyboard behavior when connecting using a linux
> > client etc.
> >
> > I then found the nxnode file (in /usr/bin/) and corrected it according to
> > the instructions given. No result. I even tried to duplicate the german
> > patch, no result. I still get the stupid [ signs when I expect danish
> > nationals instead...
> >
> > I'm about to give up now. Only, it's cost me a lot of credibility - and
> > hopefully not an entire customer.
> >
> > One bitter remark, though. I've bought quite a number of enterprise
> > licenses from NoMachine. I thought it was the proper thing to do. Also, I
> > would get 30 days or so of installation support. Well, all I got was a
> > recognized TR (Trouble Report)
>
> Is it this one:
>
>    http://www.nomachine.com/tr/view.php?id=TR02D01305
>
> ???
>
> Are you expecting miracles? Did you also take your grief to NoMachine's
> support people? Do you think that complaining *here* about it can
> change anything for the better? (In case you're in doubt: this list can
> do nothing to heal what you are now complaining about.)
>
> > and no more.
>
> I assume the fix is one the way, given that NoMachine have *publically*
> and prominently acknowledged the problem, and categorized it as
> "Severity: Serious".
>
> Just be at least as patient as you would be with Microsoft fixing their
> Terminal Server bugs.
>
> Also, don't confuse FreeNX bugs with NoMachine bugs. And don't expect
> NoMachine to fix FreeNX bugs (regardless if you pay or pay not for their
> 30 days of installation support).
>
> > That's not of much use to me or my customer.
> > What I wanted was a fix. Or a time for when it's ready.
> >
> >From what I know, this is exactly what you usually get from NoMachine
>
> if you report a problem.
>
> > I got neither.
>
> I am sure we all will be getting it; it just takes its time. Pity that
> you do not want to wait for it.
>
> > Anyhow, thank you to the list and helpers.
> >
> > Best regards,
> > Verner Kjærsgaard
> > Denmark.
>
> Kurt
> _______________________________________________

Hi Kurt and List,

Please accept my apology for being so impatient :-) I most certainly did not 
mean to upset anyone. 

I o understand (or I think so..) the difference between the excellent FreeNX 
project and NoMachine.

I'm afreid you're right, Kurt. One tends to be so incredible impatient with 
things when they don't work. What worried me - and maybe caused me to write 
in despair and anger - was that I was informed that the bug had been in the 
system since September 2005.  I thought that was a long time.

Your point with MS in spot on. In fact, I'll use it with the customer,- "if 
this was a MS bug, we'd be waiting for ever..."

Anyhow, I'm very thankfull to the people who has the skill and time to do a 
thing like FreeNX. It brings Linux quantum leaps further.

Best regards,
Verner.





-- 
------------------------------
Med venlig hilsen/Best regards
Verner Kjærsgaard