Hi,
That doesn't sound right.....
On my system there's C:\PBP3\MPASM-MPLAB_SETUP\PBP_MPASM_Connector.exe Obviously you might have PBP3 installed somewhere else but I can't see how the PBP_MPASM_Connector.exe would end up in the MPASM Suite installation folder....

Simply running it won't change anything. If you have multiple versions of MPASM installed you must make sure that the path to the correct version is what the tool points to. If the tool point to the older version you have on your system then that is what PBP will invoke for assembly and you'll get the /s parameter error - that's theory anyway.....

/Henrik.