On Wed, Mar 9, 2011 at 11:16 AM, Rance Hall <[email protected]> wrote: > This idea has merit, but let me provide another use case. > > Before I went back to school for my masters I was in industry and we were > faced with that ever present, conversion path problem. > How do you go from ancient software hardware that might have come to America > on the Mayflower, to something that slightly resembles the 20th century.
I have given the idea some more thought.... I think NO major changes to the VBox architecture would be needed... just to design a Win32 NETWORK PROTOCOL, a "dummy" network protocol for that matter, with a bridge and host-side virtual device. If I´m no mistaken, the Windows networking layer (oversimplified) goes like this: (from lower-layer to top). NIC DRIVER (ancientdevice.sys) NDIS PROTOCOL STACK (say TCP) WINDOWS SOCKETS APPS By hooking up at the protocol level, wouldn´t it have full access to the propietary NIC on the win32 guest, yet, at the same time, would be able to forward frames at the layer 2 level, to a dummy NIC on the host side... Does this make sense?. FC ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
