Bernie wrote:
>
> Sam wrote:
> >If I have a properly configured working modem installed, the first thing I
> >would do is to enter the following series of commands at the command line
> >while running in real DOS mode, (Not a Windows DOS-box):
> (snip)
> >If
> >nothing happens, then you have a winmodem. Winmodems are easily identified
> >by their unresponsiveness to DOS commands.
>
> Nope, the above test only works if the com-port is configured already -
> otherwise it will not work. I have a USRobotics 33.6 modem and it sure
> isn't a Win-Modem but the above test will not work (I know since this is
> excatly what Linux tried to do when I asked it to connect to the ISP).
>
> Something like:
> mode com1 baud=19 parity=n data=8
I have attached a zip containing comtool and a batch file you can use to
test (and identify) your modem.
Type modemtst for instruction. Operation is obvious I think.
It may not like DOSKEY. I use PCED and I must turn it off for the test.
- Clarence Verge
--
- Help stamp out FATWARE. As a start visit: http://home.arachne.cz/
--
MODEMTST.ZIP
