Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Problem invoking pcAnywhere (DOS)
Message
From
07/12/2002 02:06:14
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
 
 
To
06/12/2002 20:08:42
Henry Ravichander
RC Management Systems Inc.
Saskatchewan, Canada
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00730525
Message ID:
00730598
Views:
11
>I don't think we create the MCIBTele.bat file.

Yes you do. That's what "copy to &mawpath" line is doing. Just look at the mawpath variable, it contains the path to the .bat file.

>The macro &mAWPath will eventually execute the following:
>
>
@echo off
>cd\
>cd\AW
>AWRemote - M=D -N="MCIB" && Invokes an application called AWRemote 
>
>At this point, the DOS windows shows up and modem intialization takes place. If i reboot the computer, then the modeam appears to work, esle there does not seem to be a response from the modem when AWRemote runs.
>
>I'm really stuck here.

Haven't used PCAW for DOS for a number of years, and one of the major problems with it was that it could get stuck (well, the Windows version was not much better).

What the agency is supplying is probably a configuration file, with its phone numbers.

One way out of this would be to use an external modem, which can be reset independently from the machine itself. Another thing would be to add an "EXIT" after the last line of the batch file, so it would at least close the DOS window when done. Though, I don't know whether that would help.

The tricky part of the problem is the very use of PCAW DOS under Windows. Any of the DOS apps using modems needed individual settings - which IRQ/Com port/IO address to use, and had a very limited choice there. Specially when it comes to IRQs, you basically had IRQ3 and IRQ4, which often collided with the mouse (which was a serial device then).

Under Windows, a modem may use any port Windows gives it; while I was still using dialup, I saw IRQ 9, 11 or whichever. Furthermore, Windows supplied virtual COM ports far beyond the original two (or four, as some modems created fake ports, which was later adopted as practice on many motherboards, but they still used the same two IRQs), and the DOS communication software had very hard time getting configured.

One part of the problem may be an improper command to close the connection and reset the modem in the end of the session - which may explain why it works once. The modem may have hung up, but doesn't necessarily mean it detected the success of the hung up, or that it returned to its regular state. That's why I recommend external modem - nothing like the on/off switch to wake it up.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform