GEOS version numbers and protocol numbers

diel@intbuso.boeblingen.netsurf.de
Mon, 16 Dec 96 13:12:41 -0500

There are chances that my problem with getting my device driver loaded
has to do with version numbering or protocol numbers. Therefore, I have
the following questions:
- Are there special rules with respect to version numbers and protocol
numbers of device drivers ?
For example in driver.def is the following definitions
; Protocol number for "DriverFunction" interface. All other driver
; protocols
; will be based on this number.
;
DRIVER_PROTO_MAJOR equ 2
DRIVER_PROTO_MINOR equ 0
and in the header for DR_INIT
protominor KernelDR_INITWithGeodeHandle ; etype
- What are the (standard) means to control version numbers and protocol
numbers ?
I used the -P and -R parameters of Glue to set my version number to
2.0.0.0 and my Protocol number to 2.0.
I know GREV can also be used to control version numbers, but I had
difficulties using it (see below).
- If there are special rules, what might I have done wrong ?
This is of course a difficult question. Just in case somebody has an
idea.
- What means the statement
#PROTOCONST = xxxxx
which I found in many local.mk files for drivers ?
Does it have to do with protocols and should I have similar
definitions ?
I could not find an explanation in the SDK documentation.
- GREV commands (most of them) require a "file" parameter.
Which filename do I have to use ?
The name of the .goc file does not work.
Do I need a .REF file ? If yes, how can I build one ?

Regards, Hans Diel

-- 
-----------------------------------------------------------
diel@intbuso.boeblingen.netsurf.de
-----------------------------------------------------------