UPDATE 10/03/04
These problems have been solved by ARD2
Apple Remote Desktop 2.0 has been getting tons of positive press all over the web. Indeed it’s the slickest VNC you’ll find, with complete OSX control over remote machines and VNC control over PCs. However it’s one buggy heap of code. Aside from ridiculous limitations (such as only being able to a Linux or Winows VNC server set to Display 0), it’s got one killer bug that almost renders it useless on Powerbooks.
I’m surprised such a huge bug made it out of Apple testing. Here’s how to get ARD 2.0 to run on a Powerbook.
Before you begin, make a backup of: /Library/Preferences/SystemConfiguration/preferences.plist
Using your favorite editor (BBedit, Pico, emacs, etc.) open:
/Library/Preferences/SystemConfiguration/preferences.plist
This XML file contains all of your systems Ports and Locations. Delete everything from the file.
Launch Apple Remote Desktop 2.0. Without any Ports or Locations, the application will launch without a crash. After startup, the ARD main window will be set to network scan. Change the interface from scanning the local network to scanning a network range.
Quit ARD 2.0
Restore your original preferences.plist from the duplicate
Launch ARD 2.0. Everything works fine now, and you can set it again to scan the local network
Worked for me- however your milage may very. Happy VNCing!
"...(such as only being able to VNC a Windows PC on display 0)..."
Windows NT, XP, et. al. are not multi user OS' - as such there is only ever one session running, and in typical 'C' fashion number 1 is referred to as 0.
Dunc
when you setup a VNC server on windows (or linux) you must determine which display to serve on. ARD2.0 can only connect to display 0- a VNC server set to 1 or 2 cannot be connected to.
Setting the display controls the ports that VNC is using:
http://www.cryer.co.uk/brian/misc/port_mappings.htm
As soon as I restored the preferences.plist the Remote Desktop crashes again.