Streamdevice initialization sequence

[Christian Pauly <pauly@physik.uni-wuppertal.de>]

Hi
I have a question regarding Streamdevice and the initialization of the 
hardware on ioc startup.
I would liko to control an Agilent 33250A Pulse generator using stream 
device.
In order to put the device in a well defined ground state on startup of 
the IOC, i would like to send a RESET command ("*RST") first.
Afterwards i would like to put the device in a well-defined initial 
configuration (which might be different then the reset state) by using 
the @init directive in different protocol functions (as described in the 
streamdevice docu).

The best would be, to have a separate protocoll function with @init 
section, which is only used for initial reset+configuration, and which 
is for sure processed before all others.
However, after some trying and reading the manual, i understand that the 
individual @init sections from different protocol functions are 
processed in a more or less random, non-defined order.
How can i make sure, that a "*RST" command is executed first, before 
later the individual protocol routines @init sections are used to read 
the device status into the control records
(here i dont care any more about the sequence)?

I dont want to shift all initialization into the db record definition 
using a initialization record ("PINI 1"), since then the individual 
@init sections, used to fill the records with the actual device status 
at startup, would be processed before the *RST command, and the records 
would not reflect the real device status at startup.

Is there any standard concept for this problem ?

Thanks for any advice,

Christian