network card clock latency
network card clock latency
For some reason, my network card latency is set at 128 clocks as told to me by the 'Sandra' software. It tells me to set it down to 32 so that it doesn't steal all the PCI bus from the other components, but I haven't the slightest clue on how to do that. It doesn't appear to me that it is in the BIOS, and I can't seem to figure it out on the 'TCP optimizer' I downloaded from Speedguide.net. Anyone have a clue on how to set the latency clock?
-
- Senior Member
- Posts: 4438
- Joined: Wed Jun 07, 2000 12:00 pm
- Location: Columbus, Ohio
Ok, that makes sense. I went into my BIOS, saw the PCI configuration section, and before I selected that area, there was a little description at the bottom that said, "IRQ settings, latency timers....... ". I thought to myself, "great, now I'll just change it". Not so, once I opened it up, the only things that I could change were IRQs and DMAs. There was something else that said VGA palleted snoop, but I figured that had nothing to do with what I am trying to accomplish. I am running a IWill KK266 motherboard with the VIA KT133A chipset. I have the 0426 BIOS running. I hope this will help you to know a possible more detailed explaination on how to fix my problem. Could it be I need newer drivers from VIA? Do I need to flash my BIOS to a newer version? I appreciate the help, I am definitely closer to finding an answer than what I was this afternoon.
- mnosteele52
- Posts: 11913
- Joined: Tue Jul 24, 2001 12:00 pm
- Location: Chesapeake, VA
There is a PCI latency patch for Via chipsets, I'm not sure if it will fix your problem, but you can find it here.



-
- New Member
- Posts: 15
- Joined: Thu Mar 14, 2002 9:15 pm
- Location: San Diego
- mnosteele52
- Posts: 11913
- Joined: Tue Jul 24, 2001 12:00 pm
- Location: Chesapeake, VA
-
- New Member
- Posts: 15
- Joined: Thu Mar 14, 2002 9:15 pm
- Location: San Diego
Powerstrip is a widely used utility intended mainly for tweaking graphics cards and monitors, but which has other options as well. Web site is:
Powerstrip website
This is the module under options, adapter, in which you can adjust the latency timing of each device.
Powerstrip website
This is the module under options, adapter, in which you can adjust the latency timing of each device.
Call it concern and problems put together. Ever since something randomly screwed up with my internet connection, I have been having more lockups and my computer is just slowing down and not performing correctly at all the way it used to. I just put it together in August (Athlon 1400MHz, IWill KK266, 512 PC133) and it ran great until about 3 weeks ago. I don't know what the problem is. It started with my bandwidth slowing down to 75 kbytes/sec when I was averaging 400! I used TCP optimizer and it topped it off at 240, but I know what my computer is capable of. My computer has also had other slowing down issues so I downloaded Sandra to start picking apart at what it has told me. I understand taking it with a grain of salt, but I am getting fed up with the performance issues here so I thought for a last ditch effort I would visit the forums out there for some advice and see if changing a few values around would solve my problems before I reformat my hard drive to take care of the problem. Now.... to answer what the previous question was to yours, my NIC is an Allied Telesyn AT 2500TX. I used to have a Netgear, but I have had 2 of those just randomly break on me so I have decided that company cannot make decent hardware.
- Lobo
- SG VIP
- Posts: 17660
- Joined: Thu Nov 23, 2000 2:32 pm
- Location: Panama City, FL and a FAN of Dale Earnhardt Jr. Bud Chevy & NASCAR , and the Atlanta Braves
It has been verified by experiment that certain auto-negotiating ethernet cards (both in PCs and in Macs), when connected to certain models of cable modem, sense the ethernet duplex setting incorrectly. Such a cable modem has ethernet hardware which is capable of operating only in half-duplex mode, at 10 Mbps, yet some auto-negotiating ethernet cards sense it as full-duplex. If an auto-negotiation card incorrectly starts operating in full-duplex mode, there can be collisions between ethernet packets being transmitted in both directions at the same time, leading to packet loss, and repeated re-transmissions. There is no visible evidence of this apart from poor performance. This problem can be avoided by manually configuring your ethernet card to be 10 Mbps half-duplex. No ill-effects will transpire from doing this, even when it is not necessary. The exact wording of the setting changes required varies from one manufacturer to another, so the instructions below are necessarily rather broadly defined.
To make this change under Win98/ME, follow these steps:
Open Control Panel.
Double-click Network.
From the scrollable list, select your Ethernet adapter (rather than any dial-up) with a green icon.
Click the button Properties.
Click the tab Advanced to bring it to the front:
In the Property box, the property name to be selected varies according to model of ethernet card. Examples are: Network Link Selection, Media Type, Connection Type, Duplex Mode, or any similarly-named property which can have Values looking like Auto-Negotiation, or 10BT, or 10BaseT.
In the Value box, select a value which either (a) explicitly says half-duplex or semi-duplex, or (b) at least does not say full-duplex [e.g. 10BaseT on its own is OK]. If there is a choice between 10 and 100 with half-duplex, choose the 10. Do not choose 10Base5, 10Base2, or AUI.
Click OK to exit the Adapter settings.
Click OK all the way out - you might need to restart.
To make this change under Windows 2000 or XP, follow these steps:
Open Control Panel.
Double-click Network and Dial-up Connections.
Identify the icon for your cable modem connection: usually Local Area Connection.
Right-click that icon and select Properties.
Under the ethernet adapter icon, click the button Configure.
Click the tab Advanced to bring it to the front:
In the Property box, the property name to be selected varies according to model of ethernet card. Examples are: Network Link Selection, Media Type, Connection Type, Duplex Mode, or any similarly-named property which can have Values looking like Auto-Negotiation, or 10BT, or 10BaseT.
In the Value box, select a value which either (a) explicitly says half-duplex or semi-duplex, or (b) at least does not say full-duplex [e.g. 10BaseT on its own is OK]. If there is a choice between 10 and 100 with half-duplex, choose the 10. Do not choose 10Base5, 10Base2, or AUI.
Click OK to exit the Adapter settings.
Click OK to exit the Connection properties
To make this change under Win98/ME, follow these steps:
Open Control Panel.
Double-click Network.
From the scrollable list, select your Ethernet adapter (rather than any dial-up) with a green icon.
Click the button Properties.
Click the tab Advanced to bring it to the front:
In the Property box, the property name to be selected varies according to model of ethernet card. Examples are: Network Link Selection, Media Type, Connection Type, Duplex Mode, or any similarly-named property which can have Values looking like Auto-Negotiation, or 10BT, or 10BaseT.
In the Value box, select a value which either (a) explicitly says half-duplex or semi-duplex, or (b) at least does not say full-duplex [e.g. 10BaseT on its own is OK]. If there is a choice between 10 and 100 with half-duplex, choose the 10. Do not choose 10Base5, 10Base2, or AUI.
Click OK to exit the Adapter settings.
Click OK all the way out - you might need to restart.
To make this change under Windows 2000 or XP, follow these steps:
Open Control Panel.
Double-click Network and Dial-up Connections.
Identify the icon for your cable modem connection: usually Local Area Connection.
Right-click that icon and select Properties.
Under the ethernet adapter icon, click the button Configure.
Click the tab Advanced to bring it to the front:
In the Property box, the property name to be selected varies according to model of ethernet card. Examples are: Network Link Selection, Media Type, Connection Type, Duplex Mode, or any similarly-named property which can have Values looking like Auto-Negotiation, or 10BT, or 10BaseT.
In the Value box, select a value which either (a) explicitly says half-duplex or semi-duplex, or (b) at least does not say full-duplex [e.g. 10BaseT on its own is OK]. If there is a choice between 10 and 100 with half-duplex, choose the 10. Do not choose 10Base5, 10Base2, or AUI.
Click OK to exit the Adapter settings.
Click OK to exit the Connection properties

