Quote - About 8, I addressed this to E-Frontier. Be sure you give access to the (local) net, maybe check your firewall settings. This worked for me, however I still don't know why rendering in a separate process always accesses the network. E-Frontier says it's to check no other copy of Poser is running in the network with the same registration number, but I don't see what this has to do with rendering in a separate process.

Read those ReadMe files, people. It's clearly explained in the Poser 7 readme: > Quote - New in version 7 is the option to render in a separate process. In order to communicate with the render process, Poser uses sockets. Some personal firewall software mistakenly reports this as an attempted connection to the internet. If you wish to render in a separate process, you will have to allow network communication on localhost (127.0.0.1) in your personal firewall software for Poser.exe and FFRender.exe.