Since you have an OmniGo100 debug the application on it. Here is
instructions for swatting on an actual device (this is from the omnigo
sdk faq):
Q. How can I debug my application on an actual OmniGo device?
A. There is a batch file called ss1 which will start the Swat stub
at 9600 baud. You can start the Swat stub in one of two ways:
1. Remove "geos" from the last line of the OmniGo's autoexec.bat
file. Rebooting with the new autoexec file will land you at
the DOS prompt (which is hidden behind the splash screen).
From here you can type "ss1" to launch the Swat stub or
"geos" to continue the OmniGo's normal startup.
2. To start the Swat stub during OmniGo startup:
1) Reboot the OmniGo by pressing shift-ON-next keys.
2) Hold down the 'c' key until a dialog box comes up.
It will ask "Discard all data?"
3) Press 'n' (to keep data).
4) Wait about three seconds.
5) Hit CTRL-C. This will break out of autoexec.bat.
The splash screen is still up (and will be throughout
the DOS session). Type 'y' to cancel execution of
the autoexec batch process.
6) Type the following:
mcb
cd geoworks
ss1
This will set you in b:\geoworks and run ss1.
The only catch is, on boot-up, the power driver will turn off
the on-board serial port to save power. To get around this,
after you attach with Swat, you need to do the following:
1. Hit CTRL-C to halt Swat
2. type "spawn jpwr" and "continue"
3. when Swat halts in jpwr, type "assign serialPowerStatus 3"
and then "continue"
This will cause the power driver to leave the serial port on,
and therefore you can continue to debug.
If you have trouble with the "assign" command, try copying
JPWR.SYM to JPWR.GYM in OmniGo\Driver\Power\Jedi.