Xcopilot on Debian 2.0

1999-02-22 Thread Dan Hugo
Has anyone gotten XCopilot 0.6.6 to run on a Debian 2.0 system using a
PalmIII Rom?

I keep getting the following when I run it:


$ ./xcopilot -datadir ~/.xcopilot -romfile pilot2.rom -ramsize 2048
-memversion 2   
Bus error: read a long from undefined memory address 0x10d8


This is the binary that I built on my machine.  I also tried the debian
package and the normal intel binary from http://xcopilot.cuspy.com/
using ROMs that I downloaded with both pi-getrom and getrom2 from
pilot-link.0.9.0 (also built on my machine).

I've been reading through the code, and I can't see exactly how this is
happening (yet), but it is definitely in mc68k/memory.c.  The
scratchfile is created, the ramfile is the correct size... my guess is
that the ROM file is corrupt, but I did use two separate apps to suck
the rom out of my pilot.  I have tried a variety of command line
options, and I have read some usenet postings from people who claim to
have it working.  H.

I've only spent about an hour on this so far, but any pointers would be
appreciated.

Thanks
Dan Hugo


Re: Xcopilot on Debian 2.0

1999-02-22 Thread Dan Hugo
Note: my build does appear to work with the DEBUG Rom image from the
Palm web site, both v2.0.2 and v3.0 

I did have the 3.0.x (2 I think) update in my new ROM... perhaps this is
the problem?

Still, if anyone has any input, I would like to know, but at least I can
use it.

-dh

Dan Hugo wrote:
 
 Has anyone gotten XCopilot 0.6.6 to run on a Debian 2.0 system using a
 PalmIII Rom?
 
 I keep getting the following when I run it:
 
 $ ./xcopilot -datadir ~/.xcopilot -romfile pilot2.rom -ramsize 2048
 -memversion 2
 Bus error: read a long from undefined memory address 0x10d8
 
 This is the binary that I built on my machine.  I also tried the debian
 package and the normal intel binary from http://xcopilot.cuspy.com/
 using ROMs that I downloaded with both pi-getrom and getrom2 from
 pilot-link.0.9.0 (also built on my machine).
 
 I've been reading through the code, and I can't see exactly how this is
 happening (yet), but it is definitely in mc68k/memory.c.  The
 scratchfile is created, the ramfile is the correct size... my guess is
 that the ROM file is corrupt, but I did use two separate apps to suck
 the rom out of my pilot.  I have tried a variety of command line
 options, and I have read some usenet postings from people who claim to
 have it working.  H.
 
 I've only spent about an hour on this so far, but any pointers would be
 appreciated.
 
 Thanks
 Dan Hugo
 
 --
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null