Is the method of putting my ethernet drivers in a "My Drivers" folder in the Plugins folder still a viable technique? I can't seem to get a connection working from the cd anymore (3.12). I'm currently posting from virtual box where it has mis-identified my net card but the driver it's using is working. I have an onboard Nvidia MCP ethernet card and it's id'ed it as an AMD PCNET Family adapter.
Also is anyone noticing extremely long boot times with 3.12? It's taking 15 minutes to boot up where 3.06 took 5 mins max.

You can add to the already present NIC drivers in the folder \drivers\Net\*MY DRIVER* (Use the included drivers as a guide)
To use the \plugins directory, you must create a driver plugin.

Boot times are normally related to the build script (Autobuild)... Did the script finish without errors?

Hey, 313 was just released today... perhaps a clean start will solve the issue.

Virtual Machine means Virtual Hardware too. This is a normal NIC when using a Virtual Machine for testing. I get the same NIC detected when I use VMWare because that is the "Standard" for a virtual hardware driver.

Well I made a plugin with the Hardware Plugin Builder many versions ago. I've been copying it from build to build ever since and it's worked great.

On the boot time, I had no errors at all during the build.

You also should understand that running UBCD4Win from a virtual machine you can not expect to see the same drivers that the actual system has. So while your system may have a nVidia ethernet card... the VM uses emulated hardware... so it's not the same drivers that it ( the VM ) uses as what your actual system uses.