etherboot-developers — Discussion of developer issues

Re: [Etherboot-developers] sis640e/sis730s support for etherboot sis900 driver

[Ken Y. <ke...@nl...>]

>I have written a patch that adds sis640e / sis730s support to the etherboot 
>sis900 driver. I have testet it on a board with sis730s chipset and an 
>ics1893 phy.
>
>Peter Koegel                                            

Many thanks Peter, that will go into .23.

Re: [Etherboot-developers] sis640e/sis730s support for etherboot sis900 driver

[Marty C. <md...@th...>]

On 3/18/01 12:07 PM Peter K=F6gel pet...@to... wrote:
>I have written a patch that adds sis640e / sis730s support to the etherboo=
t 
>sis900 driver. I have testet it on a board with sis730s chipset and an 
>ics1893 phy.

Peter,  This is excellent!!

Someone sent me the latest linux driver and I was merging changes into 
the Etherboot driver, and your patch came.  What a pleasant surprise!

I will put up a test version of this on rom-o-matic.net, and will merge 
my changes with yours so it can be submitted for inclusion in the next 
release.

Best Regards and Thanks,

Marty

---
    Try: http://rom-o-matic.net/ to make Etherboot images instantly.

   Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827; Cambridge, MA 02139; USA
  Voice: (617) 491-6935, Fax: (617) 491-7046 
  Email: md...@th...
    Web: http://www.thinguin.org/

[Etherboot-developers] sis640e/sis730s support for etherboot sis900 driver

[Peter <pet...@to...>]

I have written a patch that adds sis640e / sis730s support to the etherboot 
sis900 driver. I have testet it on a board with sis730s chipset and an 
ics1893 phy.

Peter Koegel                                            

PS: I'm not in the mailing list, but you can contact me at 
pet...@to...

[Etherboot-developers] lance driver works at 10 mbs - fails at 100 mbs

[Eno C. <Eno...@Mi...>]

Have a client equiped with an AMD AM79C972 (LANCE) ethernet chip and an
unremarkable server both connected to a 10mbs 3com hub. Everything works as
expected.

When I replace the 10mbs hub with a 10/100 mbs 3com hub, the new hub
indicates all ports run at 100mbs, and the lance driver on the client will
not transmit. Literally; nothing shows up on the net when I watch it with
Aligent Lan Analyzer (which BTW is a WHOLE LOT nicer than tcpdump). The
transmit interrupt fails to arrive, as, I guess you would expect if no
transmission occurs, and the driver times out waiting for the interrupt.
Everything goes to pot after that.

Lance works at 10mbs, and the identical arrangement fails at 100 mbs. 

Does anyone have any insight into this behavior?

Eno Compton

[Etherboot-developers] Etherboot 4.7.22 (5.0RC2) released

[Ken Y. <ke...@nl...>]

I have released Etherboot 4.7.22 at http://etherboot.sourceforge.net

Changes from 4.7.21:

+ Preston Wilson pointed out that ds.internic.net should be replaced by
www.ietf.org in documentation URLs. Also RFC1090 should be RFC1094
(NFS).

+ Marty Connor pointed out some broken links due to the split in
documentation. Also comments don't match code in lance.c for change just
above. Also passed on a bug found by a user of rom-o-matic.net where
tftp was not defined when ANSIESC was defined. My mistake, I made it a
static function when it needs to be exported to ansiesc.c.

+ Christoph Plattner found that the Etherboot startup messes up the
flags while testing for a 386+. This doesn't affect Etherboot but it can
cause the loaded operating system to crash. Fix: pushf before and popf
after the CPU model testing.

+ Jean-Jacques Michel contributed patches to the via-rhine.c driver to
make it work for the VT6102 model as used on some DFE530-TX Rev.A3 NICs.

+ Luigi Rizzo sent in a fixed boot1a.s that actually works on HDs now.

+ Stefan Furtmayr sent in a list of URLs to TFTP servers for NT. Added
to directory contrib/Diskless-From-NT.

+ Paul Whittaker contributed a HOWTO in HTML format on booting with NT
as the server.  Added to directory contrib/Diskless-From-NT.

