VanBuren

its very important to follow every step in tweakguide, the most important is that you get rid of your old settings, by open cablenut, click delete cablenut tweaks, click save to registry and reboot. I suggest you dont calculate any RWIN this time, use the setting i suggested before 5000 768 and change Defult Send Window to 65536 now click save to registry again and reboot VanBuren

give me some burst !!!! VanBuren

VanBuren

ty, i always wanted to be a minipimp VanBuren

:::.. Download Stats ..::: Connection is:: 3611 Kbps about 3.6 Mbps (tested with 12160 KB) Download Speed is:: 441 KB/s Tested From:: http://www.testmy.net/ Bottom Line:: 64 times faster than 56K you can download 1MB in 2.32 second(s) Validation Link:: https://testmy.net/cgi-bin/get.cgi?Test_ID=B7NUMYKUH :::.. Download Stats ..::: Connection is:: 3352 Kbps about 3.4 Mbps (tested with 2992 KB) Download Speed is:: 409 KB/s Tested From:: http://www.testmy.net/ Bottom Line:: 60 times faster than 56K you can download 1MB in 2.5 second(s) Validation Link:: https://testmy.net/cgi-bin/get.cgi?Test_ID=DGFDSU73I 300 Kbps diffrense, so the 3 Mbps test is big enough, atleast in this speed VanBuren

I turned 30 in 9th of july VanBuren

Yea GetABeer.EXE is the way to go Where did you get that value, that value is way too high. I suggest you restart from zero and use my tweakguide for Non advanced users and use the cable and dsl file 5000 768 in mss 1460 folder, if you get problems i will help you change Defult send window to your 512 Kbps cap. VanBuren

hey cereal try with this, open cablenut change TcpWindowsize to 128480 and also change GlobalMaxTcpWindowsize to 128480 click save to registry and reboot try again and let us know how that works VanBuren

86% of advertised speed is not bad, but if you want to tweak to get closer follow this guide http://www.testmy.net/forumz/viewtopic.php?t=605 VanBuren

there is nothing more you can do, i would delete all tweaks and call my ISP and let them fix it, when they fixed it you tweak and go above your cap, hopefully lol VanBuren

man that sucks, i understand your feelings CA3LE And i agree that SmartTest work great for most ppl, its only me whining cos im overseas and dont get much burst lol keep up the good work and copyright everything so you can sue their asses if they steal again VanBuren

looking good, but maby you need to run full trottle to go faster, sometimes that will work and sometimes your speed will drop. Give it a try 1. load Cable & DSL 4000 512 in cablenut 2. Increase TcpWindowsize from 64240 to 256960 3. Increase GlobalMaxTcpWindowsize from 64240 to 256960 4. Change Tcp13230pts from 0 to 1 5. Click save to registry 6. reboot 7. test again and post score good luck VanBuren

Hey ecliptic run this test, disable firewall during test so test can ping ya http://www.dslreports.com/tweaks copy result adress (URL) and paste it here so i can see it VanBuren

Hey Marcin i said this in the sticky in make it faster topic "Well if you cant reach 90% of your ISP advertised speed you might have a problem." Thats a good tumbrule, i would leave my settings as you got em, you are indeed very close to your cap. You need to reboot everytime you change settings in cablenut program to make em change, i guess windows loading all those settings at startup and dont ask for em before you reboot again. Be happy above 90% advertised VanBuren

Since im overseas im not really a fan of SmarTest, because of very low burst on higher delay (ping). But the idea is cool, but maby he can do it for another test size, see what size ppl prefer to test with... In SmarTest, I never get "bumped up" to the 3 MB test even tho it give me faster speed. Below i found great info explaining some of this quote from http://rdweb.cns.vt.edu/public/notes/win2k-tcpip.htm "So what is the TCP window size thing? The TCP window is the amount of unacknowledged data in flight between the sender and the receiver. Data is sent by TCP in segments that are typically 1460 bytes in length. If the sender is permitted a window size of only 1 segment, the sender transmits a single segment, and waits for an acknowledgement from the receiver. If the transmission delay between sender and receiver is long, this means very low throughput (very few segments transferred per unit time). Both sender and receiver spend most of their time waiting for messages to be transmitted from one end of the connection to the other. In order to improve throughput, the sender transmits multiple segments without waiting for the next acknowledgement from the receiver. The TCP window is an estimate of the upper bound on the number of segments that will fit in the length of the pipe between sender and receiver. The window size is increased during a TCP transfer until the end-to-end path becomes too full (indicated by a segment being dropped somewhere in the network), then the size is backed off and then increased slowly again until the limit is reached. This cycle of shrinking and slowly expanding window size continues throughout the TCP connection. In this way, TCP tries to optimize the transmit window to maximize throughput over the lifetime of the connection. The receiver advertises his maximum window size to give the sender an idea of how much buffer space the receiver has available. This puts a hard limit on size of the window, even if more bandwidth is available in the network. If the pipe is pretty big, and the round-trip delay is long, a lot of segments will fit in the network between the sender and receiver. The window size needs to be pretty big in a long, fat network. How big? window size = bandwidth * delay For 10 Mbps bandwidth and a round-trip delay of 0.010 sec, this gives a window size of about 12 KB (or nine 1460-byte segments). This should yield maximal throughput on a 10 Mbps LAN, even if the delay is as high as 10 ms -- most LANs have round-trip delay of less than a few milliseconds. When bandwidth is lower, more delay can be tolerated for the same fixed window size, so a window size of 12 KB works well at lower speeds, too. For a fixed window size, large increases in bandwidth mean that small increases in round-trip delay will have a significant effect on throughput. If the end-to-end bandwidth is 100 Mbps, a 12 KB window size implies that no more than 1.05 ms of delay is tolerable if TCP throughput near 100 Mbps is desired -- that's a pretty tight bound, even for a LAN. The default maximum TCP window size in Win2000 is 17520 bytes (12 segments). This should work nicely in LANs -- even at 100 Mbps -- assuming that end-to-end delay is not much more than 2 ms. The default window size should yield TCP throughput of around 70 Mbps on a 100 Mbps LAN, assuming congestion is minimal. This default max TCP window size is also large enough for round trip delays of 70 ms and end-to-end bandwidth of up to 2 Mbps. That's no coincidence; most entities on the Internet have access pipes that are T1 (1.5 Mbps) or E1 (2 Mbps) and the nominal round-trip delay coast-to-coast in the U.S. is about 70 ms. So, as a first cut at a reasonable default setting for the TCP max window size, this ain't too bad. But what if you have a WAN connection with nominal 10 Mbps bandwidth available, and you're downloading from a distant, well-connected server. Perhaps you

http://www.fz.se/wtf/view.php?linkid=1105 VanBuren

dern thats reminds me how sucky my car

yea that would be cool but i think i prefer Da Buzz cos its DA band hehe listen to some samples http://www.dabuzz.nu http://www.dabuzz.nu/dangerous/teasers/Dangerous.mp3 I love to listen to this band when driving car, i guess im a bass freak too, got a 15" sub and a 600w amplifire, i made a huge bass box for it 350 liter, maby its better with smaller i dunno but i got a hevy bass and great sound in my old volvo 745, atleast i dont have to listen to the carengine anymore hehe VanBuren

I think he

Something for Swimmer? http://www.fz.se/wtf/view.php?linkid=1103 VanBuren

yea i hot a huge bookmark folder VanBuren