Re: New driver loading scheme for Project Evil, need input

> > You still end up needing the C compiler, objcopy, ndiscvt and (optionally)
> > iconv, but the script automates the use of all these tooks and explains
> > to the user what's going on while it's working.
> 
> It's certainly simpler than the current state of afairs and unless the kernel 
> NDIS grows the ability to directly read .sys & .inf files from your disk 
> (which would be very cool :) it's about a simple as it's going to get..

I think it's small enough as such, given that Project Evil isn't the only
thing that needs a C compiler, and iconv...how much does Project Evil require
that isn't in the base FreeBSD install anyways?

> > - What should the script be called? wintobsd.sh sounds kind of lame.
> 
> encappe
> win2elf
> pe2elf
> 

exorcist.sh ;)
ndisload.sh
driverload.sh
windriver.sh
pureevil.sh >=]

-R. Tyler Ballance

..and back to work..