🚀 go-pugleaf

Hope this is posted to the right group; the problem surfaced when I created an app that uses TCP sockets.

I'm using the WinPCap library to create raw sockets in promiscuous mode. This uses winsock2.h, which is based on winsock 2.2.  

The app compiles and runs fine.  I also need to open a standard TServerSocket to open a pipe to another application. As soon as I drop this component onto the form, the compiler complains about a multiple declaration for 'fd_set', which is defined in both winsock.h and winsock2.h.  Turns out the Borland native components call winsock.h in WinSock.hpp, so both winsock header files are used, creating the conflict.

Can I modify WinSock.hpp to call winsock2.h instead of winsock.h without destroying previous projects, or creating some kind of rift in the time-space continuum?  The change seems innocuous enough, but WinSock.hpp explicitly states "dont modify this machine-generated header".  Does this mean that even if I change the reference from winsock to winsock2, it will be overwritten anyway?  

For various reasons, I'd like to have (int the same application) the use of both my standard Borland socket components and the WinPcap library as well.

TIA

Mike