not an answer, but a guide for trouble shotting.
your best friends should be:
1) null modem 232female<->232female cable with second computer that has com port (or laptop with usb->serial converter) ... soldering cable by your self wire to wire is maybe best solution.
2) windows hyper-terminal simple but reliable application preinstalled on most windows... started in comPort mode, with same bitrate/parity/stopbits parameters that you expect from modules.
- first check if connection and cable is ok by running hterm on both comps and 'chat' few sentences
- second check if your program ok by running it on first comp, and hterm on other
- Modbus modules sometimes do not send anything before Master sends some query on module address, so maybe your program need to send something first (for that investigation you can log your modbusPool with other comp connected instead MBUS-modules)
... with all respects to windows signaling queues and MSCOmm class that is probably ok, but to eliminate all possible reasons for communication failure in project start, maybe you should prefer simple threating COM port as file, and reading from it inside some while loop ... some short version of this example... Setting serial parameters at start and reading file named comX.
above link has good cSerialClass implementation on download, but simple primer without any error checking is here at pastebin .