There are some reports about modem not working in 0.62, 0.63. The recent one was on IRC from 20. November 2004:
[21:30] <Jammet> Hiya ...
[21:31] <Jammet> The modem emulation (telnet) does not work anymore. Since DosBox version 0.61 actually. Did nobody notice that?
[21:31] <Jammet> I'd love it if this could be repaired, because I really enjoy using telnet BBS's... and I'd prefer using my old DOS terminal.
I reported previous complaints in Modem support is broken in 0.62 to CANADACOW (on betaboard), he said that modem works ok (I do not use it myself, so I did not test it).
Could anybody else confirm/disprove that there is some broken functionality connected with modem? I mean something which worked in older version, e.g. in 0.61 but does not work in 0.63.
In this thread I am not interested in hearing what never worked. I want to find out whether there is really something broken ...
BTW: I hope that all people here know that modem must be allowed in DOSBOX.CONF (it is switched off by default in 0.62, 0.63).
I confirm that modem is not working in 0.62 and 0.63.
I have modem enabled in dosbox.conf
I run BananaCom to test modem. The program can not detect modem. There are following lines in DOSBox debug window:
Stockholm, Sweden, Europe, Earth Interests: Old games & young women
mirekluza wrote:
Could anybody else confirm/disprove that there is some broken functionality connected with modem? I mean something which worked in older version, e.g. in 0.61 but does not work in 0.63.
In this thread I am not interested in hearing what never worked. I want to find out whether there is really something broken ...
As a followup to this bug report for 0.63, I re-ran the same program+dialer entry with DOSBox 0.61.
With 0.61 it worked much better 😀 The main program running in the DOSBox window, simply said:
In the DOSBox console, I saw some expected(?) debug messages, e.g.
1MIDI:Opened device:win32 2Read from B 0 3Read from B 0 4Read from E 0 5Read from E 0 6Read from E 0 7Read from E 0 8Read from E 0 9TX add 10Modem Sent Command: 11 12TX add A 13RX add A 14TX add T 15RX add T 16TX add D 17RX add D 18TX add T 19RX add T 20TX add 1 21TX add 9 22TX add 2 23TX add . 24RX add 1 25RX add 9 26RX add 2 27RX add . 28TX add 1 29TX add 6 30TX add 8 31TX add . 32TX add 1 33TX add . 34TX add 1 35TX add 0 36TX add 2 37TX add . 38TX add 8 39TX add 0 40RX add 1 41RX add 6 42RX add 8 43RX add . 44RX add 1 45RX add . 46RX add 1 47RX add 0 48RX add 2 49RX add . 50RX add 8 51RX add 0 52TX add 53Modem Sent Command: ATDT192.168.1.102.80 54 55host 192.168.1.102.80 port 17 56Failed to resolve host 192.168.1.102.80:accept() failed 57RX add 58RX add 59 60RX add N
…Show last 12 lines
61RX add O 62RX add 63RX add C 64RX add A 65RX add R 66RX add R 67RX add I 68RX add E 69RX add R 70RX add 71RX add
With 0.63, BananaCom initially reports: "Wiring problem! Modem cable? Power?" upon startup. At that point the console window only show the usual "CONFIG:Loading settings from config file modem.conf" and "MIDI:Opened device:win32".
Dialing the new entry with 0.63 gives me a "Dialing NewEntry" in the DOSBox window, and a single "Modem Sent Command:" in the console window. Then there is the long wait, and any minute now I should get the failed assertions..... Waits..... waits....Its a long wait 4 min. 20 secs so far.. Ah - there!!! some 6-7 minutes later
