So my point was that I actually didn't need help with anything until "consume this on the Vera". By "driver" on the PC, I was referring to the virtual device that turns the remote TCP port (socket) into a local Serial I/O port which allows me to write .NET code that uses System.IO.Ports. Not rocket surgery.

Point is, I don't need help with anything but Vera. WizNet gives me directions, and I've used my WizNet for 2 years with no issues. Vera on the other hand hasn't updated their documentation since, well, ever.
Vera UI7 doesn't let me configure anything until it "detects" something. How is it supposed to "detect" something that is sitting on a remote TCP port without me configuring
something (i.e. IP and port)? So, since I can't seem to get anywhere with the native UI7, I downloaded IPSerial xml files, which seems to be the only way? A few attempts, wipes, and attempts more (apparently you must create a dummy IPSerial device then restart the engine -- which makes some sense but begs why the restart on upload is default?), and I finally get a (non-virtual?) device to show up under Develop Apps -> USB/Serial Devices that is asking for several bits of information. I can't figure out if I can put in arbitrary stuff there or what (I mean I put the IP and port number, but that's two of like six fields). Anyway, eventually I see a status of connecting at the top, and the port is no longer accessible by anyone else. So it must be working, or so I think.
I select the built-in "Insteon Network" device (since I'm trying to access a remote PLM), but the built-in Insteon module still won't use the new remote port I just spent 2 days creating. As best I can tell from the logging, it expects USB or nothing at all. Furthermore, all I did was restart Vera, and now I can't seem to get it to 'connect' again. I don't feel any desire to wipe Vera again, since that seems to be the key to getting anything working in UI7.