From: STeve Andre' (andres_at_msu.edu)
Date: Sat Nov 06 1999 - 13:25:56 EST
Without having seen the code, but remembering how the old DOS programs
used to grab things like hardware by the throat, I'll bet that your
program talks directly to the hardware, bypassing the "proper" interrupt
code. In the case of the modem, the fastest way to move data was to talk
with the hardware at 0x3f8 and 0x2f8, manipulating the status registers
directly. By manipulating the modem hardware in the "right" way I'll bet
that you could confuse the MWwave modem--put it in a strange state that
it can't deal with, and gets stuck 'till the next reboot.
If you studied something like the old IBM AT Technical Reference manual,
I'll bet you could write a little 10 line assembley language program that
would reset the modem. That is, *if* it really looks like a COM1 or COMx
device. I wrote such a program back in 1985. A cursory glance at my code
archives shows nothing, so perhaps I did it on a contract basis. Sigh.
Ah, the days of DOS when people had such intimacy with their hardware...
--STeve Andre'
andres_at_msu.edu
At 07:30 AM 11/6/1999 PST, Rat Boy wrote:
>Hi Everyone,
>
>I sometimes run a very simple old DOS program on my 600E. The DOS program
>is a database of associates and their telephone numbers. The DOS program
>can dial the phone number and put me in touch with people. The problem I am
>having is the MWave modem in my 600E seems to lock up and stop responding
>if, for example, nobody answers and I disconnect the call. The only way to
>get the modem to work again, in this application, is to power off the
>computer and power on again.
>
>The MWave modem works fine with all Windows programs. Any ideas on why it
>may be locking up with this DOS program? Is there some string I could
>somehow put in there to make it work? I ask because the DOS program is old,
>but so elegant, nothing surpasses it in it's niche.
>
>Jimmy
This archive was generated by hypermail 2.1.3 : Thu Jan 23 2003 - 09:55:33 EST