fork does not work fine on windows, read perlfork

when run outside of par on windows this test program doesn't run 50 threads 1 at a time

when run after being par packed, the output is exactly the same as when run outside of par, except after the program ends/exits there is a memory violation

so fork works just the same on win32 inside/outside of par, the memory violation message can be quieted with  use Win32API::File(); Win32API::File::SetErrorMode(2);

I didn't scrutinize the OPs code to see if has logic errors because

If you're going to be calling the code "threads" this might as well use real threads , its is much better on win32 than fork