> Hand held console for comissioning some other products. At present I have
> a .sys file and a .dll that are used with the host application on a PC. As
> the Omnigo has some of the DOS components, is it possible to use any of the
> existing drivers ( .sys, .dll) that are in place at present, or should I
> forget about these all together and start from scratch with my own drivers.
.dll's will probably not get you very far, because they will require a
Windows-style protected mode environment and usually rely themselves on other
system depenedant libraries. .sys drivers can be loaded in the CONFIG.SYS of an
OmniGo, and there is some chance of getting them to work, but it will usually
require some tweaking and a number of "dirty tricks" on the side of the Geos
program (for example, DOS drivers don't know about the power management of the
OG, so an application accessing the serial port through a DOS device will have
to turn serial power on and off by directly calling the power management driver)
- - not recommended, unless you have no other choice.
A "native" Geos driver is certainly the better option.
> The other question relates to the use of the serial port. I notice the
> Omnigo platform file does not contain a reference to the stream library, so
> I am a little lost as to how I access the serial port or the serial port
> routines?
It is there anyway. :-) If you want to use a "platform omnigo" statement in your
.gp file (recommended, to make sure that library fixes in updated LDFs are taken
into account, either by causing a warning or by linking some bugfix code to your
application), you will have to add "exempt streamc" to tell Glue that it
shouldn't worry about this particular library... I haven't got a clue why this
library still hasn't made it into the official platform files.
ciao marcus