Hotsynching ROM files question.

[Bokkie]

Attached screenshot from FileZ shows a listing of some ROM files. The backup attribute is set, but it can't be changed by FileZ as you get a message that ROM files cannot be modified or deleted which is fair enough. As it is, the ROM files supposedly should be backed up if the tickbox is anything to go by, but I don't see any file on my hdd. It looks from where I sit, that there is no mechanism to get ROM only files onto my PC disk. The reason I'd like to is to try and work out how and where the QueTrip gets updated with the possible option to write an app that will write the contents to a file for hotsynching to my hdd. I suspect one of the ROM files contains the data. I'd stand a better chance of trying to hack it if I can get the ROM files to my PC, unless Garmin want to pm me and let me know where to look?;)

[JMckie]

Do you already know what the database is the database (if any) for queTrip?

[rwsmith123]

Use filez to copy the rom file to internal memory, then hotsync.

If that doesn't work, then use filez to copy the rom file to your sd card, then use a card reader to read it.

However it would be easier to write your own program to do what you want than to hack quetrip.

[Bokkie]

Originally posted by JMckie
Do you already know what the database is the database (if any) for queTrip?

No.:(

[Bokkie]

Originally posted by rwsmith123
Use filez to copy the rom file to internal memory, then hotsync.

If that doesn't work, then use filez to copy the rom file to your sd card, then use a card reader to read it.

However it would be easier to write your own program to do what you want than to hack quetrip.

Rich, I know where you are coming from. I've just done a serious clean up of the GPSInfo program and added some file writes to it. One experiment was to write a timestamp every time a GPS event occured. I let it run for a few seconds and then switched to another app for a few minutes and then I went back to GPSInfo. The file correctly showed the gap between launching the other app and then relaunching GPSInfo. If you did that whilst driving, the switchover time would translate into missing data as neither the speed or distance could be accurately retained - as I understand it.

If it was possible for a GPS event to continually fire a user defined launch code in my app whenever a GPS event ocurred than I think I'd be able to control 'background' event handling while the other app was running, as I'd still get the events even though I'm not the active or visible app. I believe this type of concept applies when database file are hotsynched - at least that's how I interpret the Palm OS documentation on launch codes.

Further comments appreciated.

[rwsmith123]

If you don't unregister for the gps events when your app stops then the app will continue to get the gps events even when you start another program.