That could well be the case, I also suspected this. They can presumably just recompile them and go, with possibly a few adjustments.

I also suspect that it's much easier to get the m68k applications to work with GVM (and maybe m68k applications are the _only_ 3party apps that are currently working, but the jury is out on this still) because m68k apps were always executed through the PACE emulator/just-in-time compiler in PalmOS5. Access would just have to modify PACE slightly so that it interfaces with the N800 Linux kernel system calls instead of the PalmOS kernel (there is actually a kernel down there in PalmOS 5, licensed from some company). Native ARM code, on the other hand, would be more tricky because compiled 3party ARM code would be geared against the PalmOS kernel and some complex intercepting would have to be done in order to get it to work correctly with the Linux kernel. Think getting Wine to work with native Windows applications on Linux, if you like. Same CPU, different operating system interface. Tricky.

I'm doing a lot of guesswork in the above, as of course I don't know what Access has actually been doing with the GVM. But this is my gut feeling as a developer.

Anyway, we'll learn more when we've all done a bit more testing..