cholla

Khronic: Glad the helped a little I think you should experiment with smaller RWIN values but you may have already done this & found the larger works better for you. This one is what is recommended if you surf or test international sites for in the country 128 is fine. DefaultTTL=255 I'm still not sure about these so I just put in the Cablenut recommended settings. MaxFreeTcbs MaxHashTableSize I've seen this one at 1 & 0 for enabled & disabled not really sure which works best. SynAttackProtect

Khronic;I'm assuming that what you have already is working OK for you so I'm going to work from that. If you want to go smaller with DefaultReceiveWindow &DefaultSendWindow multiply 4096 by an even number. If you want to go smaller with GlobalMaxTcpWindowSize & TcpWindowSize multiply 1460 by an even number. Give these a try: DefaultReceiveWindow=442368 DefaultSendWindow=442368 InitialLargeBufferCount =200 InitialMediumBufferCount=480 InitialSmallBufferCount=640 LargeBufferSize =819200 MediumBufferSize=147456 SmallBufferSize=16384 GlobalMaxTcpWindowSize=449680 TcpWindowSize=449680 DefaultTTL=255 DefaultTOSValue =240

Read the post in the topic below about AFD(Ancillary Function Driver for Winsock). http://www.testmy.net/forum/index.php?topic=9017.msg88743#msg88743 For Windows XP AFD(Ancillary Function Driver for Winsock).(1024 or 4096) Should be the multiplier of these 2: DefaultReceiveWindow DefaultSendWindow MSS should be the multiplier of these 2: GlobalMaxTcpWindowSize TcpWindowSize This is the largest RWIN that Tcpip Analyzer at Speedguide will show scaling on:65781760 At least even scaling to 64240 which is the largest multiple of 1460 under 65535.

ROM-DOS : What does your cablenut show when you select " Retreive current registry values"? Can you use find in your registry to find all the MTU & MSS settings? With the new registry program you are using is the old registry gone? If not could some of its settings be effecting your MTU &MSS?

Randon: I got your e-mail on this.First Have you made sure the mouse is still plugged into the mouse port in the back of your PC or plugged in well.Second do you have another mouse you could try.If you do plug it in & reboot to let your PC detect & install it. If that doesn't work go to System Properties Device Manager Mouse & remove any mouse that is installed there & reboot .This will let Windows reinstall the mouse it detects.If that doesn't fix it post the brand of your mouse & if you have a driver for it that came on floppy or CD. That should get you started .

jkandra ; The same way you just have only your desktop showing (no windows) hide any task or tool bars you don't want in the shot.

edit

Here are the basics on doing a screen shot . 1. Bring up the window you want a screen shot of( In this case Cablenut manual tweak screen) 2. press the Print Screen/Sys Rq. key if this is not exactly the key on your keyboard it should be simular. 3.Select paint ( Should be here StartProgramsAccessoriesPaint) 4.Once the Paint window is up L.click in the white window screen,Go to the edit drop down & select paste.This should have the screen shot in the paint window. 5.In the file drop down select save as ; in the save as window select save inMY Pictures Save as type: .jpg or .jpeg is what I use if your OS only has .bmp as a choice then save as .bmp With a .bmp you will have to convert it to .jpg to post it.Hopefully your OS will not need to do this. Mine does I have a freeware program called Ifranveiw that I use. 6. Then when you post just select Additional Options & Browse to the screen shot in My Pictures & click it. it should show in the Browse window .(just the text about the screen shot) then when you save the post it will have the screen shot in it. If you need Ifran veiw it is easy to find on the web to DL & pretty east to use .I will give you some instruction on it if you have to use it .

Skiptomylou26:Is it overheating?If the CPU gets too hot it will shut down.

nightline : I looked up the info in the link below for something else but it is supposed to affect bit torrent so you might want to take a look at it. http://www.testmy.net/forum/index.php?topic=9154.msg89060#msg89060

