From: Alexander Clouter <alex@digriz.org.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Fwd: New Chip (SEAforth 40C18) - New Challenge
Date: Tue, 7 Apr 2009 11:48:56 +0100 [thread overview]
Message-ID: <olnra6-2q1.ln1@woodchuck.wormnet.eu> (raw)
In-Reply-To: <6a3ae47e0904070207t5318879en147757ef142e411a@mail.gmail.com>
Robert Raschke <rtrlists@googlemail.com> wrote:
> On Mon, Apr 6, 2009 at 7:00 PM, maht <mattmobile@proweb.co.uk> wrote:
>>
>> SeaForth is dead already
>>
>> http://colorforth.com/vTPL.htm
>>
>> http://colorforth.com/S40.htm
>>
>
> These docs aren't dated. And I remember a lot of discussion about 1 -
> 2 years ago about the patent issues surrounding Chuck Moore's work. So
> I'm wondering if this info is outdated. The Forth Usernet group seems
> to indicate that these chips are fine and dandy.
>
For whatever it's worth:
----
alex@berk:~$ wget -S --spider http://colorforth.com/S40.htm
Spider mode enabled. Check if remote file exists.
--2009-04-07 11:47:19-- http://colorforth.com/S40.htm
Resolving colorforth.com... 207.217.125.50
Connecting to colorforth.com|207.217.125.50|:80... connected.
HTTP request sent, awaiting response...
HTTP/1.1 200 OK
Date: Tue, 07 Apr 2009 10:47:20 GMT
Server: Apache
Last-Modified: Mon, 06 Apr 2009 19:52:50 GMT <--------
ETag: "2e6982-849-49da5d92"
Accept-Ranges: bytes
Content-Length: 2121
Keep-Alive: timeout=10, max=100
Connection: Keep-Alive
Content-Type: text/html
Length: 2121 (2.1K) [text/html]
Remote file exists and could contain further links,
but recursion is disabled -- not retrieving.
alex@berk:~$ wget -S --spider http://colorforth.com/vTPL.htm
Spider mode enabled. Check if remote file exists.
--2009-04-07 11:47:21-- http://colorforth.com/vTPL.htm
Resolving colorforth.com... 207.217.125.50
Connecting to colorforth.com|207.217.125.50|:80... connected.
HTTP request sent, awaiting response...
HTTP/1.1 200 OK
Date: Tue, 07 Apr 2009 10:47:21 GMT
Server: Apache
Last-Modified: Mon, 06 Apr 2009 19:48:29 GMT <-------
ETag: "172cd95-688-49da5c8d"
Accept-Ranges: bytes
Content-Length: 1672
Keep-Alive: timeout=10, max=100
Connection: Keep-Alive
Content-Type: text/html
Length: 1672 (1.6K) [text/html]
Remote file exists and could contain further links,
but recursion is disabled -- not retrieving.
----
Cheers
--
Alexander Clouter
.sigmonster says: You will receive a legacy which will place you above want.
next prev parent reply other threads:[~2009-04-07 10:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a5903cce-4631-4d53-ab29-54a5b8b66361@x29g2000prf.googlegroups.com>
2009-03-19 3:37 ` Bruce Ellis
2009-03-19 4:36 ` David Leimbach
2009-03-19 4:47 ` Bruce Ellis
2009-03-19 6:21 ` Jeff Sickel
2009-03-19 6:30 ` Bruce Ellis
2009-03-19 9:45 ` Pavel Klinkovsky
2009-03-20 2:50 ` Bruce Ellis
2009-04-06 18:00 ` maht
2009-04-06 18:54 ` Jeff Sickel
2009-04-06 22:46 ` Bruce Ellis
2009-04-07 9:07 ` Robert Raschke
2009-04-07 10:48 ` Alexander Clouter [this message]
2009-04-07 14:24 ` maht
2009-04-07 14:52 ` Robert Raschke
2009-04-07 15:04 ` maht
2009-03-30 9:15 ` [9fans] Fwd: New Chip (SEAforth 40C18) - New Icarus Sparry
2009-03-30 12:07 ` Bruce Ellis
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=olnra6-2q1.ln1@woodchuck.wormnet.eu \
--to=alex@digriz.org.uk \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).