SAME MOTHERBOARD AS MEEE!!!!!!!!!!!!
got LEECHED?
-UNDER CONSTRUCTION
:: Comp/Tech Specs ::
Athlon 900Mhz, Iwill 266R, 40GB/30GB ATA 100 HDDs, GeForce 2 Pro, SBLive! X-Gamer 5.1, Windows XP Corporate , 1.5mbps/384kbps.
Certified MCP+SB, MCSE, A+ and CCNA
-UNDER CONSTRUCTION
:: Comp/Tech Specs ::
Athlon 900Mhz, Iwill 266R, 40GB/30GB ATA 100 HDDs, GeForce 2 Pro, SBLive! X-Gamer 5.1, Windows XP Corporate , 1.5mbps/384kbps.
Certified MCP+SB, MCSE, A+ and CCNA
Yes! I did have @home. They got bought out by mediaCom. That is when my bandwidth problems started. However, only my bandwidth on my network of computers was drastically affected. The other computers stayed the same. On top of that, I used 'TCP optimizer' on everyones computer, and everyone's computer topped out at 240 kbytes/sec or so, except for one computer that was already running at 240. I went to friend's houses that use mediaCom as well and used the TCP optimizer on their computers. They all went to 240 as well. I don't understand. Is mediaCom setting the bandwidth? If so, why would they set it lower than what @home used to have it? I didn't get a huge performance drop in bandwidth until mediacom completely took over. Like I said, before that I was getting 400/sec. I don't have a clue as to what would be causing a problem. I figured it was my latency timer causing hardware problems. Could MediaCom be the cause of this?Originally posted by Lobo
Who is your ISP, and did you used to have @home![]()
What version of bios? Guys, this is an easy one to figure out. Just ask the right questions. No need to go into software forum. This is set in the Bios. 32 is defaut, and I am afraid yours is set too high. 29 is optimum. There should be a setting, as per young Kip, in the Bios that lets you set "PCI Latency timer" settings, you're just not looking hard enough.
Let me help you out. Go into Bios, go under advanced settings, go under PCI latenct settings. There you will find adjustment to bring that puppy down to 29. If it is not there, goto website of motherboard manufacturer, and see if you can download a PDF user manual, or, if you have saved your original manual, look under index fpr PCI latency. Also, make sure you visit MB website to ensure you have latest version of Bios and that it is set to default. Then go to http://www.viahardware.com to get 4.37 4 in 1 drivers. It's really lots of fun.



