Nobody can help me ?

🙁

It's not clear exactly what you're doing. Do you have a real modem attached to COM3 which you're using in DOSBox as directserial?

You might want to try the SVN Daum version of DOSBox (or just the latest DOSBox SVN), as I believe there was a small fix made to serial port passthrough in the time since the official release of DOSBox 0.74.

You also might want to consider using the modem emulation included in DOSBox to communicate with another computer on your network. See for instance DosBox Guide to Multiplayer Games . Or is that what you're doing already? As per that link, ATDT with the emulated DOSBox modem expects an IP address.

Of course, to be sure DOSBox is only intended to work with games and support for applications is limited.

Yes! What i am doing is to use a real 56k modem on a directserial. But i am trying to use it with a dos app,that need an external modem to setup a call and for which i don't have source code and specification. Even if i know is useless, i have configured the serial port used by the app as modem emulation : the app start the ATD command !! When I configured the same port as directserial the app doesn't setup the call (I try with dos 5 and 6.22 installation in dos box with several "mode" configuration, with several at command for modem initialization without success). So, what I am trying to understand is which kind of "initialization" the dosbox modem emulator perform, in order to allow the app to setup the call (it seems that the app Is recognising the modem...). The same initialization that I am not able to setup with the real modem connected and configured on a directserial port. I hope that now the point is clear.
Maybe the developper/s of modem emulation know the answer...

J

JekhoOne wrote:

Even if i know is useless, i have configured the serial port used by the app as modem emulation : the app start the ATD command !! When I configured the same port as directserial the app doesn't setup the call (I try with dos 5 and 6.22 installation in dos box with several "mode" configuration, with several at command for modem initialization without success).

This seems to be a unique feature of your application. I would start by double-checking if you modem actually works in other situations. Can you use the modem to dial out in Windows, for instance?

In any case, if your software is happy with the emulated DOSBox modem, why not just use that instead? Even if there's a phone number hard-coded in the software, you might be able to replace it with a hex editor.

Jorpho wrote:

This seems to be a unique feature of your application. I would start by double-checking if you modem actually works in other situations. Can you use the modem to dial out in Windows, for instance?

It could be really strange but is the reality . External modem work in window (seven) environment (in old IT infrastructure) performing properly calls and exchanging data flow and inside ods box through echo AT commands sent directly to the device.

JekhoOne wrote:

In any case, if your software is happy with the emulated DOSBox modem, why not just use that instead? Even if there's a phone number hard-coded in the software, you might be able to replace it with a hex editor.

Mmm... i can't. It is needed to install on the other side (server one) another DosBox emulation with a ethernet GTW able to translate physical and logical protocol. To tough solution. I need only to understand how to let the App recognize the external modem sending ATDT command as in emulation modem mode...

JekhoOne wrote:

It could be really strange but is the reality . External modem work in window (seven) environment (in old IT infrastructure) performing properly calls and exchanging data flow and inside ods box through echo AT commands sent directly to the device.

Okay, what about other DOS terminal programs? The popular Terminate, for instance? Can you use those to dial out from DOSBox? Do they recognize the modem, specifically with the settings you mentioned before (Baud Rate=9600, Parity=None, Data Bits=8, Stop Bits=1, flow control= None) ?

It also might be useful to see if inserting the "rxdelay" parameter in DOSBox.conf helps at all.

JekhoOne wrote:

Mmm... i can't. It is needed to install on the other side (server one) another DosBox emulation with a ethernet GTW able to translate physical and logical protocol.

I'm not sure what you mean by "able to translate physical and logical protocol". Any Internet connection will do.

I will try Terminate and let you know.