FPC always reads fpc.cfg if it's in right path. In windows this means it must be placed where the binary of FPC is (and I think $HOMEDRIVE/$HOMEDIR/fpc.cfg is also checked).

The only way to NOT use fpc.cfg (if it's in right place) is to use -n option.

fp.cfg is useless for non fp users.