Heeeeeeeeeeeeeelp??

> If u do not know d answer, there is no need to reply.

I knew you were going to say that. the boards are a mess, nobody can be bothered to put a descriptive subject line any more, so we can't filter out anwerable questions from unanswerable ones. result: less people getting help.

also, there are too many people not being specific about their problem. like you. if we just let these things slip, the forums stop working and nobody gets any help. don't take offence because I'm trying to clean things up a bit. remember who's asking who for help

georgemca at 2007-7-11 22:08:48 >

Ok.

First, please include a decent title in the future. The people here help out of the goodness of their hearts, so you might want to help them help you by providing a clear and concise title.

Second, you're going to have to either go directly to the NIC's API, or you're going to have to write a program that requests that information from the operating system. Hardware is low-level stuff that Java just was not designed to work with.

Finally, the answer to your question is -way- beyond the scope of these forums. Even if you were to provide all the specs on your NIC, and the source-code for the drivers (certainly written in a language other than Java), I doubt anyone here would devote the many hours it would take to explain the process.

Joe

Joe_ha at 2007-7-11 22:08:48 >