+ CJ pointed out that the advertised message size is > 1500 bytes.
Define MAX_BOOTP_EXTLEN so that the size of the structure matches the
Ethernet payload size.

MD5 sums:

ad60ec059932d655f3bb106c49560146  etherboot-4.7.22.tar.bz2
8d26e7f447f2cd1ba2896d4ab08fac10  etherboot-4.7.22.tar.gz

There are a couple more fixes in the pipeline, don't be discouraged if I
haven't included yours in this release. Keep those bug reports coming!

Re: [Etherboot-developers] Surprising 57, Maximum DHCP Message Size

[Ken Y. <ke...@nl...>]

|The 1500 byte maximum includes the 28 bytes of 
|IP and UDP header and the UDP payload.

Ok, that makes it simpler.

Re: [Etherboot-developers] Surprising 57, Maximum DHCP Message Size

[CJ <cj...@cj...>]

The 1500 byte maximum includes the 28 bytes of 
IP and UDP header and the UDP payload.

Ken Yap wrote:
> 
> |Etherboot version 4.7.21 surprisingly offers a
> |maximum message size of 1572.  I think that is
> |72 bytes too large for ethernet, unless he'll
> |accept multiple packets.
> 
> It will be limited by the MTU of the transmitting interface anyway.  No
> DHCP server should send out a packet that large. But probably
> MAX_BOOTP_EXTLEN should be defined as
> ETH_FRAME_LEN-ETH_HLEN-sizeof(struct iphdr)-sizeof(struct
> udphdr)-sizeof(struct bootp_t)
> 
> I'll change it to that in .22. Thanks.
> 
> _______________________________________________
> Etherboot-developers mailing list
> Eth...@li...
> http://lists.sourceforge.net/lists/listinfo/etherboot-developers

Re: [Etherboot-developers] Surprising 57, Maximum DHCP Message Size

[Ken Y. <ke...@nl...>]

|Etherboot version 4.7.21 surprisingly offers a 
|maximum message size of 1572.  I think that is
|72 bytes too large for ethernet, unless he'll
|accept multiple packets.

It will be limited by the MTU of the transmitting interface anyway.  No
DHCP server should send out a packet that large. But probably
MAX_BOOTP_EXTLEN should be defined as
ETH_FRAME_LEN-ETH_HLEN-sizeof(struct iphdr)-sizeof(struct
udphdr)-sizeof(struct bootp_t)

I'll change it to that in .22. Thanks.

[Etherboot-developers] Surprising 57, Maximum DHCP Message Size

[CJ <cj...@cj...>]

Etherboot version 4.7.21 surprisingly offers a 
maximum message size of 1572.  I think that is
72 bytes too large for ethernet, unless he'll
accept multiple packets.

Re: [Etherboot-developers] Problems with sis900 (rev 81)

[Marty C. <md...@th...>]

