Coursework and Plusnet

I'll start with coursework, I'm slowly getting there with my dissertation, its way behind schedule and its going to start getting worse because I have assignments to do AS WELL, but getting there. I've been stuck on normalization for the past few days, just confuses the hell out of me, I'm starting to understand it though, thanks to Guy at Chester Uni for the handouts he gave me today and alundavid on the CustomPC forums for going out of his way to help me out.

Doing normalization has kind of been like (and reminds me of) things like sub netting and binary and hex mathematics, they both took me ages to get used to, but once it clicks in you head, its easy!

Now, trying to do all this work is not helped by a crap Internet Service Provider, mines Plusnet. 2 years ago they were top of the game, now they can't keep up with the demand (but they are still selling the product) and they are loosing customers like crazy, I might be one of them.

I have had a couple of run ins with them about the speed of service they provide, I am supposed to get 2mb/s which tends to max out at about 220kb/s. I can get this no problem and have done since ADSL max was installed at my exchange in Comberbatch.

But a couple of times now they have "limited" my service for no good reason, I haven't gone over my allowance and they would not provide a reason for this limit in service. Last time around they removed it and it has been fine since........ until yesterday.

Now, I can't break 30kb/s, which is on all accounts ridiculous for what I am paying for, so I have sent them another bitchy message asking them to remove the restrictions, we will see.

Ping logs:

Request timed out.
Request timed out.
Reply from 64.233.183.99: bytes=32 time=4038ms TTL=242
Reply from 64.233.183.99: bytes=32 time=3992ms TTL=242
Reply from 64.233.183.99: bytes=32 time=3942ms TTL=242
Request timed out.
Reply from 64.233.183.99: bytes=32 time=4224ms TTL=242
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.183.99: bytes=32 time=3407ms TTL=242
Reply from 64.233.183.99: bytes=32 time=3055ms TTL=242
Reply from 64.233.183.99: bytes=32 time=3007ms TTL=242
Reply from 64.233.183.99: bytes=32 time=3093ms TTL=242
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.183.99: bytes=32 time=4133ms TTL=242
Reply from 64.233.183.99: bytes=32 time=3576ms TTL=242
Reply from 64.233.183.99: bytes=32 time=3445ms TTL=242
Reply from 64.233.183.99: bytes=32 time=4142ms TTL=242
Reply from 64.233.183.99: bytes=32 time=3327ms TTL=242
Reply from 64.233.183.99: bytes=32 time=3472ms TTL=242
Reply from 64.233.183.99: bytes=32 time=3766ms TTL=242
Reply from 64.233.183.99: bytes=32 time=3329ms TTL=242
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.183.99: bytes=32 time=4313ms TTL=242
Reply from 64.233.183.99: bytes=32 time=3039ms TTL=242
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 64.233.183.99:
Packets: Sent = 85, Received = 34, Lost = 51 (60% loss),
Approximate round trip times in milli-seconds:
Minimum = 2528ms, Maximum = 4359ms, Average = 3480ms

Increased timeout ping logs:

Request timed out.
Reply from 64.233.183.99: bytes=32 time=5698ms TTL=242
Reply from 64.233.183.99: bytes=32 time=5040ms TTL=242
Reply from 64.233.183.99: bytes=32 time=3582ms TTL=242
Reply from 64.233.183.99: bytes=32 time=3424ms TTL=242
Reply from 64.233.183.99: bytes=32 time=3583ms TTL=242
Reply from 64.233.183.99: bytes=32 time=3223ms TTL=242
Reply from 64.233.183.99: bytes=32 time=3527ms TTL=242
Reply from 64.233.183.99: bytes=32 time=3014ms TTL=242
Reply from 64.233.183.99: bytes=32 time=4719ms TTL=242
Reply from 64.233.183.99: bytes=32 time=5776ms TTL=242
Reply from 64.233.183.99: bytes=32 time=5988ms TTL=242
Reply from 64.233.183.99: bytes=32 time=6744ms TTL=242
Reply from 64.233.183.99: bytes=32 time=6023ms TTL=242
Reply from 64.233.183.99: bytes=32 time=5287ms TTL=242
Reply from 64.233.183.99: bytes=32 time=5289ms TTL=242
Reply from 64.233.183.99: bytes=32 time=3631ms TTL=242
Reply from 64.233.183.99: bytes=32 time=3551ms TTL=242
Reply from 64.233.183.99: bytes=32 time=4440ms TTL=242
Reply from 64.233.183.99: bytes=32 time=4846ms TTL=242
Reply from 64.233.183.99: bytes=32 time=5756ms TTL=242
Reply from 64.233.183.99: bytes=32 time=5213ms TTL=242
Reply from 64.233.183.99: bytes=32 time=5412ms TTL=242
Reply from 64.233.183.99: bytes=32 time=6217ms TTL=242
Reply from 64.233.183.99: bytes=32 time=6591ms TTL=242
Reply from 64.233.183.99: bytes=32 time=5808ms TTL=242
Reply from 64.233.183.99: bytes=32 time=5413ms TTL=242

Ping statistics for 64.233.183.99:
Packets: Sent = 27, Received = 26, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 3014ms, Maximum = 6744ms, Average = 4915ms

Nearly 5 seconds average round trip!!!

Thanks Plusnet