Problem with Windows 7 and new calibre versions

[Terisa de morgan]

I think this doesn't have any sensitive information.

[Terisa de morgan]

@theducksAnyway, I'll try to start calibre (half an hour) and make that change.

@All Thank you very much for all your help.

[theducks]

Originally Posted by Terisa de morgan

I think this doesn't have any sensitive information.

Besides being in Spanish (I compared to my English version report)
all I see is:

Wow
you have a huge amount of Tunnel adapters (disconnected)

[Terisa de morgan]

Yes, I have seen it... and I don't know the reason. But it shouldn't be a problem... unless netifaces doesn't detect they are deactivated.

[PeterT]

I wonder if this hotfix might be applicable --> http://support.microsoft.com/kb/980486

[PeterT]

Also, take a look at this post / tool that describes another means to remove the multiple 6to4 adapters --> http://www.ryanvictory.com/posts/aut...val-in-windows

[FizzyWater]

It's threads like this that keep me coming back to Mobileread. I can't follow half the stuff you guys are talking about, but it's absolutely cool to see people being so bloody willing to help identify her issue with Calibre!

[Terisa de morgan]

@PeterT Thank you very much, I'll try it this evening and I'll tell the results.

[Terisa de morgan]

Thank you very much to ALL OF YOU . Through all the steps, the real problem was discovered: those tunnel interfaces, common Windows problem, that PeterT gave me the link to reach the solution: after deleting more than 700 interfaces (more than an hour ), calibre has started with no problem

[theducks]

700

I only saw a few dozen and thought that was excessive.

[cybmole]

glad it's solved, but to fix my own ignorance, even though I googled it a little: what creates a tunnel interface & how did the OP acquire 700+ of them ?

[DoctorOhh]

Originally Posted by cybmole

glad it's solved, but to fix my own ignorance, even though I googled it a little: what creates a tunnel interface & how did the OP acquire 700+ of them ?

I don't have the details but if you follow the link PeterT supplied above you should come away with some understanding of the problem.

[cybmole]

that link explains to to remove them, but not how they got there in the first place.
is this something that only happen to laptops which get connected to lots of different networks?

my desktop PC seems un-infested

[DoctorOhh]

Originally Posted by cybmole

that link explains to to remove them, but not how they got there in the first place.
is this something that only happen to laptops which get connected to lots of different networks?

my desktop PC seems un-infested

Sorry, I meant to refer to the link PeterT gave in post 50 not 51.

[BetterRed]

Originally Posted by cybmole

that link explains to to remove them, but not how they got there in the first place.
is this something that only happen to laptops which get connected to lots of different networks?

my desktop PC seems un-infested

Originally Posted by Microsoft

Consider the following scenario:

You have a computer that is running Windows 7 or Windows Server 2008 R2.
You enable the wireless Hosted Network feature to use the Virtual WiFi function on this computer.
You restart this computer without stopping the Virtual WiFi.
You start the wireless Hosted Network again.

In this scenario, a new Microsoft 6to4 adapter is unexpectedly created in Device Manager. Additionally, if you restart the computer multiple times, multiple Microsoft 6to4 adapters are created.

Every boot created more tunnels - its to do with IPv4/IPv6 on Virtual WiFi networks. Is Virtual a 'normal' configuration - I can't remember and I don't have WiFi here. Basically MS was breeding tunnel interfaces like rabbits on Terisa's computer and quantifaces was trying to get everyone of them to connect - 700 attempts on a 5sec timeout = 58 minutes. Such things are sometimes called viruses.

The larger puzzle is that this is not a new issue - the Ryan Victory blog post is May 2010; the MS one is a bit hard to work out - but at the latest it appears to be Sept 2011 - I would expect the patch to have been included in a Windows Update.

BR