MS Loopback Adapter not working...

[daytony32]

I have a target SBC with 2 NICs, but I have a need for an MS Loopback
Adapter as well. I added the Microsoft Loopback Adapter component to
my project, checked dependencies, rebuilt, then installed on my target,
but the loopback adapter did not show up when I looked for it using
"ipconfig /all".

Other than including the Microsoft Loopback Adapter component in my
project, is there anything else I have to do to get this working? Has
anyone else had trouble with this?

Thanks
- Tony H.

 

[KM]

Tony,

That component should be enough.

Do you see anything related in the SetupApi.log?

 

[daytony32]

I searched SetupApi.log for "msloop," "adapter," loop," "back,"
(fragments of "MS Loopback Adapter" and its associated service name)
but found no entries. Is that what I should have searched for?

I verified that the service exists with "sc query msloop." The service
seems to be in the STOPPED state.

I then tried to start the service using "net start msloop" and got the
following answer:
System error 1058 has occurred.
The service cannot be started, either because it is disabled or
because it has no enabled devices associated with it

I'm not completely sure what that means. Any suggestions?

Thanks.
- Tony H.

 

[KM]

Tony,

Any chance for you to attach the SetupApi.log and post it here?
Just wanted to take a look at it. Sometimes no easy-searchable names used while logging.

 

[Slobodan Brcin \(eMVP\)]

Daytony,

Interesting I have just looked at the component and I will be very
interested in hearing that it works. Two reason for that.
1. This mean that pure software driver can be installed trough Resources and
"Advanced Component Properties" without any "Registry Data" that prepopulate
Enum branch.
2. I have never took enough time to try to figure how bullet 1 can be done.
But in case that your driver ever start working then this component will be
a good template for me to analyze since it is very simple.

Anyhow use regedit from running XPe and give us here content of reg file
exported from following branch:
HKLM\SYSTEM\CurrentControlSet\Services\msloop

On running XPe image directly under msloop etry you should have entry called
Enum something like: Services\msloop\Enum
There we should see name of all enumerated instances in
HKLM\SYSTEM\CurrentControlSet\Enum branch.
For software drivers you should have only one of these not more not less but
one instance only.

If it is not filles by MS component then it is a bug and you must do that
manualy by adding reg entries in HKLM\SYSTEM\CurrentControlSet\Enum\Root\...

Regards,
Slobodan

 

[KM]

Yeah, good point. This is probably the reason for Tony not seeing anything related in the SetupApi.log.
The adapter is not actually connected to any physical media so not clear how PnP will handle it unless the request for install of
the INF is manually initiated.

I even guess that on XP Pro the adapter was actually installed manually:
http://support.microsoft.com/default.aspx?scid=kb;en-us;839013

 

[daytony32]

Anyhow use regedit from running XPe and give us here content of reg
file
Here are the contents of HKLM\System\CurerntControlSet\Services\MsLoop:
* Start 0x3
* Type 0x1
* ErrorControl 0x1
* ImagePath System32\Drivers\loop.sys
* Group NDIS
* DisplayName Microsoft Loopback Adapter Driver

note : I checked, and the file loop.sys exists in the right place.

There was no Enum directly under Services\Msloop, only the values
listed above. Then under ...\CurrentControlSet\Enum\Root, I saw no
names that looked like they corresponded to the msloop service.

So does this look like an installation bug? If so, are there any quick
ways I can quickly hack this into submission? For instance : I can
look at the registry "Enum" entries for the msloop service on my EP Pro
machine (which has the Loopabck Adapter installed). Could I just copy
those settings to my target? Or would you recommend I wait for an
official patch?

Thanks!

 

[KM]

Tony,

There was no Enum directly under Services\Msloop, only the values
listed above. Then under ...\CurrentControlSet\Enum\Root, I saw no
names that looked like they corresponded to the msloop service.

So does this look like an installation bug? If so, are there any quick
ways I can quickly hack this into submission? For instance : I can
look at the registry "Enum" entries for the msloop service on my EP Pro
machine (which has the Loopabck Adapter installed). Could I just copy

On the target, you can just install the netloop.inf with devcon tool, or using Device Manager (dependeing on you have got in your
image).
Then you can grab the entries that appear under the Enum branch and have them included in your Configuration in TD.

those settings to my target? Or would you recommend I wait for an official patch?

If you want to wait for a few month, you can do that.
The official QFE release takes a long time.

 

[Slobodan Brcin \(eMVP\)]

Tony,

1. Just install it as Konstantin said.
2. Fill bug report:
http://msdn.microsoft.com/embedded/community/community/feedback/feedxp/default.aspx
3. Let us know if it works when installed with devcon or "Device Manager"
what ever you have.

If it is working then installing it is like just adding few registry entries
in HKLM\SYSTEM\CurrentControlSet\Enum. Same entries as added during the
installation process.
Or you can even pass with only few entries that will initiate PnP
instalation. I can't tell you right now exactly what entries are required so
just add them all.

And no, you should not wait for MS to deal with this small isue for them.
Just install it or preinstall it and you will be ok.

Regards,
Slobodan

 

[daytony32]

First of all, thank you so much for your help thus far!

I used the following devcon command:
devcon install C:\Windows\inf\Netloop.inf *MSLOOP
And I got the following response:
Device node created. Install is complete when drivers are updated...
devcon failed.

There were no changes made to the \Services\Msloop registry branch.
But there was entry made to the \Enum\Root\Net registry branch. Just
for kicks, I tried the devcon command 2 more times and got the same
thing each time. The \Enum\Root\Net branch now has 3 entries in it
(0000, 0001, and 0002). "ipconfig /all" did not show any of the
loopback adapters I tried to install.

So the installation did some things, but failed overall.
Any suggestions?

- Tony H.

 

[daytony32]

Woops. I'm not quite sure what I did, but my loopback adapters are now
showing up! Maybe I didn't wait long enough after I rebooted before
checking for them. I'm about to go check them out now.

Thank you both very much for walking me through this!
- Tony H.