"Ethernet" Connection Drop

Digger said:

your 7000 reg compared to 7100 reg pre Tweak7 tweaks, with Tweak 7 tweaks, and after tweak7 reset default.

Making a SINGLE image of the registry can take 1/2 an hour.
You want me to make 5?
These files are 30-50megabytes each digger.
Plus i don't have my beta 7000 instal anymore, i deleted it's partition and re-created it for 7100 RC1.

7100 reg pre-tweak 7 is impossible now unless i were to format and re-install W7 - something i'm not inclined to do just to grab a couple of lines from the registry.

I can however link YOU to the program and YOU can make an image of your own registry. That will give you a great starting point.
From there you can tweak 7, make another image
then "un" tweak 7.
However, then it'll probably take quite litterally, months for you to pour through the 30,000 odd lines of text that make up the windows registry.

An Alternative option is to export your whole registry in regedit before making any changes.
Then set Kaspersky to monitor registry changes.
Then Tweak 7, check kasperskys' logs and view the changed registry locations.
Then "Un" Tweak 7 and again, check kasperskys' logs and view the changed registry locations.

sexytool said:

Making a SINGLE image of the registry can take 1/2 an hour.
You want me to make 5?
These files are 30-50megabytes each digger.
Plus i don't have my beta 7000 instal anymore, i deleted it's partition and re-created it for 7100 RC1.

7100 reg pre-tweak 7 is impossible now unless i were to format and re-install W7 - something i'm not inclined to do just to grab a couple of lines from the registry.

I can however link YOU to the program and YOU can make an image of your own registry. That will give you a great starting point.
From there you can tweak 7, make another image
then "un" tweak 7.
However, then it'll probably take quite litterally, months for you to pour through the 30,000 odd lines of text that make up the windows registry.

An Alternative option is to export your whole registry in regedit before making any changes.
Then set Kaspersky to monitor registry changes.
Then Tweak 7, check kasperskys' logs and view the changed registry locations.
Then "Un" Tweak 7 and again, check kasperskys' logs and view the changed registry locations.

dude, seriously... get up, walk around some... have a smoke or something....lol. i said all that in my last post in gest. Yes, thats what i would need, but i wouldnt have expected you to think about doing so unless you were very highly enthused about what it is and what and how to solve. I didnt expect that at all. I just dont like not knowing why something is the way it is.... i rarely take things at face value.

fyi, shouldnt take a 1/2 hour, it would just be a reg backup, couple minutes tops... you arent saving it to a floppy drive, lol...unless that registry has overgrown itself from XP.. but anyways, i am calling it a day, a full day... later on.

You wouldnt have to pour thru the registry if you know what to look for, and all you would do is to compare the reg files, searching for any differences. programs out there to do this. also programs that monitor the registry for the hyper-paranoid type. I'm no guru, but i've been around the reg block a time or two.

Oh, yea, and your kas i just seen you mention, may be one of the causes of your problems as this is a bear of a program. Just search around on the security forum for kas and the problems found. Even I had issues with it, tho i admit, this WAS an install on 7000. I have turned my back to them since, and not installed on the RC. Maybe thats your problem, get rid of that thing and install Avast!

Nah i'm right thx :)
I've been administrating networks since before i could drive.
Before i finished year 10 i knew the ins and outs of DoS and Win95 + 98 networking lol.

I've got a fair bit of experience up my sleeve by now, so usually any problem i run into, i can fix.

If it ever gets to that stage, i'm not affraid to just go "Ah f**k it!" and format it.

Sometimes a full format is a faster resolution XD

guys.. getting too technical ow.. is there any way i could boot up into windows vista now? i just need a stable connection!!

well, there is really no need to do much testing anymore. Guys this is all driver based. Non compatible drivers. You may find one thats maybe 80% compatible, but not 100%

Case in point: The Red X

Now i came into this thread becuase of this, and also just to see if and what similarities there were between the two, keeping in the back of my mind the overall driver concern. Now, I have found that both the wireless AND wired act the exact same way in appearance.

For example, with my wireless connection and the rex X, I found that unticking "connect automatically" and connecting manually each time "made the asterix and the X disappear". I just ran some initial driver testing on the ethernet, having the wireless situation in mind, and what do you know.... I have found that they all act in a similar fashion.

If i disable the network adapter ( causing it to not be enabled therefore not trying to connect and identify itself on the network at startup/boot like i had the wireless set to not connect auto) before i rebooted, then reboot, then come back to the desktop ( you will see the network icon trying to identify with the circle/busy icon) and then enable the ethernet adapter in question, and voila, dinner is served, no red X, everything atleast LOOKS good to go. Tho in actuality, this doesnt solve the whole issue of having a correct driver.

