Yeah, something like that.
The previous version of the .inf network installer scripting language was an
iterative programming environment allowing direct execution of whatever you
wanted as well as direct manipulation of the registry. Now, the ,inbf
language is inference-based and I haven't figured out yet how to cause the
adapter installation AND the service installation to occur from the same
invocation of the network installer GUI.
Any insight from anyone would be appreciated.
On Sunday 28 July 2002 03:21 am, Christopher J. Oliver wrote:
> Re all,
> Given the sparsity of the Win32 installation docs (included in the
> distribution), I managed to get v2.0pre14 up and running, but not without a
> few issues.
> The included installation notes mainly pertain to NT, and indicate that
> during installation you will be prompted if you want the cipe service
> installed. Of course NT and Win2k have their differences, and therefore I
> was not asked or prompted.
> The cipe adapter installed without a hitch, but when I check the Services
> with the MMC, there was no cipe-daemon/service anywhere. I confirmed from
> the win2k.inf that all the files were installed correctly. I then had to
> manually execute "cipsrvr.exe install", which to my surprise installed the
> service, and voila it's now visible in the MMC. You are then able to use
> the MMC or command line (cipsrvr) to control the service.
> Is this how the win2k installation should work, or is this another
> something to be fixed? The docs have no win2k specifics at all.