NetNews Usenet Archive 1992 #18/NN_1992_18.iso/spool/comp/os/msdos/programm/8504

Internet Message Format | 1992-08-12 | 1.7 KB

Xref: sparky comp.os.msdos.programmer:8504 comp.lang.pascal:4828
Path: sparky!uunet!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!ohstpy!miavx1!sjmadsen
Newsgroups: comp.os.msdos.programmer,comp.lang.pascal
Subject: Re: Problems using exec to run a program that accesses modem
Message-ID: <[e-mail]>
From: [e-mail] (Steve Madsen)
Date: 12 Aug 92 17:29:24 -0500
References: <[e-mail]>
Organization: Miami of Ohio
Lines: 23

> My program is a front end that calls up another specialized program that
> accesses the modem, dials a system (via script file) and collects/sends
> data, and hangs up.  It accesses the modem fine, and even connects mostly,
> but sometimes it won't connect, and when it does connect the data coming oer
> the modem is garbage.  It appears that my program, running the other
> program, causes problems with the communications...

        Stab in the dark: your modem and the serial port aren't agreeing on the
right bps rate as the remote system.

        Your program that you exec should operate no differently when you exec
it or when you run it from the command line.  The only difference it would even
see would be that there is less memory when it's exec'ed.  So, the problem
probably doesn't lie in your program but in your comm setup.  It's my
experience that getting modems and serial ports to operate flawlessly when
there is no one there to fix things is a tough thing to do.  My first
suggestion would be to make sure the bps rates are set correctly, because that
would more than account for garbage over the line.

--
Steve Madsen
Miami University  Oxford, OH
Internet: [e-mail]