No, there isn't; the blank white window behind the dialog is just for show, essentially. After you fill in the details (and supposing it can connect), another window (fullscreen, always-on-top) takes over, and the RDP session is in there.

[/quote]2. Since I want to use Bluetooth as my connection rather than wireless/IP, what information is rDesktop looking for in the following fields:
a.RDP server - Should I enter the PAN IP address (192.168.1.50, automatically assigned to my desktop's USB adapter by BlueSoleil bt application), or the MAC address of my desktop's USB Bluetooth adapter as RDP server? Or some other indetifier I haven't thought of? Again, since I'm not using my WLAN, it shouldn't be looking for a WLAN adress.[/quote]You say BT instead of wireless/IP; understand that IP is necessary for RDP, and BT is in fact wireless, so that's not especially meaningful I haven't used PAN, but if that's what you're using, you need both machines on the same PAN and seeing each other. Then the IP on the computer for the PAN connection is indeed what you need, but I'm only 99% sure... I use the fqdn; I don't think this strips the hostname for auth purposes, but it might.

I don't really know the significance of all this; the domain especially. The user and password are the obvious, same as you would use to log in at the console. The new username, and whatever password you set, should be fine, though I'd have used my existing account.
(Oh, and I hate usernames with strange characters; they cause unpredictable problems from apps that (brokenly) misunderstand them. If you ever make a new new user, name it something like "n800"; all lowercase, no spaces, increases the chance of sliding past any brokenness.)
My computer is on a direct internet connection, so I've got a fqdn. I use the network name (i.e. fqdn less hostname), and it works. I'm using local password authentication, no domain or workgroup relevance.

Oh, why am I writing all this... I'll test stuff.

OK, no domain needed here; leave it blank. (I think it filled mine in by stripping the hostname of the fqdn.) IP address works fine instead of fqdn.

So, assuming local auth, fill in IP for the server address, fill in username and password, and leave Domain blank.
We got VNCviewer, ya know. It is more stable than the GUI version of rdesktop you're using. There's a CLI version called rdesk around; you have to run it from xterm with command line arguments instead of filling in that initial dialog. But it is said to work consistently. The GUI one works perhaps one in three tries; changing some option (check/uncheck memory cards) seems to improve chances.
(None of that helps you get IP over BT of whatever form, of course. Until you can ping one machine from the other, it really doesn't matter what protocol you plan to use.)

There are no unhandled dependencies -- the underlying Debian package system sees to that.
For the BT side of things... you may need to install maemo-pan to get PAN support, if you haven't already. My inclination would be to use SPP (should be easy, I think), and run SLIP over that; but PAN might (I really don't know) be somehow better.

For whatever basic edit/code/hacking, shell scripts are all you should need, unless you get some compulsively-indenting monkey to do the hacking for you in python.There's the instability of the GUI rdesktop, of course, as I mentioned above, but almost certainly no faults/corruption peculiar to your machine.