Path: utzoo!attcan!uunet!maverick.ksu.ksu.edu!uafhp!engr!cab3 From: cab3@engr.uark.edu (Chad A. Bersche) Newsgroups: comp.windows.ms Subject: Re: Attention! Wincomm demo available Message-ID: Date: 16 Oct 90 16:04:47 GMT References: <1990Oct11.171629.10981@sj.ate.slb.com> Sender: netnews@uafhp.uark.edu Lines: 55 poffen@sj.ate.slb.com (Russell Poffenberger) writes: >Has anyone gotten wincomm to work right? I am having problems using it with a >Telebit T1000. The problems I am having are described below. >1.) There is no modem configuration for Telebits. I try to make my own "custom" >configuration, but the 2400 and higher speeds use two digit result codes, and >the "edit session" mode does not seem to allow entering two digit result codes, >even though some of the other modem configurstions (Hayes 9600) have two digit >codes in them. I had trouble with mine at first when I tried to use the Hayes compatible modem. It seems that the defaults for dialing ATDT was set to ATTD. It didn't look right, so I changed it without even trying it the other way. >2.) I cannot get a modem connection going. I make a session file, open it, then >"start" it. It initializes the modem fine, dials the number, but immediately >upon finishing dialing, wincomm come back saying "no carrier", even though the >modem itself is still making the connection. I have to shut off the modem to >disconnect since wincomm and the modem are out of sync now. A friend of mine has also had this identical problem. I set it up successfully on my 386/20 (he has a 386/25) on an Avatex 2400 baud modem and have experienced relatively few problems. He, owever, has had the exact problem. It seems that the modem will go ahead and connect fine, but since WinComm thinks that there was no carrier, he can't establish his session even though the modem is connected. >3.) This is minor, but when I say "start" for a session, it always printd >"connected to modem@300" even though I am using 9600 baud. I noticed this problem as well on my friends PC, where I have not had the reported problem. I personally tried to set up the copy of WinComm that my friend is using, and due to the very close similarities in our system configurations, I figured that the same settings I used would work fine on his. No luck. >Wincomm sounds like a good product (idea wise anyway), but it is useless to >me now because I cannot get it to work. Documentation on solving problems is >non-existent, and help is certain areas is very sparse. >I certainly wouldn't pay money for it in its present condition. I'm with you on this one. I had given it significant consideration for my Windows communications package, but as the bugs began showing up when I tried to really USE it hard, I've been discouraged. Now if the bugs were fixed and it was an easy setup, I'd consider it again. -- ----------------------------------------------------------------------------- cab3@engr.uark.edu - Chad A. Bersche University of Arkansas Fayetteville Computer Science Engineering Look, would it save you a lot of time if I just gave up and went mad now?