rdj@ttrdf.UUCP (Robert D. Jackson) (03/02/88)
I have been "Test Driving" Procomm Plus, and have a problem. I use Crosstalk all the time set to 9600,N,8,1 and it works great on a direct connect to Unix. My terminal is also set to this with no probelm. I set Procomm Plus to the same thing and it gets brain damaged (i.e. prints characters that are not recognizably English). It seems to works better when I set it to 7 data bits. Don't you need 8 data bits to use XMODEM? I thought I read that somewhere. Is Crosstalk just a more robust package? Is Procomm right and just not very robust? What is the deal here? Thanks in advance, -- Bob Jackson (rdj@ttrdf) 312-982-3578 AT&T Data Systems Group 5555 Touhy Ave., Skokie, IL 60077 PATH: ...!ihnp4!ttrdf!rdj
wnp@dcs.UUCP (Wolf N. Paul) (03/04/88)
In article <335@ttrdf.UUCP> rdj@ttrdf.UUCP (Robert D. Jackson) writes: > >I have been "Test Driving" Procomm Plus, and have a problem. >I use Crosstalk all the time set to 9600,N,8,1 and it works >great on a direct connect to Unix. My terminal is also set >to this with no probelm. I set Procomm Plus to the same thing >and it gets brain damaged (i.e. prints characters that are not >recognizably English). It seems to works better when I set it >to 7 data bits. Don't you need 8 data bits to use XMODEM? I >thought I read that somewhere. Is Crosstalk just a more robust >package? Is Procomm right and just not very robust? What is >the deal here? I don't know Crosstalk so can't comment on it. However, if you use Procomm (either Plus or 2.4.2) in 7-bit mode, it will AUTOMATICALLY switch to 8 bits when you start transferring a file with XMODEM or one of the other 8-bit protocols. I suspect that Procomm and Crosstalk handle the UART configuration differently, but can't be sure. Most UNIX systems, unless you specifically tell them otherwise using stty or one of the system calls, run in 7bit, even parity mode, therefore Procomm is consistent in not working too well at 8N. UNIX Xmodem programs also will temporarily switch their tty to 8N during a transfer, and restore original conditions when they exit. -- Wolf N. Paul Phone: (214) 306-9101 (h) (214) 404-8077 (w) 3387 Sam Rayburn Run UUCP: ihnp4!killer!{dcs, doulos}!wnp Carrollton, TX 75007 INTERNET: wnp@dcs.UUCP ESL: 62832882 Pat Robertson does NOT speak for all evangelical Christians--not for me, anyway!
cc1@valhalla.cs.ucla.edu (Max Kislik) (05/18/89)
Does anyone know how to make Procomm Plus recongnize the busy signal of the phone line like procomm 2.4.2 used to be able to do? I am using PCplustd. max.
rra90329@uxa.cso.uiuc.edu (05/19/89)
If your setup is like mine, Procomm doesn't come with the right initalization string. You need to add something to the modem initalizetion string to tell the modem that it should respond to a busy signal. I forget what the string is for Hayes compatable, but I found it easily in my modem manual. Hope this helps. Randy
malloy@nprdc.arpa (Sean Malloy) (05/20/89)
In article <24032@shemp.CS.UCLA.EDU> cc1@cs.ucla.edu (Max Kislik) writes: >Does anyone know how to make Procomm Plus recongnize the busy signal >of the phone line like procomm 2.4.2 used to be able to do? Caveat: This advice is only good for Hayes-compatible modems. You should go into Setup, select Modem Setup, and check your modem init string (should be the top option on the screen). If your modem init string doesn't have the command 'X4' in it, or has 'X0' or 'X1', change it so it does (mine has it right before 'S11=55'). [useful tip: once you select the modem init string to change, you can use the cursor keys to slide the cursor over to where you want to change; characters typed overwrite the characters on the line, but you can press the <INS> key to make them insert instead] The 'X4' command tells the modem to return all of the text strings 'BUSY', 'NO DIAL TONE', 'VOICE', 'CONNECT', 'CONNECT 1200', and 'CONNECT 2400', which Procomm+ uses to recognize connections or failed connections. Sean Malloy | "The proton absorbs a photon Navy Personnel Research & Development Center | and emits two morons, a San Diego, CA 92152-6800 | lepton, a boson, and a malloy@nprdc.navy.mil | boson's mate. Why did I ever | take high-energy physics?"
bob@consult.UUCP (Bob Willey) (05/23/89)
In article <24032@shemp.CS.UCLA.EDU> cc1@cs.ucla.edu (Max Kislik) writes: >Does anyone know how to make Procomm Plus recongnize the busy signal >of the phone line like procomm 2.4.2 used to be able to do? > >I am using PCplustd. The easiest solution would be to upgrade to the commercial version of ProComm + which is now up to V1.1B and will recognize busy signal just fine. There is also a new version of the old procom (2.4.3) out. Hope this helps.
bvickers@ics.uci.edu (Brett J. Vickers) (05/24/89)
In article <20@consult.UUCP> uunet!consult!bob (Bob Willey) writes: >In article <24032@shemp.CS.UCLA.EDU> cc1@cs.ucla.edu (Max Kislik) writes: >>Does anyone know how to make Procomm Plus recongnize the busy signal >>of the phone line like procomm 2.4.2 used to be able to do? >> >>I am using PCplustd. > > >The easiest solution would be to upgrade to the commercial version >of ProComm + which is now up to V1.1B and will recognize busy signal >just fine. There is also a new version of the old procom (2.4.3) out. >Hope this helps. This isn't necessarily true. I think the problem is that Bob hasn't got a "v1" in his modem initialization string. Stick the V1 in and the modem will send the verbose Modem Strings which Procomm recognizes. -- Brett J. Vickers ---------------- "Eritis sicut Deus, scientes * bvickers@bonnie.ics.uci.edu bonum et malum" * ---------------------------
yon@apollo.COM (David Yon) (06/02/89)
Yet another Procomm question on the net... I'm currently using Procomm 2.4.2, and have gotten into some fairly sophisticated CMD file usage. I'm running into some serious limitations that I have some questions about. VARIABLES: The only way I know of to assign values to variables is to either get them from the user, set them in the script, or get them from the host. I would like to be able to also fetch them from a file or be able to put the return code from a DOS executable in them. ASCII UPLOADS: The ASCII upload is brain-damaged. The only way that an ASCII upload will stop is through the ESC key. I've tried several different things including an EOF mark in the file. No matter what I do, Procomm will send the entire file, then just sit there waiting for you to press ESC. You would think that Procomm would detect that it has no more data in the file to send, and just stop the upload there! Oh well... Are either of these problems fixed in Procomm Plus? I have heard that the command language has been extended, but I don't know exactly what has been upgraded. Can anyone out there with access to Procomm Plus answer this question?? Thanks in advance... David Yon
wek@point.UUCP (Bill Kuykendall) (06/06/89)
> The only way I know of to assign values to variables is >to either get them from the user, set them in the script, or >get them from the host. I would like to be able to also fetch >them from a file or be able to put the return code from a DOS >executable in them. Procomm Plus has file handling and integer math (wow, iterative loops at last) and addresses a number of other shortcomings in the Procomm 2.4x CMD language. It also has a few new bugs in it's terminal emulation and host mode operation. I can't speak to your question about ascii file transfers. I haven't used that feature much in either version.
mrcheezy@pnet51.cts.com (Steve Anderson) (06/09/89)
wek@point.UUCP (Bill Kuykendall) writes: >> The only way I know of to assign values to variables is >>to either get them from the user, set them in the script, or >>get them from the host. I would like to be able to also fetch >>them from a file or be able to put the return code from a DOS >>executable in them. > >Procomm Plus has file handling and integer math (wow, iterative loops at >last) and addresses a number of other shortcomings in the Procomm 2.4x CMD >language. It also has a few new bugs in it's terminal emulation and host >mode operation. > >I can't speak to your question about ascii file transfers. I haven't used >that feature much in either version. I have come across the very same question about variables in Procomm Plus. If anyone has the information, please do tell!! ======================= //\\ \\ // \\--------------------\\ // \\ Steven R. Anderson \\ // ___ \\--------------------\\ // /_|_\ \\ Minneapolis, MN \\ // \_|_/ \\--------------------\\ // \\ \\ //______________\\____________________\\ || || || || || || || || || *----------------------------------------------------------------------------* | UUCP: {amdahl!bungia, uunet!rosevax, chinet, killer}!orbit!pnet51!mrcheezy | | ARPA: crash!orbit!pnet51!mrcheezy@nosc.mil | | INET: mrcheezy@pnet51.cts.com | *----------------------------------------------------------------------------*