On 3/12/01 11:38 AM Daniel Coletti dco...@xt... wrote:
>	I'm having a problem with the sis900 etherboot driver. The regular sis900 
>has no problem, but when I try with this particular revision (81), I get 
>the exact same problem that the sis900 kernel module had (it can't find 
>the EEPROM, therefore it can't find the card). The SiS developers have 
>solved this problem (with the v1.06.07), does anybody have a new patch 
>for this card? Has anyone solved this problem (without a path)?
>Thanks a lot!

Thanks for your report and for sending me the newest linux kernel driver, 
Daniel.  I see the changes that will be required to make the Etherboot 
driver work with rev 81 sis900 cards.  It will take a few hours to 
integrate and test the new code.

I didn't get a chance to work on it this weekend, but should have a new 
sis900 driver to test within a week or so (I mostly do my hobby 
programming on the weekends because of my other commitments).

Because Etherboot drivers have a different structure (polling, memory 
constraints, etc.) I can't just "diff and drop" the code in, but have to 
translate from "kernel-ese" to "Etherboot-ese" and adjust data 
structures.  It takes time and care.

Once I have a version to test, I'll send it to you, or I will put it in a 
test section of the rom-o-matic.net site.  I don't have a Rev 81 card to 
test with, you see.

Thanks for your reports and your patience.  We should get this fixed soon.

Regards,

Marty

---
    Try: http://rom-o-matic.net/ to make Etherboot images instantly.

   Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827; Cambridge, MA 02139; USA
  Voice: (617) 491-6935, Fax: (617) 491-7046 
  Email: md...@th...
    Web: http://www.thinguin.org/

[Etherboot-developers] Problems with sis900 (rev 81)

[Daniel C. <dco...@xt...>]

Hi,
	I'm having a problem with the sis900 etherboot driver. The regular sis900 
has no problem, but when I try with this particular revision (81), I get 
the exact same problem that the sis900 kernel module had (it can't find 
the EEPROM, therefore it can't find the card). The SiS developers have 
solved this problem (with the v1.06.07), does anybody have a new patch 
for this card? Has anyone solved this problem (without a path)?

Thanks a lot!

Daniel//
-- 
Daniel E. Coletti
Director
XTech (Soluciones Linux para E-Business)
Tel: ++54-114-782-5528
Fax: ++54-114-782-6117

Re: [Etherboot-developers] http://rom-o-matic.net/4.7.21 eepro100 FLOPPY ANSIESC

[Marty C. <md...@th...>]

On 3/9/01 11:45 PM Ken Yap ke...@nl... wrote:
>On 3/9/01 8:36 AM CJ cj...@cj... wrote:
>>Building a rom fails if either FLOPPY or ANSIESC is specified,
>>in 4.7.20 and 4.7.21, but not in 4.6.12.
>Thanks, this has been reported and will be fixed in .22. If you want to
>patch it yourself temporarily:
>In main.c:
>Remove the static from the header of tftp().
>Remove the forward declaration of tftp().
>In etherboot.h:
>Add a prototype for tftp(), it will be the same as for nfs().

I patched this on http://rom-o-matic.net/ version 4.7.21. It should work 
now.

Enjoy

---
    Try: http://rom-o-matic.net/ to make Etherboot images instantly.

   Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827; Cambridge, MA 02139; USA
  Voice: (617) 491-6935, Fax: (617) 491-7046 
  Email: md...@th...
    Web: http://www.thinguin.org/

[Etherboot-developers] Re: [Ltsp-discuss] Problem with new version of imggen for 3com 905C

[Marty C. <md...@th...>]

On 3/9/01 3:06 PM Jim McQuillan ja...@Mc... wrote:
>2)  Kernel driver.  Either 3c59x.c or 3c90x.c.  It's
>    worth trying the 3c90x.c to see if it helps.  You
>    can get that from 3com.  Look for the link on
>    the www.scyld.com site.
>I suppose that there is a chance that using different
>bootcode could help the 'Neighbour table overflow' problem.
>It was suggested a couple of days ago that someone try
>modifying the Etherboot driver to disable the card before
>handing control over to the kernel.  I haven't had a chance
>to try that.

I did some research on this issue, and is is not an Etherboot driver 
issue. 

Check out:

   http://www.scyld.com/pipermail/vortex-bug/2001-February/thread.html

and this message:

   http://www.scyld.com/pipermail/vortex-bug/2001-February/000970.html

If you're using a 2.2.x kernel, you'll need to download new kernel driver 
code from:

   http://www.uow.edu.au/~andrewm/linux/3c59x.c-2.2.19pre11.gz

Which is said to fix the problem with the 3c905cx issues.  (usually 
you'll find the file on your system in /usr/src/linux/drivers/net/).

I am broadcasting this information widely, since there have been quite a 
few messages on this topic.

In summary, if you're using 3c905cx boards with Linux kernel 2.2.x you'll 
need to update and recompile your kernel or you may get the infamous 
"Neighbour table overflow" bug in some instances.


---
    Try: http://rom-o-matic.net/ to make Etherboot images instantly.

   Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827; Cambridge, MA 02139; USA
  Voice: (617) 491-6935, Fax: (617) 491-7046 
  Email: md...@th...
    Web: http://www.thinguin.org/

Re: [Etherboot-developers] http://rom-o-matic.net/4.7.21 eepro100 FLOPPY ANSIESC

[Ken Y. <ke...@nl...>]

>Building a rom fails if either FLOPPY or ANSIESC is specified,
>in 4.7.20 and 4.7.21, but not in 4.6.12.
>
>and then:
>ld -N -Ttext 0x94000 -e _start -o bin32/3c503.tmp bin32/start32.o 
>bin32/config-3c503.o bin32/3c503.o bin32/bootlib.a
>     bin32/bootlib.a(ansiesc.o): In function `docommand':
>     /tmp/ROM8ihSOT/ansiesc.c:172: undefined reference to `tftp'

Thanks, this has been reported and will be fixed in .22. If you want to
patch it yourself temporarily:

In main.c:

Remove the static from the header of tftp().
Remove the forward declaration of tftp().

In etherboot.h:

Add a prototype for tftp(), it will be the same as for nfs().

Re: [Etherboot-developers] http://rom-o-matic.net/4.7.21 eepro100 FLOPPY ANSIESC

[Marty C. <md...@th...>]

On 3/9/01 8:36 AM CJ cj...@cj... wrote:
>Building a rom fails if either FLOPPY or ANSIESC is specified,
>in 4.7.20 and 4.7.21, but not in 4.6.12.
>
>first:
>gcc -DIMAGE_MENU -DMOTD -DASK_BOOT=3 -DANS_DEFAULT=ANS_NETWORK 
>-DBACKOFF_LIMIT=7 -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 
>-DCOMPARM=0x03 -DANSIESC -DTRY_FLOPPY_FIRST=0 
>-DUSE_INTERNAL_BUFFER -O2 -g -fstrength-reduce 
>-fomit-frame-pointer -m386 -malign-jumps=1 -malign-loops=1 
>-malign-functions=1 -Wall -W -Wno-format -Wno-unused 
>-DVERSION_MAJOR=4 -DVERSION_MINOR=7 -DVERSION=\"4.7.21\" 
>-DRELOC=0x94000  -o bin32/ansiesc.o -c ansiesc.c
>     ansiesc.c: In function `docommand':
>     ansiesc.c:172: warning: implicit declaration of function `tftp'
>and then:
>ld -N -Ttext 0x94000 -e _start -o bin32/3c503.tmp bin32/start32.o 
>bin32/config-3c503.o bin32/3c503.o bin32/bootlib.a
>     bin32/bootlib.a(ansiesc.o): In function `docommand':
>     /tmp/ROM8ihSOT/ansiesc.c:172: undefined reference to `tftp'

Thanks for the report.  This should be fixed in 4.7.22.  The tftp 
function in main.c should not be declared static.  Sorry for the 
inconvenience.


---
    Try: http://rom-o-matic.net/ to make Etherboot images instantly.

   Name: Martin D. Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827; Cambridge, MA 02139; USA
  Voice: (617) 491-6935, Fax: (617) 491-7046 
  Email: md...@th...
    Web: http://www.thinguin.org/

[Etherboot-developers] http://rom-o-matic.net/4.7.21 eepro100 FLOPPY ANSIESC

[CJ <cj...@cj...>]

Building a rom fails if either FLOPPY or ANSIESC is specified,
in 4.7.20 and 4.7.21, but not in 4.6.12.

first:
gcc -DIMAGE_MENU -DMOTD -DASK_BOOT=3 -DANS_DEFAULT=ANS_NETWORK 
-DBACKOFF_LIMIT=7 -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 
-DCOMPARM=0x03 -DANSIESC -DTRY_FLOPPY_FIRST=0 
-DUSE_INTERNAL_BUFFER -O2 -g -fstrength-reduce 
-fomit-frame-pointer -m386 -malign-jumps=1 -malign-loops=1 
-malign-functions=1 -Wall -W -Wno-format -Wno-unused 
-DVERSION_MAJOR=4 -DVERSION_MINOR=7 -DVERSION=\"4.7.21\" 
-DRELOC=0x94000  -o bin32/ansiesc.o -c ansiesc.c
     ansiesc.c: In function `docommand':
     ansiesc.c:172: warning: implicit declaration of function `tftp'

and then:
ld -N -Ttext 0x94000 -e _start -o bin32/3c503.tmp bin32/start32.o 
bin32/config-3c503.o bin32/3c503.o bin32/bootlib.a
     bin32/bootlib.a(ansiesc.o): In function `docommand':
     /tmp/ROM8ihSOT/ansiesc.c:172: undefined reference to `tftp'

Re: [Etherboot-developers] [Ltsp-discuss] Neighbour table overflow and 3com cards

[Stephan L. <la...@ph...>]

Hi

> 2) The 3c905cx-txm has the 'Neighbour' problem.
I've set up a working test kernel for the 3c905c some weeks ago.
I used suses patched linux-2.2.16er kernel sources and one of these
drivers:
- 3c59x.c:v0.99 12Jun00
- 3Com 3c90x Version 1.0.0

By the time I could test it again... waiting for some hardware. :-/

> So, any network driver hackers out there have any ideas?
I'm sure the 3c905c will work. But I could make some tests... maybe in
about one week (hope so).

Liebe Gruesse, with best regards
Stephan Lauffer

[ Pedagogical University Freiburg - Germany ]
[ http://www.ph-freiburg.de/zik/            ]

Re: [Etherboot-developers] driver for sis900

[<ke...@nl...>]

> 	Does anyone know if somebody has developed an etherboot driver for the
> sis900 card? Is there any work in process?

We had a mysterious feeling you were going to ask for this driver today so Marty
Connor wrote it a few days ago, and I released it in 4.7.21. :-)

------------------------------------------------------
This mail sent via NLC WebMail: http://www.nlc.net.au/

Re: [Etherboot-developers] driver for sis900

[Marty C. <md...@th...>]

On 3/8/01 9:19 PM Daniel Coletti dco...@xt... wrote:
>Does anyone know if somebody has developed an etherboot driver for the 
>sis900 card? Is there any work in process?

Yes, it's in Etherboot 4.7.21 and on http://rom-o-matic.net/ 

Enjoy

---
    Try: http://rom-o-matic.net/ to make Etherboot images instantly.

   Name: Martin D. Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827; Cambridge, MA 02139; USA
  Voice: (617) 491-6935, Fax: (617) 491-7046 
  Email: md...@th...
    Web: http://www.thinguin.org/

[Etherboot-developers] driver for sis900

[Daniel C. <dco...@xt...>]

Hi!
	Does anyone know if somebody has developed an etherboot driver for the 
sis900 card? Is there any work in process?

thanks!

Daniel///
-- 
Daniel E. Coletti
Director
XTech (Soluciones Linux para E-Business)
Tel: ++54-114-782-5528
Fax: ++54-114-782-6117

Re: [Etherboot-developers] eepro100 bootrom

[Doug A. <amb...@wh...>]

Vol...@da... writes:
|      but the networkbios in the flash doesn't work ;-(   i'm sure that the
| biosimage in the flash is at the right position, cause every other programm
| (e.g. the           original Intel networkcardbios ) works.
| 
|      if i use a Windws98 bootfloppy and try to boot from the harddisk it
| runs property (althouh this shouldn't be possible !!! ther's no
| harddisk....) and boots  from the flashimage?????

Are you saying here that if you use a Windows boot floppy and select the
harddisk that Etherboot then works?  If so then my guess it that 
either the boot sequence is hanging or not going through the normal boot
sequence.  To get around this try enabling NOINT19H in the Config file for 
Etherboot.  Then as soon as the rom code is seen by the BIOS it will
run without waiting for the later boot process.

Doug A.

Re: [Etherboot-developers] eepro100 bootrom

[Marty C. <md...@th...>]

On 3/7/2001 9:52 AM Vol...@da... Vol...@da... 
wrote:
>     but the networkbios in the flash doesn't work ;-(   i'm sure that the
>biosimage in the flash is at the right position, cause every other programm
>(e.g. the           original Intel networkcardbios ) works.

Which version of Etherboot are you using?  There was a recent change to 
Etherboot to make ROMs PNP compatible.  This involved some bytes that 
were swapped in the ROM image.  A detailed message on the issue is here:

    http://www.geocrawler.com/archives/3/5299/2001/1/0/4982673/

You can get an up-to-date ROM image from 

    http://rom-o-matic.net/

which should have the fix in it.

Let us know how it goes...

Marty

---
    Try: http://rom-o-matic.net/ to make Etherboot images instantly.

   Name: Martin D. Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827; Cambridge, MA 02139; USA
  Voice: (617) 491-6935, Fax: (617) 491-7046 
  Email: md...@th...
    Web: http://www.thinguin.org/

[Etherboot-developers] eepro100 bootrom

[<Vol...@da...>]

Hi...
I'm developing d diskless computer with is suppared to run under Linux;=
 it
seemed to work pretty good, but now I=B4ve got a big problem with ether=
boot.
The MachZ -- a single chip computer (www.zfembedded.com) -- runs with
Ph=F6nix bios, witch is written into the the flashram (AM29F016B  2MB) =
as
same as the networkcardbios (eepro100). Inthe end the MachZ should run =
only
over network, there will be no floppy or harddisk installed.

And that's the point:
     everthing is doing fine, when i boot from a floppy

     but the networkbios in the flash doesn't work ;-(   i'm sure that =
the
biosimage in the flash is at the right position, cause every other prog=
ramm
(e.g. the           original Intel networkcardbios ) works.

     if i use a Windws98 bootfloppy and try to boot from the harddisk i=
t
runs property (althouh this shouldn't be possible !!! ther's no
harddisk....) and boots  from the flashimage?????

So i hope you can retrace my work and you know a way witch fits to my
requirement...

Volker Stark
Research & Development
DaTARIUS Technologies GmbH
Tel: +43 5672 206 614
Fax: +43 5672 206 8 614
http://www.datarius.com=

Re: [Etherboot-developers] Problem found + Bug Fix *** More analysis to the old problem with etherboot+GRUB(diskless/disk)

[Marty C. <md...@th...>]

On 3/6/2001 6:24 PM Christoph Plattner chr...@do... wrote:
>The problem for the crashing kernel was the CPU detection in the start
>code
>of the etherboot (start32.S). The CPU detection is done via checking,
>which
>bits of the FLAGS CPU register ar stucky or not (see comment in
>start32.S).

Great work Christoph!  I wonder if this might help the problem I'm having 
with getting Etherboot .lzlilo images to load from LOADLIN under M$ 
Windows.

BTW, if anyone wants to make a few bucks, my company is willing to pay a 
few hundred US$ (or equivalent) for a solution and explanation of the 
LOADLIN problem.  Send me email if you're interested.

Regards,

Marty

---
    Try: http://rom-o-matic.net/ to make Etherboot images instantly.

   Name: Martin D. Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827; Cambridge, MA 02139; USA
  Voice: (617) 491-6935, Fax: (617) 491-7046 
  Email: md...@th...
    Web: http://www.thinguin.org/

Re: [Etherboot-developers] (no subject)

[Marty C. <md...@th...>]

On 3/6/2001 5:38 PM Eno Compton Eno...@Mi... wrote:
>Looking up port of RPC 100003/2 on 192.168.1.1 
>Root-NFS: Unable to get nfsd port number from server, using default
>I am suspicious of this because my sniffer reports the rpc request and
>response as follows
> 002584            0.000.155.040  102 Linux Server     TNS-4 Front
>Portmapper Procedure Name - 3 ( PMAPPROC_GETPORT ) Call
> 002585            0.001.892.120   74 TNS-4 Front      Linux Server
>Portmapper Procedure Name - 3 ( PMAPPROC_GETPORT ) Reply
>which seems to indicate the server did as it was requested.

Well, you might turn up the debugging level of your portmap service and 
see what appears in your /var/log/messages or /var/log/secure files.

The above only suggests that you made a request and got a response.  The 
response could very well have been "hell no!".

Also, since portmap uses /etc/hosts.allow and /etc/hosts.deny, perhaps 
you haven't given that subnet permission to use portmap.

>Can anyone tell me what this means and how I might proceed to overcome this
>embarrassment?

Hopefully they suggestions will help you preserve your honor and the 
studliness you are no doubt known for in the computer lab ;-)

Marty

---
    Try: http://rom-o-matic.net/ to make Etherboot images instantly.

   Name: Martin D. Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827; Cambridge, MA 02139; USA
  Voice: (617) 491-6935, Fax: (617) 491-7046 
  Email: md...@th...
    Web: http://www.thinguin.org/