I put this in dial-up because ROM-DOS asked me a question about it.I have a couple of links there is a patch( but I don't know if it works)It seems this would affect bit torrent &P2P most. So for dial-up probably not too much affect http://www.msfn.org/board/lofiversion/index.php/t22640.html http://www.lvllord.de/?lang=en&url=4226patch/faq There is a parameter that limits the maximum number of connections that TCP may have open simultaneously. [HKEY_LOCAL_MACHINE System CurrentControlSet Services Tcpip Parameters] TcpNumConnections = 0x00fffffe (Default = 16,777,214) Note a 16 Million connection limit sounds very promising, but there are other parameters (See below), which keeps us from ever reaching this limit. When a client makes a connect() call to make a connection to a server, then the client invisible/implicit bind the socket to a local dynamic (anonymous, ephemeral, short-lived) port number. The default range for dynamic ports in Windows is 1024 to 5000, thus giving 3977 outbound concurrent connections for each IP Address. It is possible to change the upper limit with this DWORD registry key: [HKEY_LOCAL_MACHINE System CurrentControlSet Services Tcpip Parameters] MaxUserPort = 5000 (Default = 5000, Max = 65534) Note it is possible to reserve port numbers so they aren't used as dynamic ports in case one have a certain application that needs them. This is done by using the ReservedPorts (Q812873) setting. More Info MS KB Q196271 More Info MS KB Q319502 More Info MS KB Q319504 More Info MS KB Q328476 More Info MS KB Q836429 Even when not having 3977 concurrent connections for each IP Address, then it is still possible to run out of available port numbers or TCB's. This can happen if quickly opening and closing connections, because after a connection is "closed" it enters the state TIME_WAIT, and will continue to occupy the port number for 4 minutes (2*Maximum Segment Live, MSL) before it is actually removed. This behavior is specified in RFC 793, and prevents that one tries to reconnect to the same party, before the old socket is recognized as closed at both sides. It is possible to change how long a socket should be in TIME_WAIT state before it can be re-used freely: [HKEY_LOCAL_MACHINE System CurrentControlSet services Tcpip Parameters] TcpTimedWaitDelay = 120 (Default = 240 secs, Range = 30-300) More Info MS KB Q137984 More Info MS KB Q149532 More Info MS KB Q832954 Note with Win2k the reuse of sockets have been changed, so when reaching the limit of more than 1000 connections in TIME-WAIT state, then it starts to mark sockets that have been in TIME_WAIT state for morethan 60 secs as free. It is possible to configure this limit: [HKEY_LOCAL_MACHINE System CurrentControlSet services Tcpip Parameters] MaxFreeTWTcbs = 1000 (Default = 1000 sockets) Note with Win2k3 SP1 the reuse of sockets have been changed, so when it has to re-use sockets in TIME_WAIT state, then it checks whether the other party is different from the old socket. Eliminating the need to fiddle with (TcpTimedWaitDelay) and (MaxFreeTWTcbs) any more. If using a application protocol that doesn't implement timeout checking, but relies on the TCPIP timeout checking without specifying how often it should be done, then it is possible to get connections that "never" closes, if the remote host disconnects without closing the connection properly. The TCPIP timeout checking is by default done every 2 hour, by sending a keep alive packet. It is possible to change how often TCPIP should check the connections (Affects all TCPIP connections): [HKEY_LOCAL_MACHINE System CurrentControlSet services Tcpip Parameters] KeepAliveTime = 1800000 (Default = 7,200,000 milisecs) More Info MS KB Q140325 For each connection a TCP Control Block (TCB - Data structure using 0.5 KB pagepool and 0.5 KB non-pagepool) is maintained. The TCBs are pre-allocated and stored in a table, to avoid spending time on allocating/deallocating the TCBs every time connections are created/closed. The TCB Table enables reuse/caching of TCBs and improves memory management, but the static size limits how many connections TCP can support simultaneously (Active + TIME_WAIT). Configure the size of the TCB Table with this DWORD registry key: [HKEY_LOCAL_MACHINE System CurrentControlSet Services Tcpip Parameters] MaxFreeTcbs = 2000 (Default = RAM dependent, but usual Pro = 1000, Srv=2000) To make lookups in the TCB table faster a hash table has been made, which is optimized for finding a certain active connection. If the hash table is too small compared to the total amount of active connections, then extra CPU time is required to find a connection. Configure the size of the hash table with this DWORD registry key (Is allocated from pagepool memory): [HKEY_LOCAL_MACHINE System CurrentControlSet services Tcpip Parameters] MaxHashTableSize = 512 (Default = 512, Range = 64-65536) Note Microsoft recommends for a multiprocessor environment, that the value should not be higher than the maximum amount of concurrent connections (MaxFreeTcbs), also if multiprocessor then it might be interesting to look at the registry-key NumTcbTablePartitions (Recommended value CPU-count multiplied by 4). More Info MS KB Q151418 Note if using the Professional/Home edition of Windows then it is very likely that it is crippled (By Microsoft) not to handle many concurrent TCP connections. Ex. Microsoft have officially stated that the backlog limit is 5 (200 when Server), so the Professional edition is not able to accept() more than 5 new connections concurrently. More Info MS KB Q127144 Note even if having optimized Windows to handle many concurrent connections, then connections might still be refused when reaching a certain limit, in case a NAT-Router/Firewall is placed infront of it, which is unable to handle so many concurrent connections. Note if having activated SYN-Attack-Protection or installed WinXP SP2, a limit is introduced on how many connection attempts (half-open) one can make simultanously. This will limit worms like blaster and sasser from spreading too fast, but it will also limit other applications that creates many new connections simultanously (Like P2P). EventID 4226: TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts

[move]

d1nonly; The NDT test still shows your window scaling off.Did you try these settings first? DefaultReceiveWindow 126976

Welcome to the forum d1nonly I'm not the best on faster connections but I can probably get you started.First you dont have to post the results but the site below is better for the NDT test .The nitro one always shows packet loss.etc.It didn't use to have that problem. http://speedtest.umflint.edu/ The Cablenut shows the 2000 on its XP manual tweak screen this is normal.I would try a larger rwin.You have to enable window scaling for a rwin above 65535 that is what Tcp1323Opts

<a href="http://www.nerdtests.com/ft_nq.php?im"><img src="http://www.nerdtests.com/images/ft/nq.php?val=5645" alt="I am nerdier than 48% of all people. Are you nerdier? Click here to find out!"></a> Somewhat nerdy. I mean face it, you are nerdier than about half the test takers.

organ_shifter ;Check these 2 MS articles have you tried these to fix a corrupt system? http://support.microsoft.com/kb/310747/EN-US/ START

ROM-DOS ; Sorry I didn't mean to confuse you The following was an example of it being a multiple of 4096(page size).4096 is a multiple of 1024.I used 1024 to calculate the smaller DefaultReceiveWindow &DefaultSendWindow I put in the list for the gaming settings. To set the default size of the AFD-Windows use the following DWORD registry keys : [HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Afd Parameters] DefaultReceiveWindow = 16384(Example) DefaultSendWindow = 16384(Example) So yours should be this for the gaming settings: DefaultReceiveWindow 2042 DefaultSendWindow 2042 On your C: drive these settings should also be even multiples of 1024 or 4096(page size) DefaultReceiveWindow,DefaultSendWindow , LargeBufferSize,MediumBufferSize,& SmallBufferSize in Cablenut's settings.These are all based on AFD so they are even multiples of 1024 or 4096 . These 2 are based on MTU &MSS so they should be an even multiple of MSS. TcpWindowSize & GlobalMaxTcpWindowSize

ROM-DOS: I've been looking into the AFD as it applies to the DefaultReceiveWindow,DefaultSendWindow

ROM-DOS : Those are the ones I did for the 576 MTU & 536MSS How did they do when you play the gane is the latency & lag better? The other lower ones were based on 1500 MTU & 1460 MSS. I still haven't had time to do some research on the AFD & how the 1024 is supposed to work as its base.

netmasta: I copied & pasted the reply above strait from the e-mail from my ISP.I'm Checking into it further so it may be a few days.So far they blame SBC for this because thats who has the phone lines & they don't support V.92 or the other 2 protocols. On the e-mail I do have G-mail but I mean letting people who have the E-mail address with my ISP know.Anyway I'm Looking into another ISP .

ROM-DOS;You're probably right about looking for another ISP this is my 3rd one.I just don't like the hassle of changing my e-mail .I put in a test because it shows my ISP. nts-online.net :::.. Download Stats ..::: Connection is:: 45 Kbps about 0 Mbps (tested with 97 kB) Download Speed is:: 6 kB/s Tested From:: https://testmy.net/ (server2) Test Time:: Thu Oct 20 03:03:32 CDT 2005 Bottom Line:: 1X faster than 56K 1MB download in 170.67 sec Diagnosis: May need help : running at only 3.62 % of your hosts average (nts-online.net) Validation Link:: https://testmy.net/stats/id-W7XPB1A3N

deadsnake; did you check the 2 topics at the bottom of

rayray909; How is the Cacheman program working ? Did you decide to keep using it?

This is an article on a problem with Windows Installer the newer version is supposed to have the problem fixed. http://support.microsoft.com/?kbid=898628

ROM-DOS:I found out why turning off the compression in modem properties didn't work for for me.The problem with MS/MPPC not working was not with Windows but with my ISP.I got an answer back to an e-mail to their tech department.I will put it in this post This is in response to the message you sent asking several questions. Allow me to answer them in the order asked. 1. We do not support MPPC. 2. We do not support v.44 3. We do not support v.92 protocols in your area at this time. Sincerely, Cameron Cook NTS Help Desk Technician Level 2 [email protected] 1-800-687-5556 No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.12.4/143 - Release Date: 10/19/2005