[FreeNX-kNX] Windows 98 Compatability

Kurt Pfeifle k1pfeifle at gmx.net
Sun Nov 6 21:24:12 UTC 2005


On Sunday 06 November 2005 18:52, Steve Bergman wrote:

> If you want a good laugh sometime, do this:  While keeping the idea 
> "It's not our fullt; NX is perfection itself!" firmly in mind, go read 
> their entire knowledge base.  Its a hoot.

Ok. Let's test it. I'll pick one random item from the NoMachine
Knowledge Base, and quote it fully. I happened to come across
this one (http://www.nomachine.com/tr/view.php?id=TR10C01042):


----------------  snip  --------------------------------------------

         Trouble Report:  #TR10C01042
               Added on:  2005-10-11
          Last Modified:  2005-10-12
                Product:  NX Core
              Affecting:  1.5.0
               Platform:  All MacOS/X Platforms
               Severity:  Serious
                 Status:  Open
              Opened by:  Marcello Blancasio
  Technical Responsible:  Gian Filippo Pinzari

The keyboard doesn't work properly when a X11 session is migrated 
from a x86 platform to Mac OS X and vice versa.
--------------------------------------------------------------------

When a X11 session is started on a x86 platform (e.g. Windows or 
Linux) and then resumed on a Mac platform, typing on the keyboard 
doesn't produce the expected characters. It's the same also when 
the session is started on Mac and then migrated on a different 
platform. 

This problem is due to the different keycodes used on x86 and Apple 
platforms. For example, on a x86 platform, when the user presses the 
'a' key, the X server sends an event with keycode 38, and the keymap 
used by the X11 agent permits of translating from keycode 38 to 
symbol 'a'. If the session is resumed on Mac and the user presses 
again the 'a' key, the X server sends an event with keycode 8, but 
the keymap still associates 'a' to keycode 38 and a different 
character is provided. 

Notes
-----
The keyboard doesn't work properly when a X11 session is migrated 
from a x86 platform to Mac OS X and vice versa.

Provided Solution
-----------------
        Date: 2005-10-11
  Handled by: Silvia Regis

Every time a session is resumed, the nxagent component should 
reset the keyboard device and initialize it with a new keymap, 
aligned with the platform of the remote display.

----------------  snip  --------------------------------------------


So, Steve Bergman:

which sentence gave you a good laugh? The fact that they qualified
the problem as "serious"?

Which of above sentences sound like a "defensive answer" to you?
The one explaining the different key mappings of Apple and x86
platforms to the casual reader with a concrete example?

Steve Bergman, 

your contribution was pure FUD and trolling. Continue like that
and your next messages will be ignored by everyone who could
possibly help you if you had a serious problem (other than "my
weekend is boring, this mailing list is too deed -- let's probe
if there is someone to feed a Troll")



More information about the FreeNX-kNX mailing list