charlop@blake.acs.washington.edu (Aaron Charlop) (11/30/89)
I have just down loaded Uniterm 2.0e from Terminator. When I tried it from home last night, I ran into a problem. The dialing would get locked into dialing one number if there was anything wrong with the dialup. For example, if the number I was dialing was busy, then the modem would report it and any keypress in Uniterm would cause an automatic redial of the number. Also when the connection was made, all I got was garbage on the screen as if I was using the wrong baud rate. After hanging up and trying to dial another number, Uniterm would instead dial the previous number. The [control] C did not get me out of dialing mode. Nothing would work and I would have to reboot the computer. Can anyone tell me what I am doing wrong. The setup of the terminal is the same that works in my previous terminal program. My setup is a 1040ST, TOS 1.4, TurboST 1.6, Multidesk, Cache090, Maccel2, G+PLus, and Megadisk as a 1Meg RamDisk. Thanx in advance. -- Aaron the Alchemist Charlop@uwchem.chem.washington.edu
mark@rpp386.cactus.org (Mark Lehmann) (12/01/89)
Aaron, I have noticed problems with Uniterm 2.0e also. The only way to get unstuck from the dialer is to press and hold down Alternate-H until the program runs out of retries. The modem will freak out while this is happening, but it will accomplish the goal. The problem is so frustrating that I don't use automatic redial when using Uniterm. Mark Lehmann -- +------------------------------------+-----------------------------------+ | Mark Lehmann | | | mark@rpp386.cactus.org | | | {bigtex|texbell}!rpp386!mark | |
weber_w@apollo.HP.COM (Walt Weber) (12/03/89)
In article <4685@blake.acs.washington.edu> charlop@blake.acs.washington.edu (Aaron Charlop) writes: >I have just down loaded Uniterm 2.0e from Terminator. When I tried it >from home last night, I ran into a problem. The dialing would get locked >into dialing one number if there was anything wrong with the dialup. Aaron - There is a glitch with the 'redial' command in the dialer menu. It apparently decrements FIRST, and then checks for retries == zero; if you have retries set to equal 0, it is VERY persistent at that point (:-). Set retries to 1, and it will not attempt redials. >Aaron the Alchemist >Charlop@uwchem.chem.washington.edu ...walt... Walt Weber Hewlett Packard NARC @ Apollo Systems Division (508) 256-6600 x8315 People's Republic of Massachusetts -The views expressed herein are personal, and not binding on ANYONE-
wallace@oldtmr.dec.com (Ray Wallace) (12/05/89)
In article <473088e9.20b6d@apollo.HP.COM>, weber_w@apollo.HP.COM (Walt Weber) writes... >There is a glitch with the 'redial' command in the dialer menu. It apparently Simon did post a patch to fix this bug to the net quite some time ago. It was just a one or two byte patch. I have looked through all my uniterm files and have not been able to find the patch instructions. If I come across them I will post them. --- Ray Wallace (INTERNET,UUCP) wallace@oldtmr.enet.dec.com (UUCP) ...!decwrl!oldtmr.enet!wallace (INTERNET) wallace%oldtmr.enet@decwrl.dec.com ---
keithj@ux1.lbl.gov (Keith J Groves) (12/06/89)
I believe what you need to do is to get into the setup mode and go
into the telephone setup menu. Try changing the dial retry count
to 3 or more, (the count should be at least more than one).
Once you get back into the terminal screen and you encounter the
same problem with the phone line, just hit the undo key and instead
of quitting, which uniterm will ask of you, just type no. After
that, you should be back on line.
Keith Grovesesp_05@jhunix.HCF.JHU.EDU (Stdnt 05) (12/06/89)
When Uniterm 2.0e refuses to dial a second number after the first one does (or doesn't) work, I just use the reset function from the pop-up menu, and all becomes well. Eric