tamara@ecsvax.UUCP (08/10/89)
(latest version). It takes me about 7 times before the modem connects properly with a local Vax running Unix. Sometimes it takes more than 7 times. I've tried several different things, like hanging up first, quitting, etc. and nothing seems to consistently make a difference. I don't understand why quitting the software and starting over sometimes works. I don't understand how I can have everything running okay, logoff, hang-up and come back later and I get the same symptoms. Here they are . . . (I'm not a techy so please forgive the lack of technical terms) 1) The high pitched sound after dialing is extremely high. 2) The connect prompt is always missing a baud rate. (If the baud rate is there it always works; e.g., CONNECT 1200.) 3) The last sound (after the CONNECT) is much shorter than usual. When it connects properly it makes a nice slow even sound that lasts longer. My modem is in slot 2. In the control panel I have slot 2 set for my card. I've also tried setting it as a modem slot. Am I supposed to have something special set up in my Modem assignment in the control panel? What are some of the control panel options which might make a difference? This has been a scream raising frustrating experience so any help on curing this problem will be more than appreciated. Thanks T. --------------------------------------- Tamara@ecsvax WYS is not always what you get.
krb20699@UXA.CSO.UIUC.EDU ("I can't remember...") (08/11/89)
I've had the same problem with my Datalink. When the modem puts out the 'CONNECT' without a baud rate, this means its connecting at 300 baud. The second tone is shortened to a beep when you connect at 300 baud. It's an intermittent problem with me, always correctable by redialing. I never had any problem with local BBSs, so I assumed it was the network dialin. The reason it doesn't let you type anything at 300 ud is ause your comm package is set for a higher baud, and isn't prepared to speak 300bpsish. Redialing immediately always works for me, but if your problem is more severe, I'd either talk to whoever runs your VAX dialin, or if this doesn't help, call AE. Otherwise, I'm stupmd I hate this editor! That should read "Otherwise, I'm stumped." Ken. krb20699@uxa.cso.uiuc.edu {Internet}
emerrill@pro-carolina.cts.com (Eric Merrill) (08/13/89)
Network Comment: to #4633 by obsolete!ecsvax!tamara%mcnc.org I've also experienced these same problems, but relatively infrequently. So far, I've only had this problem (connecting at 300 instead of 1200, using the DataLink 2400) with two local, private boards. My DataLink also does not recognize busy signals, of which AE is aware. I pointed out this problem to them almost six months ago, and have not heard any positive responses from them. But other than these two (quite mild) problems, I've had absolutely no problems with my DataLink and am quite satisfied with AE. Eric ___________________________________________________________________________ | | | Eric Merrill INET: emerrill@pro-carolina.cts.com SPACE FOR RENT!! | | Alink PE: Doc Neuro GEnie: e.merrill CHEAP!! | | ARPA: crash!pro-carolina!emerrill@nosc.mil $49.95/MO | | UUCP: [ sdcsvax nosc ] !crash!pro-carolina!emerrill or best offer | |___________________________________________________________________________|