looks like a "cool tool". I just tried it on the firebee:
after entering an address, the program crashes because of fmovem instruction. Can you compile a version without usage of hardware floating point requirements? Or maybe a coldfire version? But just keeping out the hardware floating point stuff should be OK...
So I restarted the application. Just selecting "Sattelite" or "Road Map" results in an bad request - probably because the longitude / latitude isn't set to an good value. The response isn't handled properly and the applications hangs ( I believe this isn't an firebee problem, but because the program doesn't do error checking? ).
Edit: It doesn't really hangs, but it times out....
Thanks for trying it out on the FireBee. I wondered how it will behave on a FireBee, now I know.
I wish I have a Firebee to try the program on, trying to save EUR 700
May be I sell one of my system.
The lat/lng values are set to zero on init. So it should go to somewhere in the Atlantic ocean. But I will check this out. Thanks for pointing it out.
Yes, it does looks like hanging during long network access. I tried using that tfork() function you mentioned in another posting, it works in non-memory protection mode (synctime uses it) but crashes on memory protection. So I did not use tfork() for the rest of my programs. This is a good excuse to re-look at Synctime, just to get threading working again on it.