You won't need that for zaurus. It's "human interface device", used to control your computer with exotic mice or remotes. Remove "HIDInterface.cpp" from the Makefile and any references (includes) to that unit.

Make sure the Makefile includes Simulator.cpp , WindowContext.cpp. See what other symbols are missing, do a grep in src/Orbiter and see what cpp files implement these missing functions and add them to the Makefile.

I'm not sure about this one, but it might be related to the first one. This happens when orbiter sends a message with confirmation to a device/plugin and that device doesn't respond. You could compare DCERouter.log when this happens and see what is the problem.

Orbiter should download from core the configuration file and then parse it (in DCERouter you should see a "Request File And Checksum" command). If you don't see it, it might be a problem with X11 commands, like those for window controller. You can deactivate them by typing a return at the beginning of WinListManager::ApplyContext from src/Orbiter/Linux/win_list_manager.cpp. Also, you can compile it with -DDEBUG to get more info.If none of these helps you, use gdb -p <pid_of_orbiter> to find out more.

We'll need to investigate this. Maybe it's a serialization problem, we'll have to find. Going with small steps, we'll have to compile MessageSend tool (src/MessageSend) which does nothing else but to send a command to the router. After compiling it, on zaurus, run it with the following arguments:./MessageSend dcerouter -r -o 0 7 1 688

Let me know if this works and also send me the lines of log from router when this happens.