Installing a Network Protocol during deployment
Jeff Reeder
Embedded device. I've successfully created the component, and it gets
loaded on the target machine just fine. However, when I go into the
networking control panel, the NetBEUI protocol doesn't show up on the
list of pre-installed protocols - I have to manually install it by
choosing "Install | Protocols | NetBEUI" from the control panel
applet. After that everything works fine.
Anybody know how to tell Target Designer to force the pre-installation
/ activation of the protocol without having to do a manual
installation every deployment? I've set the cmiIsCriticalDevice
advanced property to TRUE in the hopes that it would force the driver
to be installed as an active networking protocol, but that doesn't
happen.
Anybody got a suggestion? (aside from "don't use NetBEUI" of
course)...
Jeff Reeder
Jon Fincher (MS)
news:3c8a8a4a.02082...@posting.google.com:
> I'm working on a project where we need to use NetBEUI on an XP
> Embedded device. I've successfully created the component, and it gets
> loaded on the target machine just fine. However, when I go into the
> networking control panel, the NetBEUI protocol doesn't show up on the
> list of pre-installed protocols - I have to manually install it by
> choosing "Install | Protocols | NetBEUI" from the control panel
> applet. After that everything works fine.
I would say this negates your "successfully created the component"
statement. You may be copying the files correctly, but installing
protocol needs more than just files. Use something like SysDiff or
InCtrl5 to find out what changes are being made to your machine when you
perform the protocol installation, then make sure those changes are
reflected as resources in your component.
--
--Jon, MS
This posting is provided "AS IS" with no warranties, and confers no
rights.
Jeff Reeder
Well, I imported the .INF file that's included with the NetBEUI DLL on
the Windows XP CD, and it imports just fine into component designer
with just one warning about not understanding the "Characteristics"
entry in the .INF file. Here's the log file I get:
Info:Processing file : C:\NetBEUI\NETNBF.INF
Info:INF Importer is creating look up tables. This will take a few
minutes. Please wait...
Info:C:\NetBEUI\NETNBF.INF: type PNP device INF
Info:Creating: NetBEUI Protocol
Warning:[Install]: cannot handle key "Characteristics".
Info:Completed processing file [Import succeeded] :
C:\NetBEUI\NETNBF.INF
Here's the offending section of the .INF file:
;-------------------------------------------------------------------------
; Installation Section
;-------------------------------------------------------------------------
[Install]
AddReg=Inst_Ndi
Characteristics=0x00
;CopyFiles=CpyFiles_Sys
It makes a working component that processes just fine when doing a
build, but it doesn't pre-install the network protocol into Control
Panel. It acts just as if I copied the NBF.SYS file to the
%SYSTEMROOT%\SYSTEM32\DRIVERS\ folder, and the NETNBF.INF to the
%SYSTEMROOT%\INF\
Any thoughts?
I've done a registry diff before and after a manual installation of
the driver, and the registry changes are considerable, and difficult
to understand unless you're an experienced driver developer.
At this point, I'm starting to try to learn the .INF file format so I
can see if there's something fishy with NetBEUI's .INF file...
Any suggestions, thoughts, comments, or whatever?
Jon Fincher (MS)
> It makes a working component that processes just fine when doing a
> build, but it doesn't pre-install the network protocol into Control
> Panel. It acts just as if I copied the NBF.SYS file to the
> %SYSTEMROOT%\SYSTEM32\DRIVERS\ folder, and the NETNBF.INF to the
> %SYSTEMROOT%\INF\
>
> Any thoughts?
>
> I've done a registry diff before and after a manual installation of
> the driver, and the registry changes are considerable, and difficult
> to understand unless you're an experienced driver developer.
These are the settings you need to make this component put NetBEUI in
place just like you installed it - it's not a trivial process. Wish I
had a magic wand for you, but I don't - it's gonna be a slog.
Lucvdv
<jonfi_...@microsoft.com> wrote:
> These are the settings you need to make this component put NetBEUI in
> place just like you installed it - it's not a trivial process. Wish I
> had a magic wand for you, but I don't - it's gonna be a slog.
Other network protocols aren't "installed" by TD, the necessary files
(including INF) are copied into the target and FBA does the actual
installation.
Because some registry keys (esp. enumeration keys listing hardware
components, protocols etc.) will vary from installation to
installation, I think you must follow the same path for NetBEUI.
I just had a quick look; in the case of TCP/IP, FBA installs it by
executing this command:
%11%\snetcfg.exe -l %17%\nettcpip.inf -c p -i MS_TCPIP
You can find more information that's being passed to FBA by looking at
the "TCP/IP Networking" component in TD, go to Resources and
double-click "TCP/IP Installation | FBA Generic Command".
Additionally, TD does already pre-install a number of registry values,
but only those specific to the protocol driver in
...\System\Services\Tcpip, and not those that link the protocol to
other networking components.
Maybe this is a starting point...
Joerg Schneider
- Arguments: -l %17%\NETNBF.INF -c p -i MS_NetBEUI
- ErrorControl: 0
- FilePath: %11%\snetcfg.exe
- Flags: 0
- Phase: 3601
- Reboot: FALSE
- Start: 1
- TimeOut: 0
- Type: 1
Used files are netnbf.inf (%17%) and nbf.sys (%12%)
That's all !! Try it.
But: I have 2 adapters and both have now NetBEUI. How can I remove the
binding to one of them (netsh ??).
Joerg
"Lucvdv" <na...@null.net> schrieb im Newsbeitrag
news:v4cmmucjov4ckeaf7...@4ax.com...
Jeff Reeder
That worked beautifully!!! Thank you!!!
Now why did the rep from MS tell me there was no simple solution to my
problem? This was nice and elegant compared to manually adding the
registry entries.
Once again, thank you!
Jeff Reeder
"Joerg Schneider" <joerg.s...@de.heidelberg.nospam.de> wrote in message news:<10304430...@wienet00037.ceu.heidelberg.com>...
Jon Fincher (MS)
> Joerg,
>
> That worked beautifully!!! Thank you!!!
>
> Now why did the rep from MS tell me there was no simple solution to my
> problem? This was nice and elegant compared to manually adding the
> registry entries.
Because the MS rep didn't know that particular solution - he was still
thinking in terms of file and registry resources. :-(
We all learn new things, and the learning goes both ways - glad the
community was able to help.
Jeff Reeder
everyday" is still alive and well... Lord knows it's applying to me
in spades lately with the XPe stuff I've been assigned :)
Jeff Reeder
"Jon Fincher (MS)" <jonfi_...@microsoft.com> wrote in message news:<Xns92787B09D2712jo...@157.54.3.22>...