This is release v0.6.5 of XCopilot (12-Aug-98)	    This release was done by Gene McCulley <mcculley@cuspy.com>.  The last"official" release from Ivan Curtis was v0.2. Release v0.3b was aninterim release by Jeff Dionne.  A lot of stuff was added in thev0.4-iang series by Ian Goldberg <iang@cs.berkeley.edu>.Please note that this is still very ALPHA software, so expectproblems. Please send me any bug reports (or better yet, fixes) youdiscover.Thanks to Kresten Krab Thorup <krab@daimi.aau.dk> for the endian patchesThanks to Andrew Pfiffer <andyp@co.intel.com> for 16bpp and keyboard patchesBuilding========Building should be straightforward. You will need the Xpm and XextlibrariesIn the xcopilot-vxx directory, do./configuremakethis will make the libmc68k.a library in the mc68k directory, libmx inthe mx directory, and leave the executable xcopilot in the currentdirectory.Running=======You will need a Pilot rom image file installed in ~/.xcopilot as"pilot.rom". Please see the original copilot documentation for detailson how to get this file.doxcopilot -u for a brief command line synopsis.The emulated serial port can be hooked to any device.  eg. if yourmodem is on /dev/cua1, then doxcopilot -serial /dev/cua1Debugging=========To enable debug mode, run with the command switch -debug.  This willstart the debugger listening to socket port number 2000. To connect tothe debugger, use telnet e.g.telnet localhost 2000The debugger starts with the cpu stopped. You must explicitly startthe cpu for anything to happen (use the "start" command).You should not issue the "load" command until after the welcome screenhas gone away.Since the ram state is saved from run to run, once an app is loaded itpersists until deleted, or the pilot.ram file is removed.In this version, the -debug flag is deprecated.  You should really beusing the -gdebug flag, described below.Potential problems==================  * The default ram size is 1MB.  This can be changed by using the    -ramsize option, but be careful as you don't want to use a RAM    file for the wrong size.  * Some systems don't have the ftruncate function. There is a crude    ftruncate function in memory.c, but I think it clobbers the file    as well as truncating it. You might want to find a better ftruncate   (or get a libc with more functionality)  * The debugger uses port 2000 by default. If this port is not good for you,    the port number can be changed by changing the symbol DEBUG_PORTNUM    in main.c  * Applications larger than 64k will not load.  If you want to    install larger databases or apps, hotsync them over.  Use:      xcopilot -serial /dev/ptyqe    and in another window:      pilot-xfer /dev/ttyqe -i hugefile.pdb  * X shm should be auto-detected.  People have had problems with the    X shared memory extensions. If you have problems running from a    remote CPU, try using the -noxshm to option.  * People have had problems with the pixmap code. This could be    because I am using an older version of Xpm than most people. If    you have problems, check the code in display.c and the docs for    your version of xpm. Shortcomings============Debugging, breakpointing, tracing support is still very rudimentary.Expect more in the next release.I have developed this under i386-linux and SunOS 4.1.1, so there maybe some portability problems, which I will rely on others to pointout.I would like to coordinate further efforts on this port (certainly Iwill be continuing work on it), so if anyone else out there would liketo help out, please contact me.Anyone interested in modifying this code will benefit from studyingGreg Hewgill's copilot sources, which will need to be obtainedseparately.Ivan Curtisicurtis@radlogic.com.auLoading Databases and Programs, and Quitting xcopilot=====================================================Holding down the right mouse button while pointing to the xcopilot windowwill bring up a little menu.  Drag the pointer to the item of choice andrelease the button to select it.  Here are the options in the menu:Load database...   This will bring up a menu of the .prc (resource databases or programs),   .pdb (regular databases), and directories in your current directory   (as well as ..).  Choosing a directory will bring up a similar menu   for that directory, etc.  Choosing a .pdb or .prc file will cause   that database or program to be installed.  You can click on the title   bar of the menu ("Select File") to cancel the operation.  Note that   if you are installing a program, an older version of that same   program should not be running at the time (nor should the   "Applications" screen).  Also, the xcopilot should not be "off", and it   should not be still displaying its title screen.  Databases and   programs that can be installed via this menu are limited in size to   just under 64K.  If you need to install a larger database, use   pilot-xfer to install it, as outlined in a previous section.   If you are using a Palm III ROM, make sure to set the memversion to "2",   either using the "-memversion 2" option, or by setting the   XCOPILOTMEMVERSION environment variable to "2".  If you do not do this,   the Load database... command will not work at all.  If you do this,   however, it should be able to load databases larger than 64K.Load file...   This is just like the previous menu option, but it lists all files, not   just .prc and .pdb files.  This is useful in case you named your database   or program with an odd name.About...   This just shows some version and credit information.Quit   Choosing this option is the recommended way to quit xcopilot.Debugging with gdb==================If you compile a program with gcc, and link it with the -g flag, then youcan debug the program on xcopilot in the same way as on the real Pilot,but with the added advantage that the debugger doesn't take up the serialport (so you can debug serial and TCP/IP apps!).Start xcopilot with the -serial and -gdebug options:  xcopilot -serial [/dev/ptyqe] -gdebug [/dev/ptyqf]The arguments to these options are the ptys to which to attach; the defaultsare shown above.  Make sure you have the "gdb panel" app installed on thexcopilot; it comes with prctools,and you can install it, as with any appsmaller than 64K, with the menu on the right mouse button.  Install yourprogram as well.In another window, run:  m68k-palmos-coff-gdb prognameNote that you don't enter the .prc suffix here.  You will be given a gdbprompt, where you enter:  target pilot /dev/ttyqfNote that you use "ttyqf" here, whereas you used "ptyqf" in the xcopilotcommand line.  Of course, if you used something else there, make theappropriate change here.On xcopilot, run the "gdb panel" app and turn on gdb debugging.  Then runyour app.  gdb will stop your program at its beginning.  You can then setother breakpoints, and continue.Release Notes=============Version 0.4 changes:  * support for BIG endian machines  * support for 16bpp displays (only on little endian machines, although it    will be easy for someone with a big endian 16bpp machine to add that).  * menu user interface allows loading of .prc files without the debugger  * keyboard input  * working serial port  * debug via a socketVersion v0.4-iang changes:o Support for Palm Pilot Pro added   To use it, set the environment variable XCOPILOTROM to point to your   (1MB) Palm Pilot ROM (not included).  Alternately, if you never want   to simulate an old Pilot, just name the new ROM "pilot.rom".o Logging of flow traces   From the debug prompt ("xcopilot -debug"), "log on" and "log off" will   toggle logging of major changes in the PC (program counter).  This will   catch function calls, traps, and returns, but not conditional branches.o Improved sound support   Instead of just beeping, the correct frequency/duration/amplitude is used.o Parameter changes   The default RAM size is now 1024K, the scratch space is 64K, and   the time between screen updates is 1/20 second.Version 0.4-iang2 changes:o Support for debugging programs with gdb   To use it, run   xcopilot -gdebug /dev/ptyqf   You can, of course, choose a different pty.  You can also just say   xcopilot -gdebug   to default to ptyqf.  Then, from gdb, do