Hi Urias, > So, it was apparently something wrong with my haiku install - i wiped the > partition and re-installed fresh (instead of using the usual jam > install-haiku over my existing rev) and it seemed to work after that. Yes, sometimes one needs to check for errors from that direction. Another thing I experienced was when I did the last change on the icon renderer (to fix the problem in Vision's app menu), ever since than Tracker wouldn't display the internal icons correctly anymore (on one of my installs). After simply wiping all objects, it works great again. The icon code gets built as a static library, and though this seems to work well now for most of the time, appearantly sometimes something can still go wrong. (No worries though, Ingo, happens seldomly enough. I only mention it so that one has this in mind when going hunting for obscure bugs...) > The 3com driver works well! I decided to test a few more cards I had > lying around here and I was able to test the following cards that worked > for the following drivers: > > 3com > 10b7:9050 3Com 3C905-TX (A) > 10b7:9055 3Com 3C905B-TX (tried both rev B and D) > 10b7:9200 3Com 3C905C-TX > > etherpci > 10ec:8029 SMC1208T (RTL-8029) > > rtl8139 (new) > 1186:1300 D-Link DFE-530TX+ Rev.E1 (RTL8139) > 1113:1211 Accton Technology Corp SMC2-1211TX [8<] > Thanks again for porting those drivers, they appear to work extremely > well! This is really great news! And of course it means if the drivers are working extremely well, the networking stack itself has to be too... :-) Thanks a lot everyone involved! Seems like we ended up having the best of both worlds: A cleanly designed BeOS/Haiku-style network stack _and_ all those FreeBSD drivers! :-) Best regards, -Stephan