From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: FW: BRIAN LIVINGSTON: "Window Manager" from InfoWorld.com, Monday,June 26, 2000
Date: Tue, 27 Jun 2000 19:14:43 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0006271910410.14362-100000@localhost.localdomain> (raw)
In-Reply-To: <001f01bfe07c$96152d40$36910f8e@dpsd.gov.calgary.ab.ca>
While I don't expect that the included tip will hurt a Windows computer, I
seriously doubt it will help. I have yet to see a computer that seemed to
have a bottleneck at the NIC. I just wish I could afford such internet
access. Then again, what would be the point? Few sites are capable of
sending out the data at that rate anyway.
If anyone tries this and it helps please drop me a note. I remain quite
skeptical.
--
Kirk Wood
Cpt.Kirk@1tree.net
------------------
Seek simplicity -- and distrust it.
Alfred North Whitehead
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Stephen Dawes
` Kirk Wood [this message]
` FW: BRIAN LIVINGSTON: "Window Manager" from InfoWorld.com,Monday,June " Stephen Dawes
` FW: BRIAN LIVINGSTON: "Window Manager" from InfoWorld.com, Monday,June " Kirk Reiser
` Victor Tsaran
` Kirk Wood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0006271910410.14362-100000@localhost.localdomain \
--to=cpt.kirk@1tree.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).