OK. I get it now. I have the dependency stuff for the driver right, but the
services are (potentially) started at the same time or even before driver
loading is done.
Anyone know how to coerce the OEMWinWk.inf file to set the LoadOrderGroup for
the service ?
On Tuesday 04 February 2003 11:53 am, Richard Fudge wrote:
> The 2 service dependencies referenced in the hex strings are "Tcpip" and
> "CIPE", which as I understand it means that the CIPE_Daemon will only get
> started after both the Tcpip Service and the CIPE Adaptor have been started
> ? Sounds logical to me ....
> Not sure whether the TDI Layer group is a good thing or not :-
> "Transport Driver Interface:
> TDI provides a common, accepted way for file system drivers to talk to
> The TDI is a boundary layer that provides a common programming interface
> for file system drivers"
> Guess this means that the TDI layer will be above the Networking layer, so
> the service will get started after all the networking interfaces are up. It
> is also worth noting that the DHCP Client service is also in the TDI group
> and depends on Tcpip, so I would guess that it would be ok to keep the Cipe
> Daemon there ?
> Richard Fudge
> > -----Original Message-----
> > From: Damion Wilson [mailto:dwilson,AT,ibl,DOT,bm
> > Sent: 04 February 2003 15:02
> > To: Richard Fudge
> > Cc: cipe-l,AT,inka,DOT,de
> > Subject: Re: FYI: Cipe Service start reg patch ?
> > Can anyone explain to me which dependencies those are before I
> > put them in the
> > installer script ?
> > DKW
> > On Tuesday 04 February 2003 07:52 am, you wrote:
> > > Hi,
> > >
> > > I would have sent this to the list, but I haven't subscribed to
> > it yet :)
> > > I notice that people are still having troubles with the service
> > start issue
> > > in win2k, and I myself have had this issue with every 2k machine I have
> > > tried, but after having nearly wrecked 1 of them with bad
> > registry values
> > > for CIPE_Daemon based on the info on the list from Marco Palumbi
> > > <marco.palumbi,AT,tiscali,DOT,it>, I have finally got it right with a
> > successful
> > > registry 'patch' which I use on all my 2k machines with total success
> > > so far ... It's just adds the group and 'DependsOn...' entries. I
> > > simply install this reg file after a cipe install and bingo ...
> > >
> > > Windows Registry Editor Version 5.00
> > >
> > > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CIPE_Daemon]
> > > "Group"="TDI"
> > "DependOnService"=hex(7):54,00,63,00,70,00,69,00,70,00,00,00,43,00
> > ,49,00,50
> > >, 00,\
> > > 45,00,00,00,00,00
> > > "DependOnGroup"=hex(7):00,00
> > >
> > >
> > > It works for me where it didn't before !
> > >
> > > Richard Fudge
> > > Principal Project Leader,
> > > Consultronics Europe Ltd.