Re: Powerbook G4 problems

[Patrick Scott <pscott@xxxxxxxxxxxxxxx>]

Title: Re: Powerbook G4 problems

Mike - 

I used the 1.1.0 version and XFree86 Xdarwin binaries (woohoo! Easy = good!). Works fine for me – even the keyboard problem.

What OS X version, etc? I’ll try to help!
> From: Mike Ely <mike.ely@phoenix.k12.or.us>
> Date: Wed, 03 Apr 2002 11:08:48 -0800
> To: Jason Cwik <jason@ancept.com>, <rdesktop@rdesktop.org>
> Subject: Re: Powerbook G4 problems

> I have a question:  where are the latest patches?  When I use the base 1.1.0 source, it compiles fine, but when I use 1.0.0, or the unified patch 19-8-5, I can’t compile.  I get most of a page of the following error: rdesktop.c:62: bad macro argument list
> Then, in the middle of multiple lines of the above error, I get: rdesktop.c:580: illegal statement, missing `;’ after `)’
> Then: cpp-precomp: warning: errors during smart preprocessing, retrying in basic mode
> And it finally exits with error code 1.
> This is on OS X with the current dev tools updates (ln –s /usr/bin/gcc /usr/bin/cc) and XFree86 4.2.0.  I love rdesktop on my linux machine, but the OS X box is my laptop.  Maybe we can figure out what’s going on here?  I’d love to help.
>
> BTW, the –N switch isn’t available in the only version I can compile.
>
> Quoth "Jason Cwik" <jason@ancept.com> On 4/2/02 3:08 PM:
>
> > Just to clear this up for everyone- 
> >
> > Rdesktop 1.0.0 and 1.1.0 pass the X KeyCode from your keyboard directly to the terminal server with only a couple of fixups.  On XFree86, this is fine because the KeyCode and the Windows scancode match up pretty well.  On other X servers the codes are all different, that's why you get a really messed up keyboard.  This is also why you get the same problem even when running rdesktop on a PC but displaying remotely to a non-PC.
> >
> > The -N introduced in the latest patches takes the KeyCode and looks up the X KeySym for the key.  The KeySym is an abstract label for a key, e.g. "F1".  Then it takes the KeySym and maps it to the PC scancode.
> >
> > The patch I posted earlier is a hack to put similar functionality into 1.1.0 for those of us who have problems compiling the latest patches..