I am trying to get Modsoft running inside a VMWare image and have been unable to get it to communicate over the serial port with a controller.
Having tried to access the controller from a different machine, it all works fine.
The VMWare image has Windows 95 on it, with just Modsoft installed, currently running on a Windows XP Pro host machine.
When I attempt to connect to the controller, I get a flash on the controller's lights, but nothing more.
I have tried forcing the parity, flow control, data rate etc. on the serial ports on both the host and the guest, but this made no diference.
I tried mapping the output from the serial port from the guest OS to a file on the host and this showed that there was something getting out of the guest OS (although it did appear as a random set of characters - not sure what it should look like).
I have looked around quite extensively to figure this one, and have come out with a couple of possible issues, but I've very little knowledge about Modsoft / Modbus and couldn't confirm them. These where:
1)Maybe non-standard pins were being used on the cable that were not being emulated and passed through by VMWare.
2)The host OS (Windows XP) maybe 'intercepting' the data and altering it in some way.
Can anyone confirm or remove either of these?
Has anyone been able to get modsoft running correctly inside a virtual machine, talking out over the serial port?
Any ideas what I'm doing wrong?
Thanks
Having tried to access the controller from a different machine, it all works fine.
The VMWare image has Windows 95 on it, with just Modsoft installed, currently running on a Windows XP Pro host machine.
When I attempt to connect to the controller, I get a flash on the controller's lights, but nothing more.
I have tried forcing the parity, flow control, data rate etc. on the serial ports on both the host and the guest, but this made no diference.
I tried mapping the output from the serial port from the guest OS to a file on the host and this showed that there was something getting out of the guest OS (although it did appear as a random set of characters - not sure what it should look like).
I have looked around quite extensively to figure this one, and have come out with a couple of possible issues, but I've very little knowledge about Modsoft / Modbus and couldn't confirm them. These where:
1)Maybe non-standard pins were being used on the cable that were not being emulated and passed through by VMWare.
2)The host OS (Windows XP) maybe 'intercepting' the data and altering it in some way.
Can anyone confirm or remove either of these?
Has anyone been able to get modsoft running correctly inside a virtual machine, talking out over the serial port?
Any ideas what I'm doing wrong?
Thanks