You should consider an alternate method to fork() on Windows for concurrency. You'll find it's common to use threads, and you can create a new process, but I don't think you can fork a process in Windows at all.
Do you know what the main difference between Apache v1 and v2 is? Threads rather than fork, probably for this reason.
I've never heard of such a thing, so I'd say no. But maybe someone else may know of something. And even if something managed it, I can't imagine it making the best use of Windows resources. It's just not the Windows way of doing things. And Windows is slow enough as is don't you think?
cygwin provides a posix like api, including fork and pipe, on Windows. However, I know almost nothing about it so can't offer much advice other than that.
Truly, fork isn't as beneficial as its made out to be. Any OS since 2000 seems to be capable of threading so why not use them? Much lighter, easier to initialize.
Windows is a different OS, and it does not fork(). (Sometimes it can be made to, using undocumented -- i.e. changeable -- APIs, but that's that.)
Windows actually has a very simple, intelligent, modular design. Also, forking is a stupid idea to begin with. It isn't a very friendly way to do things.