DOS support for Winmodems

  • Thread starter Thread starter Sgt Owens
  • Start date Start date
S

Sgt Owens

I have an irreplaceable DOS program that uses a modem but 5 years ago I had
to start using an external modem because the new "Winmodems" did not support
DOS. Anyone know of a program that will let DOS use an internal Winmodem?
Thanks, everyone.
 
I have an irreplaceable DOS program that uses a modem but 5 years ago I had
to start using an external modem because the new "Winmodems" did not support
DOS. Anyone know of a program that will let DOS use an internal Winmodem?
Thanks, everyone.

It isn't likely to happen.
 
I have an irreplaceable DOS program that uses a modem but 5 years ago
I had to start using an external modem because the new "Winmodems" did
not support DOS. Anyone know of a program that will let DOS use an
internal Winmodem? Thanks, everyone.

You are complicating the simple.
 
Sgt said:
I have an irreplaceable DOS program that uses a modem but 5 years ago I had
to start using an external modem because the new "Winmodems" did not support
DOS. Anyone know of a program that will let DOS use an internal Winmodem?
Thanks, everyone.
Nope. If its that irreplacable, go buy an external hardware non USB
modem.
 
I believe you could use Bochs in windows, and run DOS as the operating
system in it, and access the winmodem through that. But the big question
is, can your system run windows and Bochs.... Check out the system
requirements of Bochs and compare them with your system. I 'think' Bochs
allows modem access..... You'll have to check and see.
 
It isn't likely to happen.

It's happened at least once. There was, a few years ago, a program
"TurboComm ViP" by Pacific CommWare, that was advertised as enabling use
of Winmodems in DOS windows under Win95. It might work under later
Windows versions. It was not freeware (advertised for $40), and I don't
know if it's still available--a quick Google search didn't turn up any
link that worked.

But an external modem is not needed to get one that a DOS program
can use. Any internal so-called "hardware" (controller-based) modem can
work under both DOS and Windows, and would probably perform better than a
Winmodem of the same nominal speed using a Windows serial port emulation
driver like TurboComm ViP. Sources of used computer accessories should
have plenty of cheap ISA hardware modems up to 56K available. If you have
no ISA slots, there are also a handful of PCI hardware modems, though they
are much harder to find. Since Linux users also have problems using
Winmodems, a Google search for something like "linux-compatible pci modem"
should yield information on models that would work for you.
 
Donald said:
It's happened at least once. There was, a few years ago, a program
"TurboComm ViP" by Pacific CommWare, that was advertised as enabling use
of Winmodems in DOS windows under Win95. It might work under later
Windows versions. It was not freeware (advertised for $40), and I don't
know if it's still available--a quick Google search didn't turn up any
link that worked.
"TurboComm ViP" was _not_ a DOS program. It was a Windows _Console_
_Mode_ program, which means it ran is a DOS box but was a real 32-bit
windows program, just without the (frequently crappy) windowed interface.

Cheers,
Gary B-)
 
Gary R. Schmidt said:
Donald G. Davis wrote:
derek / nul said:
"TurboComm ViP" was _not_ a DOS program. It was a Windows _Console_
_Mode_ program, which means it ran is a DOS box but was a real 32-bit
windows program, just without the (frequently crappy) windowed interface.

Yes, I realize that TurboComm ViP was a Windows program.
However, it might enable the OP's DOS program to use a Winmodem, provided
that the OP is able to run that program in a Windows DOS session. He
didn't specify whether he has a Windows version within which he can run
DOS, but that seems likely, so I replied with the TurboComm ViP idea. If
he has DOS alone, I am not aware of any DOS drivers for Winmodems.
 
Donald G. Davis wrote:
[SNIP]
Yes, I realize that TurboComm ViP was a Windows program.
However, it might enable the OP's DOS program to use a Winmodem, provided
that the OP is able to run that program in a Windows DOS session. He
didn't specify whether he has a Windows version within which he can run
DOS, but that seems likely, so I replied with the TurboComm ViP idea. If
he has DOS alone, I am not aware of any DOS drivers for Winmodems.
But TurboComm ViP didn't do open("COM1:", ...) [which is what DOS
programs do], it did RASDial("connection name", ...) [or something tat
starts with RAS...]. They are very, _very_ different things.

The bottom line is that a "pure" DOS program can't drive a WinModem,
unless, of course, it has been (re)written to do so.

Cheers,
Gary B-)
 
Yes, I realize that TurboComm ViP was a Windows program.
However, it might enable the OP's DOS program to use a Winmodem, provided
that the OP is able to run that program in a Windows DOS session.

But if he can run the program withint a Windows DOS session he can just
use the virtual COM port the winmodem driver set up anyway.
 
Back
Top