I have 2 PCs here:

Old: Win2K SP4, Hummingbird Exceed 8, keyboard SGI qwerty US (very
much like a PC keyboard, except no WINDOWS and no MENU key, ie the
botton row has CTRL, ALT, SPACE, ALT, CTRL, arrows)

New: WinXP SP2, Exceed 8, PC qwerty US keyboard.

I took great care to copy the old Exceed config to the new one.

On the old PC, accelerators for a Motif app, defined as ALT+D (eg)
work fine (using the right ALT key)

On the new one, they dont and xev shows that the sequence detected is
rather nonsense:

KeyPress event, serial 22, synthetic NO, window 0xc00001,
root 0x34, subw 0x0, time 12433073, (85,123), root320,390),
state 0x0, keycode 36 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyPress event, serial 22, synthetic NO, window 0xc00001,
root 0x34, subw 0x0, time 12433073, (85,123), root320,390),
state 0x4, keycode 96 (keysym 0xffea, Alt_R), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyPress event, serial 22, synthetic NO, window 0xc00001,
root 0x34, subw 0x0, time 12434557, (85,123), root320,390),
state 0xc, keycode 39 (keysym 0x64, d), same_screen YES,
XLookupString gives 1 bytes: (04) ""
XmbLookupString gives 1 bytes: (04) ""
XFilterEvent returns: False

Believe me, at no time did I touch the CTRL key!

Does this ring any bells?

(I know: (1) ALT+ accelerators have been passe for a long time -
changing that is in the pipeline :-( (2) This sounds more like an
EXCEED than a MOTIF issue - but Motif is well known for using peculiar
ways to hook for accelerators; besides, this is about the only place
where Xt-based work is still done).