Project Evil provides a set of basic functions commonly used by Windows network drivers. These functions are then translated internally to the FreeBSD driver model. To the driver, it appears that it is running in a normal Windows environment. To the OS, it appears that a native FreeBSD kernel module containing the driver is present. This article explains how it works.
Post a Comment
Member since:
---
Member since:2005-07-06
Member since:---
Member since:---
Member since:
---
There are alot of devices for which there are no open-source drivers, and probably never will, so any way to get them working is better than nothing. I for example have a Cardbus wlan-card, which doesn't work under Linux with any possible open-source drivers, but with ndiswrapper it was trivial to make it work. So, I have to say this is again a good thing =)
-WereCat
Member since:2005-07-06
Member since:
2005-07-12
Although the article wasn't entirely clear about it, Project Evil is included in the base install of FreeBSD from 5.0 on (I think, it may have been added a bit later). Anyway, install the newest version of FreeBSD and it will all be there ready to go... Or just cvsup the freebsd source if you really want to take a look at the source and how it looks.
Member since:
---
Member since:---
Member since:
---
As some folks have mention that "Project Evil" or "NDISulator" is part of the base system. With respect to where is the source code. Some additiona information can be found:
FreeBSD Handbook
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-w...
FreeBSD man page:
http://www.freebsd.org/cgi/man.cgi?query=ndis&sektion=4
http://www.freebsd.org/cgi/man.cgi?query=ndiscvt&sektion=8
Some early links "Project Evil" at kerneltrap.org
http://kerneltrap.org/node/3542
Now, with all due respect:
"I can not imagine how this is on OSNews. Where in earth do I DOWNLOAD the Source or binary. For me the article is useless without links to source."
This sounds a tad bit like a troll, updating source code (on *BSD) is a simple matter of using CVS.
As an FYI: I submitted the information to osnews (diff IP address). I assumed that CVS might be obvious; to the *BSD community. If this isn't a troll, they you have my sincerest apology and to the community. Perhaps I mad a faulty assumption. Sorry in advance
Member since:
2005-07-06
Contrast this to my experience with Zeta (which also has NDIS). Boot PC, adjust ndis_settings file (vendor and chipset ID), rescan /dev/net, go to Network preferences, adjust, Apply, surf.
Admitably, on the 2nd wireless card I tried, since the first one didn't work, since yellowTab supply no documentation as to where to put the .bin file. The above procedure only works for Windows drivers which are contained in one single file, not 2.
Member since:
2005-07-07
Member since:
2005-07-08
Sad to say, but I was never able to get Project Evil working for two different wireless cards under FreeBSD. Nor, for that matter, would ndiswrapper work for the same cards under Linux. This is why, when you have the option, you should always choose cards for which there are native drivers. I've had much luck with atheros cards under Linux and FreeBSD.
Adam
PS. I'm not trying to diminish the work the developers have done. I'm just pointing out that it doesn't always work the way it should.
