Blunted 2

thanks guys keep the idea's comin and as soon as my friend comes on i'll tell him to look here and put some links in there. i really want to help him get his site going cause he has some really cool idea's and i know he can help alot of people with his knowledge and make some of the sickest things around with some help. thanks everyone

why shrink the pagefile

i wonder how much it will jump with that.

hey if you know someone there that can connect to you wireless i bet my friend can help you connect to there cause look at the wireless link my friend wants to connect to me with

i'll check it out with my extra time

i think it is

sell that thing and make some money man cause there isnt alot to play anyway so unless you really want to play it that bad make the money. just think what you could buy with the extra cash

^^^lucky as hell in more than 1 way

he registered on here so i'll make him look at this

its so close to me but i guess its not meant for me to have yet so i'll have to wait. if you lok at a thread called so close yet so far its about 5 to 10 minutes away from me

What can help my friend get his site more people and make it better? any info is helpful and he will add alot of thing to come he just needs some info on what people think so far and what could be added to make it more helpful to others. he builds almost everything on there himself and if he had some ideas he could make some sick stuff and help alot of people out. thanks www.vyrax.com

your one too :haha:

i send it all to another comp on lan and i have 1 comp exactly the same as this 1 just incase

i like #5 :haha:

m addicted :haha:

dont let it go too long if its the HD cause you'll lose everything on the drive

yea i had the same thing happen and they eventually told me it was my switches or routers and i told them i unhooked all routers and switches and was directly connected and it was the same then it got to them saying it was my comp and it couldnt do the speed and it definitlly can cause i have transfered over 600 mb a second on lan and i'm sure 15mb would be easy and i tried it on 4 comps and then got them to fix it all free and now its good for $30 a month. i agree with ya tho the techs suck on OPT

you might have a bad block on your hard drive which means there is a scratch or something on the HD and it cant write to that spot anymore. check your error logs and it might say if it does have a bad block. as you can see i have a bad HD and i already know it has a bad block so check your logs.

even my business line i pay 280 a month for has to be legal but thats with all isp's isnt it other than that its better than cable cause you can kill it all year long and not get capped or slower speeds from sharing it like cable but it cost more and if you can pay it why not. i just want as much speed as i can get no matter how fast it is i want more :haha:

i got the 15/2 optimum and i get 1.7 to 1.9 mb upload all day long and my down is usually from about 11 to 16 mb but it was messed up when i got it. i made them give me the newest modem and replace the whole line and run some tests and now its great. if i had the chance i would also get fios but its not here yet and look at this post (http://www.testmy.net/forum/index.php?topic=10219.0) and see how close it is to me.

Speakeasy adsl C:Documents and SettingsEebobb>ping testmy.net Pinging testmy.net [67.18.179.85] with 32 bytes of data: Reply from 67.18.179.85: bytes=32 time=47ms TTL=54 Reply from 67.18.179.85: bytes=32 time=47ms TTL=54 Reply from 67.18.179.85: bytes=32 time=47ms TTL=54 Reply from 67.18.179.85: bytes=32 time=48ms TTL=54 Ping statistics for 67.18.179.85: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 47ms, Maximum = 48ms, Average = 47ms C:Documents and SettingsEebobb>ping myspace.com Pinging myspace.com [63.208.226.25] with 32 bytes of data: Reply from 63.208.226.25: bytes=32 time=86ms TTL=250 Reply from 63.208.226.25: bytes=32 time=86ms TTL=250 Reply from 63.208.226.25: bytes=32 time=87ms TTL=250 Reply from 63.208.226.25: bytes=32 time=87ms TTL=250 Ping statistics for 63.208.226.25: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 86ms, Maximum = 87ms, Average = 86ms C:Documents and SettingsEebobb>ping nyc.speakeasy.net Pinging nyc.speakeasy.net [216.254.95.2] with 32 bytes of data: Reply from 216.254.95.2: bytes=32 time=7ms TTL=62 Reply from 216.254.95.2: bytes=32 time=9ms TTL=62 Reply from 216.254.95.2: bytes=32 time=9ms TTL=62 Reply from 216.254.95.2: bytes=32 time=9ms TTL=62 Ping statistics for 216.254.95.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 9ms, Average = 8ms C:Documents and SettingsEebobb>ping 64.233.161.104 Pinging 64.233.161.104 with 32 bytes of data: Reply from 64.233.161.104: bytes=32 time=14ms TTL=249 Reply from 64.233.161.104: bytes=32 time=14ms TTL=249 Reply from 64.233.161.104: bytes=32 time=14ms TTL=249 Reply from 64.233.161.104: bytes=32 time=14ms TTL=249 Ping statistics for 64.233.161.104: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 14ms, Maximum = 14ms, Average = 14ms C:Documents and SettingsEebobb>ping 68.142.226.53 Pinging 68.142.226.53 with 32 bytes of data: Reply from 68.142.226.53: bytes=32 time=16ms TTL=57 Reply from 68.142.226.53: bytes=32 time=18ms TTL=57 Reply from 68.142.226.53: bytes=32 time=16ms TTL=58 Reply from 68.142.226.53: bytes=32 time=16ms TTL=58 Ping statistics for 68.142.226.53: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 16ms, Maximum = 18ms, Average = 16ms C:Documents and SettingsEebobb>ping speakeasy.net Pinging speakeasy.net [69.17.117.156] with 32 bytes of data: Reply from 69.17.117.156: bytes=32 time=76ms TTL=60 Reply from 69.17.117.156: bytes=32 time=77ms TTL=60 Reply from 69.17.117.156: bytes=32 time=77ms TTL=60 Reply from 69.17.117.156: bytes=32 time=78ms TTL=60 Ping statistics for 69.17.117.156: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 76ms, Maximum = 78ms, Average = 77ms C:Documents and SettingsEebobb>ping speedguide.net Pinging speedguide.net [63.217.30.70] with 32 bytes of data: Reply from 63.217.30.70: bytes=32 time=14ms TTL=53 Reply from 63.217.30.70: bytes=32 time=15ms TTL=53 Reply from 63.217.30.70: bytes=32 time=15ms TTL=53 Reply from 63.217.30.70: bytes=32 time=15ms TTL=53 Ping statistics for 63.217.30.70: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 14ms, Maximum = 15ms, Average = 14ms C:Documents and SettingsEebobb>ping lax.speakeasy.net Pinging lax.speakeasy.net [64.81.45.2] with 32 bytes of data: Reply from 64.81.45.2: bytes=32 time=78ms TTL=61 Reply from 64.81.45.2: bytes=32 time=79ms TTL=61 Reply from 64.81.45.2: bytes=32 time=79ms TTL=61 Reply from 64.81.45.2: bytes=32 time=79ms TTL=61 Ping statistics for 64.81.45.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 78ms, Maximum = 79ms, Average = 78ms C:Documents and SettingsEebobb>

to me it is but i guess its ok

:haha: :haha:

http://gameadvisor.futuremark.com/gameadvisor/service/my_system.jsp?sysInfoId=2478998 this is my POS comp and the test didnt read my sound card but it read my headset.its still good. i'll scan my other comp later.

my fastest speeds i got on the 2 up and 15 down are in my sig so you might be in a more populated area than me cause i hit over my cap quite a bit.