No matter what driver i have tried to installed, be it W7, chipset manufacturer, MB manufacturer. No matter what comp mode. I always get the same results, and find that it only enables/shows the controller as 10/100 instead of 10/100/1000. So just right there i know i driving down the road with two flat tires. Like i keep stating and repeating, this is a driver issue first and foremost, and until that is addressed, any other problems can then be fixed. But if you take a look around, not everyone is having these issues, its about 50/50 i'd say. Ones whom have a correct working driver for their ethernet/wireless will not see these effects/problems and results.

really no need to do any kind of network testing at all, be it lan or wan, when its going to be a hit and miss issue of connectivity. Like i also keep repeating, my drops/connectivity were never part of some pattern, it was all very random, as i have found that to be the case here for most ppl in this thread, especially the actual creator of this thread tongteh.

now to satisfy and rectify someone's urging me of this reset to default setting of the program tweak7... ahem.... did nothing....no good at all. Why maybe others ask? Thats because i never used it in the first place to change any variables/settings that would have and did ultimately cause problems for someone by doing so, and the FIX FOR THAT was to reset back to windows 7 defaults.

This may affect the browser and a few other settings if tweaked and played around with, who knows, you would have to closely watch the registry. Maybe an install of tea timer, but i had a bugger or two with that on 7000 so i tossed it. But by overall, this program, atleast with those specific page tweaks7 you are referring to,( as there may be others that affect different properties of hardware, like cpu tweak, gpu tweaks and so on) is not tweaking the chipset to work with the given driver thats not a true working driver in the first place.

If you thought this was the fix all, how come the entire sevenforum.com community hasnt came in here to back up your claim? One reason being is that like i said, 50% guesstimation doesnt have this issue as they have a correct working driver. And the other 50% in this thread didnt all use Tweak7 to change any settings, atleast they arent speaking up. Changes may have been done, like myself, thru the driver advanced properties tab. And maybe 1% made some manual registry changes. Cant you clue in here a little? I think you are a little arrogant and presumtious yourself that your answer could be and is the holy grail, when common sense tells a different story.

My overall explantion is this, 90% of ppl with ethernet cards 1.5 years or newer have a correct working driver. Its the older and freakish chipsets that have been coming into this thread (with maybe a 10% exception) and reporting problems, the same problems.

Buddy, you've never even told us what your NIC *IS*, so how are we supposed to use our good judgement to determine wether it's an NIC problem or a registry problem, if you don't give us the information required for us to diagnose your problem?

You said your NIC has Vista support + drivers so the automatic assumption is it's less than 1.5 years old and should work fine under W7.

You put yourself in this position by not handing out the correct information to begin with =/

EDIT: And the information you HAVE given us, is very errornous. Your K8N-SLI deluxe does NOT use a Marvell 88E8111 Gigabit LAN PHY chip, it uses a CICADA8201 Gigabit LAN PHY chip.
Tried installing the nForce system utility and driver package?

EDIT #2: Now at least, we can say for certain and have verified it's not a W7 issue.
You're using a driver that's not designed for W7 and your hardware probably never WILL HAVE a W7 driver.
That's not through any fault of microsoft, it's not a compatability issue, it's simply because the NIC is probably too old for the manufactorer to BOTHER writing a W7 driver.

Sorry for the double post; Thought it prudent to mention;
I just got my ethernet connection drop out on me =/

Jynx me much Digger? hehe, just kidding.

In all seriousness though, i didn't get it at all for a week. Then twice in 1/2 an hour. Now 3 days later i get it again.

Today i fixed it by disabling and then re-enabling my NIC in the device manager.
No need to restart thankfully.

see... you missed my post before about how i was going to run "your test" after i ran mine... Dont be sho gung ho and trigger happy trying to find something wrong with what i have posted just because your theory and fix was debunked.

You are correct, its not a marvell... on a google search last nite being up 23 hours str8 i didnt see the misguided link to the GA-8N sli pro... instead of GA-K8N sli pro... never stated deluxe tho. And yes, i have tried everything as far as drivers go, unless now i find some obtuse driver for this chipset... or get this XP driver for the board to work, which seems doubtful, but a hunting i shall go. the nvidia 4 forceware didnt fix btw.

There's been a few scenarios where i've had to use a win2k or 98SE driver for XP.

If you have the option to install a 2k or 98 driver, please give it a shot.
Unfortunately for me, i think i'd have to actually visit the M$ site and get the newer driver manually.

Windows update failed to install my "updated" driver stating a reboot may be required.

Well, i've rebooted about 3 or 5 times since then and it's still not installed =/