Re: Sydney trackwork - long weekend

[Eben Levy <thekid@connect.net.au>]

okies, you want to see what the problem is?

PING www-cr.cityrail.nsw.gov.au: 56 data bytes
64 bytes from www-cr.staterail.nsw.gov.au (203.9.151.70): icmp_seq=0. time=2982.
ms
64 bytes from www-cr.staterail.nsw.gov.au (203.9.151.70): icmp_seq=1. time=3842.
ms
64 bytes from www-cr.staterail.nsw.gov.au (203.9.151.70): icmp_seq=2. time=3938.
ms
64 bytes from www-cr.staterail.nsw.gov.au (203.9.151.70): icmp_seq=4. time=3522.
ms
64 bytes from www-cr.staterail.nsw.gov.au (203.9.151.70): icmp_seq=5. time=3338.
ms
64 bytes from www-cr.staterail.nsw.gov.au (203.9.151.70): icmp_seq=6. time=3175.
ms
64 bytes from www-cr.staterail.nsw.gov.au (203.9.151.70): icmp_seq=7. time=2925.
ms
64 bytes from www-cr.staterail.nsw.gov.au (203.9.151.70): icmp_seq=8. time=3274.
ms
64 bytes from www-cr.staterail.nsw.gov.au (203.9.151.70): icmp_seq=10.
time=3634. ms
^C
----www-cr.cityrail.nsw.gov.au PING Statistics----
14 packets transmitted, 9 packets received, 35% packet loss
round-trip (ms)  min/avg/max = 2925/3403/3938


there link is shagged :-}

WhaleOilBeefHooked wrote:

> Shaun Hopkins <wallaby@jander.fl.net.au> wrote in message
> 37e9e86b@news.syd.fl.net.au">news:37e9e86b@news.syd.fl.net.au...
> > Garry Hoddinett <hoddos@netspace.net.au> wrote:
> > : I really don't think a casual rail user could reasonably be expected to
> down
> > : load all CityRail timetables from the net and then view them later.  In
> the
> >
> > Well, first of all I discovered tihis morning from this ng that the
> > timetables could be downloaded.  I'd never noticed the tiny link before
> > until comments here made me look for it.
> >
> > I've been connected since the treansfer started at 9.30 this morning.
> > It's now 6.43 pm.  The file transfer(~3.8MB) is now at 80%.  I doubt
> > there's too many CityRail customers with the patience to wait that long to
> > d/l the tt.
>
> It only took me 40mins on a V.90 dialup connection.
>
> DaveP